While Linux can happily handle that zone as a source of or destination for traffic, most networking equipment deliberately doesn’t recognize its existence – and those boxes can’t easily be upgraded.
Any particular reason that those OEMs made that decision when releasing those boxes? Was that range blacklisted in firmware because of the legacy specification? I thought the spec just forebode range’s public allocation, but not necessarily its internal use.
Any particular reason that those OEMs made that decision when releasing those boxes? Was that range blacklisted in firmware because of the legacy specification? I thought the spec just forebode range’s public allocation, but not necessarily its internal use.
I think that’s what it means: that firmware respects the spect and doesn’t route that range – I doubt you wouldn’t be able to use it on your LAN.