On Fri, May 15, 2020 at 2:38 PM Jon Loeliger <j...@netgate.com> wrote:
>
> So, here is the same scenario using vppctl to set up the test case.
>
> vpp# nat44 add static mapping icmp local 192.168.0.53 external outside
> vpp# show nat44 static mappings
> NAT44 static mappings:
> local 192.168.0.53 external 192.168.0.53 vrf 0
> local 192.168.0.53 external outside vrf -1
>
Ole et al,
I have a better understanding of what is going on now.
The key understanding necessary is this:
The phrase "address only", and the variable "addr_only" within the
static NAT code
means "no port and no protocol".
If one sets a port, even if 0, the "address only"-ness is now "false".
However, the same is NOT true for using a protocol. But the both the
ports and protocol
are nonetheless ignored in the NAT lookup keys later via checks on the
addr_only flag.
Bottom line here is this:
Correct and expected behavior for ICMP traffic can be achieved from the
vppctl command
by specifying ports even though they are irrelevant to ICMP traffic.
Proper "address only" mappings (ie, no ports and no protocol) should not
need to have
a protocol specified.
And hey, if I am way off base here, please come shake my cage.
HTH,
jdl
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16413): https://lists.fd.io/g/vpp-dev/message/16413
Mute This Topic: https://lists.fd.io/mt/74208726/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
