Tough spot for a teacher... if this were my problem, I think I would first try to follow the systemd
procedure - the one you noted at the bottom of your question. @Ingo's answers are typically very thorough, and this answer has quite a few upvotes. He also provided another answer that contains some "checkpoints" that may be useful.
A few other comments that may or may not help... I make them only because your question omits some specifics:
With the stand-alone network you describe, there is no need for routers; a router would only be needed (for example) to route your stand-alone network traffic into the school's WiFi system, or directly to the Internet.
Re *"a simple way to do this?"*
: Simple is a relative term of course, but if you mean you do not wish to make configuration changes to your system, then I'd suggest you consider spending a bit of cash to get perhaps a human friendly commercial WiFi box - perhaps similar to this.
Also Re. "simple": One of the answers in your reference contains a link to the pi-ap
script that might take care of the pick and shovel work. I've not tried it, and can't comment except to say that it's not been updated in 3 years, has some open issues that go back a while, and the author hasn't posted in 2 years. OTOH, at least one report says it works well.
One recommendation:
If you elect to take on the pick and shovel work using either the systemd-networkd
approach, or Milliways' recommended RPi official approach, consider this for risk-mitigation:
When one makes configuration changes, there is always a risk of breaking your system; even seasoned admins face recovery risks. However, there is an outstanding and inexpensive risk mitigator available to all in the form of a spare SD card. I would strongly suggest that you start your systemd-networkd
(or RPi official approach) re-configuration using a newly-flashed SD card. Remove your current SD card, and set it aside for the time being. If your efforts wreck the system's networking configuration, restoration is a simple 60-second swap to your original SD card.
etc, etc
That likely concludes the actual answer
part of this answer. The remainder is offered FWIW:
One potential snag is that the procedures listed above were developed against the buster
version of RPi OS, and bullseye
is now current. I feel it's unlikely that the differences between buster
and bullseye
would derail the configuration, but as I've not tried this, please take that with a grain of salt!
As noted in Milliway's answer, systemd-networkd
is an alternative to the more conventional procedure outlined in the "official documentation", but his answer leaves it unclear whether or not he has verified that procedure.
Inevitably, it comes down to your choice. I felt for years that a visit to the dentist's office was the only thing worse than learning systemd
, but I now admit that it does have some useful aspects, and even this Luddite now uses it for a few things. systemd
currently acts in the role of init
on your RPi; huge role in your current RPi as the init
systemd
apparently aims to be all things to all people, and systemd-networkd
is the project's foray into networking. In general, networking is a rather fragmented business in Linux with several competing schemes, and the idea of having a single approach that works across all platforms is a compelling one.
Debian's (and therefore RPi OS) current approach to networking does not use systemd-networkd
. RPi OS specifically uses dhcpcd
as its network manager, and dhcpcd
cannot be run concurrently with systemd-networkd
.