Why Ants seems to default to the wrong IP...

[tsafa1]

Gwren says:

One pc can have MORE than one IP address OK? (if it has more interfaces
using the tcp/ip protocol). These IP addresses can be public or local
(private -> 192... 169... etc etc.)

I currently DETECT in ANts ONE AVILABLE PUBLIC IP address (excluding all
the local ones if at least one public IP is found), if you have more
than one PUBLIC IP address (PUBLIC means INTERNET ADDRESS) a random one
is selected. So if you have your pc DIRECTLY CONNECTED to internet, in a
word if you have an interface on the local machine whose MAC is linked
to a PUBLIC INTERNET IP ANts DOES detect that public IP.

BUT!

There are many kind of connections to internet. Many ADSL users have a
wireless access, an internal router with a LAN, a NAT and there are MANY
other different configuration where the IP linked to your local network
adapter is not the public one (it is a local one like 192.xxx). In all
these cases ANTs (but also ANY program) cannot state which is your
public IP. Actually it could state your IP querying a remote server, but
this WOULD BE USELESS. Because in all the former configurations, your
machine is USING an IP different than the public one that people see
from the outside, so it is NOT VISIBLE FROM THE OUTSIDE, unless you
don't configure properly your LAN, NAT or anything else you are using in
a way to TUNNEL requests from the outside to your internal IP (And this
needs a manual configuration of the network! No program can do this for
you).

for instance.

(A)204.123.42.23 --(inet)--->(B)205.54.32.12--(tunnel)--->(C)192.168.0.4

A is the external ANts client who makes a request, (B) is your NAT that
expose a public ip and is enabled to receive incoming request. (C) is
the address of your machine, ANts will never know your public exposed ip
is (B) unless you don't say it explicitly by setting it in the settings.
Also even if ants used a remote server to state that the public ip is
(B) this would be useless untill you set properly your NAT (B) to
forward request to your local machine (C).

So resuming... if ANts shows you a local IP and NO PUBLIC IPs are
present in the list this means you are NATTED and you have to set
everything on your own (if possible, that is if you can admin the NAT
else you have to remain in a state that is comparable to a LowID in
emule). If ANts shows a local IP and at least a PUBLIC IP is present in
the list, THIS IS A BUG and you have to post it on sourceforge
specifying WHICH IS THE LOCAL IP SELECTED BY DEFAULT and WHICH IS YOUR
PUBLIC IP ADDRESS SHOWED IN THE LIST. In all the other cases ANts will
show you the right ip.

[xrobot]

The ip problem is being shouted again and again! The creaters seem of no interest to solve...
Ants is so special that it is the only ONE p2p program that need to input ip by hand :sw

[tsafa1]

The ip problem is being shouted again and again! The creaters seem of no interest to solve...
Ants is so special that it is the only ONE p2p program that need to input ip by hand :sw

Keep in mind that with a lot of other programs, some users are simply not able to connect and that is the end of it. They can't change port numbers or IP numbers.

[cpugeniusmv]

The ip problem is being shouted again and again! The creaters seem of no interest to solve...
Ants is so special that it is the only ONE p2p program that need to input ip by hand :sw

False.

DC/DC++ is the same way if you're NAT'd.

Easy fix: go to www.dyndns.org and get a hostname. Have your IP automatically updated with one of the auto-update clients. Put that hostname in the program. I've been doing it in DC++ for years.