Testing outbound network access

Owned by Chris Long, created
Last updated: 25 Sept, 2021
2 min read

This guide describes how to test whether a site network allows outbound access to the Flow servers which is required by the Flow Gateway device.

To perform this test you will need:

1. Connect the computer to the network

To most accurately test the outbound access in a way that mirrors the Flow Gateway, the computer should be connected to the network in the same way as the Flow Gateway will be.
For example if the Flow Gateway will be connected via a Wi-Fi to Ethernet adapter, first setup the adapter (Wi-Fi to Ethernet adapter installation - TP-Link TL-WA850RE), then connect the computer’s wired (Ethernet) network port to the Ethernet port on Wi-Fi to Ethernet adapter

When connecting the computer via the wired (Ethernet) port it is important to also turn off Wi-Fi on the computer before performing the test

Nb. If the computer doesn't have a wired network connection, and you don't have a USB Ethernet adapter, then the next closest alternative is to connect the computer to the Wi-Fi to Ethernet adapter's wireless network, or directly to the sites wireless network.

2. Open a command prompt on the computer

To run telnet on the computer open a command prompt:

  • For Windows 10 this is shown under "Verifying The Install" here https://social.technet.microsoft.com/wiki/contents/articles/38433.windows-10-enabling-telnet-client.aspx#Verifying_The_Install

  • For OS X his is shown under Method 2 "Unsecure Connection" here https://www.wikihow.com/Use-Telnet-on-Mac-OS-X#Unsecure-Connection

3. Run telnet

At the command prompt run:

telnet a14v6cnrny0bel-ats.iot.ap-southeast-2.amazonaws.com 443

4. Verify the results

This command should immediately connect, which demonstrates that the outbound networks access is ok - eg.

telnet a14v6cnrny0bel-ats.iot.ap-southeast-2.amazonaws.com 443 Trying 54.253.111.122... Connected to a14v6cnrny0bel-ats.iot.ap-southeast-2.amazonaws.com. Escape character is '^]'.

If running this command hangs (displays nothing for a long time), displays a timeout or other error message then there is an issue with the outbound network connection.

 

Nb. To exit telnet you can just close the command prompt window, or you can press CTRL+], then type 'quit’ and press enter, then type 'exit’ and press enter) - eg.

telnet a14v6cnrny0bel-ats.iot.ap-southeast-2.amazonaws.com 443 Trying 13.236.18.218... Connected to a14v6cnrny0bel-ats.iot.ap-southeast-2.amazonaws.com. Escape character is '^]'. ^] telnet> quit Connection closed. exit