severity 879518 normal thanks On Sun, Oct 22, 2017 at 04:35:58PM +0200, Daniel wrote:
> Severity: critical
> Justification: breaks the whole system
Downgrading to normal since this bug doesn't fit the definition of
critical:
“Makes unrelated software on the system (or the whole system) break, or
causes serious data loss, or introduces a security hole on systems where
you install the package.”
> This setup was perfectly running on Jessie. After upgrading to Stretch, all
> the network stuff was down, doesn't matter if local, VMs or Internet.
> In the interfaces file below we changed the bridge-stp to off to get rid from
> the "set forward delay failed: Numerical result out of range" error.
> After this, interface bone was going up as well as eth0 but then we had the
> parent-lock error. We commented the pre-up bone[.1|.2] on each interface who
> call them
> and the system started with all interfaces up.
I see. Locking interfaces indeed prevents a VLAN interface from calling ifup on
its parent interface. It's actually with good reason; while it may have
worked on your bridge interface, it's not guaranteed to work correctly,
and it will break in situations where interface are created on demand
(like with tun/tap interfaces).
That said, it's of course necessary for the parent interface to be up
before you can bring up a VLAN interface. So I'll probably change
ifupdown to do that for you. That way, you won't need pre-up ifup
statements anymore.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: PGP signature
