Both sides of the pi3 Networking are active so it can be it’s own Wi-Fi router
but also bridge to a physical ethernet
. You may have to do some tweaking of IP addresses. Image
for the pi three is set to 192.168.0.1. For the Wi-Fi side. And it’s pretty easy to set your own fixed IP for the ethernet
side. My ethernet
is in the 192.16 8.1.*Range.You do have to have an individual device for each headset
running a Mumble client. Doesn’t have to be a pie zero. Could be an OLd pc Thin client etc
But in your environment it’s probably best to standardize, and as cheap as the pie zeros are yes kind of a no brainer. They can connect via Wi-Fi even if they’re sitting right next to your base
, or they can connect via ethernet
but they don’t have an ethernet
port like the three. They would need an adapter
for wired Cat 5. so it’s probably easiest if you have to have part of your client farm away from the base
to use either a pie three, or what we do is we have a Wireless repeater that the pi zero talks to.
I have all of my stations set up for VNC access. That way I can see status or if I need to repeat the headphone set up and calibration it can be done without having to attach a keyboard and monitor
. I used fixed IP addresses throughout.
It took me a while to get a nice stable zero client image
. I have one now. Part of the problem was I created one on an eight gig card and burn it to a 16 and the system
would run out of space because some of the file handling is wonky. So I have a 16 image
That works now and I would only burn it to a 16 SD card. Similarly the base
pay three image
I believe Is an eight gig. I keep one inside the cover
as a spare pre configured But have never had to use it
I have been using the SanDisk SD cards I hear there’s some real crap out there.