mldonkey-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mldonkey-users] Test for low ID user with wrong IP address


From: Jose Romildo Malaquias
Subject: Re: [Mldonkey-users] Test for low ID user with wrong IP address
Date: Tue, 8 Apr 2003 09:27:05 -0300
User-agent: Mutt/1.5.4i

On Tue, Apr 08, 2003 at 03:27:01AM +0200, Steffen Solyga wrote:
> Citing Romildo (Monday, 2003/04/07 21:31)...
> 
> > http://www.thedonkeynetwork.com/connection_test
> > 
> > However, the IP address the the test tells me is wrong.
> > It says it is 200.225.194.49, and it is not true.
> > My IP is dynamic assigned, and currently it is
> > 200.170.177.245. Even after rebooting my system and
> > rerunning the test, it insists my IP address is
> > 200.225.194.49.
> 
> Maybe your provider uses NAT for whatever reason?
> You may check http://absinth.dyndns.org/cgi-bin/ip also. If your IP
> (REMOTE_ADDR) is still 200.225.194.49, there's a router somewhere
> replacing your source IP with its own. But I've never heard about
> providers doing so. Maybe it's a LAN router?
> 
> And that's also a possible reason for getting a low ID: The router
> doesn't forward incoming connections because it doesn't know where to.

The reported IP address 200.225.194.49 (which resolves to
sub-redes-03-049.ctbctelecom.com.br, the word "sub-redes" means
"subnetworks") is the IP of the proxie (cache) from my internet
service provider.

I have contacted the ISP support and they tried to solve the problem.
I believe they removed the http://www.thedonkeynetwork.com/connection_test
URL from their cache and now the test succeeds (my current dynamic IP
is 200.170.176.112, as reported by /sbin/ifconfig):

        test for client on port:
                [4662] test
        your ip is: 200.170.176.112

        success ... your id should be 1890626248

But mldonkey have servers still reporting "ERROR: Your port 4662
is not reachable. You have a LOWID".

How does my current IP is told to the eDonkey servers?

Why now the connection test suceeds but eDonkey servers
still are not able to reach the 4662 port?

Any clues on how to solve this problem?

Regards.

Romildo
-- 
Prof. José Romildo Malaquias        address@hidden
Departamento de Computação       address@hidden
Univ. Federal de Ouro Preto  http://uber.com.br/romildo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]