desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Unfortunately, it's both not a simple thing to fix and there is no way
to know that missing DNS servers from DHCP is an error or if it's
expected behavior. I'm going to close this bug as Won't Fix because I
cannot see how it would be possible to resolve it.

Presumably, the router probably isn't restarted all that often either,
and in the chance this is not the case then there is probably something
else that could to be corrected on the network to mitigate this issue.

Thanks for filing this bug and helping to make Ubuntu better! Please
don't hesitate to report any further issues you may find.

** Changed in: network-manager (Ubuntu)
       Status: New => Won't Fix

-- 
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/864539

Title:
  network-manager does not retry on empty DNS server list

Status in “network-manager” package in Ubuntu:
  Won't Fix

Bug description:
  Scenario: PC on, ADSL modem router off. Router set to give out static DNS servers instead of from ISP.
  Turn router on, router boots up and starts connecting to internet. Ubuntu Natty /network-manager detects link comes up and requests address via DHCP. Router gives out local LAN IP address and gateway, but until internet is connected (which may be a minute later) does not give out any DNS servers in its DHCP responses. 
  The problem is network-manager does not seem to think a lack of any DNS servers is a problem and instead of retrying just stops. I then have to manually click 'Auto eth0' to get any internet when I know the ADSL is connected.

  This seems to go against the 'it should just work' ideaology of
  network manager and is seemingly a very simple thing to fix?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/864539/+subscriptions