aMule Forum
English => aMule Help => Topic started by: cenobite on June 11, 2005, 02:48:06 PM
-
HI !
Some months ago (after hours making aMule even start in Mandrake 10 community) I made aMule work with high ID after some router configurations. I upgraded to mandrake 10 official, later to 10.1 official. Still working with High ID... But after upgrading to LE2005 something happend, I now got Low ID ? It says I'm probebly "behind a router or firewall". The thing is I allways have !!! It worked before ? I've checked the mandriva firewall, and it's turned off. My router is still setup with the tcp 4662 in virtual server, and I also checked what programs are running while aMule is started, but can't find anything firewall related programs running.... ?? I know LE2005 comes shipped with guarddog and I also downloaded KlamAV and firestarter lately, but I don't think any of those are running while using aMule....
Anything I've missed here ?
Thanx !
Ole
-
May be you could use this wiki page to test if your 4662 is reachable :
http://www.amule.org/testport.php
xit.
-
HI !
Yes, I've tested the 4662 port. It's not reachable. That's why I can't get aMule to work with high ID..... I've also checked my router again, and it is still configured with the tcp 4662-4665 (service port), map to my IP in virtual server setup.
Thanx !
Ole
-
check if you really don't have a firewall enabled. for an iptables based one
iptables -L -n(as root) should give you some information.
-
your that your ip is still teh same as in the router setup?
maybe after upgrade to LE you know have dhcp enabled...and so you dont have a static ip anymore.
also maybe your ISP might be blocking port 4662 since a couple days, I recommend maybe switching to a completly different port, if you are really sure that IP-address and ports are setup correct in the router and mandriva firewall is off
stefanero
-
Yo !
I ran "iptables -L -n", but can't get anything out of it......Could someone figure it out for me if I post it here ? I haven't tried other ports yet. I mean, Is there other alternatives than 4662-4665 ? The IP adress is the same as before.... I'm pretty sure something changed in the network configuration somewhere when upgrading to LE2005.....
I also see that I have the 2.0.0rc7 version of aMule. I should make an update anyway....
Thanx !
Ole
-
Just made an upgrade. That didn't do it.
Now running aMule 2.0.2
-
just post the iptables -L output here...we can figure it out if its ok or not ;)
-
Hi, there !
OK, here it goes !! :-)
[ole@minlinuxboks ~]$ su
Password:
[root@minlinuxboks ole]# iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT tcp -- 192.168.1.XXX anywhere tcp flags:!SYN,RST,
ACK/SYN
ACCEPT udp -- 192.168.1.XXX anywhere
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere limit: avg 10/sec b
urst 5
DROP all -- anywhere 255.255.255.255
DROP all -- anywhere 255.255.255.255
DROP all -- BASE-ADDRESS.MCAST.NET/8 anywhere
DROP all -- anywhere BASE-ADDRESS.MCAST.NET/8
DROP all -- 255.255.255.255 anywhere
DROP all -- anywhere 0.0.0.0
DROP all -- anywhere anywhere state INVALID
LSI all -f anywhere anywhere limit: avg 10/min b
urst 5
INBOUND all -- anywhere anywhere
LOG_FILTER all -- anywhere anywhere
LOG all -- anywhere anywhere LOG level info pref
ix `Unknown Input'
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere limit: avg 10/sec b
urst 5
LOG_FILTER all -- anywhere anywhere
LOG all -- anywhere anywhere LOG level info pref
ix `Unknown Forward'
Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT tcp -- 192.168.1.XXX 192.168.1.XXX tcp dpt:domain
ACCEPT udp -- 192.168.1.XXX 192.168.1.XXX udp dpt:domain
ACCEPT all -- anywhere anywhere
DROP all -- BASE-ADDRESS.MCAST.NET/8 anywhere
DROP all -- anywhere BASE-ADDRESS.MCAST.NET/8
DROP all -- 255.255.255.255 anywhere
DROP all -- anywhere 0.0.0.0
DROP all -- anywhere anywhere state INVALID
OUTBOUND all -- anywhere anywhere
LOG_FILTER all -- anywhere anywhere
LOG all -- anywhere anywhere LOG level info pref
ix `Unknown Output'
Chain INBOUND (1 references)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere state RELATED,ESTAB
LISHED
ACCEPT udp -- anywhere anywhere state RELATED,ESTAB
LISHED
LSI all -- anywhere anywhere
Chain LOG_FILTER (5 references)
target prot opt source destination
Chain LSI (2 references)
target prot opt source destination
LOG_FILTER all -- anywhere anywhere
LOG tcp -- anywhere anywhere tcp flags:SYN,RST,A
CK/SYN limit: avg 1/sec burst 5 LOG level info prefix `Inbound '
DROP tcp -- anywhere anywhere tcp flags:SYN,RST,A
CK/SYN
LOG tcp -- anywhere anywhere tcp flags:FIN,SYN,R
ST,ACK/RST limit: avg 1/sec burst 5 LOG level info prefix `Inbound '
DROP tcp -- anywhere anywhere tcp flags:FIN,SYN,R
ST,ACK/RST
LOG icmp -- anywhere anywhere icmp echo-request limit: avg 1/sec burst 5 LOG level info prefix `Inbound '
DROP icmp -- anywhere anywhere icmp echo-request
LOG all -- anywhere anywhere limit: avg 5/sec burst 5 LOG level info prefix `Inbound '
DROP all -- anywhere anywhere
Chain LSO (0 references)
target prot opt source destination
LOG_FILTER all -- anywhere anywhere
LOG all -- anywhere anywhere limit: avg 5/sec burst 5 LOG level info prefix `Outbound '
REJECT all -- anywhere anywhere reject-with icmp-port-unreachable
Chain OUTBOUND (1 references)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT udp -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
[root@minlinuxboks ole]#
I just added some X's were I think they should be ;-)
Thanx again !
Ole
-
Hi, I'm new to this forum... nice to meet you all
I have been searching for a while for similar problems about my amule, but of course my search wans't exhaustif.
My low id problem doesn't seem to come from my router, as my 4662 port is accesible from outside, and I have linked the router's 4662 port to the server's 4662 port tcp (and 4672 udp), my firewall is actually open to everything (just until I solve my problem).
even other services can acces 4662 port in both directions and by analysing what's going on with ethereal, everything SEEMS ok...
I just can't understand.
EDIT: I also tried changing tcp port to 80, no changes
-
ow damn it, I have partially solved the problem...
running amule a root...
-
@ cenobite
can you run this as a script and root user:
make sure iptables is in path when you do it...
#!/bin/bash
echo -n "Shutting down firewall"
#flush all rules
iptables -F
iptables -X
#resettting to default policy
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
when its done, restart amule and see if you have highID
stefanero
-
@karamazof
if you have to run it as root, something in your setup is wrong...
and as a normal user you cannot use port80 since this is only availible as root user, but you should be able to run amule on high ports without problems, just check your firewall(s)
-
Hi, I tried port 35555 and it seems to work fine.
Thankyou for your help,
-
Hi folks !
I will try some of the sugestions above.
Thanx guys ! keep it up :-)
I will not give it up until this darn thing runs like ..eh.... my cpu fan.... ? (it's a darn good cpu fan) !! hehe
Will post what happend later. Will also try aMule as root since many people has done this with positive feedback ! Which I know isn't a good thing, but I'm a bit longer on my quest for a better working aMule :-)
Ole
-
stefanero
Well, I've tried run aMule as root. That didn't work at all. Then I ran the script you posted and I got High ID again !!!
So my next question is; Why ? :-)
Thanx !
Ole
-
8) thats a script to completly disable your local ip-tables firewall....
which means that your mandrive firewall was setup correct before, and therefor did not give you highID....
so basically what you have todo, is
--either shutdown mandrive firewall
--or configure it correct
the iptables you posted before where not letting amule get complety access..
stefanero
-
Thanx ! It all works great now !!
One strange thing though.....
Why was I given LowID when my mandriva firewall was turned off in the first place ?
I had to turn it on and then off again ?!?!
It's probably me, but it tricked me bit there anyway, hehe !
thank you for all help !
Ole
-
1 sec.
I just restarted my computer and it seems like I have to uncheck or check the firewall on/off button each time get highID ??
once confirming the firewall settings I can start and shutdown aMule as many times as I want to and still getting highID, until I restart or shut down the computer.......I allways have to go in the controllcenter to check or unchek (it doesn't matter if the box is checked or not) mandriva firewall to use aMule with highID.
hmmm...
-
hmm maybe use a real Linux ;) just kidding....
maybe check the runlvl editor, and see if the firewall is enabled in your runlvl by default, if so disable it from the runlvl
stefanero