[doc] backup-redmine/2024-02-03,main: doc: open-mesh/OpenHarbors (1bc95103) - commits - lists.open-mesh.org

3 Feb 2024

Repository : ssh://git@diktynna/doc
On branches: backup-redmine/2024-02-03,main
...

commit 1bc9510388e17e7b1ec42d1ef5bd225628969fad
Author: Linus Lüssing linus.luessing@c0d3.blue
Date:   Thu Feb 1 08:19:08 2024 +0000
doc: open-mesh/OpenHarbors
...

1bc9510388e17e7b1ec42d1ef5bd225628969fad
 open-mesh/OpenHarbors.textile | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile
index 298e5ac1..0897468d 100644
--- a/open-mesh/OpenHarbors.textile
+++ b/open-mesh/OpenHarbors.textile
@@ -215,21 +215,21 @@ h3. Optional/additional/future Milestones/Ideas
 * Passpoint / Hotspot 2.0 compatibility
 * additional Layer 2 encapsulation method, which skips the IP/UDP/L2TP headers and
   uses a smaller, custom ethernet frame header
-  * allows login via: <username>@<mac-address-destination>
+** allows login via: <username>@<mac-address-destination>
     -> useful to tunnel from one mesh node to another,
        within this layer 2 domain, without layer 3 routing involved
 * allow using node names for login:
-  * Gluon nodes only have an IPv6 address to be accesed.
+** Gluon nodes only have an IPv6 address to be accesed.
     And (typically) no public DNS entry for this IPv6 address.
     Having a user to enter <login-name>@<mesh-node's-IPv6-address>
     won't be usable in practice for the gluon-openharbor-server
     package. Instead the hostname, which a Gluon mesh node owner
     can set in the Gluon config-mode and is then visible on
     a central map server, should be usable for a client
-  * option A) integrate mDNS? -> nicely decentral, but likely has too high protocol overhead
-  * option B) a small nsswitch module on the openharbor AP side
+** option A) integrate mDNS? -> nicely decentral, but likely has too high protocol overhead
+** option B) a small nsswitch module on the openharbor AP side
     which resolves a given @<node>.local (or similar TLD)
     via the nodes.json fetched from the map server
-  * option C) a cronjob which fetches node names from
+** option C) a cronjob which fetches node names from
     the map server and populates /etc/hosts on the AP
 * MTU signaling compliant with "RFC:4459":https://www.rfc-editor.org/rfc/rfc4459
\ No newline at end of file

    