- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 2 2024
also dsmark qdisc was removed
@natali-rs1985 Can you check and close it?
@e.pc.yuan Read please https://blog.vyos.io/feature-requests-and-bug-reports-guidelines
A sequence of configuration commands or a complete configuration file is required to recreate a setup where the bug occurs. Please avoid partial configs: a sequence of commands is easy to paste into the console, a complete config is easy to load in a VM, and a partial config is neither! At least not until we implement a "merge from the CLI" feature that allows pasting config file chunks into a session.
You can ask on the forum
Close the task as duplicate
May 1 2024
Something like set policy route PBR rule 1 destination group network-group us such that PBR is able to route towards a GEOIP network group will be awesome. I believe it is available in firewall already.
Tested as working in: VyOS 1.5-rolling-202405010020
Well looks like you hit a WireGuard limitation here (route-leaking the default nexthop to another VRF)
In T6281#185620, @c-po wrote: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)
Thanks for the hints, that makes sense. Let's see how that can be implemented :)
For added service when typing just:
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)