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:
That fixes it. It does seem like more of a band-aid solution though. I don't want to have to do that for every router I deploy using this setup
Wireguard is not yet exists in the system when tun is already exists due to priority
vyos@r14:~$ /opt/vyatta/sbin/priority.pl | match "tun|wireguard" 380 interfaces/tunnel 381 interfaces/wireguard
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
I was able to test this for ISIS. I'll test OSPF hopefully tomorrow.
vyos@vyos:~$ show version Version: VyOS 1.4-rolling-202306270317 Release train: current
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)
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”
@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
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
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2057
Actually this uncovered a "bug" that there is no verify() section that validates if the configured interfaces actually have an IP address configured.
if len(config.get('interface', [])) < 2 or len(config.get('interface', [])) > 2:
raise ConfigError('Only two interfaces are required for udp broadcast relay "{instance}"')