Oplon Secure Access Preview Builds

New Trusted Connections NAT Preview Build

What is this?

Trusted Connection VPN lets you transparently reach devices on a remote LAN (e.g. SCADA systems, PLCs, RDP hosts) directly from your local applications — no manual port forwarding, no proxy configuration needed. Just connect and access the remote network as if you were on-site.

What you need

• The Trusted Connection client, updated to a version that supports VPN mode.
• Valid credentials/access granted by your administrator for the target LAN.
• No changes are required on your local network or firewall — the client only needs outbound access to the Oplon platform, same as for any other Trusted Connection.

How to use it

1. Open the Trusted Connection client and log in as usual.
2. Select the LAN resource you've been granted access to (your administrator will have configured this for you).
3. Start the connection.
4. Once connected, you can reach devices on the remote LAN directly from any application on your machine — browser, RDP client, SCADA software, etc. — using their normal LAN addresses (e.g. 192.168.50.10).
5. When you're done, disconnect from the client as usual to close the session.

What to expect

• You'll be assigned a private address for your session automatically — you don't need to configure anything manually.
• Devices on the remote LAN will see traffic as coming from the Oplon gateway, not from your own IP address. If you need to identify who accessed what, ask your administrator — this is tracked and available through the platform's access logs.
• Multiple users can connect to the same LAN at the same time without conflicts.

Known limitations

• This mode does not give your machine a "real" address inside the remote LAN. If an application specifically requires broadcast or local discovery (e.g. auto-discovery of devices via LAN broadcast/multicast), it may not work in this mode.

Core

• Added (1 change)

  • New openjdk 21.0.1

  • New SNMP model to enable SNMP set the definitions: -DTCO_SNMPListenerAddress and -DTCO_SNMPListenerPort with valid values

    eg.: -DTCO_SNMPListenerAddress=0.0.0.0 -DTCO_SNMPListenerPort=161

  • License management is now dynamic. It is no longer necessary to turn off and on instances to update the license.

  Startup behavior: If the license has expired or violates limits such as CPU release memory etc, the module does not start.

  During operation: During operation for all modules except the ADC module, it is possible to update the license either by sizing (CPU memory limits etc.) or by updating the expiration. For the ADC instead, if the license expires or violates the limits the ADC module performs a shutdown. This behavior is necessary to avoid that some features are disabled such as: 2FA, Firewall, WAF etc., which could compromise the security of the system.

  It is therefore recommended to update the licenses in time before they expire.

ADC

• Fixed (1 change)
  • Proxy location evaluation. Preview: node defined endPointsGroupingParams and sslCertificatesManagement