If we do not have RPKI in configuration, it also tries to start RPKI, is it expected?
Feb 07 16:00:53 r4 vyos-router[3545]: Could not start rpki because no caches are configured Feb 07 16:07:06 r4 vyos-router[3751]: Could not start rpki because no caches are configured
For 1.3 build fails
06:44:06 Unpacking vyos-1x (1.3dev0-4068-ga685e55f3) ... 06:44:06 dpkg: error processing archive /tmp/apt-dpkg-install-FMRTXF/480-vyos-1x_1.3dev0-4068-ga685e55f3_amd64.deb (--unpack): 06:44:06 trying to overwrite '/lib/systemd/system/keepalived.service', which is also in package keepalived 1:2.2.8 06:44:06 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
We probably need to remove keepalived.service as we implemented 10-override and generated it via render
cpo@LR1.wue3# set firewall group address-group test123 description foo
cpo@LR1.wue3# set firewall group address-group test123 address 1.2.3.4
cpo@LR1.wue3# comment firewall group address-group test123 address baz
[edit]
cpo@LR1.wue3# show firewall
+group {
+ address-group test123 {
+ /* baz */
+ address 1.2.3.4
+ description foo
+ }
+}thx for the backport @c-po runs fine on 1.3 rolling.
Just a note: with such tasks, we should always add context — why is the upgrade done. Is it for vulnerabilites? If yes, which CVEs? Is it for bug fixes? If yes, which bug report number? Is it to unblock a path to implementing new features and which ones?
PR https://github.com/vyos/vyos-1x/pull/2945
set firewall group address-group ONE address 192.0.2.1 description 'First' set firewall group address-group ONE address 192.0.2.2 description 'Second'
What version? Can you upgrade to 1.4?
One of my router heavily affected by this issue, so if you will wrote a fix - you may ask me to test the fix.
It seems FRR (9.0.2-36-g31dec1951) does not support this.
The route can be added, but no route is in the routing table.
vyos@r4:~$ vtysh -c "conf t" -c "ip route 192.0.2.0/24 2001:db8::1" vyos@r4:~$ vyos@r4:~$ vtysh -c "show run" | match 192.0.2.0 ip route 192.0.2.0/24 2001:db8::1 vyos@r4:~$ vyos@r4:~$ vyos@r4:~$ show ip route 192.0.2.0/24 % Network not in table vyos@r4:~$
PR for 1.5 https://github.com/vyos/vyos-build/pull/493
PR for 1.3 https://github.com/vyos/vyos-build/pull/494
Update supports via whitespace
r4(config-router)# neighbor foo path-attribute discard 23 24
FRR does not support it
r4# conf t r4(config)# router bgp 65001 r4(config-router)# no bgp ebgp-requires-policy r4(config-router)# no bgp default ipv4-unicast r4(config-router)# no bgp network import-check r4(config-router)# neighbor foo peer-group r4(config-router)# neighbor foo path-attribute discard 24 r4(config-router)# neighbor foo path-attribute discard 23,24 % Unknown command: neighbor foo path-attribute discard 23,24 r4(config-router)#
This type of configuration works perfectly fine with VyOS 1.5 when receiving routes from a BGP peer (v4 routes with v6 nexthop), so it would be very nice to be able to manually install routes in the same way.
Its not clear if its fixed or not: