HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free and registered users see less advertising! If you just want to browse through the existing questions, just select the forum that you want to visit from the selection below. Otherwise, click here to register!. We highly recommend that you print a copy of our Guide for New Members. Enjoy!

"Network is unreachable" when pinging gateway through DHCP

Hi,

After installing Fedora7, I tried to connect to the gateway 192.168.0.1, but it failed with above message. But I can connect without problem from Windows XP.
Below is some information about the network interface in my laptop:

Above is an excerpt from the ifconfig command results you posted. You may notice above that now you are using an IPv4 address i.e 192.168.0.64 for eth0. It is on the same network as your gateway, i.e 192.168.0.1. Hence you are able to connect. To permanently resolve this take the following steps:

vi /etc/sysconfig/network-scripts/ifcfg-eth0

Make the following changes
BOOTPROTO=static
IPADDR=192.168.0.64

leave the rest of the file as it is and save the changes. Now everytime you boot your system it will have the IP 192.168.0.64 and unless no network changes are made you will be able to connect to your gateway at 192.168.0.1.

Closely looking at all the information you provided, it seems that previously your DHCP was not assiging a correct IP to your system. This time it did. So your current setting may work for you unless your DHCP do no pant out. You may not need to make the above changes I suggested. In case you face the previous problem again you may run the following command to resolve it temporarily:

ifconfig eth0 192.168.0.64(this IP address could be any other IP address too. Only thing you need to take care of is that it is on the same subnet as your gateway.)

Start to see the light

Originally Posted by explorer

Closely looking at all the information you provided, it seems that previously your DHCP was not assiging a correct IP to your system. This time it did. So your current setting may work for you unless your DHCP do no pant out. You may not need to make the above changes I suggested. In case you face the previous problem again you may run the following command to resolve it temporarily:

ifconfig eth0 192.168.0.64(this IP address could be any other IP address too. Only thing you need to take care of is that it is on the same subnet as your gateway.)

It seems that the difference lies on how it loads the ethernet driver.