-
FAQs
-
Network Resilience Platform
- Adding Tailscale plugin to NR
- Capturing network traffic with Wireshark on a Gearlinx device
- Default Passwords on Gearlinx Products
- Deploy 3rd party applications
- Deploying S3-compatible object storage to a Gearlinx device
- Diagram: Cloud based Total OOB Management
- Hosting a Ubuntu virtual machine on a Gearlinx device
- How to factory reset an NR series appliance
- How to generate a support report
- Monitoring your network with Cisco ThousandEyes on a Gearlinx device
- NR Included Accessories
- NR serial console port pinout
- NR4400 - Initial network setup "out of box experience"
- NR4400 Secure Boot
- What are the business benefits of using OCI containers?
-
- Articles coming soon
-
Other
-
Duckfone
- Cellular Bands - Duckfone 4
- Default Passwords on Gearlinx Products
- Diagram: Typical Deployment of Duckfone LTE
- Distance Limit for POE with Duckfone
- Duckfone 4 Info LED Description
- Duckfone 4 Introduction
- Duckfone Accessories
- Duckfone Performance Capability
- How to do a factory reset on a Duckfone
- How to generate a support report
- What POE Injector do we recommend with the Duckfone?
-
Zero
-
Gearlinux Firmware
-
Hardware
-
Diagrams
-
Advanced/Expert
-
Containers, Apps and VMs
-
Videos
In a device configuration (or shared configuration) under the “Gearlinx ZERO” menu there is a “Synchronization” schedule setting for how often a device (or group of devices) syncs with ZERO. The default is 60 minutes.
Separately in the cloud portal ZERO under an “Organization Settings” there is a device activity timeout. This is the time after a device last synchronizes before ZERO considers the device inactive. The default is 60 minutes. However, ZERO actively checks the ongoing VPN handshake (which is renewed every 2 minutes) between the device and ZERO and in the event of a loss of connectivity ZERO will report inactivity within 3 minutes of a missed VPN handshake.
This means in a catastrophic loss of connectivity on the device side (power, some network outage event) that ZERO will report an inactive device in a reliably consistent manner within the thresholds above.
