[VPP-2080] NAT44-ed : MW using the same port is failing

[vvalderrv]

Description

nat plugin is generating a new port for different threads in case that src port should be used in rewrite.

It can be seen with cmd "show nat44 sessions":

-------- thread 0 vpp_main: 0 sessions --------
-------- thread 1 vpp_wk_0: 2 sessions --------
    i2o 172.16.4.2 proto UDP port 1025 fib 4
    o2i 100.100.1.3 proto UDP port 1025 fib 0
       external host 172.31.128.100:12
       i2o flow: match: saddr 172.16.4.2 sport 1025 daddr 172.31.128.100 dport 12 proto UDP fib_idx 4 rewrite: saddr 100.100.1.3 sport 1025 daddr 172.31.128.100 dport 12 txfib 0 
       o2i flow: match: saddr 172.31.128.100 sport 12 daddr 100.100.1.3 dport 1025 proto UDP fib_idx 0 rewrite: daddr 172.16.4.2 dport 1025 txfib 4 
       index 1
       last heard 1.89
       timeout in 299.98
       total pkts 1, total bytes 28
       dynamic translation
    i2o 172.16.5.2 proto UDP port 1025 fib 5
    o2i 100.100.1.4 proto UDP port 1025 fib 0
       external host 172.31.128.100:12
       i2o flow: match: saddr 172.16.5.2 sport 1025 daddr 172.31.128.100 dport 12 proto UDP fib_idx 5 rewrite: saddr 100.100.1.4 sport 1025 daddr 172.31.128.100 dport 12 txfib 0 
       o2i flow: match: saddr 172.31.128.100 sport 12 daddr 100.100.1.4 dport 1025 proto UDP fib_idx 0 rewrite: daddr 172.16.5.2 dport 1025 txfib 5 
       index 2
       last heard 1.89
       timeout in 299.98
       total pkts 1, total bytes 28
       dynamic translation
-------- thread 2 vpp_wk_1: 1 sessions --------
    i2o 172.16.3.2 proto UDP port 1025 fib 2
    o2i 100.100.1.1 proto UDP port 34655 fib 0
       external host 172.31.128.100:12
       i2o flow: match: saddr 172.16.3.2 sport 1025 daddr 172.31.128.100 dport 12 proto UDP fib_idx 2 rewrite: saddr 100.100.1.1 sport 34655 daddr 172.31.128.100 dport 12 txfib 0 
       o2i flow: match: saddr 172.31.128.100 sport 12 daddr 100.100.1.1 dport 34655 proto UDP fib_idx 0 rewrite: daddr 172.16.3.2 dport 1025 txfib 2 
       index 0
       last heard 1.89
       timeout in 299.98
       total pkts 1, total bytes 28
       dynamic translation

The problem is that every thread has its own port range which can use.

Assignee

Juan diego Jacobo hernandez

Reporter

Daniel Béreš

Comments

No comments.

Original issue: https://jira.fd.io/browse/VPP-2080