Ted
asked on
CentOS 6.0 networking
I am having trouble with intial network (ifconfig and route) settings on my new server, doing it three different ways to no avail. I have set the interface (ifconfig...) and the default routing (route add...), as well as use the 'setup' utility, as well as manually editing the /etc/sysconfig/network-scr ipts/ifcfg -eth0 (and route-eth0) files. While I have been able to ping the default gateway, I can't get past it. I know that default gatework works because other devices on the net have been successful. If I try to ping past the default I get something similar to a "route unreachable" error message.
Furthermore I can't save the configuration when I try to do it thru the setup utility or when I do a /etc/inid.d/network save and restart. Even when I see the /etc/sysconfig/network-scr ipts/ifcfg -eth0 and the /etc/sysconfig/network-scr ipts/route -eth0 have the correct parameters...(I think)
What am I missing?
Furthermore I can't save the configuration when I try to do it thru the setup utility or when I do a /etc/inid.d/network save and restart. Even when I see the /etc/sysconfig/network-scr
What am I missing?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
See enclosure for all outputs. It finally worked only AFTER I manually updated these last two files: /etc/sysconfig/network and
/etc/sysconfig/network-scr ipts/ifcfg -eth0
And the /etc/sysconfig/network-scr ipts/route -eth0 edit that I manually created, I'm not sure I did that right, nor am I sure that I need to have a default route in that file.
Does seem right? It shouldn't have happened that way. But for now, the networking works...
CentOS-config.txt
/etc/sysconfig/network-scr
And the /etc/sysconfig/network-scr
Does seem right? It shouldn't have happened that way. But for now, the networking works...
CentOS-config.txt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That seems right. The route-eth0 file was there only because I manually created it in the first place. The last CentOS box I worked with was 5.7, and I don't know how different 6.0 is from 5.7. I think my recollection with 5.7 was that somehow the route-eth0 file was created thru some utility I was working with. Also, I don't think I had an /etc/network file.
My next task is to install squid and turn this box into a proxy for local users. So far I have only done a "yum install squid". It was successful, now I am looking to configure and activate it.
My next task is to install squid and turn this box into a proxy for local users. So far I have only done a "yum install squid". It was successful, now I am looking to configure and activate it.
have fun.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow, I am afraid that is a new one to me. I didn't realize SELinux was already part of my distribution - I thought that was different beast altogether and I would'vd had to have that implemented separately.
I am looking this up as I write this...
(lots of "haves" in that sentence, huh)
I am looking this up as I write this...
(lots of "haves" in that sentence, huh)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
All-
Enclosed are the outputs you asked for in the last two posts. I didn't change anything. Anything catch your eye?
CentOS-config-2-.txt
Enclosed are the outputs you asked for in the last two posts. I didn't change anything. Anything catch your eye?
CentOS-config-2-.txt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've attached another file with more outputs at your request.
For the network configuration it was a combination of trying to use the configuration tool setup and making manual entries. For the route-eth0 file I created it and configured it manually -not sure if I needed it.
CentOS-config-3-.txt
For the network configuration it was a combination of trying to use the configuration tool setup and making manual entries. For the route-eth0 file I created it and configured it manually -not sure if I needed it.
CentOS-config-3-.txt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Do I really need the NetworkManager script?
Since I only have remote access today I don't want to reboot the system. Last time I did that I couldn't get back in. Apparantly not all the network config survived the reboot at that time. It may have improved now with the latest changes that I made, but I don't want to take that chance until I am in front of the machine. I haven't reboot the box since my lastest changes seemed to have improve things.
Since I only have remote access today I don't want to reboot the system. Last time I did that I couldn't get back in. Apparantly not all the network config survived the reboot at that time. It may have improved now with the latest changes that I made, but I don't want to take that chance until I am in front of the machine. I haven't reboot the box since my lastest changes seemed to have improve things.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Very interesting find. That looks similar, though not exact, to my situation. Maybe I should re-install using the "simple" server text only settings. My initial installation was "web server" setting (because I was hoping it would give me a GUI interface for intial configuration but it turns out it didn't give me that anyway). Thoughts?
I'm not going to try any changes now anyway because at the moment I only have remote access. I still haven't reboot the server yet because of the reasons I said before. And I don't know why NetworkManager wasn't installed the first time. For now, the server is reachable from the internet. And I still haven't started my squid proxy configuration yet, which was the reason for installing this server in the first place...
I'm not going to try any changes now anyway because at the moment I only have remote access. I still haven't reboot the server yet because of the reasons I said before. And I don't know why NetworkManager wasn't installed the first time. For now, the server is reachable from the internet. And I still haven't started my squid proxy configuration yet, which was the reason for installing this server in the first place...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to all. It seems to be surviving the reboots. And I have NM_Control=yes in my ifcfg-eth0 file.
ASKER
Thanks again to all.
ASKER
I don't think it is choosing the gateway for outgoing. If I remember correctly, traceroute was giving me the error message immediately just like ping was.
I can ping the gateway successfully so connectivity is there.
I'll post some details when I try it again in the next hour or so....