Supposedly, you can override NM's default use of dhclient as a DHCP client by specifying "dhcp=dhcpcd" in the [main] section of Networkmanager.conf. However, if you do this on a system whose wireless is working with NM/dhclient, NM is suddenly unable to connect, giving the following: Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) starting connection 'NETGEAR55' Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0/wireless): connection 'NETGEAR55' requires no security. No secrets needed. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Config: added 'ssid' value 'NETGEAR55' Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Config: added 'scan_ssid' value '1' Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Config: added 'key_mgmt' value 'NONE' Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Config: set interface ap_scan to 1 Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): supplicant interface state: disconnected -> scanning Dec 13 10:16:22 ftglap kernel: wlan0: authenticate with 84:1b:5e:44:cf:f2 Dec 13 10:16:22 ftglap kernel: wlan0: send auth to 84:1b:5e:44:cf:f2 (try 1/3) Dec 13 10:16:22 ftglap kernel: wlan0: authenticated Dec 13 10:16:22 ftglap kernel: wlan0: associate with 84:1b:5e:44:cf:f2 (try 1/3) Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): supplicant interface state: scanning -> associating Dec 13 10:16:22 ftglap kernel: wlan0: RX AssocResp from 84:1b:5e:44:cf:f2 (capab=0x401 status=0 aid=1) Dec 13 10:16:22 ftglap kernel: wlan0: associated Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): supplicant interface state: associating -> completed Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'NETGEAR55'. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0] ******** Note the following Dec 13 10:16:22 ftglap NetworkManager[2391]: client_start: assertion `priv->client_type != 0' failed Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): device state change: ip-config -> failed (reason 'dhcp-start-failed') [70 120 15] ******** Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Marking connection 'NETGEAR55' invalid. Dec 13 10:16:22 ftglap NetworkManager[2391]: <warn> Activation (wlan0) failed for connection 'NETGEAR55' Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0] Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): deactivating device (reason 'none') [0] Dec 13 10:16:22 ftglap kernel: wlan0: deauthenticating from 84:1b:5e:44:cf:f2 by local choice (reason=3) Dec 13 10:16:22 ftglap kernel: cfg80211: Calling CRDA to update world regulatory domain Dec 13 10:16:22 ftglap NetworkManager[2391]: <info> (wlan0): supplicant interface state: completed -> disconnected Dec 13 10:16:22 ftglap kernel: cfg80211: World regulatory domain updated: Dec 13 10:16:22 ftglap kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 13 10:16:22 ftglap kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: Calling CRDA for country: US Dec 13 10:16:22 ftglap kernel: cfg80211: Regulatory domain changed to country: US Dec 13 10:16:22 ftglap kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 13 10:16:22 ftglap kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 13 10:16:22 ftglap kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) In other words, everything works perfectly except the invocation of dhcpcd. This is particularly annoying because at the moment our dhclient does not support the DHCP domain-search option, while dhcpcd does.
CC: (none) => dmorganec, mageia, olav, tmbBlocks: (none) => 7557
Sorry, but this bug saw no action since over 2 yrs ago - no cauldron package has stayed the same - and is still assigned to Bug Squad. Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4
Status: NEW => RESOLVEDResolution: (none) => OLD
Yes, this has become moot, as dhclient now supports domain-search. I suspect this had to do with clashes between NM and ifcfg back in the days when I used the RedHat script in addition to NM.