X-Git-Url: https://git.rrq.au/?a=blobdiff_plain;f=rrqnet.8.adoc;h=e3dc8e3489be49c0e68b24e5cc0bc7bd1914e342;hb=e8cbd15f0a2d8492b5b0eaa16fb0602483b4d91a;hp=c7e18238b4d8640973ece02c56371c39953cb6d3;hpb=06f8c61d952140b0f6a82b2993a66420c14c89e1;p=rrq%2Frrqnet.git

diff --git a/rrqnet.8.adoc b/rrqnet.8.adoc
index c7e1823..e3dc8e3 100644
--- a/rrqnet.8.adoc
+++ b/rrqnet.8.adoc
@@ -92,12 +92,12 @@ hosts via UDP messaging between the hosts.
 collection of fully connected hosts, although the more common is a
 "star' formation. See the EXAMPLES section for inspiration.
 
-*rrqnet* includes logic aiming to protect against broadcast cycles.
-Howewer it does not have the more advanced spanning tree logic that is
-offered by bridge interfaces. In general it's probably best to avoid
-cabling cycles and perhaps rather run several *rrqnet* on a host with
-their taps connected with a bridge interface. Though, multiple virtual
-cabling paths between hosts might increase connection reliability.
+*rrqnet* includes logic to protect against broadcast cycles. Whilst
+acting as a switch for all its remotes it does not have spanning tree
+logic as is offered by bridge interfaces. Generally it's probably best
+to avoid cabling cycles, but *rrqnet* also handles full mesh linking
+between multiple hosts without additional configuration. Such a setup
+is also dynamically adapting to prefer the fastest link between hosts.
 
 By default *rrqnet* opens an +ipv6+ socket on the given port. This
 mode handles both +ipv6+ and +ipv4+ remotes with +ipv4+ remotes
@@ -440,6 +440,7 @@ Using +-t -+ for stdin/stdout packet traffic is compatible with
 SEE ALSO
 --------
 *rrqnet-cron(8)* - Management script to uphold a *rrqnet* plug.
+*rrqnet-ifupdown(8)* - Management script to uphold a *rrqnet* plug.
 
 *vde_plug(1)* - Virtual Distributed Ethernet plug.