Jump to content

unwanted connections in 2.х


help10

Recommended Posts

===

[2009-11-21 18:55:55] 172.19.9.212:42288(Margosha-2): Connecting: source: TI

[2009-11-21 18:55:55] 172.19.9.212:42288(Margosha-2): [µTorrent/1.8.4.0 (0.0)]: Handshake completed

[2009-11-21 18:55:56] 91.204.37.182:38820(Bolt.2008.DVDRip.Ukr.avi): Connecting: source: IX

[2009-11-21 18:55:56] 91.204.37.182:38820(Bolt.2008.DVDRip.Ukr.avi): [µTorrent/1.8.4.0 (0.0)]: Handshake completed

[2009-11-21 18:55:57] 172.19.4.51:34352(Margosha-2): Connecting: source: TI

[2009-11-21 18:55:57] 172.19.4.51:34352(Margosha-2): [µTorrent/1.8.4.0 (0.0)]: Handshake completed

[2009-11-21 18:55:58] 172.20.2.13:12142(FAQ.About.Time.Travel.2009.DVDRip.avi): Connecting: source: TI

[2009-11-21 18:55:58] 172.20.2.13:12142(FAQ.About.Time.Travel.2009.DVDRip.avi): [µTorrent/2.0.0.11 (0.0)]: Handshake completed

[2009-11-21 18:55:59] 91.204.38.0:19843(FAQ.About.Time.Travel.2009.DVDRip.avi): Connecting: source: X

[2009-11-21 18:55:59] 172.19.9.160:12696(Margosha-2): Connecting: source: TI

[2009-11-21 18:55:59] 172.18.1.33:31063(MediaInfo-0.7.14.zip): Connecting: source: TI

[2009-11-21 18:55:59] 172.19.9.160:12696(Margosha-2): [µTorrent/1.8.4.0 (0.0)]: Handshake completed

[2009-11-21 18:55:59] 172.18.1.33:31063(MediaInfo-0.7.14.zip): [µTorrent/2.0.0.11 (0.0)]: Handshake completed

[2009-11-21 18:56:00] 91.204.38.157:15729(MediaInfo-0.7.14.zip): Connecting: source: IX

[2009-11-21 18:56:00] 172.17.5.39:10811(Margosha-2): Connecting: source: TI

[2009-11-21 18:56:00] 91.204.38.157:15729(MediaInfo-0.7.14.zip): [µTorrent/2.0.0.11 (0.0)]: Handshake completed

===

here is the log of outgoing connections with client 2.0 (17341).

172.x.x.x - my local area network, traffic in it is free of charge.

91.204.x.x - IPs assigned by my ISP on vpn connections, so they are another people on my LAN, but for some reason i'm talking to them through WAN, and have to pay for this traffic.

torrent tracker resides in LAN itself, and gives only 172.x.x.x IPs in announces.

all local connections always have letter "T" in type, and all that strange connections to LAN through WAN - always have "X". i guess, "T" stands for "tracker" (peer given by tracker), "X" - for "exchange" (peer was obtained during some direct talking with another clients).

the problem is that despite any options regarding DHT and peer exchange are switched OFF, i still have this unwanted traffic (awesome and expensive enough - about 15-20 Mb per hour). due to this, i can't now be connected to the internet and seed local torrents simultaneously, because uTorrent in that case just eats my money for nothing :(

is there any way to get rid of these X-connections completely, and so stop any talking to another ppl in my free LAN through expensive WAN?

Link to comment
Share on other sites

X is peer exchange.

T is tracker

I is INCOMING.

glad i'm right with my assumptions, thanks.

but as i mentioned before, "Peer exchange" option is disabled (as like as DHT and local peer discovery) - why he still doing that exchange, and moreover - doing it with the WAN, which is completely irrelevant to the local torrents?

If you want to block the public side of your VPN range just ipfilter the entire block.

as i understand, it will prohibit any talking to my coWANers, but it sounds bad when we are working on the same torrent from internet tracker (not local one) - in that case talking to each other is not unwanted, and contrary - will speed up things. so, it's not the good solution.

UPD:

the latest 1.8.5 has the same effect :(

is there any option to completely disable these X sources? if not - it's definitely a time for feature request.

Link to comment
Share on other sites

  • 3 months later...

I have a similar problem, I have a netscreen firewall with 2 different zones of local internet traffic. my computer is on a 10. network, and my other local network is a 192.168 network. I have Peer Exchange and Local Peer Discovery turned off, but I am still getting traffic trying to access the 192.168 network from my 10. network. I just noticed this after upgrading to 2.0

This is almost definitely utorrent as I only see this traffic when it is running and connected to a torrent.

Is there a way to stop this traffic? It's not really a big deal because I am blocking it, but its filling up my firewall logs :(

Also, most of this traffic is to non existent hosts on the 192.168 network

See below:

Time Source Destination xSource xDestination Service Duration Bytes Sent Bytes Received Close Reason

2010-02-25 07:03:15 10.0.0.10:57938 192.168.1.100:53698 0.0.0.0:0 0.0.0.0:0 UDP PORT 53698 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:13 10.0.0.10:57938 192.168.1.2:65443 0.0.0.0:0 0.0.0.0:0 UDP PORT 65443 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:13 10.0.0.10:57938 192.168.1.100:53698 0.0.0.0:0 0.0.0.0:0 UDP PORT 53698 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:12 10.0.0.10:57938 192.168.1.103:61832 0.0.0.0:0 0.0.0.0:0 UDP PORT 61832 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:12 10.0.0.10:57938 192.168.1.104:56677 0.0.0.0:0 0.0.0.0:0 UDP PORT 56677 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:10 10.0.0.10:57938 192.168.1.103:61832 0.0.0.0:0 0.0.0.0:0 UDP PORT 61832 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:10 10.0.0.10:57938 192.168.1.104:56677 0.0.0.0:0 0.0.0.0:0 UDP PORT 56677 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:08 10.0.0.10:57938 192.168.1.103:61832 0.0.0.0:0 0.0.0.0:0 UDP PORT 61832 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:07 10.0.0.10:57938 192.168.1.104:56677 0.0.0.0:0 0.0.0.0:0 UDP PORT 56677 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:05 10.0.0.10:57938 192.168.1.100:53698 0.0.0.0:0 0.0.0.0:0 UDP PORT 53698 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:04 10.0.0.10:57938 192.168.1.2:65443 0.0.0.0:0 0.0.0.0:0 UDP PORT 65443 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:03 10.0.0.10:57938 192.168.1.100:53698 0.0.0.0:0 0.0.0.0:0 UDP PORT 53698 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:02 10.0.0.10:57938 192.168.1.2:65443 0.0.0.0:0 0.0.0.0:0 UDP PORT 65443 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:01 10.0.0.10:57938 192.168.1.100:53698 0.0.0.0:0 0.0.0.0:0 UDP PORT 53698 0 sec. 0 0 Traffic Denied

2010-02-25 07:03:00 10.0.0.10:57938 192.168.1.2:65443 0.0.0.0:0 0.0.0.0:0 UDP PORT 65443 0 sec. 0 0 Traffic Denied

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...