Karol Pietrzak wrote:
I want to set up a very simple gateway with no (at least not yet) firewalling capability. Just a simply gateway... I'm just got sure how to set it up. eth1: IP determined via dhcp; gateway to Internet 10.1.0.1 eth0: static IP [ 192.168.22.1 ] for internal network
If eth1 is configured via dhcp, dhcp will configure the gateway, IP, netmask, etc. You don't need to put anything in /etc/route.conf
Currently three Windows 95 machines are connected via a hub to eth0 (IP addresses of the three machines are 192.168.22.[2-5]). 192.168.22.1 is set up as the gateway and DNS as 10.1.0.1 (this is how it's supposed to be).
This network should be in /etc/route.conf (as well as local). If you configured your NIC with Yast, I suspect your /etc/route.conf is already configured properly.
How would the /etc/route.conf on the Linux gateway look like (I already turned on IP forwarding) to allow it to forward the IP packets from the three WIndows 95 machines to 10.1.0.1?
I have 2 networks working like this, and the internal and local (i.e. 127.0.0.0) are the only ones in route.conf. DHCP configures your outgoing interface (including nameserver). ie. 127.0.0.0 0.0.0.0 255.0.0.0 lo 192.168.22.0 0.0.0.0 255.255.255.0 eth0 (BTW, 192.168.x.x is usually a class C network, unless I'm mistaken, which should be 255.255.255.0 netmask)
Would I need to configure IPchains / IPtables are well?
As far as I know, for your internal network to be able to route packets to the internet will need to be masqueraded by your gateway. I would highly recommend setting up SuSEfirewall (or 2, depending on your kernel) via /etc/rc.config.d/firewall.rc.config, which has an excellent intro and comments to get you going. HTH. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris "All I have seen teaches me to trust the Creator for all I have not seen." --Ralph Waldo Emerson