Correct, if you want to test it you'd have to test on rolling. If the feature works for you, you could then request the feature get backported to 1.5. The commit was on the 1.5 board, so I'm not sure why it wasn't backported before the GA was released.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 4 2026
@L0crian the command :
Aug 3 2026
@L0crian thx for this information, this could help with my current setup. I will try it in the lab. But I also see that my patched could be usefull
I can create a patch for this if wanted
Your addition is still useful because it lets you match only on specific interfaces or traffic, but have you seen that you can already do this?:
Aug 2 2026
Aug 1 2026
Jul 31 2026
This includes but not limited to:
- Updating the CI workflows
- Troubleshooting the upstream provider changes
- Fixing failing tests
- Assisting contributors with their PRs, reviewing their PRs
- Updating branches
Jul 30 2026
It was available in 1.4 but with different variable name WLB_SCRIPT_IFACE-
The only requirement I have for this change is that the MTU versus performance conflict should be resolved completely on our side and be transparent to users. Maybe by tuning buffers data-size so they fit Jumbo frames when needed, if this solves the problem.
Do you know the version where it worked at all?
I believe we didn't pass those info to the health check scripts. If so, it should be a feature request and not a bug report.
Companion PR for the CLI side: https://github.com/vyos/vyatta-cfg/pull/153
Jul 29 2026
i report them on github security advisor
About point 2.
I observe that traffic that matches peer policies is encrypted. BUT this peer is disabled.
If I execute sudo swanctl -L , it shows nothing. But if I execute sudo ip xfrm policy, it shows polices, that were disabled in the configuration.
I think the root cause is rtradv = conf.get_config_dict(base, key_mangling=('-', '_'), get_first_key=True) in service_router-advert.py ,not sure why need key_mangling .