https://docs.edgelq.com/learn/os/networking/ Recent content on SPEKTRA Edge Hugo en https://docs.edgelq.com/learn/os/networking/fallback/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/networking/fallback/ Connection fallback Devices are often deployed where connectivity is imperfect: a misapplied network change, a flaky uplink, or a proxy that goes down. SPEKTRA Edge OS has several fallback behaviors that keep a device reachable and recoverable. This page explains the three that matter most: network configuration fallback, uplink (interface and cellular) failover, and proxy fallback. Network configuration fallback When you push a new network configuration to a device, there is always a risk that the new configuration is wrong and takes the device offline — which would also prevent you from pushing a correction. https://docs.edgelq.com/learn/os/networking/proxy/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/networking/proxy/ Proxy configuration If your devices reach the internet through a forward proxy, configure the proxy so that both the device’s connection to the SPEKTRA Edge platform and your workloads’ traffic are routed correctly. What you can set Proxy configuration consists of the standard proxy settings: Setting Meaning http_proxy Proxy URL for plain HTTP traffic. https_proxy Proxy URL for HTTPS traffic. no_proxy Hosts and networks that should bypass the proxy (comma-separated). In addition, you can specify which network interfaces the device should use to reach the platform through the proxy, so control-plane traffic uses the intended path. https://docs.edgelq.com/learn/os/networking/connectivity-and-ports/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/networking/connectivity-and-ports/ Connectivity & ports This page lists what a device needs to reach on the network and what it accepts on its own interfaces, so you can plan firewall rules for the sites where your devices run. Outbound connectivity (required) A device reaches the SPEKTRA Edge platform over secure, outbound connections. Devices do not need any inbound connections from the platform — all communication is initiated by the device. Destination Port Purpose SPEKTRA Edge platform endpoints TCP 443 Provisioning, configuration, telemetry, log forwarding, and remote access — all over TLS. https://docs.edgelq.com/learn/os/networking/time-synchronization/ Mon, 01 Jan 0001 00:00:00 +0000 https://docs.edgelq.com/learn/os/networking/time-synchronization/ Time synchronization Accurate time is important for secure connections, certificate validation, log correlation, and device attestation. Devices keep their clocks synchronized over the network using NTP. Default behavior Out of the box, a device synchronizes against public time sources, so a device with internet access keeps accurate time without any configuration. Setting custom NTP servers If your environment requires specific time sources — for example, internal NTP servers on an isolated network — you can provide your own NTP configuration.