The subject migration is added by T8492
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jun 14 2026
Jun 13 2026
Jun 12 2026
@a.apostoliuk Could you please share the full logs from the crash?
UPD: fixed by https://github.com/vyos/vyos-1x/pull/5253
Jun 11 2026
Looks like protocols_bgp.py has been refactored a bit since i last worked on this and the issue i ran into no longer exists. PR submitted.
Jun 10 2026
vyos-build: https://github.com/vyos/vyos-build/pull/1222
vyos-1x: https://github.com/vyos/vyos-1x/pull/5267
Created an initial pull request at https://github.com/vyos/vyos-1x/pull/5266
If somebody could explain to me what value addr (at https://github.com/vyos/vyos-1x/blob/a6ad73d72ba8d5256ff77978e63c07143787eb44/python/vyos/utils/network.py#L400) is set to when the current listen address is *, I might be able to come up with a PR to fix this.
I tried to work around the issue by leveraging VRRP transition scripts, when I’ve noticed haproxy by default listens to every interface (i.e. binds to *) when no explicit listen-address is set. However due to this behavior it is no longer possible to add a listen-address when haproxy is already running, as the on-commit check refuses to apply due to the port being occupied. For obvious reasons it should ignore the port being in use in such cases. The only solution for now is completely removing all haproxy config before reapplying all of it, which is very much suboptimal.
I think it should check the state of net.ipv4.ip_nonlocal_bind / net.ipv6.ip_nonlocal_bind, and if set to 1, skip the check.
I found the culprit: https://github.com/vyos/vyos-1x/pull/5186 introduced a check if the address is assigned. I think this should be changed to check for an address, that is generally available (via config), not minding if it is actually configured. Open for suggestions to send in a PR.
This is the reproduce.py I used to validate on a fresh instance.
Jun 9 2026
yes, PR is here: https://github.com/vyos/vyos-1x/pull/5261
In T8972#269009, @Russ28 wrote:VPP/LCP VRF Table Synchronization Manual Test
Manual testing was performed in a GNS3 VyOS lab with VPP enabled on eth1.
Source repo
VyOS has been built from https://github.com/inetman28/vyos-1x/tree/fix-vpp-lcp-vrf-table
In T8972#269030, @Russ28 wrote:I also noticed another issue with vpploX interfaces: currently, they cannot be assigned to any VRF.
Should we fix this in the same branch, or would it be better to handle it separately?
Branch: https://github.com/inetman28/vyos-1x/tree/fix-vpp-lcp-vrf-table
I also noticed another issue with vpploX interfaces: currently, they cannot be assigned to any VRF.
- VPP/LCP VRF Table Synchronization Manual Test
fix for rolling: https://github.com/vyos/vyos-1x/pull/5260
Jun 8 2026
Thank you for tackling this so fast!
Thank you for reporting.
PR: https://github.com/vyos/vyos-build/pull/1220
Due to being unable to edit the OP (complains about policy changes I'm not actively performing), here is the link to the related forum thread: https://forum.vyos.io/t/vyos-build-failing-to-build-image-missing-dependencies/17497
