There is a POC migrationg to overlayfs https://github.com/vyos/vyos-build/pull/1311 and see linked PRs
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mon, Sep 28
This has been implemented for quit some time
This PR has been merged
Sun, Sep 27
I made a pull-req on https://github.com/vyos/vyos-1x/pull/5507 .
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
Coder merged and removed as there are no real world callers anymore.
Fri, Sep 25
Shouldnt the comment with examples at line 219 be updated aswell?
Interface nicely shows the one only link local address
PR 5501 created.
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.
Thu, Sep 24
Thanks for the report @mrpops2ko .
Please open a new task/bug report. This was only about the port and it's now closed.
I see no need in adding mpls enable - all FRR does is writing 1/0 to '/proc/sys/net/mpls/conf/eth1/input' (see https://github.com/FRRouting/frr/blob/1dd655dda3f38ab1227683ed78e51fc35e3c254b/zebra/netconf_netlink.c#L185), VyOS does the same for set protocols mpls interface eth1. If I'm missing something please write.
not sure if this is the appropriate place for it, but the speeds are not good. here are some benchmark comparisons using the same VPN node which has wireguard enabled and DCO.
Wed, Sep 23
I made a pull-req on https://github.com/vyos/vyos-1x/pull/5494
Tue, Sep 22
here is the documenation on frr about mpls enable/disable : https://docs.frrouting.org/en/latest/zebra.html#clicmd-mpls-enable-disable
Sep 22 2026
Possible workarounds/fixes:
Sep 21 2026
we need to expose as well the following command to interfaces level :mpls enable
Sep 20 2026
Resolved in https://github.com/vyos/vyos-build/pull/1308
Sep 19 2026
Sep 18 2026
The IS-IS daemon leaks memory during its shortest-path calculation. When a node in the topology has more than 64 equal-cost adjacencies, FRR trims the excess entries but does not release their memory.
This is a duplicate of T7487 which has an open PR against is so I think this ticket should be closed.
Rather than rejecting "interval 0" in verify(), the change leaves the directive
out of the generated file: "keepalive" only stands for "ping" and "ping-restart",
and the server branch of the template sets neither on its own, so an absent
directive is the keepalive-off the interval asked for. Nothing needs a migration
and a saved configuration still commits.