ligang/vpp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gre: Walk IPv6 adjacencies during restack

Browse Source 
Type: fix

If a GRE tunnel is created and the peer is not resolved yet and an
IPv6 route is added which points to the tunnel, packets matching the
route will be dropped. When the tunnel peer is resolved, adjacencies
on the tunnel interface should be restacked and packets matching the
route can be encapsulated and sent..

There is a loop that is intended to do this for both IPv4 and IPv6.
The call to walk adjacencies is invoked in a "return" statement though.
So the loop is exited and the function returns before IPv6 adjacencies
are walked.

Remove the return so the loop finishes.

Change-Id: Ia4f695681713020209ea490ae4142857cea49c41
Signed-off-by: Matthew Smith <mgsmith@netgate.com>
This commit is contained in:
Matthew Smith 2021-05-14 17:00:15 -05:00 committed by Neale Ranns
parent 733a26e787
commit a0455ffdbe
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/vnet/gre/interface.c
View File

@ -225,9 +225,11 @@ gre_tunnel_restack (gre_tunnel_t * gt)
switch (gt->mode)
{
case TUNNEL_MODE_P2P:
return (adj_nbr_walk (gt->sw_if_index, proto, gre_adj_walk_cb, NULL));
adj_nbr_walk (gt->sw_if_index, proto, gre_adj_walk_cb, NULL);
break;
case TUNNEL_MODE_MP:
return (adj_nbr_walk (gt->sw_if_index, proto, mgre_adj_walk_cb, NULL));
adj_nbr_walk (gt->sw_if_index, proto, mgre_adj_walk_cb, NULL);
break;
}
}
}