Bugzilla – Bug 10517
netconf should use ifplugd
Last modified: 2008-10-06 06:26:50 UTC
ifplugd is a nice little app. It runs a background daemon which can launch a command script, usually ifup/ifdown, whenever a network device is plugged or unplugged. netconf could well use this feature. There is one downside to ifplugd, though: it needs the driver to be present to observe network state changes. And as SMGL's ifdown unloads the driver module if one is used, ifplugd will not be able to bring the interface back up anymore when the cable is again plugged in. (If the module is then manually loaded, though, ifplugd will take immediate action.) Nevertheless I ask for integration of ifplugd into netconf. It could be an option that's only available for static configurations, and of course only if the spell itself is installed (would be unnecessary to include it as dependency).
So it'd be an optional dependency. And just a side note: I usually put the modules in /etc/modules so that I guarantee which order they're started in so that eth0 always remains eth0. Then the module is loaded all the time, but ram is cheep these days ;)
This bug now exists in stable-rc, version 0.5
Optional is fine by me, make it so. :)
This now applies to stable-rc (0.22).
Today's netconf doesn't work with our "new" networking. It should be updated to work with /etc/network/interfaces. Does anybody know some tool (console) which work with /etc/network/interfaces? Whe need some at least for install iso.
one just needs vi and man interfaces. An example interfaces file is provided with the ifupdown spell. I don't think a gui(ish) tool is *needed* to configure this kind of networking. I would actually just blow away netconf. Nothing else is configured that way, with the exception of sorcery.
Most smgl devs feel this way (on IRC at least). Maybe we should just install a sane default and point users to the example file from the ifupdown spell. I started rewriting netconf after a couple of requests to do so, but stopped once I was told on IRC that it would be a waste of time. Personally I think a sample config is enough, but I wouldn't mind to continue rewriting netconf.
BTW, about ifplugd, we had this discussion before and it was agreed that if the SA wants to use ifplugd he'd be comfortable enough with networking to configure it himself instead of needing a tool like netconf.