Comment 5 for bug 1580146

@Andrea

Let's keep this bug specific to the original problem described.

Does this problem only occur at the office?

Can you reproduce it reliably? If so, how long after you initially connect does it take to manifest itself?

From what you provided in your initial pastebin, both the indicator and NetworkManager show wlan0 connected to the office access point. You also stated that you could ping 8.8.8.8, but that 'ping google.com' returned 'unknown host'.

The new version of NM now logs the IPv4 details when an IP address is assigned and/or renewed. One possibility here is that lease renewal is not working properly. So, if/when this problem happens again, please provide the following:

1) the entire syslog

2) the output of 'iw add show wlan0'

3) the output of 'ip route'

If you again can ping IPv4 addresses on the internet, but can't resolve hostnames, then let's checkout the dnsmasq configuration. To do this, run the following command:

$ sudo kill -SIGUSR1 `pidof dnsmasq`

This causes dnsmasq to write its current configured nameservers to the syslog, so after sending the signal, grep for "dnsmasq" in syslog and look for the lines like these:

May 12 19:55:35 ubuntu-phablet dnsmasq[2048]: server 192.168.1.1#53: queries sent 19, retried or failed 0

Also, in the future, it's better to include requested information ( output from commands, syslog, ... ) directly in comments or attachments vs. using pastebin.