- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jul 1 2026
Jun 30 2026
Jun 29 2026
Jun 26 2026
Jun 25 2026
Jun 24 2026
Jun 23 2026
I don't know if the default value of 1 is a good idea, but per feature, it could be.
For example, we use it in the OpenVPN https://github.com/vyos/vyos-1x/blob/3edf114bed538733388252da0d23b49002273558/src/conf_mode/interfaces_openvpn.py#L844
Jun 22 2026
Jun 19 2026
'Resolved for the rolling
Jun 18 2026
Jun 17 2026
Jun 16 2026
Jun 15 2026
FRR reloads the whole configuration per commit, not only one protocol
So policy-route-map is related to FRR config and prefix-lists are the same between all FRR routing daemons.
https://github.com/vyos/vyos-1x/blob/c2f87f243a1f813fbdd319b1004fd3a26397ab3e/python/vyos/frrender.py#L850
Jun 11 2026
Jun 10 2026
Jun 9 2026
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