DeterministicESPAsyncWebServer v6.28.0
Zero-allocation, bounded-execution async HTTP server for ESP32
Loading...
Searching...
No Matches
link_manager.h File Reference

Multi-interface egress selection + graceful escalation/failover (DETWS_ENABLE_LINK_MANAGER). More...

#include "ServerConfig.h"
#include <stddef.h>
#include <stdint.h>

Go to the source code of this file.

Detailed Description

Multi-interface egress selection + graceful escalation/failover (DETWS_ENABLE_LINK_MANAGER).

Once a device has more than one network interface (a wired Ethernet PHY brought up alongside WiFi STA, plus maybe a softAP), something has to decide which one carries traffic and when to switch: escalate to the wired link when it comes up (usually faster / more reliable), and fail over to WiFi when it drops. The stack owns the routes and det_net_egress() reports the live one; this is the policy that drives it - a small table of interfaces (each a kind + priority + up/down) with a deterministic "best link that is up" selection, plus change detection so the app only reconfigures on an actual transition.

Pure, no heap, no stdlib, host-testable. The real PHY bring-up (esp_eth) and the netif reconfigure are the app's; this just says which interface should be active.

Definition in file link_manager.h.