Campbell NL200, Руководство пользователя

Страница: 31 / 64

User Manual
21
also needs to be set to communicate on this port number. When TLS
communications are received on this port number, the NL200/201 will
decrypt the data and attempt to open a TCP connection to the datalogger and
forward the unencrypted data. In HTTPS communications, web browsers use
port 443. The NL200/201 will always listen on port 443 regardless of the
value of this setting. Therefore, if HTTPS communications are desired, it is
unnecessary to configure this setting.

Set the TLS Proxy Forward Physical Port to “CS I/O Port” for Configuration
A or to “Ethernet Port” for Configuration B.

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
NL200/201 IP address. For example, if the NL200/201 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 NL200/201 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
NL200/201 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
NL200/NL201’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 NL200/201 IP address. For example, if the NL200/201
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 NL200/201.
The datalogger must be listening on the same TCP port that the NL200/201 is
configured to forward TCP traffic on (NL200/201 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.
7.4.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