Campbell Scientific NL200/NL201 Network Link Interface - Manual (Page 33)

NL200/201 Network Link Interface
7.6.2 DevConfig TCP Encrypted Communication to the NL200/201
In order to use DevConfig TCP Encrypted Communication to the NL200/201,
you will need to load your TLS Private Key and TLS Certificate into the
NL200/201. This is done from the Settings Editor | TLS tab in DevConfig.
Once the private key and certificate are loaded successfully, the TLS Status
field should read Initialized.
To use TCP Encrypted Communication, select the Use IP Connection check
box in DevConfig. Input the NL200/201’s IP address (or press the browse
button to select it from a list of NL200/201s connected to the network) and
press Connect.
If the status of the TLS stack is Initialized, the NL200/201 will
automatically negotiate a secure TLS connection with DevConfig
as long as the Use IP Connection option is selected.
Encrypted Communication is required to change the TLS Private
Key and/or TLS Certificate via TCP. The private key and
certificate cannot be initialized via TCP, since the connection is
not encrypted. They must be initialized through a direct USB
connection to the NL200/201.
When the NL200/201 is in bridge mode, it cannot be configured
via a secure network connection, because in bridge mode the TLS
stack is not initialized. It can be configured via USB, RS-232, or
an unsecured network connection.
8. Applications
8.1 Working Around Firewalls
The NL200/201 can be used to provide a connection between LoggerNet and a
datalogger when both are behind firewalls. The NL200/201 must be on a
public IP address and will act as a common meeting place for all PakBus®
communications.
FIGURE 8-1. Working around firewalls
NOTES
LoggerNet
Firewall
Firewall
Firewall
Cellular Network
Internet / WAN
23