User Details
- User Since
- Jul 29 2025, 9:33 AM (68 w, 3 d)
Tue, Nov 17
Sun, Nov 15
Sat, Nov 14
Thu, Nov 12
Wed, Nov 11
@hedrok Smallest case I have is two plain FRR routers, no VyOS. r2 (AS 65002) announces 10 prefixes to r1 (AS 65001); r1 has no soft-reconfiguration inbound, so each inbound policy change shows up as one ROUTE-REFRESH that r1 sends. Every change on r1 is made with frr-reload.py --reload <file>. Measured on FRR 10.5.2.
Tue, Nov 10
Mon, Nov 9
Thu, Nov 5
Mon, Nov 2
Fri, Oct 30
Testing confirmed two ways to fix the duplicate DHCPOFFER from the VLAN parent:
Thu, Oct 29
Reproduced on rolling with openvpn 2.7.7, on a lightly loaded lab router in client mode: set interfaces openvpn vtun31 description <x> + commit on a running client gives
Wed, Oct 28
Mon, Oct 26
Oct 20 2026
Oct 19 2026
@rherold
Same result: no stuck VLAN in any test, including 15 full-table bond rebuilds each. The PR now uses the MTU-only variant: deferring the sync lost MTU changes made in VPP when several resync rounds failed in a row, and the MTU-only change kept them.
Yes: vppctl lcp resync alone, with no routes and the full buffer, left the VLAN stuck every time. T9484 only makes the overflow less likely.
Oct 18 2026
Oct 13 2026
Oct 9 2026
Oct 8 2026
Oct 7 2026
Oct 6 2026
Oct 5 2026
Oct 4 2026
Oct 1 2026
@jestabro added a pr - https://github.com/vyos/vyos1x-config/pull/95
Sep 18 2026
Sep 9 2026
@canoziia Hi! Please check if the latest nightly build resolves the issue you described - https://vyos.net/get/nightly-builds/
Aug 20 2026
Aug 15 2026
Subject fix causes firewall fqdn/domain-group regression. It narrowed fqdn_resolve() exception handling in from a bare except: statement to except gaierror:, claiming "no behavior change." That let non-gaierror OSErrors (e.g. transient network errors right after commit) escape uncaught, crashing the unguarded main loop of the vyos-domain-resolver daemon, the process that fills in D_* (domain-group) nftables sets.