Regression: WiFi connection reconnects, but dead, after waking from standby
Bug #1618839 reported by
dronus
This bug report is a duplicate of:
Bug #1639776: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface.
Edit
Remove
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Bug introduced somewhere between Ubuntu 14.04.3 and 16.04.1
If my Thinkpad T420s awakes from standby, very often the last connected WiFi network is reconnected immediately, but the connection is dysfunctional.
ifconfig shows a valid connection with an IPv4 address assigned for the wlp3s0 interface.
But there is no traffic, no success on DNS queries on the connection.
If I reconnect by clicking the connection in the nm-applet menu, all is fine again.
tags: | added: regression-update yakkety |
tags: | removed: regression-update |
To post a comment you must log in.
Same issue here after upgrading from xenial 16.04 to yakkety 16.10: After standby I can ping valid IP addresses, but DNS fails. Restarting the network manager via ` sudo /etc/init. d/network- manager restart` does mend the situation.
In this SO post https:/ /askubuntu. com/q/837575/ 94728 people report the same issue. A answer proposes to disable dnsmasq in network manager by commenting out `dns=dnsmasq` in `/etc/NetworkMa nager/NetworkMa nager.conf` as workaround.