Hi all,
I've a new CentOS 5 minimalist install; this will be the name server from my prior thread. I have configured eth0 during setup with the static IP the unit will have when in production. During this setup phase, selinux is set to permissive.
Setting up on a different network, I did this:
dhclient eth0 and successfully got a private address; I also validated that the resolv.conf file was created by the dhclient-script and it was, accurately pointing to my gateway and listing a domain name server by IP.
That's where the fun stops. Even pinging an IP, so as not to rely on name resolution, I get the dreaded 'Network is unreachable' error.
Any pointers would be more than appreciated.
Thanks in advance, ~Ray
centos@swhi.net wrote:
I've a new CentOS 5 minimalist install; this will be the name server from my prior thread. I have configured eth0 during setup with the static IP the unit will have when in production. During this setup phase, selinux is set to permissive.
Setting up on a different network, I did this:
dhclient eth0 and successfully got a private address; I also validated that the resolv.conf file was created by the dhclient-script and it was, accurately pointing to my gateway and listing a domain name server by IP.
That's where the fun stops. Even pinging an IP, so as not to rely on name resolution, I get the dreaded 'Network is unreachable' error.
Without DHCP in the picture you're not getting the needed default route set up. I'm not sure what you mean by "resolv.conf ... accurately pointing to my gateway." AFAIK, resolv.conf has nothing to do with routing gateways. If you're not going to be using DHCP, you need to run system-config-network, edit the entry for your network device, and, under the "Route" tab, enter an explicit default route and gateway address.
As a quick check before doing the above, just run
route add default gw nnn.nnn.nnn.nnn dev eth0
supplying the appropriate gateway address and device, of course.
Robert Nichols wrote:
centos@swhi.net wrote:
I've a new CentOS 5 minimalist install; this will be the name server from my prior thread. I have configured eth0 during setup with the static IP the unit will have when in production. During this setup phase, selinux is set to permissive.
Setting up on a different network, I did this:
dhclient eth0 and successfully got a private address; I also validated that the resolv.conf file was created by the dhclient-script and it was, accurately pointing to my gateway and listing a domain name server by IP.
That's where the fun stops. Even pinging an IP, so as not to rely on name resolution, I get the dreaded 'Network is unreachable' error.
<snip>
As a quick check before doing the above, just run
route add default gw nnn.nnn.nnn.nnn dev eth0supplying the appropriate gateway address and device, of course.
Robert,
Thank you. That did the trick.
It's clearly been a long day. I'd read earlier that even if I'd a static IP/NM, etc, setup, dhclient eth0 would temporarily let me use my private network, but taking the interface down and up would return to the static settings.
Never even dawned on me that it was a routing issue. yeah, it's been a long day
Thanks loads, ~R
On Fri August 3 2007 23:13, centos@swhi.net wrote:
I've a new CentOS 5 minimalist install; this will be the name server from my prior thread. I have configured eth0 during setup with the static IP the unit will have when in production. During this setup phase, selinux is set to permissive.
Setting up on a different network, I did this:
dhclient eth0 and successfully got a private address; I also validated that the resolv.conf file was created by the dhclient-script and it was, accurately pointing to my gateway and listing a domain name server by IP.
That's where the fun stops. Even pinging an IP, so as not to rely on name resolution, I get the dreaded 'Network is unreachable' error.
OK if everything is setup correctly then I would first look to see if the firewall, on that system, is blocking then check the routing to ensure it is properly setup.
-
centos＠swhi.net -
Robert Nichols -
Robert Spangler