Confirm the Dock can route internet traffic from the Aircraft/Droid
Viewing this guide for
This alarm is covered by this guide. graph TD
confirm-dock-internet-routing["<small><b>Step 1</b></small><br/>Action: SSH into the Dock"]
run-ip-a-dock["<small><b>Step 2</b></small><br/>Action: Run the following command to view the..."]
look-for-zipwan-end0{"<small><b>Step 3</b></small><br/>Question: Look for zipwan@end0 in the output...."}
zipwan-down-restart-network["<small><b>Step 4</b></small><br/>Action: Run the following command to restart ..."]
run-ip-a-again["<small><b>Step 5</b></small><br/>Action: Run the same command you ran earlier ..."]
is-zipwan-up{"<small><b>Step 6</b></small><br/>Question: Is zipwan@end0 marked as UP?"}
zipwan-up-restart-blob-agent["<small><b>Step 7</b></small><br/>Action: SSH into the Aircraft. Run the follow..."]
zipwan-not-up-manual-fix["<small><b>Step 8</b></small><br/>Action: Run the following command to get zip..."]
check-restart-blob-agent-heading("<small><b>Step 9</b></small><br/>Reference: Proceed to Check/Restart Blob Agent...")
confirm-dock-internet-routing --> run-ip-a-dock
run-ip-a-dock --> look-for-zipwan-end0
look-for-zipwan-end0 -->|Yes| zipwan-down-restart-network
look-for-zipwan-end0 -->|No| check-restart-blob-agent-heading
zipwan-down-restart-network --> run-ip-a-again
run-ip-a-again --> is-zipwan-up
is-zipwan-up -->|Yes| zipwan-up-restart-blob-agent
is-zipwan-up -->|No| zipwan-not-up-manual-fix
style confirm-dock-internet-routing fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-ip-a-dock fill:#dcfce7,stroke:#22c55e,color:#14532d
style look-for-zipwan-end0 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style zipwan-down-restart-network fill:#dcfce7,stroke:#22c55e,color:#14532d
style run-ip-a-again fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-zipwan-up fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style zipwan-up-restart-blob-agent fill:#dcfce7,stroke:#22c55e,color:#14532d
style zipwan-not-up-manual-fix fill:#dcfce7,stroke:#22c55e,color:#14532d
style check-restart-blob-agent-heading fill:#f3e8ff,stroke:#a855f7,color:#581c87 Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
SSH into the Dock
2 action
Run the following command to view the state of all network interfaces:
ip a. 3 question
Look for

zipwan@end0 in the output. Is the interface marked as DOWN?
4 action
Run the following command to restart the Dock's Network Config Service:
sudo systemctl restart network_config. 5 action
Run the same command you ran earlier to view all network interfaces:
ip a. 6 question
Is
zipwan@end0 marked as UP? 7 action
SSH into the Aircraft. Run the following command to restart the Blob Agent:
sudo systemctl restart blob_agent. Logs should start offloading. If they don't, follow this guide: Dock Network Connection Issues 8 action
Run the following command to get
If it does not resolve after 1 hour, check
zipwan@end0 back up: sudo ip link set zipwan up. Check if it succeeded with running ip a again, and if so, logs should start offloading.If it does not resolve after 1 hour, check
zipwan@end0 another time. Is it down again? This indicates flakey network connection. Follow this guide: Dock Network Connection Issues 9 reference
Proceed to Check/Restart Blob Agent.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.