Also watchfrr was disabled some time ago as FRR process handling was moved to systemd.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Aug 5 2023
FRR mgmtd can not be disabled.
Aug 4 2023
The VRF error applies to DHCPv6, too
Note, if mgmtd is of no use in VyOS then the preferred is to have it disabled all together (after updating daemons.tmpl in case it gets enabled in future).
PR created: https://github.com/vyos/vyos-1x/pull/2132
Could be added the same way https://github.com/vyos/vyos-1x/blob/8f161eaae78769e5a1d573e43f00a0f439aadc28/debian/vyos-1x.postinst#L126-L139
Aug 3 2023
Note also that 1.4 rolling as of today (3rd aug) uses FRR 9.0 (previously I think 8.5.4 were used or something like that).
Yes, i did that as option A yesterday. And rebooted. Then removed "zebra nexthop-group keep 1" and play a bit with interfaces up/down until kernel routes vanished. Then i put "zebra nexthop-group keep 1" back and rebooted again.
Will try option B then.
Meanwhile it appeared possible to fix "Route install failed" errors. I turned on debug zebra kernel, found the nhg_id which caused route install error and created it manually using nh1/nh2 provided by vtysh -c "show nexthop-group rib <nhg_id>". Just as it is described in the original thread regarding ipv6 routes.
Note that you had an "s" too much in your command.
Found that the defaults in daemons-file are set by VyOS in /usr/share/vyos/templates/frr/daemons.frr.tmpl
There is still some problem with the workaround proposed. It seems not fully working when applied on the running system with active BGP sessions. At least i still see the next hop groups in the kernel which has only one next hop after our last tests:
Hi
I would like to see last delay sessions be minimum allowed integer be 0 not 1 to 999999
Aug 2 2023
This is addressed in a PR for T5319:
https://github.com/vyos/vyos-1x/pull/2131
cool! it's interesting understand this complex scenery and how it works an real environment ,Additionally, the way it handle the zebra with the next-hop group ,int fact , I genuinely appreciate your valuable feedback so far!
From last night tests it seems to be solved. Though i'd prefer to test the node in production for a few weeks to be sure.
as I recall ,this case can be associate with this task : https://vyos.dev/T5077
@twan Can we close it?
Yesterday I tested the latest 1.4-rolling-202308011218-image which includes CONFIG_VIRTIO_FS=m, and was successfully able to (manually) activate LXD Agent in my VM.
Thank you for the quick fix.
Aug 1 2023
Done!