It mentions DuPont wire connectors which is colloquial for a common form of jump wires: the ones that can connect to breadboards, or male or female pin headers. Basically a so called “DuPont wire” is an electric wire with a pin header (either male or female) on each end leading to 3 kinds (not counting ones having multiple connectors on each wire) as male – female is the same as male – female:
female – female
female – male
male – male
Being able to group the connector end of multiple jump wires in one enclosing connector for quick opening and closing is a great idea.
Hopefully the 3D printing files will be released somewhere.
One of the comments is also inspiration for a future 3D printing project:
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.
Other typed languages and tool sets like C# and Delphi come to mind here as well though you need libraries with 1-based data structures to solve the first point.
I feel old, because I vividly remember the PCX (1985) graphics file format: it was the defacto standard under DOS.
TIFF (1986) was slightly younger, and came from the scanner background resulting in very large files though unlike PCX (which had lossless compression), TIFF supported both lossless and lossy compression.
On Windows and OS/2, you had BMP (1985, lossless initially only black and white).
All three suffered from the same problems: different implementations causing all sorts of compatibility problems
Those were the reason for the implementation of newer file formats for graphics like JPG (1992, lossy) and PNG (1996, lossless).
Everytime when installing a pfSenserouter 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).
The Wiert Corner - irregular stream of stuff 