Ping Works, but not firefox

[WhiteFeather]

Hi all, I have a server with a public facing IP.

When I tried to configure that static IP info on eth0, the subnet mask keeps getting changed to the ROUTER'S address when I save and exit.

ie, I type in
ip: 213.230.211.123 (not the real one)
mask : 255.255.255.248
gateway : 213.230.211.230 (not the real one)

But every time I save and come back to the screen later, the subnet mask is set to the gateway's number!!!!
ip: 213.230.211.123
mask : 213.230.211.230
gateway : 213.230.211.230

Finally I gave up trying to figure out why and thought to let it get a DHCP address for a minute so I could at least get out on the web to look the problem up. but that's not working either:
Although ping will successfully resolve an address
(ping google.com works, eg), no other program will, such as firefox. Why? domain names don't appeat to be resolving for any other apps.

I can't remember how to set the subnet mask with ifconfig, so no I haven't tried that.


Any idea what I should try?

Thanks for your time!

Tony

[marko]

Have you updated your system?, that's a known problem that was corrected I think

I can't remember how to set the subnet mask with ifconfig, so no I haven't tried that.

ifconfig eth0 IPADDR netmask NETMASK
route add default gw GATEWAYADDR

[shess01]

Have not had this issue myself but from reading the forums this could be your problem

The quick way to check is try disabling NetworkMager with:

service NetworkManager stop

Then try to setting your static IP and see what you get. If it works you can turn NM off altogether in the system-config-services gui.

[WhiteFeather]

Originally Posted by marko

Have you updated your system?, that's a known problem that was corrected I think

ifconfig eth0 IPADDR netmask NETMASK
route add default gw GATEWAYADDR

Thanks, that ifconfig worked well. The Network Configuration panel still shows the wrong information, but ifconfig now reports the correct info and I appear to have a static ip.

Updating now.

Thanks again!

[marko]

Try the Network Config panel after the update is done to see if it's corrected.