diff options
| author |   Alexander Chernavin <achernavin@netgate.com> | 2022-04-11 13:02:11 +0000 |
|---|---|---|
| committer |   Matthew Smith <mgsmith@netgate.com> | 2022-04-12 16:06:43 +0000 |
| commit | 65e770d895b13a6e5c73d13f436872ea626e47e3 (patch) | |
| tree | 8840bd513f485449e85d73e4d7ac4980977902a9 /src/vppinfra/vec_bootstrap.h | |
| parent | d0249ebcb2e37cd54140c078c21b6053d9d1bdfe (diff) | |
ip: fix arc start in ip46-local for local mfib entries
Type: fix
After changes made in f840880, VRRP IPv6 cannot reply for neighbor
solicitations requesting the link layer address of the configured
virtual address.
VRRP IPv6 enables the vrrp6-nd-input feature in the ip6-local feature
arc for an interface on which a virtual router is configured. When
neighbor solicitations arrive on that interface, ip6-local should start
feature arc walk for that interface and the messages should be processed
by vrrp6-nd-input. The problem is that currently, the feature arc is
started for the interface obtained from the receive DPO that has
interface unset (i.e. max u32) for local mfib entries. Thus, the feature
arc is started not on the interface the messages were received on and
vrrp6-nd-input is not traversed.
With this fix, if interface obtained from the receive DPO is unset, use
RX interface from the buffer to start the ip46-local feature arc.
Also, enable tests of this case for both IPv4 and IPv6 address families
that are currently tagged as extended and not run on every change. They
configure VRRP with priority 255 and are expected to be stable.
Signed-off-by: Alexander Chernavin <achernavin@netgate.com>
Change-Id: I11ef3d5a7a986e04431e8613d1510b8666094bd7
Diffstat (limited to 'src/vppinfra/vec_bootstrap.h')
0 files changed, 0 insertions, 0 deletions