diff options
author | Matthew Smith <mgsmith@netgate.com> | 2023-09-26 13:08:26 +0000 |
---|---|---|
committer | Neale Ranns <neale@graphiant.com> | 2023-10-25 08:46:20 +0000 |
commit | 9e5694b405e0200725a993f0c17d452fab508435 (patch) | |
tree | 070a52d52ab653ccb3611bd232be89c1bd74f979 /extras/hs-test/suite_tap_test.go | |
parent | 52aaa9b0ac20d7dca1b342c1dec3a9726ff45f4c (diff) |
fib: only update glean for interface if necessary
Type: improvement
If an interface address is added, the glean adjacency for it's covering
prefix is updated with that address. In the case of multiple addresses
within the same prefix being added, the most recently added one will end
up being used as the sender protocol address for ARP requests.
Similar behavior occurs when an interface address is deleted. The glean
adjacency is updated to some appropriate entry under it's covering
prefix. If there were multiple interface addresses configured, we may
update the address on the adjacency even though the address currently in
use is not the one being deleted.
Add a new value PROVIDES_GLEAN to fib_entry_src_flag_t. The flag
identifies whether a source interface entry is being used as the address
for the glean adjacency for the covering prefix.
Update logic so that the glean is only updated on adding an interface
address if there is not already a sibling entry in use which has the
flag set. Also, only update the glean on deleting an interface address
if the address being deleted has the flag set.
Also update unit test which validates expected behavior in the case
where multiple addresses within a prefix are configured on an interface.
Signed-off-by: Matthew Smith <mgsmith@netgate.com>
Change-Id: I7d918b8dd703735b20ec76e0a60af6d7e571b766
Diffstat (limited to 'extras/hs-test/suite_tap_test.go')
0 files changed, 0 insertions, 0 deletions