FS#42513 - [networkmanager] DHCP doesn't work in NM in some cases
Attached to Project:
Arch Linux
Opened by Mario (diraimondo) - Thursday, 23 October 2014, 15:37 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 09 June 2016, 23:32 GMT
Opened by Mario (diraimondo) - Thursday, 23 October 2014, 15:37 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 09 June 2016, 23:32 GMT
|
Details
Description:
premise: I think this is a bug already reported on network-manager 0.9.10.0 on Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758534 At some point NM stops to get the IP address in my lan by DHCP. As stated in Debian report, it looks related to systemd-journald restart. Additional info: $ pacman -Q network-manager-applet systemd network-manager-applet 0.9.10.0-2 systemd 216-3 ott 23 17:28:48 gandalf NetworkManager[8209]: <info> (wlp2s0): supplicant interface state: associating -> 4-way handshake ott 23 17:28:48 gandalf NetworkManager[8209]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> group handshake ott 23 17:28:48 gandalf NetworkManager[8209]: <info> (wlp2s0): supplicant interface state: group handshake -> completed ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'wifi'. ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled. ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started... ott 23 17:28:48 gandalf NetworkManager[8209]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0] ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds) ott 23 17:28:48 gandalf NetworkManager[8209]: <info> dhcpcd started with pid 8557 ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete. ott 23 17:28:48 gandalf NetworkManager[8209]: <info> (wlp2s0): DHCPv4 client pid 8557 exited with status -1 ott 23 17:28:48 gandalf NetworkManager[8209]: <warn> DHCP client died abnormally ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) started... ott 23 17:28:48 gandalf NetworkManager[8209]: <info> Activation (wlp2s0) Stage 4 of 5 (IPv4 Configure Timeout) complete. Steps to reproduce: It happens usually after a suspend/resume cycle. The same behavior, as suggested in the Debian report, can be reproduced as follows: - systemctl restart systemd-journald - try to reconnect to the lan: fails - systemctl restart NetworkManager - now it works |
This task depends upon
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758534#24
Unless this is still a problem for you I am going to recommend this bug be closed.