PPPoE Interface with QOS fails to be created on boot

when applying qos to a pppoe interface the whole interface is lost on a reboot because vyos tries (and fails) to apply the qos settings before the interface is created/up.


Version:          VyOS 1.3-rolling-202007012118
Release Train:    equuleus

Built by:         autobuild@vyos.net
Built on:         Wed 01 Jul 2020 21:18 UTC
Build UUID:       78616a71-1a47-4efd-88a0-295ee5ee1721
Build Commit ID:  49ca3d22e87449

Architecture:     x86_64
Boot via:         installed image
System type:      bare metal

Hardware vendor:  FUJITSU
Hardware model:   ESPRIMO P700
Hardware S/N:     Unknown
Hardware UUID:    Unknown

Copyright:        VyOS maintainers and contributors

Relevant config:

set interfaces pppoe pppoe0 connect-on-demand
set interfaces pppoe pppoe0 default-route 'auto'
set interfaces pppoe pppoe0 idle-timeout '0'
set interfaces pppoe pppoe0 mtu '1492'
set interfaces pppoe pppoe0 redirect 'ifb0'
set interfaces pppoe pppoe0 source-interface 'bond0.7'
set interfaces pppoe pppoe0 traffic-policy out 'wan-out'
set interfaces input ifb0 traffic-policy out 'wan-in'

Oh, yes, thank you for reporting.

The problem does not seem to be related to QoS, but to redirecting PPPoE traffic through the Intermediate Functional Block. Booting VyOS with such a redirection deletes the redirected PPPoE interface.

I will test it on Crux too and submit a bug report.

You can follow up here.

Hey @s.lorente,
thanks for confirming and for the bug report!