Network anomalies since F8 install

[Ric Moore]

On Sun, 2008-04-27 at 20:32 +1000, Simon Slater wrote:
> 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.

Try looking in your desktop menu for "services" or "service management"
which will kick up a nice little gui. It'll show if "Network Manager"
and "Network Manager Dispatcher" are off. If so, stop them, and save the
configuration rules. Before you do anything, click on "Edit Run Level"
and select the last choice, "ALL" so you can see what is enabled at each
run level. It might be set to run on level 3 and not on level 5, which
might be a problem. I find it on my KDE menu under "Administration". 
Great little application. Ric

-- 
================================================
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256 Sign up at: http://counter.li.org/
http://www.sourceforge.net/projects/oar
http://www.wayward4now.net  <---down4now too
================================================