>
> 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] Fi
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)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Figure out u16 mapping in NAT API output
Dear
o
> *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?
>
>
>
@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?
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?
Hi,
I wanted some information for my deterministic and non-deterministic NAT
sessions but I was unable to figure out the port numbers and protocol ID from
the result.
Here is a snippet of the output I have obtained:
vat# nat44_user_session_dump ip_address 100.64.0.3 vrf_id 0
dynamic session 10
