Ritesh Raj Sarraf wrote: > Hi, > > I followed the bug report. But I don't find Michael's answer very convincing. > Network Manager is a good tool but the way it is customized for Debian makes > it next to useless. > > There'll be most people who when connect to a wireless network through > office, > also run a vpn client.
This will be handled by NM vpn plugins. This plugins are not packaged yet, but ITPs are filed already (362005, 368748). I intend to package them after etch is released. > There'll be people who when connecting from a public wifi location want some > iptables rules to be loaded. > > And there'll be people who when connecting from their home want no firewall > settings. No problem, can be done with NetworkManagerDispatcher, at least to some degree. > This all is well done in /etc/network/interfaces, ifupdown. > > If we could add an option in /etc/network/interfaces to be Network Manager > manageable, Network Manager could leverage all the flexibilities and still be > obedient enough not to mess with other settings. > Probably something like this: > iface eth2 inet dhcp > pre-up /sbin/iptables -A INPUT -i eth2 -m state --state NEW,INVALID -j > DROP; > Network-Manager: Yes > > This allows it to be managed by Network Manager Adding a "NetworkManager: Yes" to /e/n/i doesn't magically make NM use all posibilities ifupdown provides. The problem is, that NetworkManager and ifupdown have different approaches how network has to be managed. The ifupdown configuration is rather static, whereas in NM networks can come and go. Mixing ifupdown and NM is not really easy doable and imho unnecessary. If you have a static configuration, stick with ifupdown. If you are a roaming user with changing networks, NM is for you. And with NetworkManagerDispatcher, you can at least have the scripts in /etc/network/if-*.d/ run on connection changes. 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