vyos-1x.git/src/services, branch rolling

vpp: T9161: Fix smoketests failing on NICs capped at 1500 MTU

2026-10-09T11:37:43+00:00

VPP now rejects an MTU above the NIC limit, but the CI NICs are capped at 1500, so tests using MTU 2500 on eth1 failed. The rejected commit also left a queued initial VPP dependency in the commit daemon, which the next commit ran with the old config, so every following test failed too. Pending initial dependents are now cleared before each script run in vyos-configd and vyos-commitd, and the tests use MTUs that fit any NIC.

frrender: T9368: reconcile FRR after a DHCP lease without the commit socket

2026-10-07T17:59:13+00:00

Reconciling the FRR configuration after a DHCP lease event was requested from the configuration daemon over the socket the commit pipeline uses. The daemon serves one client at a time and assumes it is the running commit, so the request either landed in the middle of the handshake which hands over the configuration, or kept the daemon busy past the 10ms a commit waits for it. Either way the commit fell back to running the conf-mode scripts directly. Those never render FRR, only the daemon does, so the commit succeeded while FRR kept the configuration rendered before it, until the next lease event. A lease event now renders FRR in its own process, and a commit which could not use the daemon renders FRR itself instead of skipping the reload. Both take the same lock. A commit post-hook would remove the second case, for a full render on every commit.

Merge pull request #5491 from omnom62/T8989-hotfix-oidc_aud_validation

2026-09-29T19:07:04+00:00

http-api: T8989: Hotfix to enforce audience validation if OIDC is configured

Merge pull request #5499 from c-po/wwan-improvements

2026-09-29T04:42:46+00:00

wwan: T9350: possible dead interface after boot, disconnect does not stick

https: T8989: Hotfix to enforce audience settings with OIDC is configured

2026-09-28T20:58:05+00:00

Merge pull request #5503 from c-po/T9354

2026-09-28T19:18:12+00:00

op-mode: T9354: replace "reset connection" with "reconnect interface"

vyos.utils: T8977: let a caller accept a non-local address as assigned

2026-09-26T07:46:08+00:00

Whether an address may be bound is not the same question as whether it is currently configured somewhere: the kernel permits binding a foreign address once the non-local bind sysctl is set, which is how a failover address is commonly handed over after the commit. Callers can now opt into that, the default is unchanged. A lookup no longer skips the VRF device itself, which carries the addresses of its own L3 domain, and an interface name can be retrieved for an address without the caller asking a yes/no question in the first place. Address and range validation is split into separate checks, so a caller no longer has to accept ranges where only an address is meaningful. The two duplicated version checks are dropped in favour of the existing ones. Co-authored-by: Christian Breunig

op-mode: T9354: replace "reset connection" with "reconnect interface"

2026-09-25T19:02:06+00:00

"connect interface" and "disconnect interface" cannot be combined to restart a dialer interface when the CLI session runs over that very interface, yet the command which does cover it was filed under an unrelated top-level node and was hard to find. It is now "reconnect interface ", mirroring the existing connect and disconnect commands. "reset connection" is removed, no alias is kept. The removed command was reachable through the REST API as a "reset" path. A dedicated "/reconnect" endpoint takes its place, so the operation stays available to API consumers.

wwan: T9350: wait for the modem to become dialable, not merely listed

2026-09-24T19:48:13+00:00

A modem is on the bus while still probing, so a dial could start too early and leave the interface without a session until something re-dialled it.

wwan: T9350: properly disconnect "disconnect interface wwanN"

2026-09-24T15:27:27+00:00

Two things kept an operator disconnect from taking effect. vyos-netlinkd re-dials every configured WWAN interface that has lost its session. It cannot tell a session lost to RF signal loss from one that was taken down on purpose, so the disconnect was undone on the next reconcile pass, at most 30 seconds later: $ disconnect interface wwan0 08:53:33 t+10s state=registered 08:53:43 t+20s state=registered 08:53:53 t+30s state=connected <- re-dialled 08:54:03 t+40s state=connected vyos-netlinkd: WWAN interface wwan0 is not connected, re-dialling... vyos-netlinkd: Re-dialled WWAN interface wwan0 Record the intent instead of inferring it from the session state. op-mode "disconnect" drops a marker in /run/vyos-wwan, which _reconcile_wwan() honours and "connect" removes again. conf_mode removes it too, so a commit keeps re-asserting the configured state - the marker only survives for as long as nobody says otherwise, and never across a reboot.