Re: Stopping NetworkManager without taking the interface down.
Dan Williams wrote: > On Sat, 2008-02-02 at 15:15 +0100, Michael Biebl wrote: >> Hi everyone, >> >> as NetworkManager (especially the 0.7 version) tries to be more than >> just a network configuration for the laptop, but also desktops and >> servers, there is one issue, that's currently suboptimal imho. >> That is, that NM always deconfigures the network interface when it is >> stopped. This is especially unfortunate, when you remotely administer >> machines and you have to restart NetworkManager (e.g. after installing a >> security update of NM. Rebooting is not ideal for servers...). > > Right, but the NM startup is the part that's going to kill you here... > Understood. Would it still be possible to add the feature though, to not deconfigure the device on shutdown, even if we can't handle the startup yet? This would still be useful, as it cuts down the possible downtime to a minimum. 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Stopping NetworkManager without taking the interface down.
On Mon, 2008-02-04 at 12:02 +0100, Alexander Sack wrote: > On Sun, Feb 03, 2008 at 09:24:44PM -0500, Dan Williams wrote: > > > > Yes, but probably not before 0.8 I think. I believe it would require > > quite a bit of coding and architecting to ensure that it's not an > > un-manageable hack. > > OK, I understand that (though I hoped that we could have this once we > support for multiple interfaces). Well, this is somewhat orthogonal to multiple active devices. Which is both good and bad. > So do you advice distributors to not restart NetworkManager on upgrade > and defer this until reboot? Is that the way fedora is (not-)dealing > with this issue too? Yes, I think that's appropriate for the moment. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Stopping NetworkManager without taking the interface down.
On Sun, Feb 03, 2008 at 09:24:44PM -0500, Dan Williams wrote: > > Yes, but probably not before 0.8 I think. I believe it would require > quite a bit of coding and architecting to ensure that it's not an > un-manageable hack. OK, I understand that (though I hoped that we could have this once we support for multiple interfaces). So do you advice distributors to not restart NetworkManager on upgrade and defer this until reboot? Is that the way fedora is (not-)dealing with this issue too? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Stopping NetworkManager without taking the interface down.
On Sat, 2008-02-02 at 15:15 +0100, Michael Biebl wrote: > Hi everyone, > > as NetworkManager (especially the 0.7 version) tries to be more than > just a network configuration for the laptop, but also desktops and > servers, there is one issue, that's currently suboptimal imho. > That is, that NM always deconfigures the network interface when it is > stopped. This is especially unfortunate, when you remotely administer > machines and you have to restart NetworkManager (e.g. after installing a > security update of NM. Rebooting is not ideal for servers...). Right, but the NM startup is the part that's going to kill you here... > That's why I think, it's an important feature for NetworkManager, to > provide the option to not deconfigure a network interface on stop and > ideally, on startup, recognize and pickup an already existing > connection, without the need to reconfigure the device. > The latter might be very hard to do for wireless interfaces, but for > wired interfaces it should be possible (and most servers and > workstations will have wired connections). Obviously this isn't something that's easy to do, especially with the richness of configuration and the number of interfaces. It's also much harder to do for anything except wired, and it's probably pretty hard to do for wired 802.1x-authenticated connections. > Dan, Tambet, would it be possible to add such functionality to > NetworkManager? Yes, but probably not before 0.8 I think. I believe it would require quite a bit of coding and architecting to ensure that it's not an un-manageable hack. Dan > Other opionions on this are very welcome. > > Cheers, > Michael > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Stopping NetworkManager without taking the interface down.
Hi everyone, as NetworkManager (especially the 0.7 version) tries to be more than just a network configuration for the laptop, but also desktops and servers, there is one issue, that's currently suboptimal imho. That is, that NM always deconfigures the network interface when it is stopped. This is especially unfortunate, when you remotely administer machines and you have to restart NetworkManager (e.g. after installing a security update of NM. Rebooting is not ideal for servers...). That's why I think, it's an important feature for NetworkManager, to provide the option to not deconfigure a network interface on stop and ideally, on startup, recognize and pickup an already existing connection, without the need to reconfigure the device. The latter might be very hard to do for wireless interfaces, but for wired interfaces it should be possible (and most servers and workstations will have wired connections). Dan, Tambet, would it be possible to add such functionality to NetworkManager? Other opionions on this are very welcome. 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
