Campbell Scientific NL240 Wireless Network Link Interface - Manual (Page 38)

NL240 Wireless Network Link Interface
• For Configuration A, leave the TLS Proxy Forward IP Address set to
0.0.0.0. For Configuration B, enter the datalogger’s IP address in the TLS
Proxy Forward IP Address setting. This address must be configured in
the datalogger. It must be a unique, static IP address on the same subnet as
the NL240 IP address. For example, if the NL240 IP address is
192.168.5.1 with subnet 255.255.255.0, a valid IP address for the
datalogger would be 192.168.5.2 provided there are no other devices on
the subnet with that address.
• Set the TLS Proxy Forward Port Number. This is the TCP port number
that the proxy server will use when it opens a TCP connection to the
datalogger to forward unencrypted data. The datalogger’s TCP server port
must be set to communicate on this port number. The default value for the
datalogger’s PakBus/TCP server is 6785, so this setting can likely be left
at the default. The datalogger listens for HTTP traffic on port 80. The
NL240 will always forward TLS traffic received on port 443(HTTPS) to
port 80(HTTP) regardless of this setting. Therefore, if HTTPS
communications are desired, it is unnecessary to configure this setting.
• It is recommended to leave the TLS Proxy Timeout set to 90 seconds
although it can be changed if desired. This will determine how fast the
NL240 proxy server and client connections will timeout if no activity is
detected.
To configure the datalogger for Configuration A, connect to the datalogger
using DevConfig and select the CS I/O IP tab. Set the CS I/O Interface IP
Address to a static IP address. Use the datalogger’s CS I/O Interface that
corresponds to the NL240’s CS I/O IP Interface Identifier setting. To
configure the datalogger for Configuration B, connect to the datalogger using
DevConfig and select the TCP/IP tab. Set the Ethernet Interface IP Address
to a static IP address.
For either configuration, the IP address must not be 0.0.0.0, and it must be
unique on the same subnet as the NL240 IP address. For example, if the
NL240 IP address is 192.168.5.1 and Subnet Mask is 255.255.255.0, the
datalogger address could be set as 192.168.5.2 provided there are no other
devices on the subnet with that address. Also set the datalogger’s Subnet Mask
to match that of the NL240.
The datalogger must be listening on the same TCP port that the NL240 is
configured to forward TCP traffic on (NL240 setting: TLS Proxy Forward Port
Number). The datalogger always listens on port 80 for HTTP, therefore, no
TCP port configuration is necessary for using HTTP.
8.2.6.2 DevConfig TCP Encrypted Communication to the NL240
In order to use DevConfig TCP Encrypted Communication to the NL240, you
will need to load your TLS Private Key and TLS Certificate into the NL240.
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 NL240’s IP address (or press the browse button
to select it from a list of NL240s connected to the network) and press Connect.
28