summaryrefslogtreecommitdiff
path: root/net/netfilter/nft_last.c
diff options
context:
space:
mode:
authorHangbin Liu <liuhangbin@gmail.com>2023-02-27 12:36:46 +0300
committerPablo Neira Ayuso <pablo@netfilter.org>2023-03-01 19:23:23 +0300
commit2067e7a00aa604b94de31d64f29b8893b1696f26 (patch)
treed3d588311a29f64121f69885021aeb4b3835054e /net/netfilter/nft_last.c
parent8f9850dd8d23c1290cb642ce9548a440da5771ec (diff)
downloadlinux-2067e7a00aa604b94de31d64f29b8893b1696f26.tar.xz
selftests: nft_nat: ensuring the listening side is up before starting the client
The test_local_dnat_portonly() function initiates the client-side as soon as it sets the listening side to the background. This could lead to a race condition where the server may not be ready to listen. To ensure that the server-side is up and running before initiating the client-side, a delay is introduced to the test_local_dnat_portonly() function. Before the fix: # ./nft_nat.sh PASS: netns routing/connectivity: ns0-rthlYrBU can reach ns1-rthlYrBU and ns2-rthlYrBU PASS: ping to ns1-rthlYrBU was ip NATted to ns2-rthlYrBU PASS: ping to ns1-rthlYrBU OK after ip nat output chain flush PASS: ipv6 ping to ns1-rthlYrBU was ip6 NATted to ns2-rthlYrBU 2023/02/27 04:11:03 socat[6055] E connect(5, AF=2 10.0.1.99:2000, 16): Connection refused ERROR: inet port rewrite After the fix: # ./nft_nat.sh PASS: netns routing/connectivity: ns0-9sPJV6JJ can reach ns1-9sPJV6JJ and ns2-9sPJV6JJ PASS: ping to ns1-9sPJV6JJ was ip NATted to ns2-9sPJV6JJ PASS: ping to ns1-9sPJV6JJ OK after ip nat output chain flush PASS: ipv6 ping to ns1-9sPJV6JJ was ip6 NATted to ns2-9sPJV6JJ PASS: inet port rewrite without l3 address Fixes: 282e5f8fe907 ("netfilter: nat: really support inet nat without l3 address") Signed-off-by: Hangbin Liu <liuhangbin@gmail.com> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'net/netfilter/nft_last.c')
0 files changed, 0 insertions, 0 deletions