On Sunday 16 December 2001 06:12, Bruce Marshall wrote:

On Sunday 16 December 2001 0:06 am, Bret Waldow wrote:

...

Hello all,

I am trying to get a desktop system to act as the router for a laptop. I seem to have DHCPD running - it assigns an IP to the laptop when it all comes up.

The setup is:

Cable modem (works fine) Desktop running DHCP gets assigned an IP from the cable modem on boot (works fine) Laptop connected to the desktop gets assigned an IP via the second ethernet card in the desktop. <snip>

Don't have this working but you need to use IP-Masquerading.... which usually means you must run one of the SuSE firewalls on your main machine and specify in the firewall setup that you want to masquerade. <snip>

you don't need a firewall, just issue this command (if it works, put it in a boot-skript): ipchains -I forward -j MASQ -s 192.168.0.0/24 -d 0/0 and use your local subnet instead of 192.168.0. that should turn on forwarding and masquerading... then you need to specify the desktop as the gateway of the laptop... now you should be all set... Johannes -- SuSE 7.3 - Linux 2.4.10-4GB - KDE 2.2.1 - KMail 1.3.1

On Sunday 16 December 2001 13:45, Anders Johansson wrote:

On Sunday 16 December 2001 20.37, Johannes Liedtke wrote:

...

you don't need a firewall, just issue this command (if it works, put it in a boot-skript):

ipchains -I forward -j MASQ -s 192.168.0.0/24 -d 0/0

echo "1" > /proc/sys/net/ipv4/ip_forward

is probably needed too. It's turned off by default.

yes, it is... sorry, I forgot... Johannes -- SuSE 7.3 - Linux 2.4.10-4GB - KDE 2.2.1 - KMail 1.3.1

On Monday 17 December 2001 00:43, Bret Waldow wrote:

Johannes Liedtke wrote:

...

you don't need a firewall, just issue this command (if it works, put it in a boot-skript):

ipchains -I forward -j MASQ -s 192.168.0.0/24 -d 0/0

and use your local subnet instead of 192.168.0.

Thanks for the suggestion. I'm afraid it doesn't work, as the 7.3 default kernel doesn't allow ipchains. Running the command gives the error: "ipchains:Protocol not available."

Your tagline suggests you are running 7.3 - are you doing something like this?

Actually not... I'm using it on a server machine (sounds good describing a P90, huh? :) ) running SuSE 7.0... If 7.3 doesn't support ipchains, what does SuSE "officially" suggest as a replacement? Is there still a quick&dirty hack or do we need to install a firewall now? Actually, one should run a firewall anyway, but I didn't have the time to get into that yet... Johannes -- Powered by SuSE 7.3 - KDE 2.2.1 - KMail 1.3.1 Version Info: Linux 2.4.10-4GB

-----BEGIN PGP SIGNED MESSAGE----- Not sure about SuSE 7.3 but if its using the 2.4.x kernel you need to use IPTables in /etc/rc.d/boot.local you should be able to add at the end of it.... You may not need to insmod ip_tables so you can remove that if it errors out All the rest should be working, I know it works on a 192.168.1.x subnet. Replace eth0 with your outside interface, the NIC or modem connected to the outside wall. I think I got everything... # Start iptables routing insmod ip_tables insmod ip_conntrack insmod ip_conntrack_ftp insmod ip_conntrack_irc modprobe iptable_nat iptables -N block iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A block -m state --state NEW -I ! eth0 -j ACCEPT iptables -A block -m state -j DROP iptables -A INPUT -j block iptables -A FORWARD -j block iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # End IPTables Routing ~Phantasm http://www.textbox.net ********************************************************************** This post is encrypted in the "english language method", any attempt to decipher meaning from these symbols is a violation of the DMCA. This includes, but is not limited to: interpreting the symbols through use of biological, visual decryption devices, translating the symbols into another language encryption scheme, and digital processing the symbols into a form conducive to oral intrepretation. Thank you for your time. ********************************************************************** -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBPB29Vrzz1EMmEs4tAQF+8wf/RBHFpZcRkXK5j7G4ivutxnGc2KAsvtPK WbFlQRNUZEg8rbDBMNU99YS1taGn03kw2RlxUszt8DuOxuG9Xd0hpUFpPsUlshjV r0AhBjsaXxBokrwtkWoKpak2PsG/j03SolBlMzT8pX2zizRgDB/Vnvt9f0e1vNBI QHWB5oxOHSKTXdI4FB+QKnU5gnLSIkATiArSODt1Y0tHOutyomVurwsHDb4+vk8g qhQQStEICi/CCeIPZpK0Mk9Xve5BhXPHvZBeWHkZxFnTrOnhmG3Db3apSGNOiksb fibTI+jE2FRM9EI55wSdVmiM1waGi4reMAOvHW5gvSJWwfsRUm4g+A== =CK8d -----END PGP SIGNATURE-----