Axon Fleet Dashboard Policy

The following guide is for Axon Fleet Dashboard for Axon Fleet 3

This is an example policy for use with Axon Fleet Dashboard. Please keep in mind that Axon has multiple products and each may require different policies.

Only two rules are needed for the Axon Fleet Dashboard Policy. The Fleet Dashboard application and Fleet 3 DVR or “Hub” discover each other over the local subnet using mDNS (UDP 5353) resolution of the name axoncar.local. Port 5353 must be routed outside the VPN tunnel to enable discovery. In order to route port 5353 outside the tunnel we use this rule.

If you are using an older version of the Mobility Server software, instead of Route network traffic outside the VPN Tunnel for address/ports, you will select Passthrough traffic for address/ports.

Communication between the Fleet Dashboard application and Hub is over the local network. This requires local networking to be enabled. Here is an example of a rule enabling local networking.

When finished it should look like this:

Don't forget to subscribe your desired users to this ruleset or add these rules to the existing ruleset as needed based on your requirements.