From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Wed, 30 Dec 2015 23:36:22 GMT." <717ee4c69b676df9ba38b2297197add7@quintile.net> References: <717ee4c69b676df9ba38b2297197add7@quintile.net> Date: Wed, 30 Dec 2015 16:16:34 -0800 From: Bakul Shah Message-Id: <20151231001634.A91CBB827@mail.bitblocks.com> Subject: Re: [9fans] bug or feature ? --- ip/ping -6 Topicbox-Message-UUID: 7b857e12-ead9-11e9-9d60-3106f5b1d025 On Wed, 30 Dec 2015 23:36:22 GMT "Steve Simon" wrote: > > It is not a common factor if you ping broadcast. > > Yep, fair point. If you're pinging plan9 machines, printing source address is not useful as they sebd ping replies with source = broadcast ip address. You have to look at the source ether addr to find out which machine responded. > I admit I have never done a ping broadcast. > > I did hear a story of somone who (in the early days of ethernet) > built a ping broadcast packet, with the source address of the broadcast addre > ss. > > This resulted in the mother of all packet storms. > > Maybe apocryphal, but a nice story none the less. Seems apocryphal or must've been very early days! Ping consists of sending an ICMP request packet, followed by the responder(s) sending back ICMP reply packat(s). No ICMP errors are sent in response to any ICMP message to avoid just such a storm. Ages ago you could send a *directed* broadcast to a place far away, which would get routed to the right subnet and many or all machines on that subnet would respond. Back then the 'Net was a friendlier place and people didn't use NAT and script kiddies were rather rare. All that changed a couple decades ago.