Mark Brown wrote: > Package: network-manager > Version: 0.6.4-6 > Severity: important > > When Network Manager is installed on a system with statically configured > network interfaces it usually reports the system as being disconnected > from the network, either like this: > > NetworkManager Tool > > State: disconnected > > print_devices(): didn't get a reply from NetworkManager. > There are no available network devices. > > if there are no other interfaces or by reporting an idle interface as > the only interface. This causes serious problems for other tools > attempting to use Network Manager's link state reporting to perform > actions - the information coming out of Network Manager can only be > trusted if Network Manager is in use and the system has a supported > configuration. > > I guess the ideal solution would be for Network Manager to have a full > and complete understanding of all the possible network configuration > methods and accurately reflect this status to other applications. > That's probably wishful thinking, though. Simpler a solution, like
Well, ifupdown is just too flexible and complex that you can't map it's features one to one to network-manager (think of mappings, the up/down commands, logical interfaces etc.). Maybe we can hack up support in NM to at least understand a standard static configuration, but that would be all that is possible. Any device that has some complexer configuration in /e/n/i will just be ignored by NM. Sorry to say that, but I don't see another possibility. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
