Router and VPN configuration - Fleet 3

These topics describe requirements, recommendations, and configuration information for the network, router, Wi-Fi, mobile data computer/terminal (MDC/T, hereafter referred to as just MDC) and mobile computing devices (Android and iOS) for Axon Fleet 3 common deployments.

For installation of the Fleet Dashboard application, see the first topic in the Dashboard operation section for your operating system on the Fleet 3 product page.

Router configuration

The Axon Fleet 3 Hub and MDC require ethernet connections to the in-vehicle router to communicate with the Axon Service (such as Axon Evidence) through cellular (3G/LTE/5G) and/or Wi-Fi connections. Axon does not provide cellular service or a SIM card. Customers using an APN or VPN may require special configurations, including firewall exemptions, to enable communication between Fleet Hub and Axon Service.

Axon Fleet 3 uses the Local Area Network (LAN) of the in-vehicle router to communicate with the MDC and the router’s Wide Area network (WAN) to communicate with Axon Service.

Cradlepoint configuration

For a Cradlepoint router, follow the configuration requirements in Cradlepoint router configuration.

Requirements

  • Hub must be connected directly to router’s LAN ethernet port
  • For best experience, MDC should also be connected to router’s LAN ethernet port; if you prefer to connect your MDC to your router over Wi-Fi, contact your Axon representative
  • MDC and hub must be on the same subnet
  • Change the router local domain to “local”

Recommendations

  • Ignition sensing capability with power off delay configured to match Axon Fleet 3’s Power Off Delay setting

VPN configuration

Depending on your agency configurations, a VPN may force all IP-based traffic to travel through its tunnel to a remote network. To allow software residing on the MDC to communicate locally to the hub, the traffic must be exempt from the tunnel.

A VPN administrator must be available during Axon Fleet installation.

Local traffic

Use a split tunnel to ensure local network traffic and traffic destined for port 5353 (mDNS) do not flow through the VPN. Refer to your VPN provider documentation for instructions on configuring this exemption.

For example, if the local in-car network is 192.168.0.0/24, implement a rule to exempt traffic destined for this network and port 5353. For details, see https://netmotionsoftware.zendesk.com/hc/en-us/articles/4402637148051-Axon-Fleet-Dashboard-Policy.

Video upload

Video data files may be quite large. If a VPN is enabled on the in-vehicle router, add an exemption for the hub domain name axoncar.local or static IP to prevent offload traffic from being steered through a remote network.

 

Next topic: MDC configuration

 

Last modified - 28 April 2026