Sorry for the late reply. First of all, you must have two ethernet cards. One for your firewall and one for your network. eth0 is to the internet and eth1 is to your network. If you have a direct connection to the net as I did, whether DHCP or a static IP from your ISP, eth0 should be already configured. You only need to: route add -net 192.168.1.0 gw 192.168.1.1 ..where 192.168.1.1 is the IP you assigned to your second ethernet card in your server. Set each Win95 client in your home/business to 192.168.1.x where X is greater than 1 and less than 255. Set the gateway of each client to 192.168.1.1. Also set your DNS in your Win95 clients to all the IP's found in your /etc/resolv.conf The reason my IP's where getting messed up was because my dumb ISP was using a DHCP server that didn't follow the RFC spec and was timing out every 30 minutes. When it came to releasing my IP, it couldn't give it back to me and was sending rubbage on the wire. Now that I have a static IP, all is well. Last but not least, you MUST call: /sbin/ipfwadm -F -p masquerade Why? I don't know. It's just required and it WORKS! Good luck! Lester On Tue, 30 Mar 1999, Jack Chu wrote:

Hey there Lester,

I intend to do the same thing, but i also am running into the same problems as you. I can not ping my gateway with my Win95 Machine. Plus my route tables get messed up also. If you get an answer could you e-mail me with your solution also. Thanks

Jack

On Fri, 26 Mar 1999 23:05:19 -0800 (PST), ljackson@techlinks.com wrote:

...

...after recompiling my kernel with IP Forwarding and Masquerading support. I can only ping my SuSE Linux gateway (i.e. eth1 with 192.168.1.1) from any Win95 clients on my local network. Given the output from the link to my dmesg/ifconfig/route results web page posted at:

<A HREF="http://www.techlinks.com/helpme.txt"><A HREF="http://www.techlinks.com/helpme.txt</A">http://www.techlinks.com/helpme.txt</A</A>>

...is there anything obvious that would suggest what the problem may be? I'm simply trying to configure my Linux box with two network cards...1 to connect to my ADSL router and the other to connect to my internal network (i.e. 192.168.1.0).

Thanks

Lester

NOTE: If this is not an appropriate place to post this message, please say so. I felt this border lined support/forum material. I'm merely looking for other SuSE users who may have experienced this. Thanks

again.

...

-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>

_______________________________________________________ Get your free, private email at <A HREF="http://mail.excite.com/"><A HREF="http://mail.excite.com/</A">http://mail.excite.com/</A</A>>

-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>