Bug#880982: ifup does not trigger scripts any more after booting

2017-11-08 Thread Narcis Garcia
I've realised this problem because of this software relies on this feature:
www.actiu.net/durruter

__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.



Bug#880982: ifup does not trigger scripts any more after booting

2017-11-08 Thread Narcis Garcia
Please try this with Debian 7 and Debian 8 to assume that behaviour has
changed about /etc/network/if-*.d scripts
(either because of ifupdown or udev)

and Debian 9 has lost this up/down triggering feature.


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.



Bug#880982: ifup does not trigger scripts any more after booting

2017-11-07 Thread Guus Sliepen
On Tue, Nov 07, 2017 at 09:55:17PM +0100, Narcis Garcia wrote:

> Thanks Guus for the suggestion about netplug as alternative.
> Network interface's configurtaion (IP) is already done when hotplugging
> the cable.
> 
> What is not working on same event is the run-parts of scripts in
> /etc/network/if-up.d [...]

Aha. If you are using DHCP, then the DHCP client will probably detect
that the cable is plugged in again at some point, and will assign it an
address. However, ifupdown is never called when that happens, so
ifupdown will not cause any of the scripts to run. Also, ifupdown will
consider the interface to be up all the time, whether the cable is
plugged in or not.

Note that dhclient itself can also run scripts when it gets or loses a
lease, see man dhclient-script.

> (as non-Systemd Debian versions did)

This has nothing to do with systemd vs. sysvinit. Maybe it is caused by
changes in udev. But on my computers, I don't see udev generating any
events when I plug or unplug a network cable...

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Bug#880982: ifup does not trigger scripts any more after booting

2017-11-07 Thread Narcis Garcia
Thanks Guus for the suggestion about netplug as alternative.
Network interface's configurtaion (IP) is already done when hotplugging
the cable.
What is not working on same event is the run-parts of scripts in
/etc/network/if-up.d (as non-Systemd Debian versions did) and maybe
other directories as:

/etc/network/if-down.d
/etc/network/if-pre-up.d
/etc/network/if-post-down.d

This bad behavior happens when no Desktop/NetworkManager is in effect,
and since Debian 9 is beyond 5 minutes after boot.

I've tried to set TimeoutStartSec=infinity with no success at
/lib/systemd/system/ifup@.service


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.



Bug#880982: ifup does not trigger scripts any more after booting

2017-11-06 Thread Guus Sliepen
Am 06.11.2017 um 17:53 schrieb Narcis Garcia:

> Interface is declared at /etc/network/interfaces :
> auto enp2s0
> allow-hotplug enp2s0
> iface enp2s0 inet dhcp
> 
> An executable script:
> /etc/network/if-up.d/test1
> only runs on boot (per each NIC). If network cable is plugged to enp2s0
> some minutes later, script is not run.
> Same behavior when booting with network, and unplugging + plugging later.

Hotplug in the context of udev is the hotplugging of a hardware PCI or USB 
device,
not of a network cable. If you want to have a network interface brought
up or down whenever a cable is (un)plugged, try installing the netplug
package, edit /etc/netplug/netplugd.conf and add enp2s0 to it, and
remove both "auto enp2s0" and "allow-hotplug enp2s0" from
/etc/network/interfaces.

Note that cable (un)plug events might not be properly supported by all
network cards.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Bug#880982: ifup does not trigger scripts any more after booting

2017-11-06 Thread Michael Biebl
Control: reassign -1 ifupdown

Am 06.11.2017 um 17:53 schrieb Narcis Garcia:
> Package: udev
> Version: 232-25+deb9u1
> Severity: serious
> 
> Tested with updated Debian 9 (amd64):
> 
> Interface is declared at /etc/network/interfaces :
> auto enp2s0
> allow-hotplug enp2s0
> iface enp2s0 inet dhcp
> 
> An executable script:
> /etc/network/if-up.d/test1
> only runs on boot (per each NIC). If network cable is plugged to enp2s0
> some minutes later, script is not run.
> Same behavior when booting with network, and unplugging + plugging later.

udev does not longer ship the ifupdown agent, so I'm reassigning this to
ifupdown.

Regards,
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


Bug#880982: ifup does not trigger scripts any more after booting

2017-11-06 Thread Narcis Garcia
Package: udev
Version: 232-25+deb9u1
Severity: serious

Tested with updated Debian 9 (amd64):

Interface is declared at /etc/network/interfaces :
auto enp2s0
allow-hotplug enp2s0
iface enp2s0 inet dhcp

An executable script:
/etc/network/if-up.d/test1
only runs on boot (per each NIC). If network cable is plugged to enp2s0
some minutes later, script is not run.
Same behavior when booting with network, and unplugging + plugging later.


-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.