X-Git-Url: https://git.rrq.au/?a=blobdiff_plain;f=rrqnet.8.adoc;h=e3dc8e3489be49c0e68b24e5cc0bc7bd1914e342;hb=b6cc804370eac298be59c275ade79a1fe7816dbd;hp=bc0aafb158f88accf8616b993643d59397f53956;hpb=24b195c20244d90e0fefa7b2dce999063b77e6ee;p=rrq%2Frrqnet.git diff --git a/rrqnet.8.adoc b/rrqnet.8.adoc index bc0aafb..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 @@ -439,7 +439,8 @@ Using +-t -+ for stdin/stdout packet traffic is compatible with SEE ALSO -------- -*rrqnet-cron.sh(8)* - Management script to uphold a *rrqnet* plug. +*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.