Our last house was big. Or at least, long. Long enough that your average router’s built-in WiFi wouldn’t reach every room properly. Since we moved in to that house in 2013, the wireless network I built predated today’s wonderful collection of mesh-based WiFi systems. The likes of the Netgear Orbi, Linksys Velop and Google Wifi devices didn’t yet exist. So I bought a bunch of Ubiquiti‘s UniFi kit (four access points in total) and spread them through the house.
This setup wasn’t as seamless or quick to set up as these new systems appear to be, but once configured it has been rock solid. The controller for these devices started life as the default install of Ubiquiti’s Java app on a Windows server, then later as a Docker image on a Synology Diskstation. For various reasons (mostly to do with constrained bandwidth) I’m not running that Synology or a powerful permanent server in the new house, but I still wanted a controller for the UniFi kit – especially as I intend to try their USG as a gateway device.
So, what were my options? Continue reading
In the category of things I do when I should be preparing to move house, I present the Iron Man Status Mask. A Raspberry Pi running a Python based RESTful API inside an Iron Man mask that can indicate any colour via his eyes. As you can imagine, Lindsay is thrilled.
I ranted a little on Twitter about OpenReach and their inability to connect a second line, a line I ordered four months ago. To be clear: I have no problem with the BT engineers – they’ve all been knowledgeable, polite and just as frustrated by the whole thing as I am. It is the admin they swim in that lets the whole thing down…
Update 27/02/2011: Added IR control and password passthrough.
I’ve recently put together a CCTV solution using a few Foscam FI8918W cameras and the excellent ZoneMinder software. This is all running on a CentOS 5.5 virtual machine under Hyper-V (more on this setup another time). The Foscam cameras have pan, tilt and the ability to set and move to preset locations. Continue reading
After a frustrating morning testing several different updated firmwares, I’ve determined that NAT (Network Address Translation) loopback is broken on firmwares 220.127.116.11 and 18.104.22.168 for the Draytek Vigor 2820VN. Other routers in the family are likely to be similarly affected.