An increasingly common setup for law enforcement is a digital camera networked to a laptop: video recordings of police activity are stored on a laptop in the police car and can be downloaded wirelessly to a server, where it can be retrieved for review or used as evidence.
The Arbitrator camera from Panasonic communicates with a laptop over a small local area network. The communication between the camera and Arbitrator software on the laptop can happen outside of the Mobility VPN tunnel, but the traffic between the laptop and anywhere else needs to be protected by the VPN. This section describes a client policy rule set that handles both types of traffic.
Mobility forces all IP-based traffic to travel through its VPN tunnel to the Mobility server. To allow software residing on the client device to communicate locally to the camera, the traffic must be passed through (such that it does not use the Mobility VPN tunnel).
The Arbitrator software uses NetBIOS to communicate with the camera (1), and Wi-Fi or WWAN to connect back to the Mobility server (2):
Example - Arbitrator Rule - Local Networking
If the laptop connects to the Arbitrator camera using an Ethernet cable, as in the diagram above, add the following rule. The example policy uses 192.168.10.0/24 because it is a default subnet for the Arbitrator camera—your deployment may use a different pre-defined scope:
The action here (set local networking on) allows local Ethernet traffic to pass through between the camera and the Mobility client (so that it does not use the Mobility VPN tunnel); this includes the NetBIOS traffic used by the Arbitrator software. Contact NetMotion Technical Support if you need help deploying Mobility with the Arbitrator equipment; sometimes advanced setting changes are necessary.