For years I’ve been searching for a passively cooled 16-24 port L2 managed POE switch to replace a Cisco SG110-16HP unmanaged POE switch. Seemingly impossible, the need to play with VLANs made me give up on this search and ended up buying a Netgear GS324TP.
The main compromise in choosing this was that it offered “near silent” operation by only spinning the fans when needed, compared to other switches where fans are on permanently.
Trouble is, when the fans do spin on the GS324TP they are audibly intrusive, whether brand new or a few months in they sound like the bearings are failing with a knock that matches the RPM, deploying four of these units previously with the same harmonics suggest it’s not a one off.
This isn’t good news when I intend to work a few feet from the switch, but from testing before the latest deployment, there’s a couple of ways to keep the GS324TP near silent…
The firewalls in front of our PBX’s are configured to only allow SIP traffic from UK IP addresses, this reduces the attack surface and is usually not an issue as almost all legitimate traffic is from the UK.
As we expand there is greater need for international connections, this is fine if they have a static WAN IP or FQDN, but the more recent requirements are for “home” users with phones on their residential connections where dynamic IPs are the standard.
Changing the whitelisted IP every time their IP changes is not only tedious, but gives poor service, plus due to recent events (here and here) I’m not prepared to open access to another country for a single extension.
In my case, these internationals are satellites of a UK based office, so the idea is having the overseas phone route all voice traffic through the UK office where its free to connect to the PBX…
A Draytek, be it a 2765, 2865, or 2927 based on WAN connectivity and LAN complexity is my go to device for a router. More than likely these are the ‘ac’ variants as WiFi provision is expected rather than featured.
In newer Draytek models the perceived performance of wireless as been lacking based on earlier models such as the rock solid 2860n/plus with reduced range and throughput speeds, in particular poor VoIP performance for my industry.
This could be down to the passage of time and how WiFI has become even more ubiquitous, in demand and ultimately a more congested radio band. Regardless an alternative solution needs to be explored.
Previous dabbling with deployment of Unifi access points have yielded trouble fee results, so this would be a quick win. Trouble is, the default AC-Pro and AC-LR are in serious supply shortages at present. Wifi 6 variants have better stock availability but also have a higher purchase cost.
The only Unifi AC product that is plentiful is the NanoHD, so in desperation lets see if it is a justifiable upgrade to the Draytek offering…
I’ve been a NordVPN customer for about 6 months now, mainly due to its ongoing support of L2TP connections. However recent changes to its service put my use of this service with my Draytek 2862 in jeopardy. Luckily there is a fix, and it’s a story of updates…
Here’s a quick one, ever thought of taking some existing phone extension wiring and converting for use in ethernet networking?
Since moving in I’ve had an analogue phone extension socket in the bedroom. The cable runs outside and down the side of the house, before returning into the house close to the BT master socket. It was connected, but was immediately removed to get the best internet speed at the master.
Unexpectedly and to much excitement, my home internet is now provided via FTTP.
For background, I was previously in a FTTC environment getting average speeds due to my distance from the cab, however good enough to assumably be overlooked for the next phase of the Openreach Ultrafast rollout. Not that I’m complaining, 2020 is the year my speed gets a much-needed boost.
2020 also turns out to be the inaugural international work from home year, so had the opportunity to have a front seat view from my home office on the activity and timeline that brought FTTP home.
I’d like to share my observations and timeline as an example of what you can expect should you get the inkling of fibre coming to your street soon.
Before we get started, as my expectations rose, I found this post by Andy’s World invaluable for identifying activity and helping me confirm that FTTP was on its way.
In a series of events that I thought wouldn’t have happened for many years, FTTP (Fibre To The Premises) has just become available to my home. With available speeds of 1000/330Mbps available the temptation is to go for the maximum, but will my current infrastructure actually deliver what’s on offer?
My current router is a Draytek 2862ac, which has an advertised 400Mbps throughput at the WAN, but what can it actually achieve in the real world? This will be the basis on choosing a FTTP speed profile.
Speed testing a router can be setup with a couple of laptops…
Following the setup of a Cent OS CCTV server, I’ve been using Raspberry Pi’s as video sources. But what if there was a Raspberry Pi in perfect situ for a CCTV camera, but was already in use as a media player?
A Linux system has always had the impression that it is
versatile, so this should be an achievable task. A barrier would be how to get
this done with the operating system installed, in this case it is LibreElec, an
OS with the tagline “Just enough OS for Kodi”. Therefore, it would be more of a
challenge than a usual Debian install.
The team at LibreElec saw this type of thing coming, and included the Docker service as a Kodi addon to allow the curious tinkerer to add more than Kodi to a Pi.
If you have the LibreElec based Pi in the opportune
placement to add a camera, here is how to add Mjpeg streaming capabilities…
If you’d ever searched for Raspberry Pi projects that
involved a camera then the results would certainly include Motioneye OS, an
easy to use self-contained operating system that is truly (write then) plug and
Looking for a CCTV project earlier this year I too was drawn in by this, and with my small abundance of RPi spares it was the cheapest choice, using a couple of RPi 3B+ for video, and a Zero W for time-lapse image capture. All processing was self-contained on each Pi with capture data passed over via SMB to a Windows file share.
This worked, but had a couple of problems that prevented it
from being trustworthy. Firstly, it stops recording video after a few days of
uptime, by creating empty files. And secondly the time-lapse camera seemed to
reset every few minutes that created in white out image capture as the camera’s
exposure setting recalibrated, ruining a time-lapse video.
Looking wider there was also the performance issue. In
Motioneye OS’ default state of managing all features, the highest FPS seemed to
max at 15 fps even on the Pi 3B+. Forums suggest this is due to the motion eye
daemon handling all the image processing in software, putting a strain on the Pi’s
The idea and goal is to move the processing and IO
responsibilities to my server, which would be far more capable than the then
latest available RPi, and as I have chosen Cent OS to be my go-to Linux OS of
choice, this is what I’ll be using.
A gateway to make this possible is an option in Motioneye OS, Fast Network Camera. This when set relinquishes the Pi of all processing duties and serves to just stream the camera capture as best as possible via MJPEG.
Here’s how to set up Motioneye on a Cent OS server to be a central data hub for a network of RPi Motioneye OS cameras.