- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 4 2024
need configuration index too or maybe name
so we can have several destinations for same protocol
I already looked a bit into it. What complicates it is the old location is a multi and one can add a list of locations.
Should be fixed after rewriting commit-archive T6304
NETNS was removed from the 1.4 series the other day so hopefully that feature can be worked on for 1.5 since its needed:
May 3 2024
What you're trying to achieve seems to be a derivate of https://www.wireguard.com/netns/
How was this configuration achieved? Or is it manually crafted?
There were some improvements for 1.3 related ipset checks and implemented in T2189, but due to the old backend it is impossible to do anything else.
The 1.5/1.4 do not have this issue
Close the task
Will be available in the next rolling release.
I think the problem is similar to https://vyos.dev/T5611
Upstream bug https://github.com/FRRouting/frr/issues/15912 fixed in https://github.com/FRRouting/frr/pull/15913
Checked. Runs without errors
The same bug as in T6283
Thanks for the heads up, first time reporting an issue, keep up the great work! Here is output of show configuration commands | strip-private
May 2 2024
Upstream bug https://github.com/FRRouting/frr/issues/15912
something native would be more powerful