Connecting to self

[Guest]

When I look at the peers that I am connected to I see my own ip address. This should not happen, I shouldn't connect to myself, so I think uTorrent should filter out own ip address when it is passed by the tracker. This happens in version 1.1.3

[NiteShdw]

Some peers report their local IP to the tracker (192.168.xxx.xxx). That IP will get sent to the other peers, who will try to connect. I've seen the address 192.168.1.1 in the list, and of course, that is my router which will forward the traffic to the torrent computer.

Perhaps uTorrent could filter out LAN ips, but this might be included in the IP blocking feature the devs plan on including later.

[Guest]

same here i see my internet ip show up on and off

[Guest]

I've seen both my LAN and WAN IP show up on the list of peers.

Only reason I noticed it was me because I thought I saw someone else using µTorrent

[smyle]

I see for an instant regularly my computername too as peer in the peer list, when i seeding :shock:

[MaV]

I think this is perfectly normal, because your computer is also a peer when seeding, isn't it?

[Ultima]

I think this is perfectly normal, because your computer is also a peer when seeding, isn't it?

Sure, it can happen, but it shouldn't. You wouldn't connect to yourself if you're seeding anyway, since you wouldn't be downloading the files that you're seeding O.o

[gabo03]

I think is not normal, i dont see this "bug" in any other client.

And i see both IPs LAN and WAN in my peers view.

[okasvi]

ive gotten this:

[Loatroll]

Just so ye know, I've seen my own ip and so on in all kinds of torrent-clients, so I doubt it is a problem with soly with µtorrent, IMHO its more likely a problem with the tracker.

Though it would certainly make sense to filter out ones own IP.

[AnacortesBoys]

This can actually show up in firewall logs if your firewall does not allow inside addresses to access the external interface, as would be the case if you had IP spoofing filters turned on.

I'm seeing my v1.500 uTorrent client attempt to connect (SYN) to my external firewall interface (my public IP) about every 2-5 minutes. Firewall drops and logs the traffic. I don't know of a purpose for this connection, but if it is necessary for uTorrent to function correctly/efficiently, it needs to be documented so firewall rules can be adjusted.

Don

[Firon]

Not necessary. It happens because it doesn't know you == you until it connects to itself and finds it has the same Peer ID. If the firewall blocks it, then it'll try over and over forever.

[nightshifted]

Shouldn't the tracker, or a peer giving you PEX info, know that you==you and therefore resist telling you about yourself? I don't know whether that would apply to DHT, though.

[AnacortesBoys]

I should include that I have DHT disabled.

[Firon]

No. Neither PEX nor the tracker include your peerid (which is what identifies you, not so much your IP). You only find that out when you connect to the person.

[nightshifted]

Thanks, Firon. I knew they don't send the peer ID but figured that if the IP and port matched, they would know you to be you.

[Firon]

Well, there's also the fact that your external IP isn't really available to you most of the time, since most people are behind some kind of router.

[Klaus_1250]

Well, there's also the fact that your external IP isn't really available to you most of the time, since most people are behind some kind of router.

UPnP can tell you the external IP, though some implemtations of it do it a little buggy (my router outputs 0.0.0.0 and the external IP).

Second, if uTorrent sends a handshake to itself on the external IP, it will receive it back with the router's addresses at the sender. uTorrent should know the IP of the router/gateway-device, so can't it recognize such a handshake? With some logic it seems theoretically possible. In practice and terms of coding is something else, but should be doable.

[Firon]

Why go through all that work when this method works fine? The only problem here is braindead firewalls.