This is resolved in T5923; any other related concerns, reopen or open a new task.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feb 8 2024
This path was changed as part of the task T3642.
The new path is generate pki wireguard key-pair, we can easily translate the old path to the new in these cases, but do we need backward compatibility here?
Looks like this path was marked as deprecated more than two years ago(Sept 21) and dropped a little bit more than one year ago(Dec 22).
Perhaps it is enough to simply update the documentation?
Feb 7 2024
PR for equuleus https://github.com/vyos/vyatta-cfg/pull/73
PR for sagitta https://github.com/vyos/vyos-1x/pull/2940
I also see this behavior when switching between images in 1.4.0-rc3" and sometimes default-boot setting does not work.
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
+ }
+}Feb 6 2024
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?
Feb 5 2024
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
Feb 4 2024
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.