I was aware that managed mode was not the default. I only changed to managed mode because an update to NM (around about the 8th October) stopped my internet connection working, and I was trying lots of things to get it working again. Launching Firefox I found that offline mode was checked (I had not had this bug previously), however, unchecking it I still could not navigate to any website and the NM icon was reporting no connection (I think).
After changing to managed mode I then noticed the lack of DNS Server setting in NM and so found the 'dns-nameservers' entry from the posts on this bug report. That got me back 'online'. My point is this, before the update my static configuration was fine, after the update I had no working internet connection. That's not good. Why did it break? I suspect something to do with NM writing it's 'blank' DNS Server setting to resolv.conf, but since I didn't check that file before desperately enabling managed mode (my bad) I can't say for sure. Had I been able to simply set my static settings in the NM GUI (including the DNS Server) without the afrementioned 'read-only' error (what's that all about?), I would have been fine and would not have had to boot into Windows to access the web to find this bug and hence the fix! -- [intrepid] new 0.7 branch ignores /etc/network/interfaces https://bugs.launchpad.net/bugs/256054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
