[Pkg-utopia-maintainers] Bug#475188: Bug#475188: using NetworkManager /etc/network/if-up.d/openssh-server does not reload

[Colin Watson]

On Fri, Jun 27, 2008 at 12:43:54PM +0200, Michael Biebl wrote:
> Colin Watson wrote:
> >Unless the network-manager maintainer says otherwise, yes, I think this
> >is a network-manager bug. It just doesn't make sense to set ADDRFAM like
> >this.
> 
> I took over this code from the previous maintainer of network-manager 
> (CCed), so  I don't know the reasoning for choosing "NetworkManager" as 
> ADDRFAM.
> 
> Some background details:
> NM provides it's own dispatcher mechanism to run scripts via 
> /etc/NetworkManager/dispatcher.d.
> For interoperability with ifupdown, NM installs the 01ifupdown script by 
> default, which calls the scripts in /etc/network/if-*.d/.
> This 01ifupdown script sets ADDRFAM="NetworkManager".
> 
> Say, ssh provided a native NM dispatcher script to reload ssh in 
> /etc/NetworkManager/dispatcher.d besides the "legacy" ifupdown hook.
> To not reload ssh twice, you need a way to differentiate connections 
> managed by ifupdown or NM.
> This could be a reason for setting ADDRFAM="NetworkManager".

A means to distinguish these two cases is of course entirely reasonable,
but surely it could be done using something other than ADDRFAM? You have
lots of possible environment variable names to play with. :-)

> I CCed the original maintainer of NM for his opinion on this matter and 
> the historical reason for this setting.
> 
> I don't have a strong preference in either way (keeping or changing this 
> setting).
> 
> As NM manages different types of connections (dialup 
> (PPP,PPPOE,GSM,CDMA), ethernet/wlan, vpn), I was wondering, what the 
> correct ADDRFAM should be, if not NetworkManager.

ADDRFAM should describe the nature of the network layer (IPv4, IPv6,
etc.), not the nature of the physical or data-link layers (PPP,
Ethernet, etc.).

Cheers,

-- 
Colin Watson                                       [cjwatson at debian.org]