On Wed, Apr 19, 2023 at 2:47 PM Per Jessen <per@opensuse.org> wrote:
Carlos E. R. wrote:
Isengard:~ # while sleep 1 ; do DATE=`date --iso=s` ; echo -n "$DATE " ; fping -c 20 --period=100 --quiet 2a02:...80d4 ; done
2023-04-19T10:11:07+02:00 2a02:...:80d4 : xmt/rcv/%loss = 20/16/20%, min/avg/max = 0.45/0.53/0.69 2023-04-19T10:11:10+02:00 2a02:...:80d4 : xmt/rcv/%loss = 20/0/100% 2023-04-19T10:11:13+02:00 2a02:...:80d4 : xmt/rcv/%loss = 20/11/45%, min/avg/max = 0.47/1.09/5.45
What do you make of 100%& loss?
Even at 10 pings/second, that is surely not right. Some questions are -
a) do the echo requests reach your router? b) does your router respond with echo replies? c) does isengard receive the echo reply?
Briefly looking at documentation for this switch, it should support port mirroring so one could capture what happens on the router side.
telcontar, same period
2023-04-19T10:10:01+02:00 router : xmt/rcv/%loss = 100/86/14%, min/avg/max = 0.27/0.39/4.83 2023-04-19T10:10:12+02:00 router : xmt/rcv/%loss = 100/92/8%, min/avg/max = 0.22/0.38/4.82 2023-04-19T10:10:23+02:00 router : xmt/rcv/%loss = 100/88/12%, min/avg/max = 0.27/0.39/4.13
10% unanswered pings still seems pretty high, even at 10/sec, but way better. What is the difference between isengard and telcontar?
Yes, the very first question :)