packet loss? #6

New Issue

sb10q · 2019-09-29T16:27:07+08:00

sb10q commented

2019-09-29 16:27:07 +08:00

On ZC706:

sudo arping 192.168.1.56

ARPING 192.168.1.56 from 192.168.1.1 enp3s0
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.600ms
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.707ms
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.689ms
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.703ms
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.703ms
Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF]  0.669ms
^C***Sent 15*** probes (1 broadcast(s))
***Received 6*** response(s)

Seems to affect other packets as well, as attempting to open a TCP connection to a closed port has a random delay before the "connection refused" error.

On ZC706: ```text sudo arping 192.168.1.56 ARPING 192.168.1.56 from 192.168.1.1 enp3s0 Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.600ms Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.707ms Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.689ms Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.703ms Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.703ms Unicast reply from 192.168.1.56 [00:23:DE:EA:BE:EF] 0.669ms ^C***Sent 15*** probes (1 broadcast(s)) ***Received 6*** response(s) ``` Seems to affect other packets as well, as attempting to open a TCP connection to a closed port has a random delay before the "connection refused" error.

sb10q commented

2019-11-07 13:36:54 +08:00

Poster

Working fine now.

sb10q closed this issue

2019-11-07 13:36:54 +08:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/zynq-rs#6