aMule Forum
English => aMule Help => Topic started by: halus on October 21, 2004, 07:05:03 PM
-
Hi
Amule tells me I have recived Low-ID, and it's probebly caused by a firewall. I guess this is the reason for my slow transfers, never been over 43 kbs DL, upload is usually around 4-500 kbs. Just tested the speed of my connection and got about 8 mbs download speed.
The Amule help pages seems to cover this issue but my problem is that I am not sure were my firewall really is.
I am on a local network so I guess it is probably a firewall controlled by the network administrator. What to do then? Is there a way to scan for open ports (if "port" is a proper term) and adjust amule to the firewall?
Also I don't know if there is a firewall on my computer. Just installed Vidalinux and it might have installed a firewall without telling me(?). If that is the case how do I find that firewall?
-
i guess ports must be open and forwarded to your pc, look here (thanks to DeltaHF):
userchannel.de/wissen/docs/Linux%20Router%20in%2020%20Minuten
-
Go to http://www.auditmypc.com/freescan/scanoptions.asp, select Firewall Test 2, locate the "Advanced..." line, (3rd one) and enter 4662 (or whatever port your aMule is listening on) to the box, then press Go.
Do it once with aMule running, once with not running.
When aMule running, it should report that open port found, bla-bla...
when aMule isn't running, it should report that no open ports found.
If this is the case you can be sure that your aMule port is open an forwarded to your computer.
If any of the checks gives other results than I said, please contact to your network administrator. :-)
-
there's a port tester at amule.org too:
http://www.amule.org/testport.php
That's eben developped by uberpenguin, so it suerly works well ;)
Greetings!
-
Thanks for the information, I"ve finally got HighID and Green smiles in Azureus. But there is one problem. If my provider blocks port 4661, will I be able to conect to razorback? Now it always ends like that:
22/10/04 20:36:31: Connecting to Razorback 2 (195.245.244.243 - 195.245.244.243:4661)
22/10/04 20:36:57: Connection attempt to Razorback 2 (195.245.244.243:4661) timed out.
-
Belegdol,
I don't think that your provider would block an outgoing connection, unless he is so evil as to block explicitly ed2k clients. That however would not fully solve his problem.
Usually providers block the incomming connections, not connections to servers, these are outgoing connections.
Notice that Razorback has one peculiarity, you must accept/port forward (if you have a router) connections from 195.245.244.241:(amule TCP port), besides 195.245.244.243. Razorback connects to you through this ip to test if you are able to get a high id. If you have IPFilter enabled, that may mislead you.
Cheers!
-
I've got public IP and I am using shorewall. How should I configure it? The tcp port that is set up in amule connection window is open.
[edit]
Enabling/disabling ipfilter.dat doesn't help. Moreover, any attempt to connect server that has 4661 port next to its ip times out. And my isp must block at least incoming traffic on 4661 - after switching to one of slsk ports I got the high id. Maybe he is as evil as you ;).
-
Did you try Jacobo's suggestion? http://www.amule.org/testport.php
aMule must be running.
-
Thanks for advices.
The port-test says port 4662 is closed with amule running. So guess I have to talk to administrator then.
But is it possible that I have an firewall on my computer. Just installed VidaLinux and have no idea what it really installed. Is there a way to scan my computer for a firewall?
-
try as root
$ iptables -L -n
and paste the result here.
-
You could always try some different ports.Amule is set up to use port 4662 by default but that doesn't mean it can't use another port instead.Just try some random ports from different ranges and see what happens,you might get lucky if the admin hasn't locked everything down.
-
Originally posted by phoenix
Did you try Jacobo's suggestion? http://www.amule.org/testport.php
aMule must be running.
Yes, I did. Port 4661 and 4662 are always closed, my shorewall settings do not matter. The port I'm now using is open - script reports success.
-
Phoenix, here is my iptables -L -n:
# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Darklegion:
I am thankful for the information that I can change the port in amule to something that can "satify" the firewall. If there is a tool that can scan for useable ports for my firewall I would be very glad (can nmap do this?).
-
Any ideas? Help would be REALLY appreciated.
-
Have you read http://www.amule.org/wiki/index.php/Firewall
Greetings!
-
Belegdol, your isp is closing those ports.
-
So I think I should bug him to allow at least outgoing traffic on 4661. Lucky me :(
-
Originally posted by halus
Phoenix, here is my iptables -L -n:
# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
No firewall. Something else is blocking you, maybe a router?
-
Phoenix wrote:
"No firewall. Something else is blocking you, maybe a router?"
I have no router.
Other people in the building having troubles getting active mode in DC++, so guess there is something in the LAN blocking.
-
Originally posted by halus
I have no router.
Other people in the building having troubles getting active mode in DC++, so guess there is something in the LAN blocking.
Sorry, I don't know dc++, but seems to me that active mode is like high id, right? Well, if other people are having trouble with other software, this should not be an aMule issue.
You said you have a building connection, are you sure your IP is real? Most probably you have a router in your building that is NAT'ing the connections and doing DHCP to distribute fake IP's. Check it.
-
Most likely the lan has a firewall,that by default is blocking pretty much everything but web traffic and other stuff required on the lan.Your setttings on your local machine will not matter,since everything is getting stopped at the gateway..so unless you can find a port that the admin didn't block there is nothing much you can do outside getting them to open the ports for you :)