On Thu, 07 May 2015 01:09:53 +0200 Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 moreinfo > > Am 07.05.2015 um 01:00 schrieb Norbert Preining: > > Package: network-manager > > Version: 1.0.2-1 > > Severity: serious > > Justification: breaks conectivity > > > > Hi, > > > > today's update of NM broke connectivity. Even a restart of the system > > didn't bring it back. The reason is that /etc/resolv.conf was empty, > > containing only > > # Generated by NetworkManager > > without any other information. > > > > Checking the journal, I see that it *did* get a ns: > > NetworkManager[694]: <info> address 10.0.0.18 > > NetworkManager[694]: <info> plen 24 (255.255.255.0) > > NetworkManager[694]: <info> gateway 10.0.0.1 > > NetworkManager[694]: <info> server identifier 10.0.0.1 > > NetworkManager[694]: <info> lease time 86400 > > NetworkManager[694]: <info> nameserver '10.0.0.1' > > and manually adding the name server fixed the problem. > >
I'm having the same problem. > > Please provide more informatin about your network setup: > a/ which interfaces are managed by NM, which are managed elsewhere > (ifupdown) /e/n/i has only the loopback interface. All else is NM-managed (ethernet and wlan). > b/ please provide a verbose debug log of NetworkManager This was a bit large for possibly mass email and I was not sure if some private info would be there. It is available at people.debian.org:~fsateler/nm.log > Do you have any custom configuration in > /etc/NetworManager/NetworkManager.conf? [main] plugins=ifupdown,keyfile [ifupdown] managed=false -- Saludos Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org