Timeline for Pinging broadcast address [closed]
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 11, 2023 at 14:50 | history | suggested | Matthias Braun | CC BY-SA 4.0 |
try to improve language
|
| Apr 11, 2023 at 12:38 | review | Suggested edits | |||
| S Apr 11, 2023 at 14:50 | |||||
| Sep 25, 2022 at 23:01 | history | closed | Ron Maupin♦ | Not suitable for this site | |
| Sep 25, 2022 at 22:45 | answer | added | Steve | timeline score: 3 | |
| Jan 21, 2021 at 9:57 | answer | added | Fuji San | timeline score: 2 | |
| May 19, 2020 at 12:00 | history | tweeted | twitter.com/StackNetworkEng/status/1262714693665390592 | ||
| May 19, 2020 at 4:19 | answer | added | JS-Ng | timeline score: 2 | |
| Mar 20, 2018 at 8:17 | comment | added | YLearn | I find it odd that you are getting duplicate echo replies. This would indicate a problem on your network of some sort. | |
| Mar 20, 2018 at 5:21 | comment | added | surya | superuser.com/questions/717627/unable-to-ping-broadcast-address might be helpful. As Ricky mentioned below, the times of machines responding to broadcasts are long gone. nmap might be a better way to scan the network with unicast pings. However, if you want to test the broadcasts, try it on routers on the same broadcast segment. | |
| Mar 20, 2018 at 2:45 | answer | added | spider | timeline score: -1 | |
| Jul 11, 2015 at 13:15 | vote | accept | ashok | ||
| Jul 11, 2015 at 1:54 | answer | added | Ricky | timeline score: 17 | |
| Jul 10, 2015 at 20:23 | comment | added | Todd Wilcox | Interesting note: Windows won't ping that address. | |
| Jul 10, 2015 at 19:34 | answer | added | phenetas | timeline score: -1 | |
| Jul 10, 2015 at 16:54 | history | asked | ashok | CC BY-SA 3.0 |