MergenHub VPN — GSM sites through one port
Connect field modems with no static IP, behind the operator's NAT, to the server. No separate VPN server, no extra program and no port-forwarding maze; the VPN runs inside the MergenHub service.
What it does
Field modems (Teltonika, MikroTik, OpenWrt and others that support WireGuard) connect to the MergenHub server through an encrypted tunnel. The PLCs, RTUs and meters behind the modem are read at the tunnel address by the Modbus, DNP3, IEC 104, BACnet… drivers.
How it is set up
Add-ons › VPN › Add site wizard: choose the site and the modem model, the LAN range is checked for conflicts, and you get model-specific setup steps and one-time links (.conf, QR). MergenHub writes the server's firewall rule itself.
Core capabilities
UDP 51820
Every site connects through one UDP port; each site has its own key pair and revoking one does not affect the others.
Ready-made setup
Teltonika RutOS menu steps, a MikroTik RouterOS 7 script, an OpenWrt script; .conf and QR code. Links are one-time and valid for 24 hours.
Modem ↔ device
Which devices each modem serves is recorded; on a "Modem only" site device addresses are switched to the tunnel address in one click (old → new list first).
_System.VPN tags
Connected sites and users, last handshake, traffic; alarms, the historian, SCADA, REST and OPC UA read the same tags. "VPN service down" and "Site VPN connection lost" alarms are built in.
Laptops and phones
Staff connect with their own profile; by default MergenHub only, and selected sites or a single PLC if an administrator allows it. The key is generated in the user's browser; a lost device is revoked with one click.
Encrypted keys, audit
Private keys are encrypted on disk and masked on screen; every action goes to the audit log. A separate "VPN management" permission for administration.
MergenHub