aMule Forum

English => aMule Help => Topic started by: metafractal on January 04, 2008, 02:45:10 PM

Title: LowID even after firewall/router configured?
Post by: metafractal on January 04, 2008, 02:45:10 PM

Hello,
I am running aMule 2.1.3 on Ubuntu Gutsy. I use TCP port  4662 and UDP port 4672. I have configured firestarter to allow  all traffic for  ports 4662, 4665 & 4672.

I also have a D-Link DI-524 router.  I have configured the router to allow these ports by creating three virtual servers: one for TCP port 4662, one for UDP port 4665 and one for UDP port 4672.  I have set myself up as a static DHCP client (i.e. static IP address) and used this IP as the "Private IP" for each of the virtual servers.

After doing all this, I am still getting LowID and the test at http://www.amule.org/testport.php says that my TCP port is unavailable, even when I have aMule running.

Can anyone tell me why this could be  happening?

Thanks.

Title: Re: LowID even after firewall/router configured?
Post by: phoenix on January 05, 2008, 12:34:08 AM

Hi metafractal,

If the test at http://www.amule.org/testport.php says that your TCP port is unavailable, you will certainly get a low id.

Maybe you can use wireshark to sniff the network packets to see where is the problem. Most certainly either your router or the firewall is eating packets.

Cheers!