Quote:
Originally posted by Spooky
I don't see aproblem with that. And all clients except LimeWire are already doing this.
My IP changes every 24 hours and there's nothing I can do against it. So why should I do this stupid administration work when Lime Wire can do this for me ? During handshake your real IP is always transmited. So it's really no big deal for Limewire to find out the IP. |
My first question is which ones? Secondly, I think he misunderstood my comments
if you're running applications on a machine with the private net IP address. The IP translation is occurring in an intermediary device which is your NAT box or router this is transparent to the remote machine and your local machine. Because of this transparency the remote machines think that your Router (limewire not running here ) is the host.
Your local machine thinks that is is communicating with the Internet Directly. Any queries to your protocol stack is going to show a 192.168.x.x address.
I'm not suggesting that determining the IP address is impossible, I'm simply stating that if someone is able to do this there using an entirely different methodology to do so for example,
Stage 1: Outbound Communications:
private_net_host_ip--->(NAT_software)-->public_net_ip--->Config_Server
Stage 2: Inbound Communications:
Config_server--->public_net_ip--->Client_Application_Port
I don't think that this is part of the current Limewire Network Implementation. You simply connect and get a list of hosts to make connections to.