Bug 1377886
| Summary: | cannot connect to wifi network after updating to NetworkManager 1.2.4-2.fc24 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom Tromey <tom> | ||||
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | bgalvani, dcbw, fgiudici, lkundrak, psimerda, tom | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-09-21 16:16:30 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Tom Tromey
2016-09-20 22:19:30 UTC
Hi, can you please try this (as root): nmcli general logging level KEEP domains DNS:TRACE echo log-queries > /etc/NetworkManager/dnsmasq.d/log-queries killall -HUP NetworkManager then connect to the wifi network, check that you don't have connectivity and run: dig fedoraproject.org @127.0.0.1 and paste the output, as well as logs from /var/log/messages (or if you prefer from 'journalctl -u NetworkManager -e'). Thanks! Does the issue go away if you run 'killall -HUP NetworkManager' after establishing the wifi connection? (In reply to Beniamino Galvani from comment #1) > Hi, can you please try this (as root): > > nmcli general logging level KEEP domains DNS:TRACE > echo log-queries > /etc/NetworkManager/dnsmasq.d/log-queries > killall -HUP NetworkManager > > then connect to the wifi network I did these steps. To connect to the wifi network, I used the gnome-shell menu to disable wifi, then re-enabled it. > Does the issue go away if you run 'killall -HUP NetworkManager' after > establishing the wifi connection? Yes, this makes it work. I will attach the requested log momentarily. The "dig" command worked fine after the killall. However if I close the laptop and reopen it (causing the failure again) it says: ; <<>> DiG 9.10.4-P2-RedHat-9.10.4-1.P2.fc24 <<>> fedoraproject.org @127.0.0.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 33659 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;fedoraproject.org. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 21 09:36:31 MDT 2016 ;; MSG SIZE rcvd: 35 Created attachment 1203375 [details]
journalctl -u NetworkManager -e
Hi, now I understand; the wireless NIC is a USB one and when the system is suspended and resumed an interface with a different ifindex appears. This triggers a known issue in dnsmasq related to wrong caching of socket descriptors. We observed this issue only with VPNs connection before, but apparently it can also happen with wifi. Upstream dnsmasq already includes a fix for this bug, while the Fedora package still lacks it and needs a backport. In the meanwhile you can use this workaround: cat <<'EOF' > /etc/NetworkManager/dispatcher.d/99-dnsmasq-restart.sh #!/bin/sh [ "$2" = up ] && killall -HUP NetworkManager exit 0 EOF chmod +x /etc/NetworkManager/dispatcher.d/99-dnsmasq-restart.sh See bugs 1373485 (Fedora) and 1367772 (RHEL) for more details. *** This bug has been marked as a duplicate of bug 1373485 *** Thank you very much. I appreciate your quick response and analysis of this. FWIW the workaround in comment #4 doesn't work for me; but doing killall -HUP manually does. |