Network Manager empties resolv.conf

Bug #328023 reported by Denis Rut'kov
2
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I still have not found the conditions under which this bugs happens. Sometimes I end up with an empty resolv.conf. Maybe it is connected with this (https://bugs.launchpad.net/bugs/306469) bug.

Revision history for this message
Alexander Sack (asac) wrote :

can you come up with a way to reproduce this? when is the resolv.conf empty? Are you connected through NM if its empty or using ifupdown or even something else?

Changed in network-manager-applet:
status: New → Incomplete
Revision history for this message
Denis Rut'kov (dendron2000) wrote :

I think my provider's DHCP server may be causing this. It often happens when I replug network cable to another computer and back. As the NM defaults to 'auto' connection it tries to reget the address, the DHCP server goes crazy (MAC address is changed twice) and returns crap instead of proper configuration. I will mark this bug as invalid for now.

Changed in network-manager-applet:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.