Skip to main content

LoRaWAN Gateway Network Configuration

CHARP uses Kerlink Wirnet iFemtoCell evolution gateways, connected to the ThingPark Enterprise platform by Actility.

When is network configuration needed?

info

Gateways are configured to use 4G by default and require no network configuration. This guide is only relevant if you want to use an Ethernet connection on a managed or locked network.

On corporate or institutional networks, Ethernet ports are often locked down by IT policies. In these cases, your IT department will need to whitelist the gateway and open the required ports.

Connection methods

The gateway supports two connection methods to the ThingPark platform:

  • IPSec -- encrypted tunnel using IKE and ESP protocols
  • TLS -- encrypted connection using stunnel
tip

We recommend asking your IT department to support both IPSec and TLS connections for maximum flexibility and failover capability.

Information for your IT department

Provide your IT department with the following:

  • Gateway MAC address -- found on the label on the underside of the gateway

MAC address label

Required network flows

LRR flows (IPSec)

#From SystemFrom AppTypeProtocolDest PortTo SystemTo AppDescription
i6LRRIKEIPSecUDP500, 4500LRCIKEIKE negotiation for IPSec tunnel
i7LRRESPIPSecESP--LRCESPEncapsulated Security Payload
i7aLRRstunnelTLSTCP3001--3003LRCstunnelTLS tunnel (fallback)
i8aLRRICMPNetworkICMP--LRCICMPConnectivity check
i10LRRDNS clientNetworkUDP53DNSDNS serverDNS resolution
i11LRRDHCP clientNetworkUDP67, 68DHCPDHCP serverIP address assignment
i11bLRRSFTP clientFile transferTCP22SFTPSFTP serverFirmware updates
i9LRRSSH clientManagementTCP22SMSSSH serverRemote management
i17LRRNTP clientNetworkUDP123NTPNTP serverTime synchronization

LRR flows (TLS)

#From SystemFrom AppTypeProtocolDest PortTo SystemTo AppDescription
i7aLRRstunnelTLSTCP3001--3003LRCstunnelTLS tunnel for LRR data
i8aLRRICMPNetworkICMP--LRCICMPConnectivity check
i10LRRDNS clientNetworkUDP53DNSDNS serverDNS resolution
i11LRRDHCP clientNetworkUDP67, 68DHCPDHCP serverIP address assignment
i11bLRRSFTP clientFile transferTCP22SFTPSFTP serverFirmware updates
i9LRRSSH clientManagementTCP22SMSSSH serverRemote management
i17LRRNTP clientNetworkUDP123NTPNTP serverTime synchronization
caution

If using TLS only, ensure that TCP ports 3001--3003 are open for outbound traffic. If using IPSec, UDP ports 500 and 4500 must also be open, along with the ESP protocol (IP protocol 50).