Thanks for the report @mrpops2ko .
Please open a new task/bug report. This was only about the port and it's now closed.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Sep 24 2026
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.
Sep 23 2026
I made a pull-req on https://github.com/vyos/vyos-1x/pull/5494
Sep 22 2026
here is the documenation on frr about mpls enable/disable : https://docs.frrouting.org/en/latest/zebra.html#clicmd-mpls-enable-disable
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.
This is a regression caused by the version bump we just merged (from 2.7.5 to 2.7.7).
The following commit
Sep 17 2026
Created PR - https://github.com/vyos/vyos-1x/pull/5487
Update: the fix moved to vyos-1x, https://github.com/vyos/vyos-1x/pull/5486
Completion fix: https://github.com/vyos/vyos-build/pull/1308
Sep 16 2026
Rejected - Superseeded by
Looks like a firewall misconfiguration, not a real bug.
Re-open it with the minimal steps to reproduce or the configuration that maintainers can use to confirm.
Or open a topic at the forum if you need help with firewall settings.
Closing the task
Update on #5468 (defect 1 fix).
I hit this on my own fleet and put up a PR for fix (a): https://github.com/vyos/vyos-build/pull/1304. It sets ForwardToSyslog=no in data/live-build-config/includes.chroot/etc/systemd/journald.conf, which is where the image gets its journald.conf. That line came in with vyos-build bc0406ce3 (T552, 2018), back when the rsyslog config only loaded imuxsock and imklog. imjournal showed up later, in vyos-1x e143e496e (T6989, 2025-01-13).
Sep 15 2026
Draft PR here https://github.com/vyos/vyos-1x/pull/5478 implementing a method as discussed in https://github.com/vyos/vyos-1x/pull/4765. Draft until addition of remaining XML annotations, but the simple method is complete.
- Update: Unfortunately, the system went offline again today (September 15) with a complete freeze/loss of connectivity, requiring a manual reboot.
PR created: https://github.com/vyos/vyos-1x/pull/5476
Let me know what I am missing:
https://github.com/vyos/vyos-1x/pull/5473