Utorrent issues with 2.0-RC1 (i386)
bab5470 last edited by
Ever since upgrading to PFsense 2.0 beta and RC's (I run regularly update to the latest nightly build - presently running build Thu May 5 06:05:22 EDT 2011) I've been having problems using utorrent. Most of the times torrents won't download even where there are lots of seeds and peers. I've enabled both UPnP port mapping and NAT-PMP port mapping in both utorrent and also pfsense. I've also specified a port for incoming connections in utorrent and I've configured NAT and firewall rules in PFsense to forward that traffic. Still I'm having problems.
I see entries like this in the firewall log:
May 8 17:29:13 LAN 18.104.22.168:64396 192.168.0.3:6000 TCP:RA
May 8 17:29:20 LAN 22.214.171.124:56893 192.168.0.3:6000 TCP:A
May 8 17:29:24 LAN 126.96.36.199:56893 192.168.0.3:6000 TCP:RA
May 8 17:29:27 LAN 188.8.131.52:1453 192.168.0.3:6000 TCP:FPA
Why is traffic to port 6000 being blocked if I've specifically opened it in NAT/Firewall rules? As mentioned above this issue has been ongoing for some time despite upgrading to new builds. The problem seems to go away for a short period of time if I reset pfsense or directly connect my system to the cable modem (bypassing pfsense). Anyone have any ideas for anything else I can try?
Why would you be seeing blocks on your LAN interface for IPs that are clearly public?
Also if your going to manual create the forwards - then you have no need of UPnP port mapping or NAT-PMP to be set on the utorrent client. I would suggest you turn those off, and make sure your client is not set to randomize port on restart, etc.
Then post up your firewall rules and nat rules
All that is required is to create a nat, and it will create the firewall rules.
So either you have rules that are blocking it, or dont' have the rules setup correctly. Or your pfsense is behind some other device blocking - ie maybe your "modem" you say you connect to and is working is really a gateway doing nat along with modem? Post up model number of your modem. Your pfsense is getting a public IP on its wan interface?
This is a simple forward and works just fine with 2.0 RC1 I have too also update quite often and currently on build
built on Tue May 3 10:16:12 EDT 2011
And even running development code for IPv6 support - and torrents were even working with ipv6 before I turned it off, ipv6 through my tunnel gives away more info then I wanted with torrents ;)
Post up your firewall rules and happy to help you with your issues.