The issue was fixed with update container image vyos/vyos-build:current to the latest
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 29 2023
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”
Jun 28 2023
@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
Jun 27 2023
This would be a great feature to have on VyOS.
PR Equuleus: https://github.com/vyos/vyos-build/pull/368
Jun 26 2023
PR for equulues https://github.com/vyos/vyos-1x/pull/2058
Jun 25 2023
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.
Jun 24 2023
if len(config.get('interface', [])) < 2 or len(config.get('interface', [])) > 2:
raise ConfigError('Only two interfaces are required for udp broadcast relay "{instance}"')