* [LTP] [PATCH] ipneigh01.sh: Fix an issue where ipneigh01_arp test case fail due to ARP timeout
@ 2023-08-15 8:57 Xu Senmiao via ltp
2023-09-22 9:10 ` Petr Vorel
0 siblings, 1 reply; 2+ messages in thread
From: Xu Senmiao via ltp @ 2023-08-15 8:57 UTC (permalink / raw)
To: ltp
When the ARP status of the rhost is stale,
lhost ping rhost and the lhost deletes the ARP record,
the record in the rhost changes from stale to delay.
Then, the probe request is sent to the lhost, and the lhost ARP information is updated.
rhost(10.0.0.1) lhost(10.0.0.2)
t1 10.0.0.2 STALE ping 10.0.0.1
10.0.0.1 REACHABLE
arp -d 10.0.0.1
t2 10.0.0.2 DELAY
t3 probe 10.0.0.2
t4 10.0.0.1 REACHABLE
Clear the ARP entries of rhost before each round of test.
Signed-off-by: Xu Senmiao <xusenmiao@huawei.com>
---
testcases/network/tcp_cmds/ipneigh/ipneigh01.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh b/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
index e67ff5cc8..4db675f8f 100755
--- a/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
+++ b/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
@@ -56,6 +56,7 @@ do_test()
tst_res TINFO "stress auto-creation $entry_name cache entry deleted with '$CMD' $NUMLOOPS times"
for i in $(seq 1 $NUMLOOPS); do
+ tst_rhost_run -c "arp -d $(tst_ipaddr lhost)"
ping$TST_IPV6 -q -c1 $(tst_ipaddr rhost) -I $(tst_iface) > /dev/null || \
tst_brk TFAIL "cannot ping $(tst_ipaddr rhost)"
--
2.33.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [LTP] [PATCH] ipneigh01.sh: Fix an issue where ipneigh01_arp test case fail due to ARP timeout
2023-08-15 8:57 [LTP] [PATCH] ipneigh01.sh: Fix an issue where ipneigh01_arp test case fail due to ARP timeout Xu Senmiao via ltp
@ 2023-09-22 9:10 ` Petr Vorel
0 siblings, 0 replies; 2+ messages in thread
From: Petr Vorel @ 2023-09-22 9:10 UTC (permalink / raw)
To: Xu Senmiao; +Cc: ltp
Hi Xu,
> When the ARP status of the rhost is stale,
> lhost ping rhost and the lhost deletes the ARP record,
> the record in the rhost changes from stale to delay.
> Then, the probe request is sent to the lhost, and the lhost ARP information is updated.
> rhost(10.0.0.1) lhost(10.0.0.2)
> t1 10.0.0.2 STALE ping 10.0.0.1
> 10.0.0.1 REACHABLE
> arp -d 10.0.0.1
> t2 10.0.0.2 DELAY
> t3 probe 10.0.0.2
> t4 10.0.0.1 REACHABLE
> Clear the ARP entries of rhost before each round of test.
Do you have idea why ARP status of the rhost is stale?
I've never encountered problem like this.
> Signed-off-by: Xu Senmiao <xusenmiao@huawei.com>
> ---
> testcases/network/tcp_cmds/ipneigh/ipneigh01.sh | 1 +
> 1 file changed, 1 insertion(+)
> diff --git a/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh b/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
> index e67ff5cc8..4db675f8f 100755
> --- a/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
> +++ b/testcases/network/tcp_cmds/ipneigh/ipneigh01.sh
> @@ -56,6 +56,7 @@ do_test()
> tst_res TINFO "stress auto-creation $entry_name cache entry deleted with '$CMD' $NUMLOOPS times"
> for i in $(seq 1 $NUMLOOPS); do
> + tst_rhost_run -c "arp -d $(tst_ipaddr lhost)"
IMHO we use $DEL_CMD as we use later in the test function, because some systems
does not have arp installed. i.e. use the tool which is used for testing.
Otherwise we endup with: sh: arp: command not found
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-09-22 9:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-15 8:57 [LTP] [PATCH] ipneigh01.sh: Fix an issue where ipneigh01_arp test case fail due to ARP timeout Xu Senmiao via ltp
2023-09-22 9:10 ` Petr Vorel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox