On 2017-09-20 00:12, Alarig Le Lay wrote:
Because this range is not aimed to be routed or added to any host, cf. https://tools.ietf.org/html/rfc1112 section 4.
Section 4 defines only 224.0.0.0/4 (multicast), but in my case it is 240.0.0.0/4
Though this space is "reserved for future addressing modes", I see no reason
why it is "bogus", especially when routers perfectly accept them. Hardcoding anything that is not loopback is bad idea, IMHO. Best regards, Alexander.
