Timeline for Can communication to broadcast 224.0.0.1 be made to reach hosts outside of the local subnet?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2019 at 5:20 | history | edited | Ron Maupin♦ |
edited tags
|
|
| Oct 10, 2019 at 16:17 | comment | added | Ricky | To be very non-PC, the person(s) who designed this "solution" are morons who don't know anything about multicast. 224.0.0.1 is "every multicast capable node on the segment", not just the ones interested in whatever your specific application is pushing. (I see this sort of misuse of 224.0.0.x all the time. eg. nuts sending video streams to 224.0.0.1) | |
| Oct 10, 2019 at 8:53 | comment | added | IllvilJa | It is not a schoolwork situation. I got a CCDP so I have studied the subject. It is from a real life situation with people having a situation where they depend on using 224.0.0.1 to reach certain machines and it turned out that one of those machines happened to be on a different subnet. Hence the question "can you make the network forward it so we don't need to change our stuff?" being asked. There was some actual beliefs that such a functionality existed and I posted this question as a sanity check before saying "No" to them. | |
| Oct 10, 2019 at 8:31 | vote | accept | IllvilJa | ||
| Oct 10, 2019 at 6:20 | review | Close votes | |||
| Oct 10, 2019 at 13:13 | |||||
| Oct 10, 2019 at 6:18 | answer | added | Ron Maupin♦ | timeline score: 7 | |
| Oct 10, 2019 at 6:03 | comment | added | Ron Trunk | This sounds very much like a schoolwork question, which sadly is off topic here. | |
| Oct 10, 2019 at 4:51 | history | asked | IllvilJa | CC BY-SA 4.0 |