In this setup, we are trying to make the two Device Servers act as the transparent extension of Serial cable.
First, one need to understand that each Tibbo Device Server will have its own unique IP Address and is seen as independent network hardware. This means that the "port number" on the Tibbo Device Server is device specific, meaning multiple devices can all use the same port number. Just be sure that both sides are using the same protocol (TCP / UDP).
To connect two Tibbo Device Servers to each other via Ethernet, this in effect turns the two devices into a virtual serial cable and depending on your connection requirements, and there are a few ways to go about this.
(1) A single side will always initiate the connection.
In this scenario, one Device Server will be the "server" and the other the "client," and this can be defined by the "Routing Mode" setting. In a client/server structure, "client" is the side that will initiate the connection, so, what you would do is for the Client Device Server, you will define the the IP and port of the Server Device Server" as the Destination IP" and "Destination Port."
As for when the connection is made, this is defined by the "Connection Mode" setting, in most situations, either "Immediately" or "On Data or Command" are used, the other two options are rarely used and is meant for use with older systems that have these needs. "Immediately" means that when the serial port of the client Device Server is opened, the Device Server will try to make a connection to the server Device Server even if no data are coming in from the serial port. "On Data or Command" means that the connection will only be made when data or command is coming in from the serial port of the client Device Server.
(2) Either side can initiate the connection.
In this scenario, all that are defined above holds true except that for "Routing Mode," you need to select "server/client" and point the "Destination IP" and "Destination Port" to the other device on both Tibbo Device Server.