Interface Modes
A Reticulum instance has one or more interfaces, which are physical or logical connections to a network. While there are reasons to use modes on a single interface, such as path seeking, they are mostly used to determine network topography. Properly configured interfaces can tailor network usage for slower links, mobile stations, or fixed infrastructure. The propagation rules are posted below for reference, and the Primer contains multiple example implementations.
| Mode: | Full |
|---|---|
| Path Expiration | 7 Days |
| Seek Path | No |
| Notes | Default interface mode. Lack of path seeking means it can only answer network queries for announcements its seen directly. |
| Mode: | Gateway |
|---|---|
| Path Expiration | 7 Days |
| Seek Path | Yes |
| Notes | Alias "gw". Full interface with additional path-seeking logic. This allows networks to reduce announce load while still having full direct connectivity to destinations. |
| Mode: | Access Point |
|---|---|
| Path Expiration | 24 Hours |
| Seek Path | Yes |
| Notes | Alias "ap". Remains silent until requested; ideal for radio connections. Path seeking allows it to query the network on behalf of its clients. Any announces into an AP will propagate to all other interfaces except other APs. |
| Mode: | Roaming |
|---|---|
| Path Expiration | 6 Hours |
| Seek Path | Yes |
| Notes | Designed to be used on mobile interfaces. Low expiration time reduces the need to test paths that may no longer be valid due to movement. It also only passes announces to full interfaces, keeping downstream connections clean from transient paths. |
| Mode: | Boundary |
|---|---|
| Path Expiration | 7 Days |
| Seek Path | No |
| Notes | Designed as the edge of a logical network, particularly over different hardware. Some internal differences, but mostly for announce propagation. Announces from a boundary interface will not be broadcast over AP or Roaming interfaces. |
From Mark Qvist's Reticulum Manual.
