PR https://github.com/vyos/vyos-build/pull/1011
PR https://github.com/accel-ppp/accel-ppp-ng/pull/3/commits/083da789232da872142878506cc12cd8e5a23008
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 18 2025
@Viacheslav
Rolling release isn't affected due to this bit of code and the import of the related signal library: https://github.com/vyos/vyos-1x/blob/69cd4845861c88285ab496339f19103dec7a32b6/src/op_mode/firewall.py#L29
here's the topology and full cofig. running on VyOS 2025.05.29-0019-rolling
In T3936#219798, @gmurphy42 wrote:Just gonna bump this again. Would be great to see support for this as it would be super helpful for complex architecture-based netboot configurations.
A post from the forum showing a perfect example of the use case: https://forum.vyos.io/t/how-to-setup-vyos-to-let-it-support-netboot-xyz/14391/5
Aug 17 2025
Does the rolling release also affected?
If yes, you should add a PR to the “current” branch.
And then it will be tested in the rolling and if works fine, it will be backported to the stable branches.
PR submitted here https://github.com/vyos/vyos-1x/pull/4664 but it was auto-closed as pull-requests on sagitta branch aren't accepted per the Bot (I don't recall this block on past contributions).
Aug 16 2025
Adding (1) and (2) to this bug report:
I am working here on this use case https://github.com/vyos/vyos.vyos/pull/429
Aug 15 2025
appears to be working again with VyOS 2025.08.13-0020-rolling
this might be interacting with firewall global-options receive-redirects
Correction to the steps required to support ALL kea options programatically- it may need to be more like this:
As a note for myself and any other users not familiar with the project who need to perform a task like this in the feature, a few notes on changes needed based on a quick survey:
In T7723#232731, @Viacheslav wrote:You need to add changes only in the vyos-1x repo
This appears to be a logical bug. I have opened a Pull Request to fix it.
https://github.com/vyos/vyos-1x/pull/4663
You need to add changes only in the vyos-1x repo
I would like to send a PR for this if I have time as it seems like a relatively good first issue to work on.
Could you share the interface configuration or topology and expected entries?
What about the latest rolling?
Pardon my typo in the notes, the correct option number is 26 as in the title of the issue
To clarify, I’m only asking that this option can be set to an integer. It would be neat to be able to instruct it to set the option to a value dynamically, deriving it from a specified interface, but that’s a lot more effort and probably rarely worth it
Aug 14 2025
Will be fixed in https://github.com/vyos/vyos-build/pull/1009
Re-opened, image still does not include this package
DEBUG - show version all | grep -e "vpp" -e "vyos-1x" DEBUG - ii libvppinfra 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--runtime libraries DEBUG - ii libvppinfra-dev 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--runtime libraries DEBUG - ii python3-vpp-api 25.06.0-21~g43212d8f7-dirty amd64 VPP Python3 API bindings DEBUG - ii vpp 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--executables DEBUG - ii vpp-dev 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--development support DEBUG - ii vpp-plugin-core 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--runtime core plugins DEBUG - ii vpp-plugin-dpdk 25.06.0-21~g43212d8f7-dirty amd64 Vector Packet Processing--runtime dpdk plugin DEBUG - ii vyos-1x 1.5dev0-3397-g33b13061b amd64 VyOS configuration scripts and data DEBUG - ii vyos-1x-smoketest 1.5dev0-3397-g33b13061b all VyOS build sanity checking toolkit DEBUG - vyos@vyos:~$ l
Thanks for the details. This is a regression as a result of T7588. Fix here:
https://github.com/vyos/vyos-1x/pull/4661
Aug 13 2025
will be fixed in PR https://github.com/vyos/vyos-1x/pull/4658