Re: Why does NM deactivate active connections at startup?

[Dan Williams <dcbw redhat com>]

On Mon, 2007-10-29 at 13:58 -0600, Orion Poplawski wrote:
> This causes problems esp. with systems that have come up with NIS or NFS 
> active from a system config setup.

NM isn't compatible with network connections set up before NM starts,
and there aren't any plans to make it so.  The solution is to use the
system settings daemon that Soren just wrote, and that I'm about ready
to import into SVN, to allow NM to start up network connections earlier
than login.  Part of the problem is that if NM were to respect
connections that were set up before it got started, that really only
works for ethernet, and even then NM would have to inspect 20+
properties of the interface and system configuration, compare them to an
existing saved connection, and if there was no saved connection that
matched, it would tear down the interface anyway.  It gets worse with
bluetooth, wireless, PPP, etc, since the number of properties multiplies
quite a lot there.  It's just not something that's going to happen.

Dan