@decentnetwork/lan 0.1.132 → 0.1.134

package/dist/proxy/multi-exit-router.js

@@ -73,9 +73,15 @@ function hostMatches(host, suffixes) {
     host = (host || "").toLowerCase();
     return suffixes.some((s) => host === (s.startsWith(".") ? s.slice(1) : s) || host.endsWith(s));
 }
-const HEALTH_INTERVAL_MS = 1000;
-const HEALTH_TIMEOUT_MS = 1500;
-const DOWN_AFTER_FAILS = 2;
+const HEALTH_INTERVAL_MS = 1500;
+// Probe connect timeout. A single remote exit reached over agentnet can sit at
+// 300-900ms RTT and spike higher under load (CCTV opens dozens of tunnels), so a
+// tight timeout makes a perfectly usable exit "flap". Keep this generously above
+// the worst observed RTT.
+const HEALTH_TIMEOUT_MS = 4000;
+// Consecutive probe failures before marking an exit DOWN. Higher = more tolerant
+// of transient jitter on a long-haul path (don't blackout a region on one blip).
+const DOWN_AFTER_FAILS = 3;
 const CONNECT_TIMEOUT_MS = 8000;
 /**
  * Start the multi-exit router. Returns a stop() that closes the listener.
@@ -178,12 +184,21 @@ export function startMultiExitRouter(opts) {
     }
     // ---- exit selection (scoped to one region) --------------------------------
     function pickOrder(region) {
-        const healthy = exits.filter((e) => e.healthy && e.region === region);
-        if (healthy.length === 0)
+        const inRegion = exits.filter((e) => e.region === region);
+        const healthy = inRegion.filter((e) => e.healthy);
+        // Best-effort fallback: if NO exit currently passes health checks but the
+        // region HAS exits, try them anyway instead of 503-ing the user. A single
+        // high-latency exit under load makes the probe flap DOWN/UP every few
+        // seconds (observed: China exit at ~900ms RTT serving CCTV), yet the actual
+        // CONNECT tunnels keep working. The real forward() has its own timeout +
+        // retry, so trying a "down" exit costs little and avoids blacking out the
+        // whole region on a transient probe blip. Prefer healthy when we have them.
+        const pool = healthy.length > 0 ? healthy : inRegion;
+        if (pool.length === 0)
             return [];
         if (mode === "failover")
-            return healthy; // priority order (input order)
-        return [...healthy].sort((a, b) => a.active - b.active || a.served - b.served);
+            return pool; // priority order (input order)
+        return [...pool].sort((a, b) => a.active - b.active || a.served - b.served);
     }
     // Whether ANY exit is configured for a region (healthy or not). Lets us tell
     // "region has no exits at all → fall through" from "exits all down → 503".

package/docs/CONFIGURATION.md

@@ -43,6 +43,9 @@ paths:
 proxy:
   enabled: false             # `agentnet proxy enable` flips this
   port: 8888
+  egress: ""                 # ""=OS default; "physical"=bind outbound dials to
+                             # the real NIC (skip Tailscale/overlay); or an
+                             # explicit source IPv4. See docs/CHINA-EXIT.md.
 
 friends:
   autoAccept: true           # accept incoming friend-requests automatically

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@decentnetwork/lan",
-  "version": "0.1.132",
+  "version": "0.1.134",
   "description": "Private virtual LAN for self-hosted services and AI agents, built on Elastos Carrier. NAT-traversal, name service, ACL, all over a peer-to-peer mesh — no public IP required.",
   "type": "module",
   "main": "./dist/index.js",
@@ -79,7 +79,7 @@
   },
   "dependencies": {
     "@decentnetwork/dora": "^0.1.11",
-    "@decentnetwork/peer": "^0.1.69",
+    "@decentnetwork/peer": "^0.1.70",
     "ink": "^5.2.1",
     "js-yaml": "^4.1.0",
     "react": "^18.3.1",