The setting… I recently started adopting WireGuard VPN into more and more of my server infrastructure. Consequently, I was wondering if the Linux-based JetKVM could also be integrated into these networks - especially useful since I do not want to use their cloud solution, but still want to deploy these onto remote locations as needed. So, getting WireGuard to run there was both harder and easier than expected - here is a write-up on how to do it.
What was going on? Recently, I had once again the unique opportunity to flash a “Fritz!Box 6490 KDG Edition” with the guarantee of no consequences in case I completely brick it. This time, because I needed the DECT functionality still working after this operation, I chose to stay on the proprietary firmware by AVM. 🤷♂️ So, here is my battle plan: Get the stock firmware for the device from its vendors download-server with its recovery-tool in case it goes really wrong.
What was going on? Recently, I had the unique opportunity to open-source flash a “Fritz!Box 7360 EWE Edition” with the guarantee of no consequences in case I completely brick it! So my first choice fell on OpenWrt, as it is a well-known and well-documented open-source firmware for routers and modems. Especially, this would fix issues with increasingly decreasing wireless performance with the original firmware after multiple weeks of uptime (thanks AVM).
Leadup Everything started as I bought the “LED Panel, Colour Temperature Fully Adjustable […]” by “B.K.Licht” off Amazon. It worked great with the also shipped remote control and it was only a little bit inconvenient to never have the remote when needed. It is a 15W LED panel with RGB/WW/CW and therefore 5 channels. I chose it because the pictures in the reviews indicated a modular power supply and also showed some minor information about the wattage and ratings.
Copyright © 2025, Simon Beginn; all rights reserved.
Page version info
Template by Bootstrapious. Ported to Hugo by DevCows.
