"Telemetry2U supply gateways that are plug-play-compatible with our servers in most cases

You simply need to supply power and an internet connection through either Ethernet, Wi-Fi or 4G

Telemetry2U LoRaWAN Gateway Network Setup

When you purchase a LoRaWAN gateway and licence from Telemetry2U, it will arrive pre-loaded with the latest firmware, factory tested, and ready to plug-and-play. In most cases, depending on your IT security and settings, all that is required is power and ethernet to get it up and running. In most cases, there's 'no need to change any settings on your router or firewall.

If you find your gateway is not communicating with Telemetry2U’s servers, you may need to add some rules and exceptions. You can read more about router and firewall settings here.

Telemetry2U is compatible with many LoRaWAN gateways on the market, but we supply Dragino’s range of LoRaWAN gateways through our online store. The links below will take you directly to Dragino’s product manuals and clearly explain features about the gateway:

The below information (based on a Dragino LG308 LoRaWAN gateway) is developed to provide users with an overview on key features and how the gateway operates with Telemetry2U. The menu structure and settings are similar between all Dragino’s gateways.

Once you receive your gateway, there are a couple of settings that you may want to change and configure, such as changing the password and configuring your Wi-Fi connection. To do this, you’ll need to log into your gateway with a username ‘admin’ and password ‘dragino’.

Connecting to the Gateway for the First Time

You can connect to the LG308 in three ways:

  1. On initial power up, the LG308 will generate an unsecure Wi-Fi access point called ‘Dragino-xxxxxx’. You can use any Wi-Fi enables device (laptop, PC or smartphone) to connect to this Wi-Fi network using the password ‘dragino+dragino’. The LG308 has a default IP address of 10.130.1.1, your device will be given an IP address of 10.130.1.x. Enter the LG308 IP address ( http://10.130.1.1) into the web browser to configure your settings. It is recommended to change the Wi-Fi access point password to prevent unauthorised access. Once you have configured your gateway for ethernet or Wi-Fi, it can be switched off to reduce likelihood of unauthorised access.
  2. The LG308 has a LAN port that, by default, is configured as a DHCP router that can connect directly with a laptop or PC (assuming it’s in DHCP mode). You can then access the User Interface (UI) from a web browser on http://10.130.1.1. Some gateways does not have a LAN port so this feature is unavailable.
  3. The LG308’s WAN will connect through your router when using an ethernet cable or a Wi-Fi connection (if configured). In cases where the router uses DHCP, the LG308 will be automatically assigned an IP address. That IP address can be used through port 8000 on a web browser to access the LG308’s UI. For example, http://IP-ADDRESS:8000. To determine the IP address allocated to your gateway, log into your router and check its connected devices list – the gateway will be labelled ‘Dragino-xxxxxx’. Alternatively, use the Wi-Fi access point to log into your gateway and navigate to Network>>Network Status where the IP address for the WAN, LAN and Wi-Fi is shown. The gateway must be connected to Wi-Fi and/or ethernet for the IP addresses to be displayed.
Dragino LoRaWAN Gateway Network Status

Gateway Home Page After Logging In

The home screen provides information on the status of all the connections.

  • A green tick indicates the connection is OK and in use.
  • An orange tick means the connection is OK but not in use.
  • A red cross means the connection has failed.

Hover over any of the icons to see more details about any of the connections.

Dragino LoRaWAN Gateway Home Screen

The 4G (cell) connection is generally used as a back-up connection, but can also be used as the primary internet connection if required. With a successful connection the LoRa, IoT Service and at least one Internet icon must have a green tick. Anything else indicates a failed connection and will not work. If a green tick on the Internet Icon is not visible, you may need to change/add some rules to the router and firewall.

After logging in to the gateways user interface (UI), the following steps are recommended for security.

Change Gateways User Interface (UI) Password

Dragino’s default username and password are publicly accessible in the documentation, therefore it’s recommended that the interface password is changed to prevent unauthorised access over the network. This can be achieved by navigating to System>>General.

Change LoRaWAN Gateway User Interface (UI) Password

There are no restrictions on user passwords. A password is made strong by using at least one capital letter, number and a special character. Once a password has been entered, select the ‘SetPassword’ button before hitting the ‘Save&Apply’ button.

Configure Wi-Fi connection

To configure a gateway's Wi-Fi setting so it can connect to the internet wirelessly rather than using an Ethernet cable, click on Network>>WiFi from the main menu.

To enable a gateways Wi-Fi client select ‘Enable WiFi WAN Client Settings’. The following details must be entered:

  1. Host WiFi SSID – your WiFi ID.
  2. Passphrase – your WiFi password.
  3. Encryption – usually always WPA2 but depends on your router’s settings.

It is possible to turn off the WiFi Access Point at this stage. However, it is recommended that users ensure they can connect to the gateway through a WAN connection first. Failure to do so may require a reset of the gateway to connect again.

Gateways supplied by Telemetry2U don’t require and configuration changes. In instances where gateway settings are accidently reset or changed the below information lists the most important information related to gateway settings and connecting to Telemetry2U hardware and servers.

Gateway LoRa Settings

Gateways use a Long-Range (LoRa) wireless 915MHz RF link to communicate in both directions with end-devices (e.g. temperature sensors). The radio settings for this link is found under LoRa>>LoRa from the gateway’s main menu and must match the end-devices supplied by Telemetry2U - they should not be changed. In Australia, Telemetry2U uses AU915 on sub band 2, 918.8~918.2MHz, but this will vary between countries.

Configure LoRaWAN Gateway LoRa Settings

Dragino gateways don’t have a GPS module. Coordinates can be manually entered and will be sent to Telemetry2U’s network server. This is not a requirement.

A problem or mismatch with any of these settings will be indicated by a red cross on the LoRa icon on the home screen.

Gateway LoRaWAN Settings

The gateway uses LoRaWAN to communicate with Telemetry2U’s network server and deliver the sensor data. To access the gateway LoRaWAN settings, select LoRaWAN>>LoRaWAN from the navigation bar.

Telemetry2U use a Custom / Private LoRaWAN server at the address ‘gateway.telemetry2u.com’.

The Email address and Gateway ID are unique to each gateway and should not be changed – a mismatch between these settings and Telemetry2U’s server will mean your gateway won’t connect and is indicated by a red cross on the IoT Service icon on the gateway home page.

Telemetry2U use a different Uplink and Downlink port for each frequency plan. For AU915, we use UDP port 1701 for both outgoing and incoming data.

The packet filters should be set to 0.

Router and Firewall rules Exceptions

In most circumstances, nothing needs to be done to connect your gateway to the internet, but in some workplaces with tight IT security there may be a need to add rules and exceptions to the router and/or firewall.

The gateway sends data to the Telemetry2U server over UDP port 1701 (in Australia). Most routers handle UDP by default, otherwise it might be necessary to open port UDP 1701 for traffic to get through to the server.

When the server receives a packet from the gateway, the server sends an acknowledgement back to advise that the packet was received OK. This response (PUSH_ACK) goes back to the source port on a random ephemeral port either from the gateway or from the NAT / firewall. Most firewalls will check that the IP address and destination port match up, meaning it’s an existing connection so it’s not really any different from an outgoing TCP connection from that point of view. The router/firewall doesn’t need a permanently open incoming UDP port, just the ability to receive that incoming packet after data is sent.

Outgoing UDP port 123 access is required to connect to an NTP (Network Time Protocol) server because the LoraWAN gateway requires an accurate time for operation. The following NTP servers are used and currently there is no way to configure alternatives:

  • server 0.openwrt.pool.ntp.org
  • server 1.openwrt.pool.ntp.org
  • server 2.openwrt.pool.ntp.org
  • server 3.openwrt.pool.ntp.org

However we ask that clients allow access to any host over UDP port 123 as the IP addresses bound to these DNS entries are subject to change. Also note that your router and firewalls must be configured to allow the UDP reply to be received back at the gateway. As per usual UDP conventions these replies will be sent to the ephemeral port that originated the request.

The gateway determines whether an Internet connection is available by pinging addresses such as 1.1.1.1 (CloudFlare DNS) and 8.8.8.8 (Google DNS) so the network should be configured to allow ICMP echo requests to be sent and ICP echo replies to be received.

It may be necessary to white-list the gateways MAC address and assign an IP address. The Wi-Fi MAC address is located on the sticker on the bottom of the gateway and is unique to each gateway. The Ethernet MAC address is the same as the Wi-Fi MAC address except you MUST add 2 to the last HEX character. For example, if the Wi-Fi MAC address is equal to A8:40:41:AA:BB:CC, the ethernet MAC address will be A8:40:41:AA:BB:CE.

Read more about the technical details of LoRaWAN and how it works with Telemetry2U here.

You may also want to check out the the LoRa Alliance for some more information.

If you have any question regarding the set-up and configuration or your LoRaWAN gateway connected to Telemetry2U, please get in touch with us.