QauNuckShin Posted October 16, 2005 Report Share Posted October 16, 2005 In my peer list for a certain torrent, I'm connected to localhost! Ok, I thought.. Few seeds and peers, maybe some bug where it connects to itself?Then I noticed.. this client is using BitComet (I'm using µTorrent), and has downloaded 7.2 MB of data from me! Weird... Link to comment Share on other sites More sharing options...
1c3d0g Posted October 16, 2005 Report Share Posted October 16, 2005 Screenshot? :? Link to comment Share on other sites More sharing options...
vurlix Posted October 16, 2005 Report Share Posted October 16, 2005 It just means that the reverse dns resolved that peer's ip to "localhost"... It's possible, but rare. Link to comment Share on other sites More sharing options...
Martin Posted October 16, 2005 Report Share Posted October 16, 2005 Some people love messing with NS records. Link to comment Share on other sites More sharing options...
sethg Posted October 16, 2005 Report Share Posted October 16, 2005 You can tell the difference between a remote host with a broken rDNS record and a real internal loopback by doing netstat -n. You will see the raw IP with no rDNS lookup. Local loopback connections will have 127.0.0.1 or 0.0.0.0 as foreign address.Local loopbacks are pretty common. For example, I have Skype installed, which establishes one TCP loopback connection from port 1085 to 1086 and another from port 1086 to 1085. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.