RCN - Documentation: https://rcn.varia.zone/ - Almanac: https://rcn.varia.zone/almanac/ - Clients: https://rcn.varia.zone/clients/ - Contact: https://rcn.varia.zone/contact/ - Events: https://rcn.varia.zone/events/ - Experiments: https://rcn.varia.zone/experiments/ - Gallery: https://rcn.varia.zone/gallery/ - Glossary: https://rcn.varia.zone/glossary/ - Links: https://rcn.varia.zone/links/ - Network: https://rcn.varia.zone/network/ # Public TCP Backbones ## `berenklauw` TCP backbone with transport mode enabled. * **Location**: Charlois * **Host**: `178.224.128.168` * **Port**: `24242` Probing is also enabled. ```bash rnprobe rnstransport.probe fccab52e2a58a13db94c0e1793b75ad0 ``` ## `frikandel` > [!WARNING] > Disabled due to lack of resources on this machine. TCP backbone with transport mode enabled. * **Location**: Delfshaven * **Host**: `45.83.235.53` * **Port**: `24242` Probing is also enabled. ```bash rnprobe rnstransport.probe 1d4c00b846309ba4b94af79247e25bd9 ``` # Private TCP Backbones Each public TCP backbone provides an [IFAC](https://docs.ratspeak.org/docs/deployment/community-mesh#ifac-or-open-mesh) protected internal interface. This network segment is for mesh local connectivity. Clients which mesh locally can still call out to the distributed network and viceversa. We have used [this workaround](https://rns.recipes/forum/build-guides/discoverable-interfaces-working-around-limitations) to ensure our public backbones are discoverable (forcing `gateway` mode) without flooding the internal network segment with announce traffic. Private TCP backbones mesh with each other. This means that local network participants do not need to connect to the network through the public backbones. Using `AutoInterface` at home or in connected social spaces should be enough to reach all corners of the citywide mesh and distributed network. Access to the private backbone depends on being involved in RCN and meeting operators in person. ## `bitterballen` > [!IMPORTANT] > IFAC passphrase is required for access. * **Location**: Charlois * **Host**: `178.224.128.168` * **Port**: `24243` ## `kroket` > [!IMPORTANT] > IFAC passphrase is required for access. * **Location**: Delfshaven * **Host**: `45.83.235.53` * **Port**: `24243` # Propagation nodes Propagation nodes are configured to only peer directly with each other and not with the wider distributed network of PNodes. We do this to avoid a flood of global traffic following [this approach](https://rns.recipes/forum/general/lxmf-propagation-node-internal-offline-inbox-with-global-accessibility). ## `berenklauw` Destination hash is `fc2407d88f64bc4dc2b137ef24fb1eca`. ```bash rnpath fc2407d88f64bc4dc2b137ef24fb1eca ``` ## `frikandel` Destination hash is `6204f3b90840475095f30c203fd8fb1b`. ```bash rnpath 6204f3b90840475095f30c203fd8fb1b ``` # Relay chat We are running a [`rrcd`](https://reticulum.network/manual/software.html#reticulum-relay-chat) instance alongside the [`berenklauw`](/network#berenklauw) backbone. The destination hash of the hub is as follows. ```bash 4663fa0e41071ac6245eee6519b40a31 ``` Here's a Ratspeak QR Code. Please read the Relay chat [docs](https://rrc.kc1awv.net) to learn more about how it works.