Today
Sun, Jul 6
It’s completely doesn’t work even with PBRD https://github.com/FRRouting/frr/issues/3160 (I didn’t check)
Fri, Jul 4
Tue, Jul 1
Sat, Jun 28
Fri, Jun 27
Thu, Jun 26
$ sudo nft add element inet vrf_zones ct_somethingelse_map { "vni" : 100 } Error: syntax error, unexpected vni add element inet vrf_zones ct_somethingelse1_map { vni : 100 } ^^^
Thu, Jun 19
Wed, Jun 18
Mon, Jun 16
Use flowtable on all interfaces including tun.
Sat, Jun 14
I have not tested this in the latest version (1.5), so please excuse me if the issue has already been fixed there.
Fri, Jun 13
Version: VyOS 1.4.2
Release train: sagitta
Release flavor: generic
We are moving from legacy OpenNHRP (which is unmaintained) to an FRR solution.
Could you check the rolling release? It uses FRR nhrpd.
Could you send the minimum "set of commands" to reproduce?
Do you use a flowtable on tun or ethernet only?
Thu, Jun 12
Wed, Jun 11
Tue, Jun 10
Jun 8 2025
An easy mitigation is to just update the command that is run to:
journalctl --no-hostname --boot -k | grep "ipv4-NAM-${6:0:15}"The only issue with this as the only solution, is you could lose granularity in logging if you were to have names like:
test-test-test-1 test-test-test-2
Running show log firewall ipv4 name test-test-test-1 would return log entries for both names since the string would be ipv4-NAM-test-test-test-. That's where a warning could come into play, stating it is recommended to keep names to no more than 15 characters.
Jun 6 2025
Jun 5 2025
Need to check with the latest rolling release, as we have more flexibility in the bridge firewall. But command set interfaces bridge br0 ip adjust-mss '1377', with no extra config, most probably won't have desired effect.
Jun 4 2025
Jun 2 2025
Probably another task, but nice to have reset all connections soft in and soft out
vyos@r14:~$ reset ip bgp all Possible completions: <Enter> Execute the current command