Not sure If I want to dive to deep into this. But I think it would be better if... DSL - 192.168.0.1/24 North NIC - 192.168.0.1/24 Default Gateway 192.168.0.1 South NIC - 192.168.1.1/24 (Internal LAN where Firewall routes traffic from North to South interfaces n visa versa) Internal IPs 192.168.1.2-254/24 On Tue, 1 Mar 2005 18:29:20 -0500, Jeffrey Laramie <suse-linux-e@trans-star.net> wrote:

On Tuesday 01 March 2005 18:22, Your Name wrote:

...

I just got DSL today. The modem is working from the server with only minor annoyances. However, I can't seem to access the internet from other linux (9.0) I'm suspecting some kind of a routing/gateway problem.

I had to change the IP for my server box to 192.168.0.2 from 192.168.0.1 because the modem wants to be 192.168.0.1.

I added a 2nd NIC as 192.168.0.3.

I've setup the gateway on all my boxes as 192.168.0.2

I can ping everything on my internal network, but everything outside gets errors (unable to find host)

Any clues??

Did you configure NAT on the box that serves as the gateway?

Jeff

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

On Tuesday 01 March 2005 18:51, Ian Philpot wrote:

Not sure If I want to dive to deep into this. But I think it would be better if...

DSL - 192.168.0.1/24 North NIC - 192.168.0.1/24 Default Gateway 192.168.0.1 South NIC - 192.168.1.1/24 (Internal LAN where Firewall routes traffic from North to South interfaces n visa versa)

Internal IPs 192.168.1.2-254/24

Good point; I didn't notice that. He should have each NIC on a different subnet. Jeff

James Knott wrote:

Try pinging outside your network, using the IP address, instead of host name.

That didn't work either, but I tried a silly experiment. I switched the setups for eth0 and eth1. That worked. I think that the DSL interface has to be loaded first, and the boot load order is by alphabetic order. Thanks, Jim