I had to pick up a package keying in a 6 digit code using the below PostNL UI.
It was horrible. Don’t implement your numeric input UI like this: use a telephone keypad like or calculator numpad like keypad UI.
Posted by jpluimers on 2026/01/14
I had to pick up a package keying in a 6 digit code using the below PostNL UI.
It was horrible. Don’t implement your numeric input UI like this: use a telephone keypad like or calculator numpad like keypad UI.
Posted in Development, Software Development, UI Design, User Experience (ux) | 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:
Posted in GL.iNet, GL.iNET GL-SFT1200, Hardware, Network-and-equipment, pfSense, Power User, routers | Leave a Comment »