I think I found the real problem:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 30 2023
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:
Jun 29 2023
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”
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}"')Jun 23 2023
Just tested again with 1.3.3. When setting set firewall send-redirects enable, ICMP redirects work fine until I reboot the router.
Before rebooting:
root@vyos:~# sysctl -a | grep send_redirect net.ipv4.conf.all.send_redirects = 1 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.eth0.send_redirects = 0 net.ipv4.conf.eth1.send_redirects = 0 net.ipv4.conf.eth2.send_redirects = 0 net.ipv4.conf.eth3.send_redirects = 0 net.ipv4.conf.lo.send_redirects = 0 net.ipv4.conf.wg0.send_redirects = 0
After rebooting:
root@vyos:~# sysctl -a | grep send_redirect net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.default.send_redirects = 0 net.ipv4.conf.eth0.send_redirects = 0 net.ipv4.conf.eth1.send_redirects = 0 net.ipv4.conf.eth2.send_redirects = 0 net.ipv4.conf.eth3.send_redirects = 0 net.ipv4.conf.lo.send_redirects = 1 net.ipv4.conf.wg0.send_redirects = 0
Jun 22 2023
This problem still exist on VyOS 1.4-rolling-202306070317
@fernando It seems related task https://vyos.dev/T5302
I'm also encountering this issue on the latest rolling release.