aMule Forum
English => aMule Help => Topic started by: misterj on September 16, 2006, 11:34:56 PM
-
I've alwys the kad firewalled.
I suppose I have any firewall active, but i don't know what I can do to get kad unfirewalled
thank you to all
misterj
-
First, make sure you have port forwarding set up properly:
You need to forward the ports that aMule uses in your router. Take a look at http://portforward.com/routers.htm, that page has detailed step-by-step instructions for pretty much every router on the market.
aMule uses three ports (see Preferences->Connection) that need to be forwarded:
- a client TCP port
- a client UDP port (this is the above port +3)
- and an eMule extended UDP port
Also, if you are running any firewall software (e.g., OS X's built-in firewall, which you can control via System Preferences->Sharing->Firewall) on your computer, you need to open the above ports there as well.
You can use the connection tester (http://www.amule.org/testport.php) to check whether the client TCP port can be reached from the outside, that is, whether it is forwarded properly in your router and not blocked by any firewall software.
Good luck. :)
Once port forwarding is set up properly, it might still take some time (up to an hour I'd say) for aMule to detect that kad is not firewalled.
-
Hi,
I'm not sue if anyone's still watching this topic but I have the same problem.
amule connects and Kad is off/red I then disconeect and re connect and the Kad arrow goes yellow/ firewalled. After a while, jowever, it returns to off/red.
I tried the connection tester and got the response "Success The TCP port 4662 is available. You should be able to use the ED2K P2P service without any problems."
Any suggestions?
Thanks
-
Check if your UDP ports are correctly forwarded.
-
I also have this problem. I have aMule running on a Linux box acting as a router (so aMule shouldn't be NAT'ed because traffic is to and from the external interface). I have opened up all outgoing traffic (from the router) and allowed 4662 TCP in, 4672 and 4665 UDP in, and even 4661 in. I do not, however, have UPnP enabled and won't either.
When I copy a fresh nodes.dat to the ~/.aMule directory, after a short period I will get Kad (firewalled). I've sometimes caught it saying Kad (ok) for a short period, but for the most part, if I go away for a few hours and check on the status I get Kad (off).
Oh yes, I am using amuled not the GUI. aMule 2.1.3, wxGTK2 v2.6.3, Unicoded, OS: Linux
-
Likewise, I haven't seen KAD anything but firewalled for a long time. These are my PF rules:
rdr on $ext_if proto tcp from any to any port 4662 -> 192.168.1.2 port 4662
rdr on $ext_if proto udp from any to any port 4665 -> 192.168.1.2 port 4665
rdr on $ext_if proto udp from any to any port 4672 -> 192.168.1.2 port 4672
pass in on $ext_if inet proto tcp from any to any port 4662
pass in on $ext_if inet proto udp from any to any port 4665
pass in on $ext_if inet proto udp from any to any port 4672
From the amule logfile:
2007-12-30 15:30:32: MuleUDPSocket.cpp(77): MuleUDPSocket: Created Server UDP-Socket at port 4665
2007-12-30 15:30:32: MuleUDPSocket.cpp(77): MuleUDPSocket: Created Client UDP-Socket at port 4672it looks like amule is definitely using those two UDP ports.
KAD works though. Am I missing anything?
I'm running the 20071212 CVS.
-
From the amule logfile:
2007-12-30 15:30:32: MuleUDPSocket.cpp(77): MuleUDPSocket: Created Server UDP-Socket at port 4665
2007-12-30 15:30:32: MuleUDPSocket.cpp(77): MuleUDPSocket: Created Client UDP-Socket at port 4672it looks like amule is definitely using those two UDP ports.
KAD works though. Am I missing anything?
Yes. The extended protocol also uses a UDP connection. TCP portnumber + 3. That's the second UDP listener.
-
I had the same problem with "kad-firewalled/off" after Ubunu upgrade. But when I reinstalled Ubuntu aMule works perfect. Strange way to deal with a problem but.. it works :)
-
First, make sure you have port forwarding set up properly:
You need to forward the ports that aMule uses in your router. Take a look at http://portforward.com/routers.htm (http://portforward.com/routers.htm), that page has detailed step-by-step instructions for pretty much every router on the market.
aMule uses three ports (see Preferences->Connection) that need to be forwarded:
- a client TCP port
- a client UDP port (this is the above port +3)
- and an eMule extended UDP port
Also, if you are running any firewall software (e.g., OS X's built-in firewall, which you can control via System Preferences->Sharing->Firewall) on your computer, you need to open the above ports there as well.
You can use the connection tester (http://www.amule.org/testport.php) to check whether the client TCP port can be reached from the outside, that is, whether it is forwarded properly in your router and not blocked by any firewall software.
Good luck. :)
Once port forwarding is set up properly, it might still take some time (up to an hour I'd say) for aMule to detect that kad is not firewalled.
the extended UDP port is +3, not the client udp port ;)