If you add this config after the server is configured, it works as it requires a restart of the service
sudo systemctl restart accel-ppp@pppoe.service
Or reconfigure the service again
If you add this config after the server is configured, it works as it requires a restart of the service
sudo systemctl restart accel-ppp@pppoe.service
Or reconfigure the service again
@L0crian Some TC combinations are affected by locks, so they are impossible to use with, for example, /16 networks.
Add the set of commands to reproduce.
Should be fixed in T6373
Great work, thanks for checking that case too.
This is without my patch applied, confirming both the problem and a workaround:
If possible, can you try duplicating with more than one vni configured, then delete one of them? I'm pretty sure I tried that case a few weeks ago on an older 1.4 rolling with same issue. This was just the minimum config to reproduce.
The command option exists for peer groups in the docs and CLI, but it doesn't appear to actually be able to be applied to a peer group, so this may actually be irrelevant now.
Created PR:
NFT rate-limiting is effectively a policer instead of a shaper, so I don't think it'd be a good way to accomplish this. All drops would be aggressive and not tail-drops.
Also the config section could perhaps be name "custom" (with subsections) so that section will survive an upgrade aswell - otherwise config lines will vanish during boot/commit.
Duplicate
On testing, it looks like vyos.utils.network.get_vxlan_vni_filter() doesn't know how to handle when there are no vni filters installed.
I've created a quick PR to give sane feedback from the validator: https://github.com/vyos/vyos-1x/pull/3572
Tested as working in: VyOS 1.5-rolling-202405310019
I've created a PR for this that fixed a mistake with my original patch: https://github.com/vyos/vyos-1x/pull/3570