GNOME Bugzilla – Bug 600167
if-pre-up.d and if-post-down.d scripts do not run - depended on by many packages
Last modified: 2010-01-20 22:39:18 UTC
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518368 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/336736 Many packages in Debian install if-pre-up.d and if-post-down.d scripts and expect them to run. It is important for many things. The most important need is for security, to limit firewall access before the interface comes up, instead of leaving the interface wide open for a period of time after address association and before scripts in if-up.d run. There was no warning and no need to remove this essential function. Please bring it back. These are packages in Debian Squeeze that install if-pre-up.d or if-post-down.d scripts: maggie:~# apt-file search etc/network/if-pre-up.d bridge-utils: /etc/network/if-pre-up.d/bridge ethtool: /etc/network/if-pre-up.d/ethtool hostap-utils: /etc/network/if-pre-up.d/hostap-utils hostapd: /etc/network/if-pre-up.d/hostapd ifenslave-2.6: /etc/network/if-pre-up.d/ifenslave ifupdown-extra: /etc/network/if-pre-up.d/00check-network-cable ifupdown-scripts-zg2: /etc/network/if-pre-up.d/00README.linkdir linux-wlan-ng: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up uml-utilities: /etc/network/if-pre-up.d/uml-utilities vde2: /etc/network/if-pre-up.d/vde2 vlan: /etc/network/if-pre-up.d/vlan whereami: /etc/network/if-pre-up.d/whereami wireless-tools: /etc/network/if-pre-up.d/wireless-tools wpasupplicant: /etc/network/if-pre-up.d/wpasupplicant maggie:~# apt-file search etc/network/if-post-down.d avahi-daemon: /etc/network/if-post-down.d/avahi-daemon bridge-utils: /etc/network/if-post-down.d/bridge hostapd: /etc/network/if-post-down.d/hostapd ifenslave-2.6: /etc/network/if-post-down.d/ifenslave ifupdown-scripts-zg2: /etc/network/if-post-down.d/00README.linkdir linux-wlan-ng: /etc/network/if-post-down.d/linux-wlan-ng-post-down sendmail-base: /etc/network/if-post-down.d/sendmail vde2: /etc/network/if-post-down.d/vde2 vlan: /etc/network/if-post-down.d/vlan wireless-tools: /etc/network/if-post-down.d/wireless-tools wpasupplicant: /etc/network/if-post-down.d/wpasupplicant Thank you. Mark
post-down should already be handled by dispatcher scripts in /etc/NetworkManager/dispatcher.d, or a script could be placed there to run those post-down scripts quite easily. Some of these scripts aren't necessary with NM anyway: wpa_supplicant - NM controls the supplicant, and it shouldn't be executing up/down scripts when controlled by NM as that may well interfere with NM wireless-tools: this script shouldn't be run either, since it may interfere with NetworkManager's configuration of the wifi device as well avahi-daemon: avahi listens on D-Bus already, so it might be better to have avahi just listen for NM signals. In any case, avahi has adequate netlink event handling to notice up/down without script kicks liek this. linux-wlan-ng-post-down: this is a non-upstream kernel driver that is simply broken in many ways, and it's not worth caring about. Nor is it likely that this driver (which hasn't been updated in years) is going to work well with wpa_supplicant/NM anyway since it's not part of the upstream kernel and has known WEXT compatibility issues. hostap-utils: this also shouldn't be necessary as the firmware loading should already be covered by the kernel driver, or the 'orinoco' driver, or if not, should be added to the kernel driver. My point is that just because there are a lot of scripts that use pre-up/post-down, doesn't mean we want those scripts running when NetworkManager is being used. But yes, there are a few that should be. This is better tracked in bug 387832. *** This bug has been marked as a duplicate of bug 387832 ***