kauer at biplane.com.au
Sun Oct 5 18:29:18 UTC 2008
On Sun, 2008-10-05 at 15:04 -0300, Derek Broughton wrote:
> > It should not have been necessary to restart NM, because as you yourself
> > said, it just uses whatever comes back from DHCP. Restarting networking
> > should have done the trick.
> You're not paying attention.
Don't be insulting. There is a difference between "not paying attention"
and "missing the point". I do now see what you are getting at, thank
you, and that was indeed the point I was missing at the time, too.
> > The interface concerned was not in /etc/network/interfaces.
> So, you need to do "/etc/dbus-1/event.d/25NetworkManager restart".
To restart NetworkManager, yes. To cause new nameserver info to be
retrieved from the DHCP server? I'm still not sure that's needed (though
it would certainly work).
I think just getting NetworkManager to reconnect would have have done
the trick. That is, left-click on the NetworkManager applet, then select
the same network as it already has. That makes it disconnect and
reconnect, and it then picks up any changes made on the DHCP server.
Karl Auer (kauer at biplane.com.au) +61-2-64957160 (h)
http://www.biplane.com.au/~kauer/ +61-428-957160 (mob)
GPG fingerprint: DD23 0DF3 2260 3060 7FEC 5CA8 1AF6 D9E3 CFEE 6B28
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part
More information about the ubuntu-users