Echelon OpenLDV - Manual (Page 118)

110 Extending xDriver
Field Description
Next Authentication Key This field represents the next authentication key to be used by the
RNI. The next authentication key is usually the same as the
current authentication key. The authentication key must be
entered as a 32-character hexadecimal string representing a 128-
bit MD5 key. For example:
0102030405060708090A0B0C0D0E0F10
You can initiate a change to the authentication key used by the
RNI by changing this field to a value different than the current
authentication key. The authentication key configured into the
RNI will then be updated to match this field.
Setting this field to all 0s causes xDriver to use the default
authentication key as the next key for the RNI. The default
factory authentication key is not secure.
When no change to the current authentication key is desired, this
key must be the same as the current authentication key. For more
information about how the lookup extension component handles
authentication, see Authentication Key Handling on page 111.
LNS Network Name The name of the LNS network to be opened. This field is optional,
and only used if an LNS Server is the client and the session is an
uplink session, because the network name is specified manually
within the LNS application in a downlink session. For an example
of such an application, see Opening a Single Remote Network With
xDriver on page 138. The LNS network name can be a maximum
of 85 characters.
Additional Downlink
Packet Header
Additional Downlink
Packet Trailer
These fields are not required under most circumstances, and are
only applicable to downlink sessions. They can be used to specify
a series of bytes to be prepended or appended to every packet sent
during a downlink session if there is an intermediate proxy
between the OpenLDV application and the RNI. These bytes can
be used to provide routing information that the proxy might
require.
When you configure an xDriver profile that uses these properties,
you might also need to select Send Routing Packet, which causes
xDriver to send the proxy a null packet (with the header and
trailer bytes specified here) when the connection is established.
This selection provides the proxy with the information that it
requires to route the connection properly. For more information,
see xDriver Profiles on page 134.
Encryption Type The type of encryption used by the RNI. Currently, xDriver
supports RC4 encryption only. Selected packets are encrypted
using an RC4 encryption algorithm if this option is selected.