CentOS-5.5 # uname -a Linux inet05.hamilton.harte-lyne.ca 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'?
Jan 13 08:25:31 inet05 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bridge0 ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: error: Unknown connection type 'Bridge' Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: read connection 'System eth0' Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: Ignoring connection 'System eth0' and its device because NM_CONTROLLED was false. Jan 13 08:25:32 inet05 gconfd (byrnejb-5832): Resolved address "xml:readwrite:/home/byrnejb/.gconf" to a writable configuration source at position 0 Jan 13 08:25:34 inet05 pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found Jan 13 08:25:35 inet05 nm-system-settings: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_1c_c0_d2_ef_82
My script files look like this:
#bridge0 DEVICE=bridge0 TYPE=Bridge BOOTPROTO=static IPADDR=216.185.71.25 NETMASK=255.255.255.0 GATEWAY=216.185.71.1 ONBOOT=yes
#eth0 DEVICE=eth0 ONBOOT=yes BRIDGE=bridge0 NM_CONTROLLED=no
On Thu, Jan 13, 2011 at 11:26 AM, James B. Byrne byrnejb@harte-lyne.ca wrote:
My script files look like this:
#bridge0 DEVICE=bridge0 TYPE=Bridge BOOTPROTO=static IPADDR=216.185.71.25 NETMASK=255.255.255.0 GATEWAY=216.185.71.1 ONBOOT=yes
#eth0 DEVICE=eth0 ONBOOT=yes BRIDGE=bridge0 NM_CONTROLLED=no
To start bridge0 should be br0
/etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BRIDGE=br0
/etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge
Ryan
On Thu, Jan 13, 2011 at 11:47 AM, Ryan Wagoner rswagoner@gmail.com wrote:
On Thu, Jan 13, 2011 at 11:26 AM, James B. Byrne byrnejb@harte-lyne.ca wrote: To start bridge0 should be br0
/etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BRIDGE=br0
/etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge
Ryan
My mistake I just realized it doesn't matter. I have always used br0. Sorry for the confusion.
Ryan
On 01/13/2011 08:26 AM, James B. Byrne wrote:
CentOS-5.5 # uname -a Linux inet05.hamilton.harte-lyne.ca 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'?
Jan 13 08:25:31 inet05 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bridge0 ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: error: Unknown connection type 'Bridge' Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: read connection 'System eth0' Jan 13 08:25:32 inet05 nm-system-settings: ifcfg-rh: Ignoring connection 'System eth0' and its device because NM_CONTROLLED was false. Jan 13 08:25:32 inet05 gconfd (byrnejb-5832): Resolved address "xml:readwrite:/home/byrnejb/.gconf" to a writable configuration source at position 0 Jan 13 08:25:34 inet05 pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found Jan 13 08:25:35 inet05 nm-system-settings: Adding default connection 'Auto eth0' for /org/freedesktop/Hal/devices/net_00_1c_c0_d2_ef_82
My script files look like this:
#bridge0 DEVICE=bridge0 TYPE=Bridge BOOTPROTO=static IPADDR=216.185.71.25 NETMASK=255.255.255.0 GATEWAY=216.185.71.1 ONBOOT=yes
#eth0 DEVICE=eth0 ONBOOT=yes BRIDGE=bridge0 NM_CONTROLLED=no
I saw something similar and it turned out the bridge-utils package was not installed.
I get the same errors, but my bridges still work. I keep NetworkManager disabled, but nm-system-settings still parses the files.
About the only difference is, I don't assign an ip addresses to the bridge, as my VM clients only use it to access the lan to obtain their own ip addresses.
Is something not working?
On 01/13/2011 08:26 AM, James B. Byrne wrote:
Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'?
I don't believe NetworkManager supports bridges. If you want to use TYPE=Bridge, you should disable NetworkManager and use the classic "network" service instead.
On Mon, Jan 17, 2011 at 1:49 PM, Gordon Messmer yinyang@eburg.com wrote:
On 01/13/2011 08:26 AM, James B. Byrne wrote:
Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'?
I don't believe NetworkManager supports bridges. If you want to use TYPE=Bridge, you should disable NetworkManager and use the classic "network" service instead.
NetworkManager is utterly useless for server grade work, such as pair bonding and bridges. It may be helpful for wireless management or modem connections, but I find it safer to to rip it *out* on CentOS 4 and CentOS 5, and urge turning it off by whatever means are feasible for RHEL 6 or CentOS 6 when it comes out.
On 01/21/11 7:41 PM, Nico Kadel-Garcia wrote:
NetworkManager is utterly useless for server grade work, such as pair bonding and bridges. It may be helpful for wireless management or modem connections, but I find it safer to to rip it *out* on CentOS 4 and CentOS 5, and urge turning it off by whatever means are feasible for RHEL 6 or CentOS 6 when it comes out.
is there a good howto somewhere on how to manually setup wireless connections without NetworkManager ?
wifi requires a lot of juju to be setup just so.
On Fri, 21 Jan 2011 21:40:34 -0800 John R Pierce pierce@hogranch.com wrote:
is there a good howto somewhere on how to manually setup wireless connections without NetworkManager ?
wifi requires a lot of juju to be setup just so.
This works for me (actually on fedora-13, but centos-5 should be similar, maybe even the same) - it assumes you've got the driver installed - mine is ath5k and it comes up with device wlan0 in "ifconfig -a":
of course, edit this for your network:
/etc/sysconfig/network-scripts/ifcfg-wlan0:
# Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor DEVICE=wlan0 HWADDR=00:22:b0:70:ac:e3 ONBOOT=yes BOOTPROTO=none IPADDR=192.168.101.18 USERCTL=yes PEERDNS=yes IPV6INIT=no NM_CONTROLLED=no TYPE=Wireless ESSID=Baroona MODE=Managed RATE=auto SEARCH="oz.promptu.com" DOMAIN="oz.promptu.com" GATEWAY=192.168.101.1 DNS1=211.29.132.12 DNS2=198.142.0.51 SECURITYMODE=open NETMASK=255.255.255.0 NETWORK=192.168.101.0 BROADCAST=192.168.101.255 CHANNEL=
/etc/sysconfig/network-scripts/keys-wlan0: KEY=xxxxxxxxxx
/etc/sysconfig/network-scripts/route-wlan0:
# this is the 'old' format: just gets added to "ip route add " 192.168.101.0/24 dev wlan0 default via 192.168.101.1
Then just the usual: ifup wlan0
Cheers
Bob
On 01/21/2011 10:17 PM, Bob Hepple wrote:
/etc/sysconfig/network-scripts/route-wlan0:
# this is the 'old' format: just gets added to "ip route add " 192.168.101.0/24 dev wlan0 default via 192.168.101.1
Based on your other configs, this appears to be redundant. You only need the "route" file if you are adding routes other than the network which is local to your address and the default gateway.
On 01/21/2011 07:41 PM, Nico Kadel-Garcia wrote:
NetworkManager is utterly useless for server grade work, such as pair bonding and bridges. It may be helpful for wireless management or modem connections, but I find it safer to to rip it *out* on CentOS 4 and CentOS 5, and urge turning it off by whatever means are feasible for RHEL 6 or CentOS 6 when it comes out.
Turning it off on CentOS 6 and current versions of Fedora is accomplished by the same means it always has been:
chkconfig NetworkManager off chkconfig network on
On Sat, Jan 22, 2011 at 5:32 PM, Gordon Messmer yinyang@eburg.com wrote:
On 01/21/2011 07:41 PM, Nico Kadel-Garcia wrote:
NetworkManager is utterly useless for server grade work, such as pair bonding and bridges. It may be helpful for wireless management or modem connections, but I find it safer to to rip it *out* on CentOS 4 and CentOS 5, and urge turning it off by whatever means are feasible for RHEL 6 or CentOS 6 when it comes out.
Turning it off on CentOS 6 and current versions of Fedora is accomplished by the same means it always has been:
chkconfig NetworkManager off chkconfig network on
Unfortunately, this is not sufficiently reliable. Some idiot may re-run it, and from some bitter experience, I don't trust the system-config-network to behave well. NetworkManager is awkward to rip out of RHEL 6. (Not modular enough: too many tools that don't actually need it have RPM dependencies on it, so it winds up re-installed anyway.)
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it, but it seems to work in keeping NetworkManager's greedy little paws off my stable settings.
On 01/22/2011 08:28 PM, Nico Kadel-Garcia wrote:
Unfortunately, this is not sufficiently reliable. Some idiot may re-run it
Re-enabling NetworkManager requires the root password. If someone can turn it back on with 'chkconfig' or another service management tool, they can also re-install it.
You may feel that it is worth the effort to remove NetworkManager entirely, but I think most people will agree that there's no need to do so.
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it
File a bug with the "initscripts" component. That setting *should* be documented in /usr/share/doc/initscripts-*/sysconfig.txt, but isn't.
On Sat, Jan 22, 2011 at 21:05, Gordon Messmer yinyang@eburg.com wrote:
On 01/22/2011 08:28 PM, Nico Kadel-Garcia wrote:
Unfortunately, this is not sufficiently reliable. Some idiot may re-run it
Re-enabling NetworkManager requires the root password. If someone can turn it back on with 'chkconfig' or another service management tool, they can also re-install it.
You may feel that it is worth the effort to remove NetworkManager entirely, but I think most people will agree that there's no need to do so.
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it
File a bug with the "initscripts" component. That setting *should* be documented in /usr/share/doc/initscripts-*/sysconfig.txt, but isn't.
Minimize the number of people who have root password.
Those who need to perform actions that require root access should be given *norrow* permissions to do so via sudo.
Now make certain that all actions performed are logged and that such logs are audited.
Try to eliminate as much as possible any actions that require root access that are not or cannot be executed via sudo.
Train everyone who has root access and/or sudo access about what are approved actions (policies and procedures document).
HTH, Ken Wolcott
Still, it could get re-enabled with an update, RH loves to do this for some services.
Kai
On 01/23/2011 04:31 AM, Kai Schaetzl wrote:
Still, it could get re-enabled with an update, RH loves to do this for some services.
Having reviewed the scripts for all of the services on a server that runs many, I'm very confident that the reason you see that happen is that you are using "chkconfig --del <service>" rather than "chkconfig <service> off" to disable services. If you turn them off, they'll stay off. None of the post install scripts that I've found will enable a service; nearly all use "chkconfig --add" which will put a service in its default state *if* no state is currently configured.
Gordon Messmer wrote on Sun, 23 Jan 2011 14:56:51 -0800:
Having reviewed the scripts for all of the services on a server that runs many, I'm very confident that the reason you see that happen is that you are using "chkconfig --del <service>" rather than "chkconfig <service> off" to disable services.
I suspected that, thanks for confirmation. When I started seeing this happen back with 5.1 and 5.2 I stopped removing the services and just set them "off". I haven't done a scrutenizing effort to check if that really fixed the problem, but later it seemed to occur less often that unwanted services wanted to run.
Kai
On Sun, Jan 23, 2011 at 12:05 AM, Gordon Messmer yinyang@eburg.com wrote:
On 01/22/2011 08:28 PM, Nico Kadel-Garcia wrote:
Unfortunately, this is not sufficiently reliable. Some idiot may re-run it
Re-enabling NetworkManager requires the root password. If someone can turn it back on with 'chkconfig' or another service management tool, they can also re-install it.
I often have to hand off as-stable-as-possible systems to developers, and have done so in different professional roles. Turning it off at chkconfig is like taking the bullets out, but locking them in the same cabinet as the gun.
Ripping out NetworkManager (for RHEL 5/CentOS 5) is like taking away all the bullets. Putting in the NM_CONTROLLED="no" setting allows a bit more refinement: it can be disabled on a port by port basis.
You may feel that it is worth the effort to remove NetworkManager entirely, but I think most people will agree that there's no need to do so.
It's really painful for RHEL 6
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it
File a bug with the "initscripts" component. That setting *should* be documented in /usr/share/doc/initscripts-*/sysconfig.txt, but isn't.
Good point. Next week, with my service contracts in hand.
On 01/23/2011 06:20 AM, Nico Kadel-Garcia wrote:
On Sun, Jan 23, 2011 at 12:05 AM, Gordon Messmeryinyang@eburg.com wrote:
You may feel that it is worth the effort to remove NetworkManager entirely, but I think most people will agree that there's no need to do so.
It's really painful for RHEL 6
Assuming you mean that removing it is the painful part, I would say that is a considerable part of the reason that most people would agree there's no need to do so.
On Sat, Jan 22, 2011 at 11:28 PM, Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sat, Jan 22, 2011 at 5:32 PM, Gordon Messmer yinyang@eburg.com wrote:
On 01/21/2011 07:41 PM, Nico Kadel-Garcia wrote:
NetworkManager is utterly useless for server grade work, such as pair bonding and bridges. It may be helpful for wireless management or modem connections, but I find it safer to to rip it *out* on CentOS 4 and CentOS 5, and urge turning it off by whatever means are feasible for RHEL 6 or CentOS 6 when it comes out.
Turning it off on CentOS 6 and current versions of Fedora is accomplished by the same means it always has been:
chkconfig NetworkManager off chkconfig network on
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it, but it seems to work in keeping NetworkManager's greedy little paws off my stable settings.
In both the RH and FP docs, the only reference that I've found is in this section: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiza...
RHEL 5 has a similar section so it's not a new setting, just a not-well-documented one (like a DNS or DHCP one that you referred to recently).
On Sun, Jan 23, 2011 at 2:46 AM, Tom H tomh0665@gmail.com wrote:
On Sat, Jan 22, 2011 at 11:28 PM, Nico Kadel-Garcia nkadel@gmail.com wrote:
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it, but it seems to work in keeping NetworkManager's greedy little paws off my stable settings.
In both the RH and FP docs, the only reference that I've found is in this section: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiza...
Yeah, "libvirt" is not your friend for network configurations, nor is the "bridged" network setup used for KVM. It's not well supported, especially in the documentation.
RHEL 5 has a similar section so it's not a new setting, just a not-well-documented one (like a DNS or DHCP one that you referred to recently).
libvirt is also not your friend for correct documentation. This *will not work* for RHEL 5 or CentOS 5, because there is nothing in the actual /etc/sysconfig/network-scripts to support it. You have to disable NetworkManager with chkconfig or rip it out, which is actually safer.
On 01/23/2011 06:30 AM, Nico Kadel-Garcia wrote:
Yeah, "libvirt" is not your friend for network configurations, nor is the "bridged" network setup used for KVM. It's not well supported, especially in the documentation.
It's very well supported and documented. The URL in the message to which you replied contains complete documentation on setting up bridged networking for KVM.
libvirt is also not your friend for correct documentation. This *will not work* for RHEL 5 or CentOS 5, because there is nothing in the actual /etc/sysconfig/network-scripts to support it. You have to disable NetworkManager with chkconfig or rip it out, which is actually safer.
There is nothing that initscripts *needs* to do to support it. The setting only tells NetworkManager not to manage the interface.
On Sun, Jan 23, 2011 at 9:30 AM, Nico Kadel-Garcia nkadel@gmail.com wrote:
On Sun, Jan 23, 2011 at 2:46 AM, Tom H tomh0665@gmail.com wrote:
On Sat, Jan 22, 2011 at 11:28 PM, Nico Kadel-Garcia nkadel@gmail.com wrote:
The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is the setting NM_CONTROLLED="no" in the /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in RHEL 6, and I'm having difficulty finding documentation for it, but it seems to work in keeping NetworkManager's greedy little paws off my stable settings.
In both the RH and FP docs, the only reference that I've found is in this section: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiza...
Yeah, "libvirt" is not your friend for network configurations, nor is the "bridged" network setup used for KVM. It's not well supported, especially in the documentation.
RHEL 5 has a similar section so it's not a new setting, just a not-well-documented one (like a DNS or DHCP one that you referred to recently).
libvirt is also not your friend for correct documentation. This *will not work* for RHEL 5 or CentOS 5, because there is nothing in the actual /etc/sysconfig/network-scripts to support it. You have to disable NetworkManager with chkconfig or rip it out, which is actually safer.
I was just pointing out the only section of RH documentation where NM_CONTROLLED is mentioned. :)
-
Bob Hepple -
compdoc -
Emmett Culley -
Gordon Messmer -
James B. Byrne -
John R Pierce -
Kai Schaetzl -
Kenneth Wolcott -
Nico Kadel-Garcia -
Ryan Wagoner -
Tom H