diff options
| author |   Matthew Smith <mgsmith@netgate.com> | 2018-04-09 11:49:20 -0500 |
|---|---|---|
| committer |   Damjan Marion <dmarion.lists@gmail.com> | 2018-04-10 10:30:11 +0000 |
| commit | 537eeeca36dcc08a3c337a7cfd1c1c426d43f563 (patch) | |
| tree | 6a8cf50bef441c1e3277c84a3e9db6866da5f04a /src/vpp-api/java | |
| parent | 13adc3d48d562b13422259d8c7ac411fb43c7e8b (diff) | |
Make IPsec tunnel intf work with IPv4 output features
With no IPv4 output features on an IPsec tunnel inferface,
when packets are forwarded to that interface, they reach
the ipsec-if-output node via the output_node_index on the
hw interface and they are handled correctly.
When an IPv4 output feature (e.g. output ACL, outbound
NAT) is enabled on an IPsec tunnel interface, outbound
IPsec stops working for that interface. The last node in
the ip4-output feature arc is interface-output. From there
a packet is sent to ipsec<N>-output, and then ipsec<N>-tx.
The tx function for an IPsec tunnel interface that is
called by ipsec<N>-tx is a dummy that doesn't do anything
except write a warning message.
Enable a feature on the interface-output feature arc for
an IPsec tunnel interface so the ipsec-if-output node is
reached from the interface-output node.
Change-Id: Ia9c73d3932f5930ec7ce0791a0375b1d37148b01
Signed-off-by: Matthew Smith <mgsmith@netgate.com>
Diffstat (limited to 'src/vpp-api/java')
0 files changed, 0 insertions, 0 deletions