@rayzilt Could you re-check and close it if solved?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 22 2023
Oct 21 2023
Could you try it locally and see what happens?
@Apachez I suppose it is.
- biosdevname is called by scripts in the initrd, so we can't remove it just yet.
- it's not completely abandoned and had quite a few releases since the point when Vyatta forked it.
- I sent a PR to allow biosdevname to run in VMs (that's the only thing that vyatta-biosdevname has and that's used in scripts): https://github.com/dell/biosdevname/pull/12
I could not find any uses of "slave" in current VyOS versions. If anyone finds any, feel free to start a discussion. VRRP "master" terminology cannot be changed because it's a part of the protocol spec itself, and, as said above, its counterpart is "backup".
Closing due to Crux EOL.
Crux is EOL now, but if similar issues appear in newer versions, feel free to report them!
The new-style op mode is well-established now, it's time to close the task.
The problem was resolved in the forum. Whether the underlying cause in FRR was resolves is another question...
vni100 should be the bridge slave here.
So those options could be in the same level of "allowed-vlan" and "native-vlan"
Oct 20 2023
PR for Saggita: https://github.com/vyos/vyos-1x/pull/2388
PR for 1.5 https://github.com/vyos/vyos-1x/pull/2386
Is vni100 the vxlan interface or the bridge interface?
Just in case: using anything except current image scripts for installation is not possible without a full chroot into the installation candidate. Python versions and modules may be different and new scripts in many cases will not work in the old environment.
Oct 19 2023
PR for 1.4 https://github.com/vyos/vyos-1x/pull/2383
PR for 1.3 https://github.com/vyos/vyos-1x/pull/2381
PR for 1.5 current https://github.com/vyos/vyos-1x/pull/2378