When will Limewire support this feature that all other gnutella clients support ? I'm firewalled with a port forwarded to my PC. I really need any p2p application to detect my real IP.

This fact has always kept me from using LimeWire...

I second that. It seems pretty simple to accomplish ... unless Java somehow blocks it?

If this were added, LimeWire should also auto-detect the port in use. I have several computers behind NAT and each is statically bound to a different port so all can use LimeWire at once. Auto-detecting the IP address would be useless in these situatons unless the port was also auto-detected.

You can set your port to whatever you want. Why would you need to detect it ? If you are behind a NAT router, you should forward a port to each computer running LW and set the correct port in each installation. But to make this work you either have to set your IP manually, which is quite tireing if you get a new IP every 24 hours or LW could do this automatically...

That's the point, right now you have to set it manually, but it could be automatically detected.

Mark

After watching this conversation I realize that this would be a nice feature for people who have problems setting up their NAT based host to use a single real IP.

There is a technical aspect to this whole issue that is being overlooked in requesting that the Limewire Application detect the IP and that technical aspect is this.

Internet -->Real_ip -->router -->NAT_address_space_hosts_apps

Because the Application is running on a NAT based Host the detection mechanism will use the stack on the local machine to determine the ip-address for the machine. Can anybody tell me why this does not accomplish what you want?

Can you see why this would be very problematic? If you can't figure it out I will explain it in another post.

Anyway since the IP translation is handled by the BRIDGE (I call it a bridge because most of these devices don't do any routing in the traditional sense of the word.) Your solution to this problem is simply as stated before by one of the other posters.

A. Enable port forwarding.
B. There are websites that can tell you what your real ip is (or IP address of your NAT-BOX)
C. Force this IP in limewire
D. If you have a DHCP ip address / from my experience unless they are forcing your device to change its IP address every few days--if you leave your NAT-BOX ON it will usually retain the address given to it over longer periods of time.

Again this has been my experience in what I've seen in the field.

I know people hate doing this type of administration but sometimes its necessary when you want to accomplish something that wasn,t designed to support all of its pactical implementations.


Hope this helps.


http://www.leeware.com

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

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.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

Clients which auto-detect the IP:
- Shareaza
- Bearshare
- Gnucleus

You seem to know how NAT routers work. So do you know what port forwarding is ? You're right LimeWire is not running on the router of course, but if you forward a port to the Computer running Limewire, it will be as if Limewire was running on the Router. But to make it possible for other clients to download from this user without a push request, Limewire needs to send them the correct IP, which should be auto detected!

Yes, I know what port forwarding is and how it works. I think however the success or failure of this will largely depend on the NAT implemenation. There are several ways nat is implemented and although I'm not sure how the products you mentioned implement port dectection. I assume that the methodology is built into the startup squence of the clients and I assume that they use a remote machine to determine the ip of the connecting client and then send that configuration information back to the application which is unable to determine correctly what its real ip is from stub domain behind a NAT device.

This is something that out of my own curiousity I might look into.

__________________
Lee Evans, President
LeeWare Development
http://www.leeware.com

If you use Gnucleus, you can look at the handshake if you select Extened information in the contextual menu of a connection in the connection window (Advanced). There you'll see that in almost every handshake there is an option called Remote-IP like that is followed by your IP. That's the way the other programs detect it.

And I can asure you that it works. Me and a lot of other users are connected to Gnutella like this.