ACCESS2000 Long-Range Wireless Gateway:
Network Requirements

Supported Network Configurations 

ACCESS2000 Long-Range Wireless Gateway supports deployment using either a wired PoE Ethernet connection or Wi‑Fi, depending on the installation environment. 

Ethernet (PoE) Requirements: 

• Power: IEEE 802.3af or 802.3at PoE 

• Network Interface: 10/100/1000 Mbps Ethernet 

• Backhaul: Wired Ethernet connection to the customer’s LAN 

Wi‑Fi Requirements:

• Wi‑Fi: Customer‑provided wireless network (2.4 GHz / 5 GHz, as supported by device firmware) 

• Security: WPA2/WPA3 (per device configuration options) 

• Signal Quality: Installation location must ensure stable signal strength and low interference 

General Network Requirements: 

• IP Addressing: DHCP or static IP (customer‑managed) 

• Internet Access: Required for CTC Connect communication, data upload, and firmware updates 

ACCESS2000 should be installed on a stable, business‑class network with sufficient uptime, bandwidth, and administrative controls. 

CTC recommends a hardwired Ethernet connection to the gateway whenever possible. A wired connection offers the greatest stability and the lowest risk of RF interference. In some facilities, however, network restrictions may prevent a wired connection. 

Wifi connectivity to the gateway is best utilized in places where the network has security policies in place that will impact the functionality of the gateway, such as VPN, NTP, or other network protocols required to connect to or manage the gateway. 

Firewall and Security Requirements 

The customer is responsible for allowing required outbound traffic: 

• Outbound HTTPS (TCP 443) to CTC Connect services 

• Outbound NTP (UDP 123) to connect to Global NTP servers 

• DNS resolution enabled 

Unsupported or Customer‑Managed Configurations 

The following configurations may be technically possible, but are not supported under CTC Connect Support. CTC does not provide configuration guidance, documentation, or troubleshooting for these scenarios: 

• Cellular routers, cellular modems, LTE/5G gateways, or hotspots used as network backhaul 

• Wi‑Fi networks with captive portals, user‑based authentication, splash pages, or rotating credentials 

• VPN tunnels, private APNs, or secure overlay networks 

• Customer‑managed firewall rules, deep packet inspection, proxying, or traffic shaping 

• MQTT broker hosting, configuration, or message routing infrastructure 

• Network policies that block, throttle, proxy, or intermittently disrupt required outbound traffic 

Any connectivity, latency, reliability, or data‑loss issues caused by these configurations are outside the scope of CTC Connect Support. 

Remote Management of Gateways 

• Internet connection to include the industrial network of the facility where the equipment is installed or cellular (such as Teltonika RUTM20) or satellite (such as Starlink).  

• Software VPN connection to securely connect to the local network where the gateway is installed. VPN connection will require the use of a static IP address for the cellular connection to the gateway or the use of DYNDNS (Dynamic DNS). Please note that the use of a static IP address is preferred for stability. 

PLEASE NOTE: Industrial networks are often secured by a corporate firewall which will cause challenges in being able to VPN to the gateway and/or there may be port blocking rules put in place which will limit TCP/UDP connections to the gateway or internet