On Sun, Oct 13, 2019 at 11:05:23AM +0100, Alex DEKKER wrote: > This is what happens without dad-attempts 0 on br0: > [...] > Oct 13 10:31:31 westogre ifup[1521]: run-parts: executing > /etc/network/if-up.d/mountnfs > Oct 13 10:31:31 westogre systemd[1]: networking.service: Main process > exited, code=exited, status=1/FAILURE > Oct 13 10:31:31 westogre pppd[2055]: Terminating on signal 15 [...] > Oct 13 10:31:31 westogre pppd[2055]: Exit. > Oct 13 10:31:31 westogre systemd[1]: networking.service: Failed with result > 'exit-code'.
I think the issue is that systemd kills the pppd process when ifup
reports an error bringing up br0. And that's probably because ppp0 was
brought up during startup of the networking service, and thus systemd
keeps track of all processes spawned at that time.
A possible workaround is to make ppp0 bringup not part of the network
initialization, but rather during the "hotplug" event of eth3. So
instead of having:
auto ppp0
iface ppp0 inet ppp
...
Write this:
allow-hotplug eth3
iface eth3 inet manual
mtu 1508
up ifup ppp0
down ifdown ppp0
iface ppp0 inet ppp
provider provider
post-up sh /root/firewall/delayed-post-up.sh
Note that hotplug doesn't mean when the cable is plugged in, it means
when the system detects the network card hardware. And for a built-in
network card, it detects it at boot time. So effectively you still get
ppp0 brought up at boot time this way.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: PGP signature
