examples/ipsec-secgw: fix usage of incorrect port
authorAnoob Joseph <anoob.joseph@caviumnetworks.com>
Tue, 12 Dec 2017 08:32:25 +0000 (08:32 +0000)
committerPablo de Lara <pablo.de.lara.guarch@intel.com>
Sat, 20 Jan 2018 15:08:34 +0000 (16:08 +0100)
commit3de3a0418c35deb9a0dd657701b6a22fb6dcb4db
tree3d1979451dafb873a7d94620685ef556bd18226b
parent3a55855081da3a354eedf51e37af4bad8b13c22a
examples/ipsec-secgw: fix usage of incorrect port

When security offload is enabled, the packet should be forwarded on the
port configured in the SA. Security session will be configured on that
port only, and sending the packet on other ports could result in
unencrypted packets being sent out.

This would have performance improvements too, as the per packet LPM
lookup would be avoided for IPsec packets, in inline mode.

Fixes: ec17993a145a ("examples/ipsec-secgw: support security offload")

Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Acked-by: Radu Nicolau <radu.nicolau@intel.com>
doc/guides/sample_app_ug/ipsec_secgw.rst
examples/ipsec-secgw/ipsec-secgw.c