[dpdk-dev] [PATCH] examples/ipsec-secgw: wrong spi read from packet

2016-06-07 Thread Slawomir Mrozowicz
In ipsec-secgw wrong SPI number is read from incoming ESP packet. The problem exist inside function inbound_sa_lookup(). The SPI is read from mbuf where the information is stored in big-endian. In low-endian environment the value is erroneous. Fixed by add conversion rte_be_to_cpu_32(). Fixes: d29

[dpdk-dev] [PATCH] examples/ipsec-secgw: wrong spi read from packet

2016-06-07 Thread Sergio Gonzalez Monroy
On 07/06/2016 13:17, Slawomir Mrozowicz wrote: > In ipsec-secgw wrong SPI number is read from incoming ESP packet. > The problem exist inside function inbound_sa_lookup(). > The SPI is read from mbuf where the information is stored in big-endian. > In low-endian environment the value is erroneous.