Hi @c-po and thanks for the insight. I understand that this is a workaround for a reboot safe configuration if you're using vrf bgp neighbors.
We are also using vrf inside our infrastructure as well without vrf bgp neighbors and only redistribute connected routes and advertise them via EVPN.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 26 2025
This changes switches the hsflowd to the following commit-id: dffc277
The similar task T6223
I think the entire idea was missguided and misslead by the fact that tokens are not supported on every interface type - only interfaces supporting "ARP" in the iproute2/Kernel source code but thats wrong in a different story.
Aug 25 2025
The feature is really missing - I raised a PR to work on it https://github.com/vyos/vyos.vyos/pull/433
interface {
inside vpptun10.144
outside vpptun10.145
}I have found an interesting project with EINat/fullcone NAT implementation https://github.com/EHfive/einat-ebpf
Use cases https://github.com/EHfive/einat-ebpf/blob/main/docs/guide/use-case.md
https://github.com/EHfive/einat-ebpf/blob/main/docs/reference/rfc-compliance.md
You can download a static binary to play with it.
In T7665#230894, @fernando wrote:
Aug 24 2025
The feature is available in the latest Galaxy collection
https://galaxy.ansible.com/ui/repo/published/vyos/vyos/content/module/vyos_l3_interfaces/
Aug 23 2025
In this case, can we have a proper error message for unsupported hw?
Also it seems strange that x710 supports VPP/DPDK but lacks TC_SETUP_FT.
Aug 22 2025
Nevermind, adding "use-routing" isn't sufficient; it doesn't handle all requests properly. I'm solving this by containerizing kea, so no need to half-fix the built-in version.
Will be fixed after migration to the accel-ppp-ng T7744
@kakurpiel is correct, TC flowtable does not work with Intel cards due to lack of driver support. I suggest this ticket can be closed.
I guess fixing this would require a rework of the nftables ruleset to use a single table inet vyos_filter for both v4 and v6. Probably a big change - though personally I think it would also be a huge useability win to not have to have two copies of every ACL. It would shorten my config a lot, and prevent screwups due to not keeping the v4 and v6 ACLs in sync.
Aug 21 2025
Will be fixed in the next rolling release.
Nice to re-check after 21 August
@dmbaturin, @c-po, @jestabro and @n.fort