Don_Dickle@lemmy.world to Today I Learned@lemmy.worldEnglish · 11 days agoTIL the network utility "Ping" was written by a single person in an evening in 1983, and he named it after the sound a submarine sonar makesen.wikipedia.orgexternal-linkmessage-square61linkfedilinkarrow-up1630arrow-down16cross-posted to: todayilearned@lemmit.online
arrow-up1624arrow-down1external-linkTIL the network utility "Ping" was written by a single person in an evening in 1983, and he named it after the sound a submarine sonar makesen.wikipedia.orgDon_Dickle@lemmy.world to Today I Learned@lemmy.worldEnglish · 11 days agomessage-square61linkfedilinkcross-posted to: todayilearned@lemmit.online
minus-squareBaggie@lemmy.ziplinkfedilinkEnglisharrow-up3·10 days agoMan they really need to check for loops in the network, that sounds like a feedback loop. Although my experience only goes back to like 2012 so it might have been a older hardware thing
minus-squareLandless2029@lemmy.worldlinkfedilinkEnglisharrow-up1·9 days agoI mean a easier and sinister solution would be to unplug two computers and patch the two ports together. Broadcast storm.
minus-squareBaggie@lemmy.ziplinkfedilinkEnglisharrow-up1·8 days agoAh that’s the term I forgot, had a nasty one 2014 before I repatched all the servers. Took the office network out for a few hours before I fixed it
Man they really need to check for loops in the network, that sounds like a feedback loop. Although my experience only goes back to like 2012 so it might have been a older hardware thing
I mean a easier and sinister solution would be to unplug two computers and patch the two ports together. Broadcast storm.
Ah that’s the term I forgot, had a nasty one 2014 before I repatched all the servers. Took the office network out for a few hours before I fixed it