LimeWire 4.9.30 giving wrong browsed IP addresses
 

I just noticed something after upgrading to LimeWire 4.9.30. Seven times out of ten, when I browse a user I usually get the same same IP address except for the last two digits; 192.168.XXX.XXX. The third number alternates between 1 or 2.

Is it just giving me the IP of the leaf/node/LimeWire server/whatever instead of the user's address? Has the browse function been tweaked not to show another users true IP address?

Thanks,
Swanky

192.168.x.x are users behind routers. 10.0.x.x are users behind NAT.

OIC...never realized that. Thanks for the info! I thought it was some great conspiracy or something. ;)

technically right, but those are just more commonly known as private ip addresses. (or private address space). they can be used on any network with any topology. these addresses are not routable outside the intranet network. (basically you cant connect to them). i personally use and like the 10.*.*.* address space because it has the most ip's available for a network (and subnets), and its the easiest to remember. but for some reason (i have no idea why) companies like to default there routers to use the 192.168.*.* address space.

Excerpt from RFC1918 (HERE):

3. Private Address Space

The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

Actually, I kind of feel stupid for not knowing that. I'm a pretty geeky guy, but don't have much experience dealing with routers, wif-fi, nats, etc. LOL, for a second I thought LimeWire was masking users IPs in order to thwart the RIAA or MPAA.

I suppose I could always do a "netstat -n" and track down their address. When I find someone sharing good stuff I like to grab files over a period and not leech off 'um all at once.

Thanks for additional the info.