[00:00] In this lesson, I'll demonstrate how to create a gateway network connection between two gateways. Setting this up is easy and simply requires two ignition gateways on the same network. If I take a look at my web browser, I have this local gateway ignition A and I want to connect it to this remote gateway named ignition B. I'll start on my local gateway by navigating to the network tab and clicking on the gateway network settings page. This will open up the general settings page for the gateway network, which is where I can configure the basic rules for the system, including the security rules. For example, I can configure whether or not connections are required to use SSL. By default, this will be true, and that means that any incoming connections to this gateway that don't use SSL won't be allowed. If I scroll down, there's also the allow incoming connection setting, which determines the allowed direction of connections for this gateway.

[01:03] This also defaults to true, which means that this gateway will allow connections from other gateways. There's also the connection policy setting below it, which potentially further restricts which connections are allowed. By default this only allows approved connections, which means that any incoming connections from other gateways need to be approved from the incoming connections tab before they're allowed. If I scroll down some more, I can configure the ping settings for any potential incoming connections. Each of these settings will have a short description that goes along with it, but I'll link to our user manual page with additional information. Now that I've gone over the settings, I'll create the actual connection. We'll go to the connections page, and on this outgoing connections tab, we can click on this button to create an outgoing connection to the remote gateway. Keep in mind, with the default settings, incoming and outgoing connections are allowed, so I could have also chosen to create a connection from the remote gateway and there'd be no difference in the end result.

[02:02] Since I'm connecting to the remote gateway, I'll paste in its address here in the host. Next is the port number. For SSL connections this is going to use the default port of 8060, but any non SSL connections would use the default port of 8088. By default, the use SSL setting will be set to true, which is good. If I accidentally unchecked this, my connection wouldn't work because of the required SSL setting that is still set to the default of true on my remote gateway. I'm going to leave the rest of the settings at their default values for this connection, but I could configure things like the rate that the remote gateway is pinged at and the timeouts for web socket and HTTP connections. Since I'm not going to change anything else, I'll click create outgoing connection. I'll see the connection show up here, but it'll say faulted because I'm not done yet. If you remember, in the general settings, by default, only approved connections are allowed, so we'll need to head over to our remote gateway to approve the connection.

[03:04] Before we do that, we should also approve the remote certificate on this page since we are connecting with SSL. Then we'll head over to the remote gateway and click on the incoming connections tab. On the connections page, we'll approve the remote certificate for ignition A, and then we'll see our incoming connection come through. Since I do recognize this connection, I'll go ahead and approve this, and in just a moment we'll be able to see that it's running, meaning that we have successfully connected gateways across the Gateway Network, and if we go into our overview page, we'll see that the gateways are connected in our diagram. You are certainly not limited to connecting just two gateways either. If your ignition architecture supports even more than two gateways, you would simply follow the same process and create more outgoing connections as needed.