@SamLue will be available in the next rolling release, can you check when it will be available?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jul 2 2024
In T6486#193845, @Viacheslav wrote:@adestis Can you add an example of the expected configuration if use-lzo-compression is configured and not configured?
https://github.com/vyos/vyos-1x/blob/e270712f7ebd76e4e1be598766d999cef4f05e26/src/op_mode/generate_ovpn_client_file.py#L57
I have similar problem, testing setup:
VyOS 1.5-rolling-202407010024 as VM in proxmox 8.2
Intel x710 card in pci-e passthrow to the VM
There are some nuances with it, until we do not have a route from to default VRF to the peer it won't work
set vrf bind-to-all set vrf name first table '123'
We are not going to implement it.
Should fix it https://github.com/vyos/vyos-1x/pull/3747
PR https://github.com/vyos/vyos-1x/pull/3747
Also it should fix T6379
Jul 1 2024
So with nftables output apparently the rule is correctly in place.
I've created the FRR bug report :
We do not use iptables, we use nftables.
Check the rules with sudo nft list ruleset
What exactly does not work?
@adestis Can you add an example of the expected configuration if use-lzo-compression is configured and not configured?
https://github.com/vyos/vyos-1x/blob/e270712f7ebd76e4e1be598766d999cef4f05e26/src/op_mode/generate_ovpn_client_file.py#L57