It doesn’t happen a lot, but every so often I come across a device that isn’t wi-fi supported. This latest case was my security system. On one hand, I like that my cameras aren’t taking up bandwidth on my home network and that the system is largely a closed loop. On the other, not having access to my security system without having it tethered into the router is a bit of a pain. For one, my home networking setup isn’t that elegant (yet). Second, the last thing I want to do is have more stuff out in the open, co-located with my router. So I decided to get a little creative. Sure, I could’ve bought a wi-fi adapter, but where’s the fun in that. On top of that, I had some other reasons:
- I didn’t want to spend money on an adapter for this system. Even though they aren’t that expensive, I would likely need to wait for one to come in which would probably happen after I left for my trip.
- Eventually, I want to do some real-time video processing and having a device closer to the box is promising. This would let me process data straight from the box rather than needing to transmit all that information over wi-fi to another machine.
- Finally, I already have more than a dozen pis around. For the first version of this, I wound up using a 3b+. I would likely upgrade this later on when I add the real-time processing.
Today, I show how I set up and configured a Raspberry Pi to act as a WAN client for a connected device.