Download Ubiquity User Guide
Transcript
Ubiquity User Guide 3.4.5 How does Ubiquity handle the IP conflicts? The use of the VPN connections suggest to consider the possible conflict between the sub networks that you are going to connect. Ubiquity implements the necessary countermeasures to automatically solve any type of conflict. There are two possible cases. 3.4.5.1 The Control Center WAN sub network is the same as the Ubiquity Runtime LAN sub network The case is automatically solved by using the interface metric property. Ubiquity Control Center sets the metric of the “Ubiquity VPN” virtual adapter to “1” (highest) getting by this way priority over the WAN. In this case, with connected VPN, all the remote IPs are reachable; all the local IP in conflict with remote IPs are masked and they become not reachable. The solution works even in the special case in which the remote IP goes in conflict exactly with the local IP used by the gateway. The proper use of some routing rules makes possible that Control Center stay connected to its gateway and at the same time communicates with the remote IP. 3.4.5.2 The Ubiquity Runtime LAN and WAN sub network are the same The case is automatically solved by using the interface metric property. Ubiquity Runtime is able to dynamically set the highest priority for the routing rules corresponding to the ALN sub network in compare to the LAN ones. As final result we have that the WAN IPs in conflict with the LAN ones, are automatically made unreachable. 3.4.5.3 PLC IP address and LAN Gateway IP address are the same If the IP address of the PLC to be reached is the same of the IP address of the gateway in the LAN subnet in which Control Center is present, the conflict is solved taking in consideration that the gateway has to receive messages that are addressed to “external” subnets, while the message to send to the PLC require that the “destination” is an IP address in the subnet. At operative system level, a message addressed to the IP address of the gateway will be readdressed to the Ubiquity VPN interface. 3.5 Runtime command line options The “Runtime.exe” program can be launched using some command line option. For example, you can assign commands to these actions from an HMI application, to make the presence of Runtime fully transparent. -connect -disconnect -noui Connects "Runtime" to the Ubiquity servers, making it visible to Control Center. You use this option when Runtime is already running but disconnected, because, as default, runtime connects automatically, unless the option -disconnect is not specified. If Runtime is already running and connected to the servers, this command disconnects it from the servers, making it unavailable to the Control Center. Active remote sessions with Control Centers are dropped while Runtime continues to run. If Runtime is not running, it will start it but it will not connect it to the remote assistance service. Used only during the first execution of Runtime. It does not create the icon Page 87 / 156