Hi all, I'm using nat44 plugin to test to achieve the following:
■what someone wants to achieve - nat each outer-ip to the expected ip without specifying ports For example, if the outer-ip received is 10.1.1.2, nat 10.1.1.3 Also, if the outer-ip received is 10.1.1.4, nat 10.1.1.5. I did the following nat44 configuration and tried to achieve it, but the unexpected nat processing was done. In fact, if outer-ip was 10.1.1.2, it was nat to 10.1.1.5 instead of 10.1.1.3 ■nat44 configuration ``` vpp# sh nat44 interfaces NAT44 interfaces: GigabitEthernet1b/0/0 in GigabitEthernet13/0/0 in vpp# sh nat44 addresses NAT44 pool addresses: 10.1.1.2 tenant VRF: 1 0 busy other ports 0 busy udp ports 0 busy tcp ports 0 busy icmp ports 10.1.1.3 tenant VRF: 1 0 busy other ports 0 busy udp ports 0 busy tcp ports 0 busy icmp ports 10.1.1.4 tenant VRF: 2 0 busy other ports 0 busy udp ports 0 busy tcp ports 0 busy icmp ports 10.1.1.5 tenant VRF: 2 0 busy other ports 0 busy udp ports 0 busy tcp ports 0 busy icmp ports NAT44 twice-nat pool addresses: vpp# sh nat44 static mappings NAT44 static mappings: local 192.168.140.100 external 10.1.1.2 vrf 1 local 192.168.150.50 external 10.1.1.3 vrf 1 local 192.168.140.100 external 10.1.1.4 vrf 2 local 192.168.150.50 external 10.1.1.5 vrf 2 ``` Here may be the question: *In order to achieve the above, is there a mistake in the configuration of nat44?* Any suggestion would be helpful. Best Regards, Kyosuke Hori
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20574): https://lists.fd.io/g/vpp-dev/message/20574 Mute This Topic: https://lists.fd.io/mt/87448375/21656 Mute #nat44:https://lists.fd.io/g/vpp-dev/mutehashtag/nat44 Mute #vpp:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp Mute #nat:https://lists.fd.io/g/vpp-dev/mutehashtag/nat Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
