Fix is in this PR https://github.com/vyos/vyos-1x/pull/4808
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 23 2025
Fix is in this PR https://github.com/vyos/vyos-1x/pull/4808
This is not implemented by FRR at the moment https://github.com/FRRouting/frr/issues/19110
@sarthurdev please take attention.
Thanks.
Oct 22 2025
Hello,
Sorry for the delay in getting back to you.
I'll rebuild the scenario, design and update the configurations, and I'll bring you updates shortly, including the network design, hardware, and applications.
I can test with a CGNAT of approximately 15,000 clients, with 2,000 ports allocated per client, to test performance, reaching approximately 25G/s of aggregate traffic.
According to @a.melnychenko researches:
SHIM accepted by review-board
Oct 21 2025
I have tested in different ways, and currently stayed with the case where I have a very small DHCP pool and receive error from kea.
PR was now merged. Please also backport to 1.4. Thanks!
Now that T5942 has been merged, is there any interest in extending it to add PPPoE support? The state change hooks would be nice as well. Thanks!
New patch v3 lkml:
https://lkml.org/lkml/2025/10/21/1117
Hi, yeah oops, should have mentioned that!
Oct 20 2025
I believe the root cause of this memory leak lies in the default-originate route-map logic. This issue has already been addressed in the FRR upstream with the following commit: FRR Commit 74c1d4f
Found procedure to easily trigger bug in https://github.com/FRRouting/frr/issues/19359