Firewall SuSE

From AMule Project FAQ
Revision as of 23:21, 11 November 2004 by Jacobo221 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

By Tuxlover

NOTE: This document has been tested on SuSE Linux 8.2

Using SuSE Linux as a router/firewall

If you use SuSE Linux on your router/firewall to connect to the internet you can do the following to forward the ports used by e/amule to your client: You need to set your firewall to forward all connections coming to it on ports 4662 and 4672 in tcp and udp to your internal client machine.

Open /etc/sysconfig/SuSEfirewall2, and locate FW_FORWARD_MASQ (it's in 14.). Now, assuming your client's ip is 192.168.0.3, set this to this value:

FW_FORWARD_MASQ="0/0,192.168.0.3,tcp,4662 0/0,192.168.0.3,udp,4662 0/0,192.168.0.3,tcp,4672 0/0,192.168.0.3,udp,4672"

(Note that a rule like "0/0,192.168.0.3,tcp,4662" simply means that incoming tcp connections over port 4662 from any address (0/0) will be forwarded to your the machine 192.168.0.3, on the same port.)

For this to work, you have to have FW_ROUTE (5.) set to "yes" in the same file.

After making these changes, save the file and then start yast. Go to "Security and users" (or similar), and there choose "Firewall". Now simply go through all dialogs and finish them; at the end it will restart your firewall with these new rules. Watch out; depending on your config you can lock yourself out of your (remote) machine! To restart the firewall you can *probably* also do

  1. /sbin/SuSEfirewall2 stop; /sbin/SuSEfirewall2 start


Using SuSE Linux as a client machine

If you run SuSE on your client machine which runs a firewall itself, you need to do the following to allow the correct ports to come through: You basically need to allow tcp and udp ports 4662 and 4672 to be open.

Open /etc/sysconfig/SuSEfirewall2, and locate FW_SERVICES_EXT_TCP and FW_SERVICES_EXT_UDP. Now add to both of these the above ports: FW_SERVICES_EXT_TCP="4662 4672" FW_SERVICES_EXT_UDP="4662 4672" Note that you should keep ports that are already in there.

After making these changes, you can restart the SuSEfirewall2 (thanks g-maverick) by running:

/sbin/SuSEfirewall2 stop && /sbin/SuSEfirewall2 start

but be aware that if you are connected to the router remotely, if something failed during this process, this could terminate your connection and so, leave the router in an accessible way.