In T4989#144426, @MartB wrote:

set qos policy shaper test bandwidth 100mbit
set qos policy shaper test class 10 bandwidth 50%

It wont be used right now if I add a class that uses a percentage, it will always use the interface speed.
The base __rate_convert should include some check if the "base" speed was already set.

Fix for match protocol https://github.com/vyos/vyos-1x/pull/2047

PR https://github.com/vyos/vyos-1x/pull/2047

It expects ip protocol 1 instead of 'ip protocol icmp' in tc
wrong generation for protocols

PR https://github.com/vyos/vyos-1x/pull/2046

https://github.com/vyos/vyos-build/pull/363

After reboot, I connect to the node and execute reboot again without any config change
But I still see a Warning, that looks like a bug in this case.

PR:
https://github.com/vyos/vyos-1x/pull/2045

If class['bandwidth'] == auto then we should get global bandwidth

PR https://github.com/vyos/vyos-1x/pull/2044
Config

The same config in 1.3 doesn't have tc filter in 1.3

It's time to separate this task into subtasks.

Should be possible when new refactor is merged: T5160

This would have to be handled with DNS and not in the firewall. Hostnames work on firewall because they are resolved prior to use in rules.

It fails on the server. I have reproduced the issue in our internal lab. Will share the details.

Don't see errors with this configuration:

set interfaces ethernet eth1 vif 11 address '192.0.2.2/24'
set interfaces input ifb0 description 'WAN Ingress'

vhost modules are not included to kernet

I've found the reason why this command fails, it' happens because the logic to match the dscp parameter is missing. So, it tries to apply the basic policy with the tc filter parameters by default :

Wow! Glad to see its moving on!

Thanks!

PR: https://github.com/vyos/vyatta-cfg/pull/65

That did fix the issue. So how do I get that change in the main code?

PR https://github.com/vyos/vyos-1x/pull/2042

set service config-sync mode 'load'
set service config-sync secondary address '192.168.122.11'
set service config-sync secondary key 'foo'
set service config-sync section 'nat'

You can try edit with sudo nano /opt/vyatta/sbin/vyatta-cfg-cmd-wrapper

Nope it hasn't, you skim read the bug report.

Your current version is too old, this function has been changed or removed, try upgrading to the new rolling version.

From my testing, all traffic that originates from an interface attached to a VRF, will show the source interface as the VRF master interface, regardless of the zone attached to that interface. This will make it difficult to segment traffic between interfaces attached to the same VRF. For example:

PR: https://github.com/vyos/vyos-1x/pull/2041

I opened an issue on github:

Hi @jestabro I saw that feature request but I wasn't sure. Thank you!

cf. https://vyos.dev/T5249, currently being assessed.

Thanks, @jestabro
It works in my tests!!