I've encountered the following problem while using the NAT (Network Address
Translation, Port Forwarding) mechanism. VPP is running on the central device.
One interface faces the external world and is configured as an ' *out* '
interface. The other two interfaces face local network segments and are
configured as ' *in* ' interfaces.
A port forwarding rule has been set up on the central device, which forwards
port 22 traffic destined for the external IP address to a local device, dev_2.
This part works predictably.
Next, I try to access device dev_2 from device dev_3, also using the port for
which forwarding is configured (I used port 22 as an example, but it could be
any other port). My expectation is that the NAT mechanism should not trigger
for the local ('in') interfaces. Traffic should be handled by routing alone.
HOWEVER, I see that the correct packet arrives at the target device, but it is
immediately followed by a packet that has passed through the port forwarding
rule, even though this rule should not apply to the 'in' interfaces. Other
traffic between devices dev_2 and dev_3 is transmitted correctly. This problem
only occurs when a port forwarding rule exists.
Has anyone else encountered this same behavior with the NAT mechanism?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#26542): https://lists.fd.io/g/vpp-dev/message/26542
Mute This Topic: https://lists.fd.io/mt/116414691/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
