- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
May 14 2024
May 12 2024
May 11 2024
@alainlamar what's the preferred CLI command?
May 10 2024
Sorry for the noise - see workaround
May 9 2024
May 8 2024
@alainlamar can you check my PR https://github.com/vyos/vyos-1x/pull/3430 ?
May 7 2024
There is an ongoing discussion in the background between the maintainers for more then a year how to get rid of the hw-id node in general and do such a detection once during initial boot.
May 4 2024
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?
Upstream bug https://github.com/FRRouting/frr/issues/15912 fixed in https://github.com/FRRouting/frr/pull/15913
May 2 2024
Upstream bug https://github.com/FRRouting/frr/issues/15912
something native would be more powerful
May 1 2024
Well looks like you hit a WireGuard limitation here (route-leaking the default nexthop to another VRF)
You probably should get the wireguard interface running in your default VRF first and see if traffic properly passes - once that's working for oyu you can move it into a VRF. Please not only the decrypted side of the WireGuard interface will reside in the VRF. The side passing encrypted packets ALWAYS is in the default VRF (Linux Kernel)