Please re-test with latest current rolling release. Reverted back for FRR 7.5 and that bug should have been fixed in there.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Feb 14 2021
Feb 13 2021
I am suggesting switching to https://github.com/vyos/vyos-vm-images for everything, except ISO images. This will solve the problem automatically. It is already able to create images for QEMU, VMware, Hyper-V, GCE, AWS, OpenStack, Oracle, Packet, and more not mentioned in the https://github.com/vyos/vyos-build. The only what I have not tried yet is Azure.
Setting Ethernet interfaces addresses, routes, and name servers are supported in both versions now. Advanced features like bonding, bridges, VLANs could be added later on-demand.
Nice idea - it should be generated by https://github.com/vyos/vyos-build/blob/current/scripts/make-version-file
This was resolved via dhclient hooks - there is a protection mechanism now, which allows deleting only routes with tag 210 that set by hooks to all DHCP routes.
The config module without this problem is available in the crux, should be released in the 1.2.7 version.
The config module backported to the crux, should be available with 1.2.7 release.
Backported to the crux branch, should be released with 1.2.7.
Feb 12 2021
Created PR: https://github.com/vyos/vyos-1x/pull/731
Tested with:
Possible fix, pending testing: https://github.com/varesa/vyos-1x/commit/4a0504a96cf0f3078e964ed201f196fb55172e00
I *think* that there was a fix that happened on a task somewhere by someone in the underlying operating system that happened to fix this problem, but I for the life of me don't know what/where it would be. I'll have to ask around on it as I think there was changes on it 100% certain. The reason is is because I *saw* this problem too on a very old install too but it went away very quickly and I made no changes to fix it.
@c-po I would say that it would be better whether to report the problem upstream
I have updated from an older version.
Just curious.
Version:
$show version
Hmmm...I am still not able to replicate...
Feb 11 2021
migrated to vyos-1x
This is clearly an issue with the Linux Kernel (incompatible ABI change) as the error is not present on 1.3-beta which uses 5.4 kernel series but it exists on 1.4-rolling which uses the 5.10 series.
I agree