We learn something new every day. This is a community dedicated to informing each other and helping to spread knowledge.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rule 1- All posts must begin with TIL. Linking to a source of info is optional, but highly recommended as it helps to spark discussion.
** Posts must be about an actual fact that you have learned, but it doesn't matter if you learned it today. See Rule 6 for all exceptions.**
Rule 2- Your post subject cannot be illegal or NSFW material.
Your post subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-TIL posts.
Provided it is about the community itself, you may post non-TIL posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you vocally harass or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
When my cousin learned about Ping at school in the 2000s he setup ping gateway -t on all the computers in his highschool class.
Took down the school network for the day. He didn't get in trouble I think. Just a laugh from the school admin (they knew each other and he volunteered there). Admin blocked ping after that.
What was the rate of packets sent? Modern ping is typically setuided and has a limit of 1 per second if you're not root.
First thing you do to debug connectivity to a remote host problem is the ol' ping.
I learned about pings in college, because apparently my torrent client was constantly sending them, but the university network did not allow pings and they sent an email threatening to shut off my internet if I didn't stop pinging.
At work we say "i pung it"
Because pinged doesn't sound right. And pung is more fun.
Another one we haven't named yet is when an address goes through translation. Is it NATted? "Its been NATted"
Doesn't feel right.
Oh so 'NUT' is not work appropriate language? Take it up with the author of NAT and with linguists
That person was Mike Muuss, who tragically died in a car crash in 2000, only 42 years old.
Pong
Ping?
Pong
!
In a cli type "ping 8.8.8.8"
command not found: in
digging through man pages makes you realize that most of the stuff that makes the modern internet consists of one-man projects glued together.
It's also when the scope of those projects could be accomplished by one person.
The original idea behind Unix was to have small tools doing very specific task and do it will.
Then you could use shell to combine them together to do more advanced stuff.
Even if projects could be solo efforts, it's probably better to avoid the bus factor.
Even worse than bus factor, it’s really easy to compromise when no one double checks your work:
What’s your BGB Plan? (Big Green Bus, I guess you could alter for the colour of buses in your city)
And many of those one men were Dave Plummer
I love it when the TILs read like "I discovered my toes and they're called toes".
Vasili. One ping only.
"PING! The magic duck!
Using deft allegory, the authors have provided an insightful and intuitive explanation of one of Unix’s most venerable networking utilities.
Even more stunning is that they were clearly working with a very early beta of the program, as their book first appeared in 1933, years (decades!) before the operating system and network infrastructure were finalized.
The book describes networking in terms even a child could understand, choosing to anthropomorphize the underlying packet structure. The ping packet is described as a duck, who, with other packets (more ducks), spends a certain period of time on the host machine (the wise-eyed boat).
At the same time each day (I suspect this is scheduled under cron), the little packets (ducks) exit the host (boat) by way of a bridge (a bridge). From the bridge, the packets travel onto the internet (here embodied by the Yangtze River).
The title character — er, packet, is called Ping. Ping meanders around the river before being received by another host (another boat). He spends a brief time on the other boat, but eventually returns to his original host machine (the wise-eyed boat) somewhat the worse for wear.
If you need a good, high-level overview of the ping utility, this is the book. I can’t recommend it for most managers, as the technical aspects may be too overwhelming and the basic concepts too daunting.
As good as it is, The Story About Ping is not without its faults. There is no index, and though the ping(8) man pages cover the command line options well enough, some review of them seems to be in order. Likewise, in a book solely about Ping, I would have expected a more detailed overview of the ICMP packet structure.
But even with these problems, The Story About Ping has earned a place on my bookshelf, right between Stevens’ Advanced Programming in the Unix Environment, and my dog-eared copy of Dante’s seminal work on MS Windows, Inferno.
Who can read that passage on the Windows API (“Obscure, profound it was, and nebulous, So that by fixing on its depths my sight — Nothing whatever I discerned therein.”), without shaking their head with deep understanding. But I digress."
This review was so good I had to see if it was a real book! It is: The story about Ping.
Bravo, the world needs more reviews like this.
Bravo.
ACK
It was also backronym'd to mean Packet Internet Groper, but I get why not a lot of people would want to embrace that
time to grope me some internet real quick. Just grabbing those packets and going all in
I've never heard that before and I was better for it.
Well it goes along with the ethos of other commands suck as touch, finger, mount,...
Is the response back called a "pong"?
That name was already taken in the software world ;)
I believe it's technically called an "echo response", but "pong" is a very common unofficial name for it.
I thought it was called that because of pingpong where you shoot a ball and the other person shoots it back.
I could have written it, too.
But today it has a lot more features.
Fun fact, most military ships and submarines use fmcw sonar, that doesn't really ping in the same way.
Fuck My Concurrent Walrus?
yes. they use the slapping sound of someone on board fucking walruses as the ping sound