I'm just starting to test CentOS 6 in our environment, and as a first step did a basic install from DVD (Desktop target, all defaults). Next I will try to automate the installations as I did for CentOS 5 using the anakonda-ks.cfg file generated by the manual install.
However, I can't wrap my brain around the new NetworkManager to get it to configure the eth0 interface to obtain an IP address from our DHCP server. I've seen the FAQ on the wiki and the interface is up, but it doesn't get an IP address. I've done the installation from DVD multiple times now, each time with the same result. What am i missing?
Alfred
On Tue, Aug 16, 2011 at 4:57 PM, Alfred von Campe alfred@von-campe.com wrote:
I'm just starting to test CentOS 6 in our environment, and as a first step did a basic install from DVD (Desktop target, all defaults). Next I will try to automate the installations as I did for CentOS 5 using the anakonda-ks.cfg file generated by the manual install.
However, I can't wrap my brain around the new NetworkManager to get it to configure the eth0 interface to obtain an IP address from our DHCP server. I've seen the FAQ on the wiki and the interface is up, but it doesn't get an IP address. I've done the installation from DVD multiple times now, each time with the same result.
If you mean during the install, add "--activate" to your kickstart file's "network ..." line.
If you mean after the install, what's the output of "chkconfig --list NetworkManager", "chkconfig --list network", and your NIC's ifcfg-X?
On Aug 16, 2011, at 18:37, Tom H wrote:
If you mean during the install, add "--activate" to your kickstart file's "network ..." line.
That's good to know for the near future when I will be tweaking my existing kickstart files.
If you mean after the install, what's the output of "chkconfig --list NetworkManager", "chkconfig --list network", and your NIC's ifcfg-X?
I will check and post this information when I am back in the office tomorrow.
Alfred
On Aug 16, 2011, at 18:37, Tom H wrote:
If you mean after the install, what's the output of "chkconfig --list NetworkManager", "chkconfig --list network", and your NIC's ifcfg-X?
I ended up re-installing the system from DVD this morning (don't have my kickstart server set up yet), and this time I noticed a "Configure Network" button in one of the screens. It was there that I enabled a setting to start the network on boot, and now it's working "out of the box". I can't stop to wonder why upstream decided to make this optional. Who doesn't want their network up, especially because it's not obvious how to start it once you are logged in?
But the story doesn't stop there. When I enabled the network during the installation, the connection name was "System eth0". When I logged in (as root, because this is just a test system and I hadn't configured local or network accounts yet), the network was running but using a connection named "Wired connection 1" and I had two ifcfg-X files:
# cat network-scripts/ifcfg-eth0 DEVICE=eth0 HWADDR=bc:30:5b:e7:a7:1c NM_CONTROLLED=yes ONBOOT=no BOOTPROTO=dhcp TYPE=Ethernet USERCTL=no PEERDNS=yes IPV6INIT=no
#cat network-scripts/ifcfg-Wired_connection_1 HWADDR=BC:30:5B:E7:A7:1C TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="Wired connection 1" UUID=44c68048-52ba-4e5e-807f-adf8a881552f ONBOOT=yes LAST_CONNECT=1313586374
Why on earth would NM create another config file for the same interface? Also, how do I tell NM to include the DHCP_HOSTNAME variable in the config file so that my DHCP server creates a DNS entry?
I think I don't like the NM "overhead" in CentOS 6. Is it just a matter of doing a "chkconfig --del NetworkManager" to get rid off it?
I'll be working on getting the CentOS 6 installation automated via kickstart later this week and hope to resolve all these issues before then.
Thanks for all the help/pointers, Alfred
Alfred, I would not delete network manager, it would be better if you stop it "service NetworkManager stop" and disable from booting "chkconfig NetworkManager off"....it can turn a useful tool for troubleshooting in the future. In a second note about the multi-NIC, i would focus in the actual card that have the connections....here at work we have system with 8 NIC for redundant links, but my main focus is in the actual ports that have connectivity. Take a look at /etc/sysconfig/network-scripts.....focus in the ifcfg-ethx that is actually working in your box. Don't forget that you can always use system-config-network-tui as an alternative to using the GUI, as long as you have it install "yum install system-config-network-tui -y".....I think you are in the right path, let us know how it turn out. In reference to the host name, take a look at the file /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg_ethx to assign host name information....I hope I didn't confuse you more....the Redhat documentation is rocksolid, take a glance at it. Best of luck to you.
Alfred von Campe alfred@von-campe.com 8/17/2011 9:50 AM >>>
On Aug 16, 2011, at 18:37, Tom H wrote:
If you mean after the install, what's the output of "chkconfig --list NetworkManager", "chkconfig --list network", and your NIC's ifcfg-X?
I ended up re-installing the system from DVD this morning (don't have my kickstart server set up yet), and this time I noticed a "Configure Network" button in one of the screens. It was there that I enabled a setting to start the network on boot, and now it's working "out of the box". I can't stop to wonder why upstream decided to make this optional. Who doesn't want their network up, especially because it's not obvious how to start it once you are logged in?
But the story doesn't stop there. When I enabled the network during the installation, the connection name was "System eth0". When I logged in (as root, because this is just a test system and I hadn't configured local or network accounts yet), the network was running but using a connection named "Wired connection 1" and I had two ifcfg-X files:
# cat network-scripts/ifcfg-eth0 DEVICE=eth0 HWADDR=bc:30:5b:e7:a7:1c NM_CONTROLLED=yes ONBOOT=no BOOTPROTO=dhcp TYPE=Ethernet USERCTL=no PEERDNS=yes IPV6INIT=no
#cat network-scripts/ifcfg-Wired_connection_1 HWADDR=BC:30:5B:E7:A7:1C TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="Wired connection 1" UUID=44c68048-52ba-4e5e-807f-adf8a881552f ONBOOT=yes LAST_CONNECT=1313586374
Why on earth would NM create another config file for the same interface? Also, how do I tell NM to include the DHCP_HOSTNAME variable in the config file so that my DHCP server creates a DNS entry?
I think I don't like the NM "overhead" in CentOS 6. Is it just a matter of doing a "chkconfig --del NetworkManager" to get rid off it?
I'll be working on getting the CentOS 6 installation automated via kickstart later this week and hope to resolve all these issues before then.
Thanks for all the help/pointers, Alfred
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Aug 17, 2011, at 9:58, Lisandro Grullon wrote:
In a second note about the multi-NIC, i would focus in the actual card that have the connections
That's my point, I only have one NIC (it's a desktop system) yet NM created two config files, one with ONBOOT=no and the other with ONBOOT=yes. I reinstalled the system yet again, and this time there was only one. I don't really like how NM affects the system; I think I'll disable it and edit the ifcfg file by hand (well, with a script).
Alfred
From: Alfred von Campe alfred@von-campe.com
I don't really like how NM affects the system; I think I'll disable it.
+1 Must be helpful for end users connecting to multiple networks,
but I really prefer static configurations for servers.
JD
On Aug 17, 2011, at 10:58 AM, Alfred von Campe alfred@von-campe.com wrote:
On Aug 17, 2011, at 9:58, Lisandro Grullon wrote:
In a second note about the multi-NIC, i would focus in the actual card that have the connections
That's my point, I only have one NIC (it's a desktop system) yet NM created two config files, one with ONBOOT=no and the other with ONBOOT=yes. I reinstalled the system yet again, and this time there was only one. I don't really like how NM affects the system; I think I'll disable it and edit the ifcfg file by hand (well, with a script).
The ifcfg-eth0 is for when NM is disabled and ONBOOT should then be set to yes for this and no for the ifcfg-Wired_Connection_1 an this should be set by NM when you tell it not to manage this interface.
There is another option I believe, something like NM_CONTROLLED=no, which if present in ifcfg causes NM to not attempt to control the device. For servers this should be present.
I agree though that NM not automatically enabling all interfaces under it's control should be filed as a bug.
-Ross
Is there a technical reason...like the system won't network at all.. as to not removing network manager?
On 8/17/2011 9:58 AM, Lisandro Grullon wrote:
Alfred, I would not delete network manager, it would be better if you stop it "service NetworkManager stop" and disable from booting "chkconfig NetworkManager off"....it can turn a useful tool for troubleshooting in the future. In a second note about the multi-NIC, i would focus in the actual card that have the connections....here at work we have system with 8 NIC for redundant links, but my main focus is in the actual ports that have connectivity. Take a look at /etc/sysconfig/network-scripts.....focus in the ifcfg-ethx that is actually working in your box. Don't forget that you can always use system-config-network-tui as an alternative to using the GUI, as long as you have it install "yum install system-config-network-tui -y".....I think you are in the right path, let us know how it turn out. In reference to the host name, take a look at the file /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg_ethx to assign host name information....I hope I didn't confuse you more....the Redhat documentation is rocksolid, take a glance at it. Best of luck to you.
On Aug 18, 2011, at 9:16 PM, William Warren hescominsoon@emmanuelcomputerconsulting.com wrote:
On 8/17/2011 9:58 AM, Lisandro Grullon wrote:
Alfred, I would not delete network manager, it would be better if you stop it "service NetworkManager stop" and disable from booting "chkconfig NetworkManager off"....it can turn a useful tool for troubleshooting in the future. In a second note about the multi-NIC, i would focus in the actual card that have the connections....here at work we have system with 8 NIC for redundant links, but my main focus is in the actual ports that have connectivity. Take a look at /etc/sysconfig/network-scripts.....focus in the ifcfg-ethx that is actually working in your box. Don't forget that you can always use system-config-network-tui as an alternative to using the GUI, as long as you have it install "yum install system-config-network-tui -y".....I think you are in the right path, let us know how it turn out. In reference to the host name, take a look at the file /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg_ethx to assign host name information....I hope I didn't confuse you more....the Redhat documentation is rocksolid, take a glance at it. Best of luck to you.
Is there a technical reason...like the system won't network at all.. as to not removing network manager?
I believe in C6 there are so many dependencies on NM removing it removes half the OS.
You can disable it though.
-Ross
From: Alfred von Campe alfred@von-campe.com
However, I can't wrap my brain around the new NetworkManager to get it to configure the eth0 interface to obtain an IP address from our DHCP server. I've seen the FAQ on the wiki and the interface is up, but it doesn't get an IP address. I've done the installation from DVD multiple times now, each time with the same result. What am i missing?
Unless I am mistaken (only tried one manual install some time ago), I kind of remember the need to check an "activate at boot" box in the network properties at setup time...
JD
-
Alfred von Campe -
Always Learning -
John Doe -
Lisandro Grullon -
Ross Walker -
Tom H -
William Warren