Under any LonTunnel, only one tunnel connection is supported at any one time—if a tunnel connection is active and another tunnel client (PC) attempts to connect, that remote user sees a popup dialog saying that the “Desired tunnel is busy.”
In the station (tunnel server), any active tunnel connection results in a “Tunnel Connection” child component, named as the
remote (client’s) hostname or IP address, with a “#1” suffix (Figure B.5).
In the example above, the remote host that is currently Lon tunneling is “JKLM.” When a tunnel connection is terminated, this Tunnel Connection component is removed.
Properties of a TunnelConnection (either LonTunnel or SerialTunnel) are all read-only, as follows:
-
Established
Date-timestamp of when this tunnel connection was first established.
-
User Name
User in the station that is currently tunneling.
-
Remote Host
Windows hostname of the remote tunneling client.
-
Protocol Version
Version of the (remote) Lon tunneling client application being used.
-
Last Read
Date-timestamp of when the last read of a station item occurred over the tunnel connection.
-
Last Write
Date-timestamp of when the last write to a station item occurred over the tunnel connection.
In addition, a TunnelConnection has an available (right-click) action:
-
Disconnect
Disconnects the active tunnel connection, removing the parent TunnelConnection component. This causes a popup “Connection closed by remote host” to be seen on the client tunnel side.
A LonTunnel component also has its own “Disconnect All” action, which effectively performs the same function.