PR: https://github.com/vyos/vyos-1x/pull/5523
doc PR: https://github.com/vyos/vyos-documentation/pull/2324
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Today
Today
Yesterday
Yesterday
@mrpops2ko FYI the MTU problem I described was addressed in https://vyos.dev/T9364 . Can you give the latest rolling another try, if have a chance to?
In any case, please report any faulty findings in a new task, so we can take it from there.
We reviewed this issue and are planning to submit a documentation pull request for it this afternoon.
eli-sterling added a comment to T7371: VyOS DHCP Server shared-network concept and behaviour is not properly documented.
We reviewed this issue and are planning to submit a documentation pull request for it this afternoon.
eli-sterling added a comment to T9089: vyos-api docs: document /retrieve showConfig behavior on empty or missing subtrees (HTTP 400).
Verification update: the current rolling API guide documents that showConfig returns HTTP 400 when a schema-valid path has no configuration, gives the "Configuration under specified path is empty" response, and recommends checking exists first or treating that exact error as empty configuration: https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#retrieve. This guidance appears in commit https://github.com/vyos/vyos-documentation/commit/3a952350bf5b5b38a7db1208ed3c910ded7b4b24. This appears to address T9089. Suggested status: Resolved if the task author or a maintainer confirms the documentation meets scope.
eli-sterling added a comment to T9088: vyos-api docs: document /show with path ["configuration","commands"] (set-command export).
Verification update: the current rolling API guide documents /show with path ["configuration", "commands"] as exporting the running configuration to flat set commands, and includes an example response: https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#show. This guidance appears in commit https://github.com/vyos/vyos-documentation/commit/ca902d4eebd49697f476d538eadfcaeb8ebb2232. This appears to address T9088. Suggested status: Resolved if the task author or a maintainer confirms the documentation meets scope.
eli-sterling added a comment to T9087: vyos-api docs: document commit atomicity — multi-field nodes must be set in one /configure request.
Verification update: the current rolling API guide states that each /configure request is committed immediately and that fields of a single configuration node must be included in the same request. It gives task-scheduler, NAT, and firewall examples plus related validation errors: https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#configure. This guidance appears in commit https://github.com/vyos/vyos-documentation/commit/0b88b491d043e5f281d8e3ae499c4d045da28f28. This appears to address T9087. Suggested status: Resolved if the task author or a maintainer confirms the documentation meets scope.
eli-sterling added a comment to T9092: vyos-api docs: add operational guidance for large configuration applies (batch sizes, geoip cost, body-size limit).
Review update: T9092 appears partially completed in the current rolling API guide. Its Bulk configuration section covers moderate-sized batches, reconciling state after request timeouts, applying geoip/remote-group operations one per request, the default 1 MB request-body limit, and commit-confirm as a safeguard: https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#bulk-configuration. This guidance was added in commit https://github.com/vyos/vyos-documentation/commit/af04731c74b0383bc36c66addd6cc22ba41c55e0. The task also asks to direct bulk-apply users to the REST API background configure operations; I could not find that guidance in the current API guide. Suggest keeping T9092 open until that point is documented or the reporter confirms it is unnecessary.
eli-sterling added a comment to T9091: vyos-api docs: document error semantics of batched /configure arrays (failing op not identified).
Verification update: the current rolling API guide documents the batched /configure failure semantics: failed operations do not commit changes for that component, cross-component partial commits are possible, and errors identify the component and missing information or conflict. See https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#configure. The documentation was added in https://github.com/vyos/vyos-documentation/commit/f002549a5fe3ae782be8fe02160fa2796e7e0471 and its atomicity/error wording was refined in https://github.com/vyos/vyos-documentation/commit/4631db6a1578550dd4c1410a8416575899f36936. This appears to address the task's core documentation gap. The current guide does not promise an exact failing-operation index/path or recommend bisecting a failed batch; if that remains part of the requested scope, T9091 may need to stay open or that API behavior could be tracked separately. Suggested status: Resolved if the reporter/maintainer agrees the documentation meets scope; otherwise keep open for the remaining error-location guidance.
eli-sterling added a comment to T9090: vyos-api docs: clarify that save works on /config-file, not /configure.
Verification update: the current rolling API guide now warns in the /configure section that this endpoint does not accept {"op":"save"} and directs users to /config-file: https://github.com/vyos/vyos-documentation/blob/rolling/docs/automation/vyos-api.md#configure. This guidance is present in commit f002549a5fe3ae782be8fe02160fa2796e7e0471 (https://github.com/vyos/vyos-documentation/commit/f002549a5fe3ae782be8fe02160fa2796e7e0471), dated July 14, 2026, titled "vyos-api: T9090: T9091: batched /configure semantics; save via /config-file". This appears to address T9090. Suggested status: move from Open / Need Triage to Resolved, if the reporter or maintainer confirms.
Tue, Sep 29
Tue, Sep 29
c-po added a comment to T9367: smoketest: vrf: only assert on the leaked flows in the VRF conntrack zone.
c-po changed the status of T9367: smoketest: vrf: only assert on the leaked flows in the VRF conntrack zone from Open to In progress.
RC added a comment to T9351: Accel-PPP: RADIUS: Add Message-Authenticator attribute support for Access packets (Blast-RADIUS mitigation).
Accel-ppp-ng : https://github.com/accel-ppp/accel-ppp-ng/pull/39
vyos-1x CLI: https://github.com/vyos/vyos-1x/pull/5442
documentation PR: https://github.com/vyos/vyos-documentation/pull/2260
xTITUS_MAXIMUSx added a comment to T9284: dhcp6c integer overflow / garbage value in pltime causes vyos-netlinkd loop and loss of connectivity.
I tried to reproduce this on 2026.09.23-0027-rolling (wide-dhcpv6-client 20080615-23). On a test link, Kea handed out an IA_NA address and a /48 IA_PD with pltime 3000 / vltime 4000 and T1=20, and radvd sent RAs on the same link.
Mon, Sep 28
Mon, Sep 28
Reproduced this on rolling with Kea 3.0.3-vyos.
c-po added a comment to T5388: Something is fishy with commit and boot times when more than a few hundred static routes are being used.
There is a POC migrationg to overlayfs https://github.com/vyos/vyos-build/pull/1311 and see linked PRs
This has been implemented for quit some time
This PR has been merged
Sun, Sep 27
Sun, Sep 27
c-po changed the status of T9361: Remove debug noise when running config load tests from Open to In progress.
c-po changed the status of T9360: BGP: ORF send + receive causes unnecessary session resets on unrelated policy commits from Open to In progress.
t.shiroma added a comment to T9360: BGP: ORF send + receive causes unnecessary session resets on unrelated policy commits.
I made a pull-req on https://github.com/vyos/vyos-1x/pull/5507 .
t.shiroma added a comment to T9345: BGP: Unsupported address families in named VRFs bypass configuration validation.
I've confirmed that the pull request has been merged, so I'll mark this ticket as Resolved. Thank you!
This has been fixed with this PR https://github.com/vyos/vyos-1x/pull/5495
Sat, Sep 26
Sat, Sep 26
c-po added a comment to T8859: `verify_diffie_hellman_length()` does not protect `int(min_keysize)` and has unused `keysize` variable.
Coder merged and removed as there are no real world callers anymore.
c-po changed Is it a breaking change? from none to compatible on T9356: PPPoE: traceback if IPv6 is unavailable on BRAS.
c-po changed Version from 2026.09.25-1909-integration to 2026.09.25-1909-integration, 1.5.1, 1.4.5 on T9356: PPPoE: traceback if IPv6 is unavailable on BRAS.
c-po changed the status of T9356: PPPoE: traceback if IPv6 is unavailable on BRAS from Open to In progress.
Fri, Sep 25
Fri, Sep 25
c-po triaged T9327: Add native support for NAT64 session synchronization (joold) as Wishlist priority.
c-po changed the status of T9354: op-mode: replace "reset connection" with "reconnect interface" from Open to In progress.
c-po triaged T9347: telegraf: add vyos_system_image metric for monitor image version as Wishlist priority.
c-po triaged T9336: Remote syslog server defined by FQDN fails to work when configured in a non-default VRF as Normal priority.
c-po changed the status of T9338: mpls inter-as - l3vpn-multi-domain-switching from Open to In progress.
c-po changed the status of T9332: GeoIP source/destination nftables set collision from Open to In progress.
c-po changed the status of T9345: BGP: Unsupported address families in named VRFs bypass configuration validation from Open to In progress.
Shouldnt the comment with examples at line 219 be updated aswell?
c-po added a comment to T9060: pppoe: spurious synthetic EUI64 /64 link-local address breaks DHCPv6-PD.
Interface nicely shows the one only link local address
c-po closed T9060: pppoe: spurious synthetic EUI64 /64 link-local address breaks DHCPv6-PD as Resolved.
PR 5501 created.
haakon.nore changed the status of T9319: VXLAN: expose the Group Policy extension through a gbp CLI node from Open to In progress.
VXLAN-GBP support has been merged into rolling via https://github.com/vyos/vyos-1x/pull/5484.
Documentation remains open and awaiting review: https://github.com/vyos/vyos-documentation/pull/2248. It covers configuration, limitations, and a firewall example.