FS#43601 - [networkmanager] eduroam - can not start DHCP client
Attached to Project:
Arch Linux
Opened by abc (Xiflite) - Tuesday, 27 January 2015, 22:32 GMT
Last edited by Jan de Groot (JGC) - Monday, 25 December 2017, 23:04 GMT
Opened by abc (Xiflite) - Tuesday, 27 January 2015, 22:32 GMT
Last edited by Jan de Groot (JGC) - Monday, 25 December 2017, 23:04 GMT
|
Details
Description:
- try to connect to eduroam (http://en.wikipedia.org/wiki/Eduroam) - PEAP with MSVCHAPv2 - get a loop of "connecting", "dhcp client could not be started" and "disconnected" Additional info: only 1.0.0-1 effected - downgrade solves this problem immediately |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 25 December 2017, 23:04 GMT
Reason for closing: Fixed
Additional comments about closing: internal dhcp client is default now, so this should work as dhcpcd is not used by default now.
Monday, 25 December 2017, 23:04 GMT
Reason for closing: Fixed
Additional comments about closing: internal dhcp client is default now, so this should work as dhcpcd is not used by default now.
I was only able to downgrade because I was able to connect to a third WPA2 network for 3-4 minutes at a time (after that it would disconnect and fail to reconnect, not even getting to the dhcp stage).
Here's my wifi card from lspci -vv:
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Which may be a dupe of this bug: https://bugzilla.gnome.org/show_bug.cgi?id=743472
For anyone who sees this, the answer is to downgrade, use dhclient instead of dhcp (install dhclient and make sure you don't have "dhcp=dhcp" in /etc/NetworkManager/Networkmanager.conf; NM tests for it before falling back to dhcp), or to wait for a future version of NetworkManager: they plan to drop their dhcpcd backend in favor of an internal dhcp implementation.
Reading this https://bugzilla.gnome.org/show_bug.cgi?id=743472#c9 let me propose to make networkmanager dependent on dhclient and not on "dhcp-client" until they drop support for both and use their own implementation.
Downgrade to 0.9.10.0-4 works for me.
sudo pacman -U /var/cache/pacman/pkg/networkmanager-0.9.10.0-4-x86_64.pkg.tar.xz
Also disabling networkmanager and connecting over wifi-menu.
Fwiw, I posted the log output of my system in a forum thread:
https://bbs.archlinux.org/viewtopic.php?pid=1500473
Why don't we make networkmanager dependent on dhclient (not on "dhcp-client") until they drop support for both and use their own implementation? That would fix this issue.