I've done some more investigating and identified the problem; I'm just not sure what the solution is. The problem is that nm decides the network is "up" as soon as there are no interfaces that still have work to be done ( such as obtaining a dhcp lease ). My e1000e interface comes up in the disconnected state, which nm considers to be an unusable state with no work to be done, and so it declares the network to be all set up. I'm not sure why, but it takes another 20 seconds for the e1000e to auto negotiate the 100 mbps link speed with my router, and then the link transitions to up, and nm starts trying to get a dhcp lease.
I suppose I'm still wondering why it takes so long for the link to come up, but I guess the real problem is the fact that nm will consider networking to be up so long as there is no link yet. I'm thinking it needs patched to not consider the network up until at least one interface is actually functioning. Another possible fix is for mediatomb and any other services that depend on "network" to instead depend on "[email protected]". ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453602 Title: mediatomb starts before network comes online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediatomb/+bug/1453602/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
