*nix Sees Router, Router Sees Internet, Browsers Don't See Interne

We pulled the DHCP address from the ISP THROUGH the router. So it sees everything it's just not accessing the internet in any of the browsers. We've also removed the router (though it seemed pointless) and after resetting the modem's power still received the same results: it recognizes everything but it just does not access the web!

What do you mean by saying it recognizes everything? Can you ping external sites or ip addresses? Can you do DNS resolution?

Also, out of curiosity, why are you using a router if you're just passing straight through to the system? I assume from your description you've got internet -> router -> modem -> computer ? You're not using the router for handling the modem and managing internal connections ?

Cheers,
KV

Modem --> Router --> LAN --> Linux

The system is pulling the ISP information. I'm able to access the router's firmware via 192.168...etc. The router shows that it has an internet connection. I can't ping anything and we tried browsing Google via it's IP address and pinging it's IP address as well of course.

So it seems the path between the modem and Linux is there but something in the network settings (wherever THOSE are) is only letting me access the router's firmware.

Thanks for replying!

Ok, so to clarify, the router is pulling the IP address from your ISP, and your system is receiving a leased DHCP address from your router, since you can access the router on a private subnet? If your system was pulling the IP address directly from the modem, you wouldn't be able to access your router on a private subnet, and the router wouldn't recognize an active internet connection.

Does your router's web interface include any tools for things like pinging external sites? You could try that just to verify there is no issue between the router and the internet.

Without knowing more, I'm guessing that Suse hasn't configured a default gateway, that's often the problem when you can reach the router but not the internet.

Check your routing table (command route from CLI), it should look something like this:

Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.252.0 * 255.255.255.0 U 0 0 0 wlan0
loopback * 255.0.0.0 U 0 0 0 lo
default my.firewall 0.0.0.0 UG 0 0 0 wlan0

In my case, my.firewall (my router/firewall, or ip address 192.168.252.1) is my default gateway out. If I didn't have that default listed, I wouldn't be able to access anything off of my own subnet 192.168.252.x.

The default gateway should be configured as part of your dhcp lease, unless you've made manual changes to the network config. On the other hand, this problem has cropped up before where it just doesn't get created. You can always force a default gateway in your Yast network config, in your case you would set it to be 192.168.x.1 (the ip address for your router).

If you do have a default gateway set, then there's a whole seperate issue going on and we'll have to dig into a couple of different things.

Hope this helps...

Cheers,
KV