On 10/13/21 11:59 AM, Ido Schimmel wrote:
On Wed, Oct 13, 2021 at 11:26:50AM +0200, Daniel Borkmann wrote:
On 10/12/21 6:31 PM, Ido Schimmel wrote:
In our HW the nexthop table is squashed together with the neighbour
table, so that it provides {netdev, MAC} and not {netdev, IP} with which
the kernel performs another lookup in its neighbour table. We want to
avoid situations where we perform multipathing between valid and failed
nexthop (basically, fib_multipath_use_neigh=1), so we only program valid
nexthop. But it means that nothing will trigger the resolution of the
failed nexthops, thus the need to probe the neighbours.
Makes sense. Given you have the setup/HW, if you have a chance to consolidate
the mlxsw logic with the new NTF_MANAGED entries, that would be awesome!
Yes, I will take care of that
Perfect, thanks a lot!
