@daniil could you re-check?

set qos interface eth0 ingress '1G-in'
set qos policy limiter 1G-in default bandwidth '1gbit'
set qos policy limiter 1G-in default burst '125000000b'

Could you explain the use case?
Can you archive it with the class?

vyos@r14# set qos policy limiter test class video match 1 ip dscp 
Possible completions:
   <0-63>               Differentiated Services Codepoint (DSCP) value
   default              match DSCP (000000)
   reliability          match DSCP (000001)
   throughput           match DSCP (000010)
   lowdelay             match DSCP (000100)
   priority             match DSCP (001000)
   immediate            match DSCP (010000)
   flash                match DSCP (011000)
   flash-override       match DSCP (100000)
   critical             match DSCP (101000)
   internet             match DSCP (110000)
   network              match DSCP (111000)
   AF11                 High-throughput data
   AF12                 High-throughput data
   AF13                 High-throughput data
   AF21                 Low-latency data
   AF22                 Low-latency data
   AF23                 Low-latency data
   AF31                 Multimedia streaming
   AF32                 Multimedia streaming
   AF33                 Multimedia streaming
   AF41                 Multimedia conferencing
   AF42                 Multimedia conferencing
   AF43                 Multimedia conferencing
   CS1                  Low-priority data
   CS2                  OAM
   CS3                  Broadcast video
   CS4                  Real-time interactive
   CS5                  Signaling
   CS6                  Network control
   CS7                  None
   EF                   Expedited Forwarding

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

@aztec102 Do you have build kernel again?

Good afternoon
Unfortunately it didn't help.

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

The policy route works only with an interface (inbound direction) and doesn't work otherwise.
It's always been like this.

In T5324#151418, @greenpsi wrote:

I think I found the real problem:

The 62-temporary-interface-rename.rules udev rule runs in initramfs before the USB modem is detected:

Jun 30 14:32:11 vyos kernel: r8169 0000:03:00.0 e3: renamed from eth1
Jun 30 14:32:11 vyos kernel: r8169 0000:02:00.0 e2: renamed from eth0

[...]

Jun 30 14:32:11 vyos kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
Jun 30 14:32:11 vyos kernel: ata2: SATA link down (SStatus 4 SControl 300)
Jun 30 14:32:11 vyos kernel: ata1: SATA link down (SStatus 4 SControl 300)
Jun 30 14:32:11 vyos kernel: usb 1-1: New USB device found, idVendor=12d1, idProduct=1f01, bcdDevice= 1.02
Jun 30 14:32:11 vyos kernel: usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
Jun 30 14:32:11 vyos kernel: usb 1-1: Product: HUAWEI HiLink
Jun 30 14:32:11 vyos kernel: usb 1-1: Manufacturer: HUAWEI

So the modem does not get renamed to eX and thus, if the modem has an ethX name that conflicts with the configuration from the 65-vyos-net.rules udev rule, the renaming of the interfaces from eX to ethX fails because a duplicate already exists.

So in conclusion, if VyOS wants to support USB Ethernet devices, the 62-temporary-interface-rename.rules udev rule should be deferred until the USB devices are detected or something like that.

It did work in the test enviroment, I just returned from a long vacation and will be deploying that update to some production boxes and enabling it on there tomorrow.

Yes, checked it working, please closed it.

@ServerForge Could you check if it works as expected?
If yes you can close it.

@cuongdt1994 Could you check it? If it works as expected, we can close it.

Requires to rewrite PIM to get_config_dict https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/protocols_pim.py

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

set qos interface eth0 egress 'test'
set qos policy shaper test bandwidth '300mbit'
set qos policy shaper test class 23 bandwidth '150mbit'
set qos policy shaper test class 23 match one ip protocol 'tcp'
set qos policy shaper test class 23 match two ip protocol 'udp'
set qos policy shaper test default bandwidth '20mbit'
set qos policy shaper test default queue-type 'fair-queue'
commit

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

set qos interface eth0 ingress '300m-in'
set qos policy limiter 300m-in default bandwidth '300mbit'
set qos policy limiter 300m-in default burst '125000000b'
commit

The IPv6 reverse path filter functionality would be great if it worked properly.
On the other hand, the current sysctl based solution does not allow for adding exceptions.

I think I found the real problem:

Thank you very much, I compiled the image, now it remains only to check.
As soon as I check, I will write.

Hi @vfreex . The idea is to add this feature, and several more, once we get new firewall cli structure: https://github.com/vyos/vyos-1x/pull/2016

The above setting works and also if configured like this:

Try set protocols bgp neighbor eth1 interface remote-as xxx

Same in https://forum.vyos.io/t/need-some-help-troubleshooting-nic-detection/11291/15

I was able to test this for ISIS. I'll test OSPF hopefully tomorrow.

In rolling release, it does not accept remote-as configured as a part of peer-group, commit error is received:

I opened PR https://github.com/vyos/vyos-1x/pull/2062 for this.

The issue was fixed with update container image vyos/vyos-build:current to the latest

I found the following log in /run/udev/log/vyos-net-name from the vyos_net_name python script:

In T5324#151306, @Viacheslav wrote:

e2 it is a temporary name to rename ethX in correct way
You have to use “ethernet ethX address x.x.x.x”

I found invalid interface name with lastest build (fresh install and none configuration)

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

I found your devices supported but I need build and check again.

@aztec102 please show version running.

e2 it is a temporary name to rename ethX in correct way
You have to use “ethernet ethX address x.x.x.x”

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

@apasheev it were rewritten in https://github.com/vyos/vyos-1x/pull/1567/files#diff-7839502816137d55f673c064e6ec87a2eed7dc80563b1e307363c3e4b090a2b3R302

set policy route-map FOO rule 10 set extcommunity rt '1111:2222222'
set policy route-map FOO rule 10 set extcommunity rt '33:444'
set policy route-map FOO rule 10 action permit

PR https://github.com/vyos/vyos-1x/pull/2059
PR https://github.com/vyos/vyos-build/pull/369

This would be a great feature to have on VyOS.

PR Equuleus: https://github.com/vyos/vyos-build/pull/368

PR for equulues https://github.com/vyos/vyos-1x/pull/2058