At the root of it is a cultural conflict, which won't make much sense in the global village. Still I'll give it a try.
A South-Asian country has invested on electricity and Internet connectivity to most of its bigger rural schools. Rudimentary, still quite a feat. The problem is the client device. So far only PCs in the cabled LAN are allowed - for (physical) security and to protect the root of the culture, the young school kids, from the ugly things that travel the same lines. A big topic, for us it means no Wi-Fi connectivity.
My argument is for a wall-mounted MoodleBox, giving Wi-Fi access to its own content. The schools I know are small enough that one MoodleBox would suffice. Still the MoodleBox need access from the Ethernet LAN for maintenance, for the teachers in the Ethernet LAN, for example. So the default is no routing. But for special occasions, the routing may be activated.
As I said, this is an argument put to the IT people. When I re-think, quite a lot could be achieved even if routing is permanently disabled, as long as the MoodleBox is reachable in the Ethernet LAN. I can show them how to do that on the Linux CLI.
Long story, there is no strong need. Not worth touching MoodleBox for a potential application. There are plenty of other problems unrelated to MoodleBox.