docs/multidomain-site-example/domains/alpha_centauri.conf

+{
+  -- multiple codes/names can be defined, the first one is the primary name
+  -- additional aliases can be defined
+  domain_names = {
+    alpha_centauri = 'Alpha Centauri',
+    rigil_kentaurus = 'Rigil Kentaurus',
+    proxima_centauri = 'Proxima Centauri',
+  },
+
+  -- 32 byte random data in hexadecimal encoding
+  -- This data must be unique among all sites and domains!
+  -- Can be generated using: echo $(hexdump -v -n 32 -e '1/1 "%02x"' </dev/urandom)
+  domain_seed = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
+
+  -- unique network prefixes per domain
+  prefix4 = '10.xxx.0.0/20',
+  prefix6 = 'fdxx:xxxx:xxxx:xxxx::/64',
+
+  next_node = {
+    ip4 = '10.xxx.yyy.zzz',
+    ip6 = 'fdxx:xxxx:xxxx:xxxx::xxxx',
+  },
+
+  wifi24 = {
+    channel = 1,
+    ap = {
+      ssid = "alpha-centauri.example.org",
+    },
+    mesh = {
+      id = 'ueH3uXjdp', -- usually you don't want users to connect to this mesh-SSID, so use a cryptic id that no one will accidentally mistake for the client WiFi
+    },
+  },
+
+  wifi5 = {
+    channel = 44,
+    ap = {
+      ssid = "alpha-centauri.example.org",
+    },
+    mesh = {
+      id = 'ueH3uXjdp',
+    },
+  },
+
+  mesh = {
+    batman_adv = {
+      routing_algo = 'BATMAN_IV',
+    },
+  },
+
+  mesh_vpn = {
+    fastd = {
+      groups = {
+        backbone = {
+          peers = {
+            peer1 = {
+              key = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
+              remotes = {'"peer1.example.org" port xxxxx'},
+            },
+            peer2 = {
+              key = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
+              remotes = {'"peer2.example.org" port xxxxx'},
+            },
+          },
+        },
+      },
+    },
+  },
+}

docs/multidomain-site-example/i18n

+../site-example/i18n/
\ No newline at end of file

docs/multidomain-site-example/image-customization.lua

+features {
+	'autoupdater',
+	'ebtables-filter-multicast',
+	'ebtables-filter-ra-dhcp',
+	'ebtables-limit-arp',
+	'mesh-batman-adv-15',
+	'mesh-vpn-fastd',
+	'respondd',
+	'status-page',
+	'web-advanced',
+	'web-wizard',
+}
+
+packages {
+	'iwinfo',
+}
+
+if not device_class('tiny') then
+	features {'wireless-encryption-wpa3'}
+end

docs/multidomain-site-example/modules

+../site-example/modules
\ No newline at end of file

docs/package/gluon-config-mode-domain-select.rst

@@ -5,7 +5,7 @@ the node will be placed in. If the selection has changed the upgrade scripts in
 ``/lib/gluon/upgrade/`` are triggered to update the nodes configuration.
 
 Hiding domains could be useful for default or testing domains, which should not
-be accidentally selected by a node operater.
+be accidentally selected by a node operator.
 
 domains/\*.conf
 ---------------

docs/package/gluon-config-mode-geo-location-osm.rst

+.. _package-gluon-config-mode-geo-location-osm:
+
+gluon-config-mode-geo-location-osm
+==================================
+
+When package *gluon-config-mode-geo-location-osm* is enabled, the configuration wizard will
+try to load an OSM-based map to allow the user to specify the node location.
+Loading the map requires a working internet connection, for example via WLAN
+(while connected to the Gluon node via Ethernet).
+
+.. image:: gluon-config-mode-geo-location-osm.png