So from @Andrea's latest pastebin: - NM shows both modem and wlan0 as connected
- syslog shows one DHCP renewal period - a do-add-ip4-address error is logged, however the IP address is still configured ( ip addr show confirms this ); need to investigate whether the error log message is correct, and possible adjust the text of the message - dnsmasq has four nameservers configured ( wlan0: ipv4 & ipv6; modem: two ipv4 ) - the internet is reachable, as 8.8.8.8 can be pinged - DNS lookups fail ( ping google.com responds with 'unknown host' ) - the DHCP lease interval appears to be just shy of 10m ( 571s ) - the problem seems to occur after the lease renewal - the device may have been asleep between the time the WiFi connection was working and the failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1580146 Title: [touch] Internet connection stops working while WiFi is still connected Status in Canonical System Image: New Status in network-manager package in Ubuntu: Incomplete Bug description: krillin, rc-proposed, r329 Description: It often happens that the internet connection stops working while the device is still connected to a (working) WiFi AP. The indicator shows that the phone is connected to the AP, here's the ouput of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/ Tapping on the AP in the network indicator resets the connection and fixes the issue, which however reappears after a while. Here's also a "grep NetworkManager" from syslog http://pastebin.ubuntu.com/16344990/ How to reproduce: I don't have a recipe, but here's what usually happens on my phone 1) I connect to the office WiFi (Canonical's HQ, BlueFin office) 2) Use browser, perform random google searches to check internet is working 3) After a while (sometimes I put the phone to sleep, sometimes I checked the Updates from system settings a few times), I go back to the browser, and it starts returning "Network Error". NM, as you can see from the logs, says WiFi is "connected" 4) At this point I use Terminal app and discover that "ping 8.8.8.8" is working correctly, "ping google.com" immediately returns "unkown host", i.e. it doesn't seem to be waiting for a timeout, it returns pretty fast. There are no related crash files in /var/crash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
