On 2/8/21 1:42 PM, Petr Machata wrote: > To illustrate the usage, consider the following commands: > > # ip nexthop add id 1 via 192.0.2.2 dev dummy1 > # ip nexthop add id 2 via 192.0.2.3 dev dummy1 > # ip nexthop add id 10 group 1/2 type resilient \ > buckets 8 idle_timer 60 unbalanced_timer 300 > > The last command creates a resilient next hop group. It will have 8 > buckets, each bucket will be considered idle when no traffic hits it for at > least 60 seconds, and if the table remains out of balance for 300 seconds, > it will be forcefully brought into balance. (If not present in netlink > message, the idle timer defaults to 120 seconds, and there is no unbalanced > timer, meaning the group may remain unbalanced indefinitely.)
How did you come up with the default timer of 120 seconds? overall this looks really good.
