Hi, Your use case is not supported now, you can configure multiple outside interfaces but it has very limited usage, “multiple outside interfaces” is in work list https://wiki.fd.io/view/VPP/NAT#Work_list.
Regards, Matus From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of st.linux.ily via vpp-dev Sent: Wednesday, September 27, 2017 1:25 PM To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] NAT plugin -- Input ACL support before NAT and Multiple outside interfaces Hi Matus, From https://lists.fd.io/pipermail/vpp-dev/2017-March/004393.html, I know it's support multiple outside interfaces. But how to make the taffic do the correct NAT action? For example: traffic to 192.168.20.22 will go to host-wan1 with 192.168.20.20 as new source ip; traffic to 192.168.30.22 will go to host-wan2 with 192.168.30.20 as new source ip; vpp# show nat44 detail NAT plugin mode: dynamic translations enabled loop0 in host-wan1 out host-wan2 out 192.168.20.20 tenant VRF independent 0 busy udp ports 0 busy tcp ports 10 busy icmp ports 192.168.30.20 tenant VRF independent 0 busy udp ports 0 busy tcp ports 0 busy icmp ports Requirement: Destination-based NAT scenarios where the same inside address needs to be translated to more than one outside address, depending on where the traffic is destined. Thanks in advance! BR, xliao
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
