Recent content by ghostwolf59

Will look into it. Just a bit worried going back to a release *forked out before my current firmware* - Last I want it so find myself with a bricked router - Dont have anything decent to fall back on - and other that this port forwarding issue, I dont have any issues with it - serves me well...

Dont know where to look for that, but transmission is a well proven and possible the most commonly used torrent tool that dont require a client. I dont need to worry about anything - FreeNAS installation of transmission sort it for me. Im way passed using a client to download stuff. ... and with...

Isnt 374.43 and old fork? My version is 380.70 The "feature" of 374.43 does not seem to introduce anything of value what I can see ?

Outdated firmware - true, but little I can do since they ceased further development on my ASUS router - using the latest released. Other option is to buy another router such as RT-AC68U, but even this being a better router its still getting old now. Seem to be limited support on latest routers...

Its not as it dont work with Double NAT, but the speed of up/download changes. I have decent NBN network and I noticed a significant difference in speed since ports are closed - still work, but slow *much slower* Hence me today finally wanted to resolve the issue - but so far all I achieved is...

It bogs down to speed, trackers and peers you connect to *I think* - To effectively use torrents you should be able to use port forwarding and the port should be open. PIA made some changes a few years back as I understand it - never used to be a problem, where they now only offer a few selected...

No way around this or...? Dont seem to have achieved anything other than loosing my VoIP by putting my router in Bridge mode! Seem to have the same issues and nothing improved doing so when looking at transmission using openvpn :( A creeping frustration @ my end atm ;)

Ok, so lets assume the router dont know - If so, then shouldn't a port forwarding on the router to the destination ip resolve the issue then? Not practical, but at least a way to check if this is the problem. Yea, heaps of post about transmission and closed ports, but also many posts stating...

If you use this script with transmission and set up a cron task, then the port returned in between vpn tunnels *assuming you use one of the vpn servers PIA support port forwarding for*, your transmission interface would be updated automatically - works!

PIA that I am connected to, indeed support port forwarding *but only via a few selected servers* I have the script that picks up the port offered whenever a new tunnel is created. That is automatically fed to transmission that start using this port. Works perfectly. But transmission still report...

The 192.168.... is local lan ip. the 10.63.10.1 seen on second hop is also a local ip *but nothing known to me* - hence creating a double NAT! The traceout should give me my local ip followed by the external one immediately - if not, its a double nat state *that creates issues with close ports...

Hi, I am having issues with double NAT when connected to PIA where I configured my ASUS RT-AC66U router with a few openvpn clients (Merlin DDWRT firmware 380.70 (last release for this router *no more support offered on it :( ) My main issue that bugged me for some time is that transmission on...