Bugzilla – Bug 141292
NetworkManager does not read ifcfg-files for WLAN devices
Last modified: 2006-01-03 20:17:12 UTC
To test NM with my setup, i configured my interfaces with Yast and then switched to Network manager by clicking "Managed by Network Manager". These are the ifcfg-files: strolchi:/etc/sysconfig/network # cat ifcfg-eth-id-00\:12\:79\:59\:37\:34 BOOTPROTO='static' BROADCAST='' IFPLUGD_PRIORITY='20' IPADDR='10.10.129.126' MTU='' NAME='Hewlett-Packard Company NetXtreme BCM5751M Gigabit Ethernet PCI Express' NETMASK='255.255.0.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='ifplugd' UNIQUE='rBUF.pSVHHPgiS3B' USERCONTROL='no' _nm_name='bus-pci-0000:10:00.0' strolchi:/etc/sysconfig/network # cat ifcfg-wlan-id-00\:0e\:35\:b0\:c9\:9e BOOTPROTO='static' BROADCAST='' IFPLUGD_PRIORITY='10' IPADDR='10.10.129.126' MTU='' NAME='Hewlett-Packard Company PRO/Wireless 2915ABG MiniPCI Adapter' NETMASK='255.255.0.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='ifplugd' UNIQUE='JNkJ.EU1Le8cv1T7' USERCONTROL='yes' WIRELESS_AP='' WIRELESS_AUTH_MODE='eap' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='/etc/cert/cacert.pem' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='ttls' WIRELESS_ESSID='wpa2-test' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='yes' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='idonttell' WIRELESS_WPA_PASSWORD='gofigureitout' WIRELESS_WPA_PSK='' _nm_name='bus-pci-0000:02:04.0' NM correctly sets up the wired interface, but apparently it does not honor the settings for the wireless interface. I also cannot connect to wpa2-test in neither knetworkmanager nor nm-applet (i get only the networks found by scanning, but not the hidden wpa2-test i configured) There might also be a yast bug in there because although i clicked on "managed by..." there is still "startmode=ifplugd" in the ifcfg-files (in fact they did not change at all).
of course the setup works without any problems when not using NM but ifplugd.
What does 'does not honor' mean? It ups the interface but uses DHCP? Or it does not work at all? The only settings that NM pulls from ifcfg- are static IP settings. Since WPA is not-yet-implemented, that won't work, either.
"does not honor" means there is a dhcdbd running although none of the interfaces is configured for dhcp (i'm not sure if this is a bug) and it does not try to associate to wpa2-test (which is a hidden essid) nor show it in nm-applet or knetworkmanager. Which is kind of normal if it doesn't pull this setting from ifcfg :-) It probably just could use ifup for wireless instead of implementing everything by itself?
Yes, dhcdbd should sitll be running. As I said, the wireless settings are not used from ifcfg and WPA is not yet supported. So I don't see a bug here.
*** This bug has been marked as a duplicate of 134238 ***