PathSpot HandScanner operating on untrusted VLANs
The PathSpot HandScanner is designed to work securely in networks where inbound connections are blocked (such as an untrusted VLAN). Any cloud-to-device instructions (config updates, software updates, etc.) are delivered via an existing outbound TLS MQTT session from the device to AWS IoT Core - No inbound session initiation is required.
π PathSpot HandScanner on Untrusted VLANs
Secure Connectivity with Outbound-Only Communication
π‘οΈ Designed for Secure, Inbound-Blocked Networks
| β Feature | π‘ Description |
|---|---|
| π Device-Initiated Only | All connections are outbound (device to cloud). |
| π« No Inbound Required | No port forwarding, no pinholes, no external access. |
| βοΈ Cloud Updates via AWS | Config/software updates are pulled via secure outbound MQTT + HTTPS. |
π Required Network Access
| π Destination | π’ Port | π Protocol | π Purpose |
|---|---|---|---|
| Router (local) | 53 | UDP | DNS resolution |
| Router (local) | 67, 68 | UDP | DHCP assignment |
a16pvx628lslju-ats.iot.us-east-1.amazonaws.com |
443 | TCP (MQTT over TLS) | Device heartbeat, status updates |
c17vf01fhrpedp.credentials.iot.us-east-1.amazonaws.com/role-aliases/s3uploadrolealias/credentials |
443 | TCP (HTTPS) | Device authentication & AWS credentials |
*.s3.amazonaws.com |
443 | TCP (HTTPS) | Large file transfers (updates) |
clients3.google.com/generate_204 |
80 | TCP (HTTP GET) | Captive portal detection |
pathspot.app/blank |
80 | TCP (HTTP GET) | Captive portal detection |
1.us.pool.ntp.org |
123 | UDP | Time sync (SNTP) |
π Traffic Patterns
| π Event | π€ Frequency |
|---|---|
| π MQTT Heartbeat | Every 3 min, and: on scan, every 5 min, 20 min, 59 min, on connect |
| π HTTPS Auth | Hourly |
| β¬οΈ S3 Downloads | At boot, during updates, on scan |
| π Captive Portal Check | On network connection |
| β° NTP Time Sync | On app launch |
π§° VLAN Configuration Summary
| βοΈ What to Allow | β What to Block |
|---|---|
| β Outbound TCP: 443, 80 | π« No inbound TCP required |
| β Outbound UDP: 53, 67, 68, 123 | π« No static IPs needed |
| β Domain Whitelisting if outbound filtering is enforced | π« No port forwarding |
| β MAC Address Allowlisting (if MAC filtering is in place) | π« No special routing rules |
π Key Takeaways
β PathSpot HandScanner β Network Setup Made Easy
-
No need to open any ports on your network. The device only makes outbound connections, like how your phone connects to the internet.
-
It checks in with the cloud regularly to send data and receive updates.
-
Works great on restricted networks (like untrusted VLANs) that block inbound traffic.
π What Your Network Needs to Allow
-
Outbound internet access on these:
-
TCP ports: 443 (secure web), 80 (basic web)
-
UDP ports: 53 (DNS), 67/68 (DHCP), 123 (time sync)
-
-
If your network filters websites, allow access to specific PathSpot and AWS domains (we'll provide the list).
-
Static IPs aren't needed. If you use MAC filtering, just ask us for the device's MAC address. This is also on the back of the scanner
π οΈ You Don't Need To:
-
Open any firewall ports
-
Set static IPs
-
Set up port forwarding
-
Allow inbound traffic
Bottom line:
If your network allows secure outbound internet traffic, the PathSpot HandScanner will work β no special setup required.