Many thanks Matus for the patch.

I will add the changes and rebuild the code on my setup. Will let you know
the results.

Regards,
Hamid.

On Wed, May 2, 2018 at 1:02 PM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco) <matfa...@cisco.com> wrote:

> https://gerrit.fd.io/r/#/c/12309/
>
>
>
> Matus
>
>
>
> *From:* Hamid Rasool <14mseesras...@seecs.edu.pk>
> *Sent:* Wednesday, May 2, 2018 7:24 AM
> *To:* Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) <
> matfa...@cisco.com>
>
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Figure out u16 mapping in NAT API output
>
>
>
> Dear Matus,
>
>
>
> Thanks for looking into it. So, is there any way I can apply any
> encoding/decoding formula on these values to obtain the correct mapping?
>
>
>
> Thanks,
>
> Hamid.
>
>
>
> On Wed, May 2, 2018 at 10:02 AM, Matus Fabian -X (matfabia - PANTHEON
> TECHNOLOGIES at Cisco) <matfa...@cisco.com> wrote:
>
> There is bug, fields are decoded wrong way in 
> vl_api_nat44_user_session_details_t_handler
> (nat_test.c)
>
> Just note, nat44_user_session_dump works only with non-deterministic NAT.
>
>
>
> Matus
>
>
>
>
>
> *From:* vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> *On Behalf Of *Hamid
> via Lists.Fd.Io
> *Sent:* Wednesday, May 2, 2018 6:50 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Figure out u16 mapping in NAT API output
>
>
>
> Cannot find a decoder for these fields so I think these incomprehensible
> value for port numbers and protocol number should be reported as a bug?
>
> 
>
>
>

Reply via email to