On 13-01-05 You asked me to try iptables -F and I did.
Result on that occasion was LOW-id being got from the connected server.
to be sure it was right i closed amule and restarted it with no firewall (I mean having the rules flushed).
Today I started amule and got LOW-id again (will dso the -F thing with iptables and report back)
Chain INPUT (policy DROP)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
after doing the iptables -F command and get a LOW-id.
Now changing the INPUT Policy to accept (Errrrr).
now rules look like this...
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
the test (from website
http://uberpenguin.they-are.us/temp/testport/index.php) is below.
Error: TCP port 4662 is unavailable. Make sure your firewall or router is allowing/forwarding this TCP service port and your ED2K client is running.
Explanation
TCP Error 111: The port is available for connections but a connection was refused meaning there is nothing listening on that port. This most likely means you can use ED2K but your client is not currently running. Try using this test again with an ED2K client running to make sure you can really establish a connection.
185.reserved.callplus.net.nz (203.184.24.185)
Coding by uberpenguin, idea by deltaHF, which he found here
Loaded amule up and got a LOW id.
BTW i am running MDK 10.0 Official with IPtables ver 1.2.9
One last thing i have tried and that is to add NEW to the -state option so the INPUT chain looks like this now....
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state NEW,RELATED,ESTABLISHEDACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere tcp dpt:4662
ACCEPT udp -- anywhere anywhere udp dpt:4672
ACCEPT udp -- anywhere anywhere udp dpts:4662:4665
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
Now i loaded aMule and got a LOW id again (closed it down then reloaded with rules above in operation.
the website referred to earlier gave me a success as below
Success The TCP port 4662 is available. You should be able to use the ED2K P2P service without any problems.
185.reserved.callplus.net.nz (203.184.24.185)
Coding by uberpenguin, idea by deltaHF, which he found here
So what is going on
?
Also my concern is that anyone will be able to getin via the rule in my firewall.