Sometimes, after an improper shutdown, docker might fail to (re)start and report a network conflict due do multiple bridge networks having the same name.
This happens because of leftover files in docker’s configuration.
By default Virtualmin locks out and replaces a disabled site with a “virtualmin here; this site has been….” page, but it serves this page with a 200 OK status code to all visitors. This can be problematic if whatever content was on that site is used elsewhere and that elsewhere checks this status code.
Interrupting the Windows update process may leave the system in a broken non-bootable state. This can manifest by the boot never finishing (getting stick at the spinning circle screen forever) or simply crashing and automatically restarting after a while.
At some point I noticed that my Task Manager’s processes list becomes empty. This usually happens after a long(er) uptime, in the order of weeks/over one month.
Digging around the internet for similar issues revealed nothing useful until I’ve hit a hidden gem of a thread that made an idea instantly click.
OpenWRT is a great open-source operating system for embedded devices with great extensibility, benefiting from thousands of additional packages with extra functionality.
These additional packages can be installed on the device’s internal storage when such storage is available. For situations where the storage space is limited, OpenWRT can also install those packages in RAM memory instead of flash storage – with the side-effect of such installations not surviving reboots.
The device seems to have some compatibility quirks concerning Linux support at least with the firmware version I received it with. An elusive update which cannot be found anywhere is claimed to resolve the issues.
For OpenWRT I eventually managed to use information from multiple sources to botch up a script that performs the necessary mode switching to get it working.
I recently got some new toys to play with, one of them being the GL.iNet GL-M300N-V2 mini (read that as ultra-small) smart router.
The “Mango” is indeed very small, and for the price packs some pretty decent hardware specs, not to mention that it’s running a (slightly modified – with good additions I’d say) OpenWrt release.
I have been using Jellyfin as my main media player more and more lately. I’ve always been a fan of VLC and its compact-ness, but I found a some pluses in Jellyfin over VLC. However, there are things that bother me with Jellyfin as well. One of them is the playback controls which simply take way too long to disappear when not used.
If you’ve tried changing the MAC address on a recent Ubuntu VM running under KVM/QEMU, you may have noticed that changing the address in the VM configuration on the host yields no result in the guest machine. Also, a change done using either Virtualmin’s configuration or the command line on the guest doesn’t survive a reboot.
LuCI (the OpenWrt web UI) has a default session duration of 1 hour, after which an idling session will be logged out and require a new login.
That can quickly become annoying if you’re one to just leave tabs open and stare at statistics.
From WireGuard’s perspective, there is no server and client – all points in a WireGuard network are called peers, and they can connect to each other without a central point and not necessarily in a star topology. However, in this particular configuration scenario and because one peer is central to the whole infrastructure I’m setting up (as it’s the only one to always have a static public IP address, open ports and it can also be used to tunnel all other peers’ traffic), I’m calling it a server – while all other peers I will consider clients.
