Lando Posted March 6, 2007 Report Share Posted March 6, 2007 According with wiki suggestions I've written the commands below ,but they seem not working properly.....Someone can help me to write them with Shorewall code ? Many thanks. iptables -A INPUT -p tcp --dport 4662 -j ACCEPT iptables -A INPUT -p udp --dport 4662:4665 -j ACCEPT iptables -A INPUT -p udp --dport 4672 -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -P OUTPUT ACCEPT Quote Link to comment Share on other sites More sharing options...
scoonma Posted March 6, 2007 Report Share Posted March 6, 2007 According with wiki suggestions I've written the commands below ,but they seemnot working properly.....Someone can help me to write them with Shorewall code ? Hi Lando, you should first take a look at the well-written comments in these shorewall config files: /etc/shorewall/interfaces /etc/shorewall/zones /etc/shorewall/policy /etc/shorewall/rules You'll get a concept how shorewall is working. IMHO, it's much easier than directly manipulating iptables. Given your shorewall is already working, you'll just have to add some entries to the rules file. (In case the machine you'll want to run amule on is behind a router, you'll have to take care of that, too.) Your rules files may include these entries after editing (just an example, depending on your network config): ... ACCEPT net loc tcp 4662 ACCEPT net loc udp 4662:4665 ACCEPT net loc udp 4672 INCLUDE rules.drakx #LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE After editing, you should "service shorewall restart" to get your changes activated. Quote Link to comment Share on other sites More sharing options...
Lando Posted March 6, 2007 Author Report Share Posted March 6, 2007 It seems not so easy....... [root@localhost lando]# service shorewall restart Compiling... Initializing... Determining Zones... IPv4 Zones: net Firewall Zone: fw Validating interfaces file... Validating hosts file... Validating Policy file... Determining Hosts in Zones... net Zone: ppp0:0.0.0.0/0 eth0:0.0.0.0/0 Pre-processing Actions... Pre-processing /usr/share/shorewall/action.Drop... Pre-processing /usr/share/shorewall/action.Reject... Pre-processing /usr/share/shorewall/action.Limit... Deleting user chains... Compiling /etc/shorewall/routestopped ... Compiling Accounting... Creating Interface Chains... Compiling Proxy ARP Compiling NAT... Compiling NETMAP... Compiling Common Rules Compiling IP Forwarding... Compiling IPSEC... Compiling /etc/shorewall/rules... ERROR: Undefined Server Zone in rule "ACCEPT net loc tcp 4662 " /sbin/shorewall: line 774: 7684 Terminated $SHOREWALL_SHELL ${SHAREDIR}/compiler $debugging $nolock compile ${VARDIR}/.restart [root@localhost lando]# Quote Link to comment Share on other sites More sharing options...
scoonma Posted March 6, 2007 Report Share Posted March 6, 2007 It seems not so easy....... Compiling /etc/shorewall/rules... ERROR: Undefined Server Zone in rule "ACCEPT net loc tcp 4662 " /sbin/shorewall: line 774: 7684 Terminated $SHOREWALL_SHELL ${SHAREDIR}/compiler $debugging $nolock compile ${VARDIR}/.restart [root@localhost lando]# Please check your zones file. If you are directly connected to the net, you likely have only to zones: net (outbound) and fw, which would be local in that case. So you'd have to replace "loc" with "fw" and it should work. Quote Link to comment Share on other sites More sharing options...
Lando Posted March 6, 2007 Author Report Share Posted March 6, 2007 Thanks.I 've changed loc with $FW and the restart is OK. The output in "service -s " is >>> ACCEPT tcp -- anywhere anywhere tcp dpt:4662 ACCEPT udp -- anywhere anywhere udp dpts:4662:4665 ACCEPT udp -- anywhere anywhere udp dpt:4672 But the test in http://www.amule.org/testport.php fails and says >>>>> 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 (i.e. aMule, eMule). Detailed Error Message TCP Error 110 Connection refused Any idea ? Thanks a lot . Quote Link to comment Share on other sites More sharing options...
scoonma Posted March 7, 2007 Report Share Posted March 7, 2007 But the test in http://www.amule.org/testport.phpfails and says >>>>> 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 (i.e. aMule, eMule). Detailed Error Message TCP Error 110 Connection refused Hm. Are you behind a firewall (router) in a larger net? That had to forward connections to port 4662, too. Some providers also block known p2p ports. I don't know for amule, but for mldonkey i.e. you can choose your port freely, just following some rules - see here: http://mldonkey.sourceforge.net/FireWall So with the newer edonkey protocol you could change the incoming port to nearly anything (should be at least above 1024), opening tcp with the udp port number (your choice)+4. I'm not sure about the SYN flag thing mentioned at the end of the article. For testing I wouldn't rely on a testing tool, but instead run amule and check wether it works. Even now you should at least get a low id connection. Quote Link to comment Share on other sites More sharing options...
Lando Posted March 7, 2007 Author Report Share Posted March 7, 2007 Hi scoonma , my problem is low ID ( the message is Kad firewalled....) then very slow downloads. I've tried to uninstall shorewall (..then no firewall) but the problem is still the same ! I am not behind a router ...only a simple modem on a 2 MB adsl line . ....no reply from www.amule.org forum ...... Quote Link to comment Share on other sites More sharing options...
Lando Posted March 7, 2007 Author Report Share Posted March 7, 2007 I 've reinstalled shorewall , then service restart.....and everything work fine ! Your statements then were right .... maybe service restart is not enough...I don't know ! The online tests work fine and the ID is high . Many thanks. Quote Link to comment Share on other sites More sharing options...
scoonma Posted March 8, 2007 Report Share Posted March 8, 2007 I 've reinstalled shorewall , then service restart.....and everything work fine !Your statements then were right .... maybe service restart is not enough...I don't know ! I presume a "service network restart" should have worked, not just shorewall. Anyway, good to hear it works now. :-) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.