From caabee3251dd013f0fa4566ef98136540a3e9761 Mon Sep 17 00:00:00 2001 From: Ralph Ronnquist Date: Fri, 19 Jun 2020 21:55:11 +1000 Subject: [PATCH] minor corrections --- rrqnet.8.adoc | 30 +++++++++++++----------------- 1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/rrqnet.8.adoc b/rrqnet.8.adoc index 5afd0d8..f2159fb 100644 --- a/rrqnet.8.adoc +++ b/rrqnet.8.adoc @@ -117,14 +117,14 @@ Ethernet switch that provides connectivity among its +UDP+ channels without involving the host network other than for the tunneling. -REMOTE DECLARTIONS -~~~~~~~~~~~~~~~~~~ +REMOTE DECLARATIONS +~~~~~~~~~~~~~~~~~~~ .ipv4 address block This format declares remotes by +ipv4+ address, with optional network prefix length (0-32), optional port (1-65535) and/or optional key file -pathname. *updtap* will accept packets from sources that match. If the +pathname. *rrqnet* will accept packets from sources that match. If the network prefix length, +n+, is omitted or given as 32, and a port is given, then the remote is taken as an _uplink_. @@ -139,7 +139,7 @@ given, then the remote is taken as an _uplink_. .plain ipv6 address block This format declares remotes by ipv6 address, with optional network -prefix length (0-128) and/or optional key file pathname. *updtap* will +prefix length (0-128) and/or optional key file pathname. *rrqnet* will accept packets from sources that match. This format (without square brackets) is without port number part, and it thus only declares a prefix mask for allowed sender hosts. @@ -148,7 +148,7 @@ prefix mask for allowed sender hosts. This format declares remotes by ipv6 address, with optional network prefix length (0-128) within square brackets, then optionally a port -number and/or an optional key file pathname. *updtap* will accept +number and/or an optional key file pathname. *rrqnet* will accept packets from sources that match. If the network prefix length, +n+, is omitted, or given as 128, and a port number is given, then it declares an _uplink_. @@ -371,7 +371,7 @@ than a tap for local network traffic. This operation mode has some rare use cases, such as linking two *rrqnet* daemons, or connecting to a VDE network. For example: -.stdio network between two updtap plugs +.stdio network between two rrqnet plugs ==== ---- # dpipe rrqnet 1400 0.0.0.0/0=keyfile0 = rrqnet 1401 0.0.0.0/0=keyfile1 & @@ -409,16 +409,14 @@ communication. *rrqnet* bridges its connections, and forwards Ethernet broadcasts to all known end-points except the incoming one. The input logic takes -care of avoiding broadcast cycles. Still, the safe advice is that one -should avoid a cyclic *rrqnet* set up except for single-hop cliques of -host groups. +care of avoiding broadcast cycles. -*rrqnet* does not have any Spanning Tree Logic (STL), but only some -simple timing logic based on binding MAC addresses to remotes. That -binding is sticky for a short time: 6s for broadcast and 20s for -unicast. Any packet received during that time from the same MAC -address via another remote is dropped. Also, a downlink without -incoming traffic for 3 minutes is considered stale. +*rrqnet* does not have Spanning Tree Logic (STL), but some simple +timing logic based on binding MAC addresses to remotes. That binding +is sticky for a short time: 6s for broadcast and 20s for unicast. Any +packet received during that time from the same MAC address via another +remote is dropped. Also, a downlink without incoming traffic for 3 +minutes is considered stale. *rrqnet* sends a "heartbeat" of an empty UDP message on its uplinks every 30 seconds. This is done in order to maintain the channel with @@ -435,8 +433,6 @@ SEE ALSO -------- *rrqnet-cron.sh(8)* - Management script to uphold a *rrqnet* plug. -*udptun(8)* - Packet tunneling over UDP. - *vde_plug(1)* - Virtual Distributed Ethernet plug. AUTHOR -- 2.39.2