On Sun, 2008-04-27 at 17:50 +0930, Tim wrote:
On Sun, 2008-04-27 at 17:39 +1000, Simon Slater wrote:
> I must still be in the wrong place. Turned avahi-daemon off in
> runlevels 345 and rebooted, yet NM's connection information still has
> a 169.254 address. Should the next step be turn NM off and service
> network on to see what happens then?
I'm not sure of Network Manager works this way, but some other systems
will re-use the last IP they had, as a default.
You are certain the daemon isn't running?
service avahi-daemon status returns Avahi daemon is not running and
chkconfig --list has it off for all runlevels.
I haven't seen any good information about how Network Manager
works, I
wonder if it also uses link-local addresses, internally.
What I've found as NM docs is fairly superficial. There must be some
somewhere.
--
Regards
Simon