From eed113c527ec34292e43f3a00e676a548fc5bfc7 Mon Sep 17 00:00:00 2001 From: Felix Faerber Date: Thu, 28 May 2026 15:01:27 +0300 Subject: [PATCH] bee: pin homelab_bee as static peer MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PSS chunks targeting prod's ff89* neighborhood are being routed by homelab pushsync to random peers in the ff prefix (e.g. ff7adaed) rather than prod_bee at ff896a93, because Bee 2.8's routing table evicts prod_bee from homelab's bin-1 when other ff peers appear. Same problem in reverse — prod has no protection on its homelab connection. --static-nodes keeps the libp2p connection alive across kademlia churn. Co-Authored-By: Claude Opus 4.7 --- hostinger/prod-stack.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/hostinger/prod-stack.yaml b/hostinger/prod-stack.yaml index 6f36fbc..8bf7d8b 100644 --- a/hostinger/prod-stack.yaml +++ b/hostinger/prod-stack.yaml @@ -228,6 +228,12 @@ services: BEE_NETWORK_ID: "1" BEE_WELCOME_MESSAGE: "t4t-gateway" BEE_DATA_DIR: /home/bee/.bee + # Pin homelab_bee as a static peer so the libp2p connection survives + # routing-table churn. Without this, PSS chunks the homelab pushes + # toward us are landing at random ff-prefix peers (e.g. ff7adaed) + # instead of prod_bee at ff896a93, so the gateway never receives + # provider ack/deliver envelopes. + BEE_STATIC_NODES: "/dns4/bee.ffaerber.duckdns.org/tcp/1634/p2p/QmZTZyeQhFBMtta9XhtHUoLE3EtDKrzv76uoQX9h9SowQC" volumes: - bee-data:/home/bee/.bee ports: