Archive for the ‘Network-and-equipment’ Category
Posted by jpluimers on 2026/01/21
This should stau stays pretty up to date over time:
–jeroen
Posted in Cloud, Containers, Docker, Infrastructure, VPN, Wireguard | Leave a Comment »
Posted by jpluimers on 2026/01/15
On OpenWRT GL.iNET based devices, the WireGuard client does not restart upon reboot, even if it was started before rebooting.
Hopefully the /usr/bin/wireguard_watchdog script will help with this as others indicates it should.
My first try was no succes, but since it is supposed to run from cron it does no output. The script on GL-SFT1200 firmware version 3.215, script /usr/bin/wireguard_watchdog is different from the one in the OpenWRT repository, so it needs some investigation.
Some links for checking this out:
Read the rest of this entry »
Posted in *nix, *nix-tools, ash/dash, ash/dash development, Development, GL-AR300M, GL.iNet, GL.iNET GL-SFT1200, OpenWRT, Power User, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2026/01/14
TL;DR: the connection problem was because of a public key mismatch between the pfSense central location and GL.iNET peer.
Since the pfSense cannot export configuration in either text or QR format (see rcmcdonald91/pfSense-pkg-WireGuard: This is a port of the original WireGuard UI bits as implemented by Netgate in pfSense 2.5.0 to a package suitable for rapid iteration and more frequent updating on future releases of pfSense.), I made a copy paste mistake.
This resulted in the WireGuard client connection indicator on the GL.iNET to turn yellow instead of green. This means that the handshake is only partially completed (there is a WireGuard connection but there is no returning traffic on it).
GL.iNET VPN status explanation:
- no color: no VPN
- yellow: VPN not fully established
- green: VPN established
How I found out
Read the rest of this entry »
Posted in GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, pfSense, Power User, routers | Leave a Comment »
Posted by jpluimers on 2026/01/12
Some links and notes that might help me getting WireGuard site-to-site VPN working between GL.iNET and pfSense.
Read the rest of this entry »
Posted in GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, Power User, VPN, Wireguard | Leave a Comment »
Posted by jpluimers on 2026/01/06
Everytime when installing a pfSense router from scratch, I seem to re-learn a few of the below quirks. So it was finally time to document them (:
Quite a few of my pfSense configurations are just doing routing between various networks, should not provide DHCP leases and do not always need or have a WAN connected (i.e. they are LAN-only).
Read the rest of this entry »
Posted in Communications Development, Conference Topics, Conferences, Cyberchef, Development, DHCP, Encoding, Event, Hardware, HTTP, Internet protocol suite, MikroTik, Network-and-equipment, pfSense, Power User, routers, Software Development, SSH, TCP, TLS, UDP | Tagged: 8846 | Leave a Comment »
Posted by jpluimers on 2026/01/05
At the time of writing (during the Covid-19 Pandemic) the [Wayback/Archive] Product Comparison – GL.iNet contains the below products.
I got 3 of them (2 are variations of the same model) and their quality/price ratio is great, even with the prices that risen during the 2020-onwards global chip shortage.
Read the rest of this entry »
Posted in Ethernet, GL-AR300M, GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, Power User | Leave a Comment »
Posted by jpluimers on 2025/12/26
TL;DR: avoid Digitus AC fans, but use DC case fans with built-in/external temperature controller plus 12V or USB-step-up power supply and optionally fan grilles/meshes.
A while ago, I bought a 7U shallow 19-inch rack cabinet to house some of our network equipment for the offices and other rooms at the top floor: [Wayback/Archive] DIGITUS Professional Network Wall Housing – Soho Wall Cabinet: Amazon.de: Computer & Accessories
Since it was to be mounted in the boiler room, which is on the top floor under a flat roof, it would get warm so I wanted fans installed in it under or over the air vents in the housing (the cabinet is delivered as flat-pack with parts pictured below and requires about half an hour assembly time):
Read the rest of this entry »
Posted in Hardware, LifeHacker, Network-and-equipment, Power User | Leave a Comment »
Posted by jpluimers on 2025/12/26
Anxious to see how many routers have improved their algorithms to prevent Bufferfloat.
[Wayback/Archive] Bufferbloat, The Internet, And How To Fix It | Hackaday
The following YouTube videos in it are embedded below the blog signature:
Read the rest of this entry »
Posted in Communications Development, Development, Internet protocol suite, LifeHacker, Network-and-equipment, Power User, routers, TCP, UDP | Tagged: bufferbloat, latency, jitter, WiFi, Linux, OpenWRT | Leave a Comment »
Posted by jpluimers on 2025/12/25
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, GitHub, Hardware, Network-and-equipment, pfSense, Power User, routers, Software Development, Source Code Management, Tailscale | Tagged: 11281, 73 | Leave a Comment »
Posted by jpluimers on 2025/12/19
TL;DR: it failed
Since GL.iNET does not support site-to-site “Peer to Peer” OpenVPN (only “Remote Access” is supported) which is needed to route to/from the networks on both sides of the connection. the below did fail.
Original idea
Below was what I hoped to function.
Some links that should get me started (though my situation is a tad more difficult, see below):
Read the rest of this entry »
Posted in Ethernet, Firewall, Fritz!, Fritz!Box, GL-AR300M, GL.iNet, GL.iNET GL-SFT1200, Hardware, Infrastructure, Network-and-equipment, pfSense, routers | Leave a Comment »
The Wiert Corner - irregular stream of stuff 