Also this story is about problems with the connection of their house, not the wi-fi. I find it hard to believe that a networking engineer and his son that's also an engineer use the incorrect term?
Also this story is about problems with the connection of their house, not the wi-fi. I find it hard to believe that a networking engineer and his son that's also an engineer use the incorrect term?
Depends on the OS. Linux and macOS ping will keep pinging until you ctrl+c. Windows ping I guess is what you're talking about? Even then, I assume Windows ping has a command-line option to change the default number of pings.
> Even if you increase the count, after 20 lost packages wouldn't you have decided the connection isn't up?
Maybe not? It feels like you're just trying to come up with random excuses as to why this isn't real.
> Also this story is about problems with the connection of their house, not the wi-fi.
The connection to their house is a point-to-point line-of-sight WiFi link between the house and the author's father's office building.
Re: your other comment. When my dad has problems with the internet, he will say the wifi is not working. And this isn’t incorrect, even if the source of the issue is not happening between the router and his device. Sure, the underlying issue may be something else. But by that logic putting anything but the final root cause in the title would be misleading or “real network engineers wouldn’t do that”, but I would argue that would just be bad storytelling..