diff options
| author |   Neale Ranns <neale@graphiant.com> | 2021-10-08 07:30:47 +0000 |
|---|---|---|
| committer |   Beno�t Ganne <bganne@cisco.com> | 2021-11-19 14:41:28 +0000 |
| commit | 6fdcc3daa40ebfcb793998b6e4527dd6db03cfb7 (patch) | |
| tree | 8b8afab4ef1f1d1f8381b388010e92e4d470022b /build-data | |
| parent | ad80663eb3fd954f42607168ad4babb91cb0edcc (diff) | |
fib: Don't use [midchain] adjacencies to change an interface's feature arc
Type: fix
Using the adjacency to modify the interface's feature arc doesn't work, since there are potentially more than one adj per-interface.
Instead have the interface, when it is created, register what the end node of the feature arc is. This end node is then also used as the interface's tx node (i.e. it is used as the adjacency's next-node).
rename adj-midhcain-tx as 'tunnel-output', that's a bit more intuitive.
There's also a fix in config string handling to:
1- prevent false sharing of strings when the end node of the arc is different.
2- call registered listeners when the end node is changed
For IPSec the consequences are that one cannot provide per-adjacency behaviour using different end-nodes - this was previously done for the no-SA and an SA with no protection. These cases are no handled in the esp-encrypt node.
Signed-off-by: Neale Ranns <neale@graphiant.com>
Change-Id: If3a83d03a3000f28820d9a9cb4101d244803d084
Diffstat (limited to 'build-data')
0 files changed, 0 insertions, 0 deletions