[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 two tabs open, one from my local gateway and the other from my remote gateway. I'll start on my local gateway by navigating to config, networking, and gateway network. 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. 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.

[01:14] 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, including any changes to these settings that have occurred for the various 8.1 versions. Now that I've gone over the general settings, I'll create the actual connection. I'll do that by scrolling up and clicking the outgoing connections tab. Then I can click create new connection to connect 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. Since I'm connecting to the remote gateway, I'll enter its host name here, but I could also provide the IP address. 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.

[02:07] 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 gonna 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 gonna change anything else, I'll click create. I'll see the connections show up here, but it'll say it's faulted because I'm not done yet. If you remember, in the general settings, by default, only approved connections are allowed, so I need to head over to my remote gateways gateway network page and go to the incoming connections tab and approve the connection. First, since I'm using SSL, I'll need to approve this certificate, and once that's approved, I'll approve the connection by clicking more and then approve. The status will then change to running, and if I switch back to my local gateway webpage, that will also say running, and now I have an active gateway network connection between my two gateways.