aMule Forum
English => aMule Help => Topic started by: kappy on June 11, 2005, 03:51:17 AM
-
Hi,
I've installed aMule 2.0.2 in my FC3 with no problems, but i can only connect with high-Id as root.
If i connect as a normal user I get LowID in any server.
I use the default ports, 4662 TCP, 4665 UDP and 4672 UDP, all forwarded in the NAT.
iptables is empty.
Am I missing somethig?
Thnkx
-
Hi I have the same problem under Ubuntu. When I run aMule as root (sudo aMule ) it receives high id and the port testing reports open ports. However, when I run the program as a non-root user aMule receives low id and the ports are reported as unavailable. Have you found any resolution?
-
you guys have a firewall
-
Kry, if we had a firewall causing the problem, why would aMule work correctly when run with root permissions?
By the way, I installed eMule under wine, it has the same behavior: when run as normal-user, it reports "can't bind a socket" error and goes on with low id. If run as root, it works perfectly.
Any more ideas?
-
Yes. You have a firewall (or you're using a port bellow 1024).
-
Hi Kry, thanks for the reply.
>You have a firewall
Could you explain why a firewall would accept packets to aMule when aMule is run as root, but reject the very same packets when aMule is run by a non-root user?
best,
r.
-
iptables has, amongst other options, owner options for outgoing packets, and quite probably for ports and incoming packets.