Bug 465847
| Summary: | NetworkManager does not respect NM_CONTROLLED=no | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gilboa Davara <gilboad> | ||||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 9 | CC: | dcbw, fschwarz, wtogami | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | |||||||||||
| : | 499583 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2009-02-17 12:00:38 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Uggh... Hit send by mistake. Versions: $ rpm -qa | grep NetworkManager NetworkManager-gnome-0.7.0-0.11.svn4022.fc9.x86_64 NetworkManager-glib-0.7.0-0.11.svn4022.fc9.x86_64 NetworkManager-0.7.0-0.11.svn4022.fc9.x86_64 Easily reproducible. Created attachment 319579 [details]
Network configuration. (ifcfg-eth?, ifcfg-vbr?) [Fixed tar]
$ /usr/sbin/nm-system-settings --debug --plugins=ifcfg-fedora ** Message: Loaded plugin ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. ** Message: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... ** Message: ifcfg-fedora: error: Ignoring loopback device config. ** Message: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-vbr1 ... ** Message: ifcfg-fedora: error: Unknown connection type 'Bridge' ** Message: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth1 ... ** Message: ifcfg-fedora: read connection 'System eth1' ** Message: ifcfg-fedora: Ignoring connection 'System eth1' and its device because NM_CONTROLLED was false. ** Message: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-vbr0 ... ** Message: ifcfg-fedora: error: Unknown connection type 'Bridge' ** Message: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... ^C (Killed because it hanged) Can you attach the output of 'lshal' as well? I'd like to see if/how HAL detects the bridges... Created attachment 320543 [details]
lshal (NM disabled, for now)
For me this worked on F10. Reporter, is this still a problem for you? I just enabled NM (under F10), and it does honor NM_CONTROLLED=no. Bug seems to be fixed. Please close. Ok, thanks! |
Created attachment 319578 [details] Network configuration. (ifcfg-eth?, ifcfg-vbr?) Description of problem: I'm setting up a hybrid bridged / wired / wireless network on my laptop. I want NM to control two devices - br0 (bridged to eth0) and wlan0 - nothing else. However, even-though ifcfg-eth[0/1] and ifcfg-vbr1 have NM_CONTROLLED=no, Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: $ grep NM_CONTROLLED= /etc/sysconfig/network-scripts/ifcfg-* /etc/sysconfig/network-scripts/ifcfg-eth0:NM_CONTROLLED=no /etc/sysconfig/network-scripts/ifcfg-eth1:NM_CONTROLLED=no /etc/sysconfig/network-scripts/ifcfg-vbr0:NM_CONTROLLED=yes /etc/sysconfig/network-scripts/ifcfg-vbr1:NM_CONTROLLED=no $ grep BRIDGE= /etc/sysconfig/network-scripts/ifcfg-* /etc/sysconfig/network-scripts/ifcfg-eth0:BRIDGE=br0 /etc/sysconfig/network-scripts/ifcfg-eth1:BRIDGE=br1 $ /etc/init.d/network start Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Bringing up interface eth1: [ OK ] Bringing up interface vbr0: Determining IP information for br0... done. [ OK ] Bringing up interface vbr1: [ OK ] $ ifconfig | egrep -e 'br|eth' -A2 br0 Link encap:Ethernet HWaddr 00:1C:25:7E:BA:29 inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::21c:25ff:fe7e:ba29/64 Scope:Link -- br1 Link encap:Ethernet HWaddr 00:E0:98:33:72:51 inet6 addr: fe80::2e0:98ff:fe33:7251/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 -- eth0 Link encap:Ethernet HWaddr 00:1C:25:7E:BA:29 inet6 addr: fe80::21c:25ff:fe7e:ba29/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 -- eth1 Link encap:Ethernet HWaddr 00:E0:98:33:72:51 inet6 addr: fe80::2e0:98ff:fe33:7251/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 $ /etc/init.d/NetworkManager start Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] $ ifconfig | egrep -e 'br|eth' -A2 br0 Link encap:Ethernet HWaddr 00:1C:25:7E:BA:29 inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::21c:25ff:fe7e:ba29/64 Scope:Link -- br1 Link encap:Ethernet HWaddr 00:E0:98:33:72:51 inet6 addr: fe80::2e0:98ff:fe33:7251/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 -- eth0 Link encap:Ethernet HWaddr 00:1C:25:7E:BA:29 inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::21c:25ff:fe7e:ba29/64 Scope:Link -- eth1 Link encap:Ethernet HWaddr 00:E0:98:33:72:51 inet addr:172.18.130.95 Bcast:172.18.130.255 Mask:255.255.255.0 inet6 addr: fe80::2e0:98ff:fe33:7251/64 Scope:Link ===== Both eth0 and eth1 should not get an IP address... far worse, shouldn't NM automatically ignore bridged network devices? ===== - Gilboa