Carlos E.R. wrote:
On 2023-04-18 21:43, Per Jessen wrote:
The same test, if run directly, without a switch, works perfectly.
On a ptp link, I'm sure it does.
It proves that the router has no problem responding a ping flood.
Well, yesterday I read the fping man page - with your scheme, you're not flooding anything (my mistake, I misread the meaning of the '-i' argument). It is one ping per second. If instead you use '-p' to reduce the interval between pings, you can indeed flood your router (or anything else). If I were running those ping tests, and if I kept seeing lost packets, I would try to identify the culprit. Look at the interface stats - maybe your router is responding just fine, but somehow the response is dropped.
Fine, suggest some other way to prove/test connectivity from computer to router.
I think I would try some large download, maybe an ISO file and then keep an eye on the interface stats. Run wireshark and look for tcp errors. Something like that.
Again: many web pages take seconds to start responding and load.
Yes, many websites have been getting increasingly top-heavy :-) I am not sure if testing with ping (icmp) is a particularly useful way of diagnosing slow-to-load websites (tcp). -- Per Jessen, Zürich (10.5°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes