Traffic Policy Removal When Disabling Interfaces in VyOS

I’ve encountered an issue in VyOS where disabling an interface causes any associated traffic policies (such as QoS configurations) to be automatically removed. This is problematic since these settings are crucial for managing network traffic, and they don’t seem to automatically reapply when the interface is re-enabled.

  • Is this the expected behavior in VyOS, or am I missing something?
  • Are there any best practices to ensure that traffic policies persist or are automatically restored after the interface is re-enabled?
  • Has anyone else experienced this, and how have you dealt with it in your setups?

I would appreciate any insights or suggestions from the community to avoid having to manually reconfigure traffic policies each time an interface is disabled and re-enabled.

Which version? If you can reproduce it on 1.5 open a bug report (https://vyos.dev/) with steps to reproduce

1 Like

I apologize for not providing a test environment earlier. I’m using VyOS version 1.3.

Here’s my QoS configuration:

set traffic-policy shaper shaper_001 bandwidth '4mibit'
set traffic-policy shaper shaper_001 class 10 bandwidth '100%'
set traffic-policy shaper shaper_001 default bandwidth '20%'
set traffic-policy shaper shaper_001 default burst '1000k'

When I applied this configuration to the l2tpeth3001 interface with the following command:

set interfaces l2tpv3 l2tpeth3001 traffic-policy out shaper_001

everything worked as expected. However, after running:

set interfaces l2tpv3 l2tpeth3001 disable

and saving the configuration, I noticed that the QoS settings for the interface were removed, as shown in the attached screenshot. (please see the attached screenshot)

I’ve reviewed various sources, and some suggest that removing an interface could lead to dynamic configurations like QoS being cleared, which might be normal behavior. However, the QoS configuration still persists in the VyOS configuration mode (in conf), which leads me to wonder if this is a bug or intended behavior. Any insights would be appreciated. Thank you!

I apologize for not providing a test environment earlier. I’m using VyOS version 1.3.

Here’s my QoS configuration:

set traffic-policy shaper shaper_001 bandwidth '4mibit'
set traffic-policy shaper shaper_001 class 10 bandwidth '100%'
set traffic-policy shaper shaper_001 default bandwidth '20%'
set traffic-policy shaper shaper_001 default burst '1000k'

When I applied this configuration to the l2tpeth3001 interface with the following command:

set interfaces l2tpv3 l2tpeth3001 traffic-policy out shaper_001

everything worked as expected. However, after running:

set interfaces l2tpv3 l2tpeth3001 disable

and saving the configuration, I noticed that the QoS settings for the interface were removed, as shown in the attached screenshot. (please see the attached screenshot)

I’ve reviewed various sources, and some suggest that removing an interface could lead to dynamic configurations like QoS being cleared, which might be normal behavior. However, the QoS configuration still persists in the VyOS configuration mode (in conf), which leads me to wonder if this is a bug or intended behavior. Any insights would be appreciated. Thank you!