Problems with utorrent, source IP…



  • OK, tried reading and seraching the forums but couldn't really find anything that helped me….

    I'm running utorrent on a computer behind a pfsense installation, have created a NAT-rule to forward port 2330 to the internal ip 192.168.8.100 (the computer running utorrent).
    But I'm still not really connectable, when doing the built-in-test in utorrent it says my port is not open.

    But if I try it myself with http://www.yougetsignal.com/tools/open-ports/ everything looks fine.

    So I did a little more digging and it seems that utorrent is reporting that I'm on IP 192.168.8.100 to the tracker (I'm thinking it just sees source IP), wich is my internal IP-adress.
    I'm thinking this has something to do with pfsense not changeing source-IP on outgoing traffic.

    So what to look for to fix this?


  • LAYER 8 Global Moderator

    Tell utorrent to use your public IP.. Do you have your private IP in this box?




  • @johnpoz:

    Tell utorrent to use your public IP.. Do you have your private IP in this box?

    Actually it doesn't matter what I put in that box, my external IP 37.123….... or any of my domain names (resolves to that IP)

    It still reports my local IP to the tracker, wich leads me to believe it is something pfsense is doing or not doing.
    Seeing from the log from one of the trackers i use, it started using my local adress 2013-08-31 14:48:11 and since then it has only used that adress.
    I think it is around the time I upgraded to 2.1 and installed squid.

    EDIT: I noticed that the build date for my 2.1 install is september 11th, so that kind of rules that out. leaving something with squid, or some other setting I made around that time...

    EDIT 2: first entries in my proxyreport is from august 31st, I'm seeing a pattern here, now I just need to figure out why squid makes utorrent behave like this....

    Maybe this thread should be moved to packages then.


  • LAYER 8 Global Moderator

    Where exactly are you seeing that its sending your private IP in the tracker in the setup guide test?  I sniffed the traffic and it doesn't even send an IP.. It does a get with your PORT..

    Are you using a proxy..  The tester should try and come back to the IP you hit him from.. I don't see how pfsense could do anything with the traffic that is being sent that changes what IP you hit their server from.

    Where are you seeing that it sent your local private IP - or is that just a guess on your part for why its showing that your port is closed?




  • @johnpoz:

    Where exactly are you seeing that its sending your private IP in the tracker in the setup guide test?  I sniffed the traffic and it doesn't even send an IP.. It does a get with your PORT..

    Are you using a proxy..  The tester should try and come back to the IP you hit him from.. I don't see how pfsense could do anything with the traffic that is being sent that changes what IP you hit their server from.

    Where are you seeing that it sent your local private IP - or is that just a guess on your part for why its showing that your port is closed?

    @tracker:

    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:55:58
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:55:57
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:55:56
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:55:55
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:55:54
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:44
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:39
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:38
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:37
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:35
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:53:34
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:52:24
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:52:14
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:51:54
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:51:18
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:51:17
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:51:16
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:51:14
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:48:59
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:48:58
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:48:57
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:48:56
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:48:55
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:40
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:39
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:38
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:37
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:36
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:35
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:46:34
    192.168.8.100 192.168.8.100 uTorrent/2210(25302) 2013-12-18 17:40:20

    That is from from the log of the tracker, the IP that is reported by utorrent to send out to the other peers.

    I'm thinking it is pfsense that doesn't change "sourceIP" or something…..

    EDIT: Could it be something with NAT reflection, since the port utorrent is sending also should resolve to 192.168.8.100 on incoming traffic.

    EDIT2: Found this thread and thought it could be something similar: http://forum.pfsense.org/index.php/topic,68115.0.html
    unfortunately there is no solution in that thread.


  • LAYER 8 Global Moderator

    "I'm thinking it is pfsense that doesn't change "sourceIP" or something….."

    No -- do you think there is some torrent helper like there is with ftp to change your private IP.. pfsense has NOTHING to do with some tracker your running in utorrent sends out..

    So it seems that setup guide test is BROKEN!!!  Says you have to have UPnP or NAT-PMP enabled..  Which No that is not enalbed in pfsense by default.. But could be.. Be if you can see your port open from say canyouseeme.org your port is open.  Where are seeing this tracker log.. I do not see that anywhere.



  • @johnpoz:

    "I'm thinking it is pfsense that doesn't change "sourceIP" or something….."

    No -- do you think there is some torrent helper like there is with ftp to change your private IP.. pfsense has NOTHING to do with some tracker your running in utorrent sends out..

    No absolutely not.
    Of course pfsense has nothing to do with random tracker, but it affects all traffic passing through the firewall does it not?

    But when the traffic leaves the LAN-computer the package should say sourceIP=192.168…. When leaving the router the package should say sourceIP=37.123.... or I'm wrong in this?


  • LAYER 8 Global Moderator

    Pfsense is not going to change the IP some your torrent software sends out.. If your torrent software does not figure out the public IP, then pfsense is not going to change it for it.. This is not a ftp helper.. There is not torrent helper in pfsense.

    Again where are you seeing this - you sure that is not some private tracker your running looking for local peers or something.

    ARe you torrent not working, are you not getting any peers?  There is NO way for pfsense to change the IP address that some client sends out in data.

    The only "helper" of that sort is the ftp helper.

    I show peers connecting to me.  Now I put my public IP in the box I showed you before.. If I was sending my 192.168.1.100 IP that would be impossible.

    But when the traffic leaves the LAN-computer the package should say sourceIP=192.168…. When leaving the router the package should say sourceIP=37.123.... or I'm wrong in this?

    Yeah completely and utterly wrong - pfsense is not going to manipulate data inside packets.. Other than the ftp helper, and for that to work you have to use 21 for the control channel so pfsense knows to look there and modify..  Your running on some random port..  Your thinking that pfsense would do layer7 inspection on every single packet leaving and say - OH that is torrent traffic better change that private IP to the wanIP..  No that does not happen ;)




  • Did some wiresharking and it seems like squid is adding my LAN-IP at the end of the package in a field called "X-Forwarded-For"
    Turned that function off in squid solved my problem, now the right IP is reported by utorrent.


  • LAYER 8 Global Moderator

    Yup proxies do that ;)  Like post 2 when I asked you "Are you using a proxy..  "  You might of mentioned that you were using squid ;)



  • @johnpoz:

    Yup proxies do that ;)  Like post 2 when I asked you "Are you using a proxy..  "  You might of mentioned that you were using squid ;)

    I missed that, my bad, sorry man!
    (although if you read my second post you would already know that I am using squid, and had made a connection between that and my problem….)

    Where are seeing this tracker log.. I do not see that anywhere

    The tracker log is from the actual tracker, not anywhere in my system.

    Where exactly are you seeing that its sending your private IP in the tracker in the setup guide test?  I sniffed the traffic and it doesn't even send an IP.. It does a get with your PORT..

    That get actually contains the IP aswell: ….peer_id=-UT2210-....&port=2330&uploaded=0&downloaded=0&left=0&corrupt=0&key=....&numwant=200&compact=1&no_peer_id=1&ip=37.123….


  • LAYER 8 Global Moderator

    My bad - those were edits and must of missed them ;) about using squid – well its sorted so all water under the bridge now ;)


Log in to reply