Talk:Broadcast storm

Query
Please add to this. Where is this a problem. What kinds of networks. What usually causes it. This stub is about the extent of my knowledge/experience with such things. —Preceding unsigned comment added by Rgarvage (talk • contribs)

This needs a diagram showing the looping etc. 195.195.0.77 14:44, 19 October 2006 (UTC)

Move discussion in progress
There is a move discussion in progress on Talk:Broadcast radiation which affects this page. Please participate on that page and not in this talk page section. Thank you. —RMCD bot 17:18, 21 October 2020 (UTC)

Info
commonly you can identify a broadcast storm by synchronous blinking of the switch.

"A misinterpretation is that a broadcast can be responded to with a broadcast. This is not true. A broadcast can, however, be issued to gather information needed to respond to an initially received broadcast. In a redundant looped topology this second broadcast can reach the interface that sent the initial broadcast."

what does this mean? a broadcast can indeed be responded to with a broadcast by a host or an application written to do this. the old "send ping to broadcast, from broadcast" (I think it is called chernobyl packet or something like that) used to work because the hosts would respond to the broadcast with one of their own. 65.51.90.2 (talk) 22:27, 20 May 2011 (UTC)


 * I see problems understanding the entire Misinterpretation section. It needs to be cleaned up. The whole article is marked for cleanup, in fact. --13:22, 22 May 2011 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 3 one external links on Broadcast radiation. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added tag to http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd20e.htm
 * Added archive https://web.archive.org/web/20061211033218/http://www.securitydocs.com:80/library/2553 to http://www.securitydocs.com/library/2553
 * Added archive https://web.archive.org/web/20061022124143/http://www.securitydocs.com/pdf/2553.PDF to http://www.securitydocs.com/pdf/2553.PDF
 * Added archive https://web.archive.org/web/20061211001411/http://manageengine.adventnet.com:80/products/wifi-manager/disassociation-broadcast-attack.html to http://manageengine.adventnet.com/products/wifi-manager/disassociation-broadcast-attack.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 02:51, 9 November 2016 (UTC)

Requested move 21 October 2020

 * The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this section. 

Broadcast radiation → broadcast storm – Never heard of layer-2 loops or broadcast storms being referred to as &#8220;broadcast radiation.&#8221; Sounds to me more like a term relating to electro-magnetic radiation. Bwrs (talk) 16:45, 21 October 2020 (UTC) —Relisting. -- Calidum  18:51, 29 October 2020 (UTC)


 * The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.