User Details
- User Since
- Aug 3 2017, 1:55 PM (354 w, 2 d)
- Roles
- Administrator
Today
This is a known issue as explained in detail in T4628. You're best choice is to remove the whitespace prior to upgrading. Thanks for reporting this anyways!
Thu, May 16
Tue, May 14
Sun, May 12
Sat, May 11
@alainlamar what's the preferred CLI command?
Fri, May 10
Sorry for the noise - see workaround
Thu, May 9
Wed, May 8
@alainlamar can you check my PR https://github.com/vyos/vyos-1x/pull/3430 ?
Tue, May 7
There is an ongoing discussion in the background between the Maintainers for mor then a year how to get rid of the hw-id node in general and do such a detection once during initial boot.
Sat, May 4
Fri, May 3
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
Thu, May 2
Upstream bug https://github.com/FRRouting/frr/issues/15912
something native would be more powerful
Wed, May 1
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)