Addressed review on https://github.com/vyos/vyos-1x/pull/5342 (e17b4e433):
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 20 2026
Addressed review on https://github.com/vyos/vyos-1x/pull/5341 (e1d43131f):
Addressed review on https://github.com/vyos/vyos-1x/pull/5340 (fe9ceb1ac):
Aug 19 2026
add sys-rawio :
@Viacheslav if we could merge it soon that would be fantastic: https://github.com/vyos/vyos-1x/pull/5418
Aug 18 2026
Hey @Viacheslav, sure, why not, give me a couple of days.
Commit for this is in my own fork until VyOS catches up to FRR 10.7: https://github.com/jvoss/vyos-1x/commit/b3f0f77de5fef0a380f015c21e739198d8a4598c
@ebowsky would you like to claim the task and add a PR?
Aug 17 2026
I second that it should be at least well documented that setting this sysctl is required to allow non local binds. I had to introduce a check for it being active in my PR solving a regression with HAProxy (and other services relying on the same code path) here: https://github.com/vyos/vyos-1x/pull/5266
@jestabro can we close it?
Implemented in https://github.com/vyos/vyos-build/pull/1222
vyos-1x PR https://github.com/vyos/vyos-1x/pull/5412
Aug 16 2026
I can still reproduce the AES-GCM issue on a newer build.
Aug 15 2026
I stumbled across the same issue and as far as i could debug it, its due to usb/hid devices being outosuspended by the current vyos kernel/config.
Thanks for catching this, a.kudientsov — and sorry for the regression. The mistake was narrowing the bare except: in fqdn_resolve() to except gaierror: based on the assumption that getaddrinfo() only ever raises gaierror, without checking that other OSErrors (e.g. transient network failures) can hit the same call and need to keep being
swallowed here too. c-po's fix in #5406 (back to except OSError:, since gaierror is a subclass) looks correct to me.
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.
Thanks for looking into this and merging the patch.