# LORA <> global ret gateway configuration _Build Guides · started by shades on Tue, Jul 7, 2026 9:46 PM_ Tags: Question, LoRa, RNode, Help --- ## Original post **shades** · Tue, Jul 7, 2026 9:46 PM I've been building a node on an rpi zero 2 w connected to a heltec rnode with the idea being it should be a gateway for people using lora to access the global ret. it has two interfaces: a tcp interface connected over wifi to another node on my home server, and a lora interface. it seems like a common usecase that isn't quite solved yet (at least not that I've found) the main pain points are how to treat announces? it seems like the appropriate treatment of announces depends on the interface they come through. someone roaming the world, announcing via lora, the announce should travel through the node and to the global ret. however global announces that come from the ret (tcp interface) should NOT broadcast over LORA, as it would clog the bandwidth. also the node itself should announce occasionally so that other LORA nodes can see it. I have a little script that stores recent announces and makes them visible on a nomad net page so someone can access global nodes via links. I tried the announce simulator and I think it might actually be incorrect, at least i dont remember it matching IRL behavior. anyone have any recipes for this specific kind of 'gateway' behavior? also wondering if there's appetite for a kind of plug and play gateway node program to run that comes complete with a page to see global nodes --- ## Reply 1 **Zenith** · Tue, Jul 7, 2026 10:20 PM Boundary mode. In boundary mode announces are sent out to the LoRa network, but throttled and not immediate. Announces from the global network will trickle down through the 2% announce cap. Nodes that are connected via the LoRa boundary transport can also make path requests to discover destinations on the TCP network From the manual: > The purpose of the boundary mode is to specify interfaces that establish connectivity with network segments that are significantly different than the one this node exists on. As an example, if a Reticulum instance is part of a LoRa-based network, but also has a high-speed connection to a public Transport Node available on the Internet, the interface connecting over the Internet should be set to boundary mode. Like this: ![image.png](/storage/forum/D5pE6DJqrEpjoMP8lEbAlgZXEqnd3oYl6SYBS80W.png) --- ## Reply 2 **shades** · Thu, Jul 9, 2026 4:32 PM is the 2% cap built into 'boundary-mode' or is that a separate configuration setting? --- ## Reply 3 **Anonymous** · Thu, Jul 9, 2026 5:10 PM **shades** wrote: > is the 2% cap built into 'boundary-mode' or is that a separate configuration setting? It's a seperate setting called `announce-cap` https://reticulum.network/manual/interfaces.html#common-interface-options ---