site.rst 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532
  1. Site configuration
  2. ==================
  3. The ``site`` consists of the files ``site.conf`` and ``site.mk``.
  4. In the first community based values are defined, which both are processed
  5. during the build process and runtime.
  6. The last is directly included in the make process of Gluon.
  7. Configuration
  8. -------------
  9. The ``site.conf`` is a lua dictionary with the following defined keys.
  10. hostname_prefix
  11. A string which shall prefix the default hostname of a device.
  12. site_name
  13. The name of your community.
  14. site_code
  15. The code of your community. It is good practice to use the TLD of
  16. your community here.
  17. prefix4 \: optional
  18. The IPv4 Subnet of your community mesh network in CIDR notation, e.g.
  19. ::
  20. prefix4 = '10.111.111.0/18'
  21. Required if ``next_node.ip4`` is set.
  22. prefix6
  23. The IPv6 subnet of your community mesh network, e.g.
  24. ::
  25. prefix6 = 'fdca::ffee:babe:1::/64'
  26. timezone
  27. The timezone of your community live in, e.g.
  28. ::
  29. -- Europe/Berlin
  30. timezone = 'CET-1CEST,M3.5.0,M10.5.0/3'
  31. ntp_server
  32. List of NTP servers available in your community or used by your community, e.g.:
  33. ::
  34. ntp_servers = {'1.ntp.services.ffac','2.ntp.services.ffac'}
  35. This NTP servers must be reachable via IPv6 from the nodes. If you don't want to set an IPv6 address
  36. explicitly, but use a hostname (which is recommended), see also the :ref:`FAQ <faq-dns>`.
  37. opkg \: optional
  38. ``opkg`` package manager configuration.
  39. There are two optional fields in the ``opkg`` section:
  40. - ``lede`` overrides the default LEDE repository URL. The default URL would
  41. correspond to ``http://downloads.lede-project.org/snapshots/packages/%A``
  42. and usually doesn't need to be changed when nodes are expected to have IPv6
  43. internet connectivity.
  44. - ``extra`` specifies a table of additional repositories (with arbitrary keys)
  45. ::
  46. opkg = {
  47. lede = 'http://opkg.services.ffac/lede/snapshots/packages/%A',
  48. extra = {
  49. gluon = 'http://opkg.services.ffac/modules/gluon-%GS-%GR/%S',
  50. },
  51. }
  52. There are various patterns which can be used in the URLs:
  53. - ``%n`` is replaced by the LEDE version codename
  54. - ``%v`` is replaced by the LEDE version number (e.g. "17.01")
  55. - ``%S`` is replaced by the target board (e.g. "ar71xx/generic")
  56. - ``%A`` is replaced by the target architecture (e.g. "mips_24kc")
  57. - ``%GS`` is replaced by the Gluon site code (as specified in ``site.conf``)
  58. - ``%GV`` is replaced by the Gluon version
  59. - ``%GR`` is replaced by the Gluon release (as specified in ``site.mk``)
  60. regdom \: optional
  61. The wireless regulatory domain responsible for your area, e.g.:
  62. ::
  63. regdom = 'DE'
  64. Setting ``regdom`` is mandatory if ``wifi24`` or ``wifi5`` is defined.
  65. wifi24 \: optional
  66. WLAN configuration for 2.4 GHz devices.
  67. ``channel`` must be set to a valid wireless channel for your radio.
  68. There are currently three interface types available. You many choose to
  69. configure any subset of them:
  70. - ``ap`` creates a master interface where clients may connect
  71. - ``mesh`` creates an 802.11s mesh interface with forwarding disabled
  72. - ``ibss`` creates an ad-hoc interface
  73. Each interface may be disabled by setting ``disabled`` to ``true``.
  74. This will only affect new installations.
  75. Upgrades will not change the disabled state.
  76. Additionally it is possible to configure the ``supported_rates`` and ``basic_rate``
  77. of each radio. Both are optional, by default hostapd/driver dictate the rates.
  78. If ``supported_rates`` is set, ``basic_rate`` is required, because ``basic_rate``
  79. has to be a subset of ``supported_rates``.
  80. The example below disables 802.11b rates.
  81. ``ap`` requires a single parameter, a string, named ``ssid`` which sets the
  82. interface's ESSID.
  83. ``mesh`` requires a single parameter, a string, named ``id`` which sets the mesh id.
  84. ``ibss`` requires two parametersr: ``ssid`` (a string) and ``bssid`` (a MAC).
  85. An optional parameter ``vlan`` (integer) is supported.
  86. Both ``mesh`` and ``ibss`` accept an optional ``mcast_rate`` (kbit/s) parameter for
  87. setting the multicast bitrate. Increasing the default value of 1000 to something
  88. like 12000 is recommended.
  89. ::
  90. wifi24 = {
  91. channel = 11,
  92. supported_rates = {6000, 9000, 12000, 18000, 24000, 36000, 48000, 54000},
  93. basic_rate = {6000, 9000, 18000, 36000, 54000},
  94. ap = {
  95. ssid = 'alpha-centauri.freifunk.net',
  96. },
  97. mesh = {
  98. id = 'alpha-centauri-mesh',
  99. mcast_rate = 12000,
  100. },
  101. ibss = {
  102. ssid = 'ff:ff:ff:ee:ba:be',
  103. bssid = 'ff:ff:ff:ee:ba:be',
  104. mcast_rate = 12000,
  105. },
  106. },
  107. wifi5 \: optional
  108. Same as `wifi24` but for the 5Ghz radio.
  109. next_node \: package
  110. Configuration of the local node feature of Gluon
  111. ::
  112. next_node = {
  113. ip4 = '10.23.42.1',
  114. ip6 = 'fdca:ffee:babe:1::1',
  115. mac = 'ca:ff:ee:ba:be:00'
  116. }
  117. The IPv4 next-node address is optional.
  118. mesh \: optional
  119. Options specific to routing protocols.
  120. At the moment, only the ``batman_adv`` routing protocol has such options:
  121. The optional value ``gw_sel_class`` sets the gateway selection class. The default
  122. class 20 is based on the link quality (TQ) only, class 1 is calculated from
  123. both the TQ and the announced bandwidth.
  124. ::
  125. mesh = {
  126. batman_adv = {
  127. gw_sel_class = 1,
  128. },
  129. }
  130. mesh_vpn
  131. Remote server setup for the mesh VPN.
  132. The `enabled` option can be set to true to enable the VPN by default. `mtu`
  133. defines the MTU of the VPN interface.
  134. The `fastd` section configures settings specific to the *fastd* VPN
  135. implementation.
  136. If `configurable` is set to `false` or unset, the method list will be replaced on updates
  137. with the list from the site configuration. Setting `configurable` to `true` will allow the user to
  138. add the method ``null`` to the beginning of the method list or remove ``null`` from it,
  139. and make this change survive updates. Setting `configurable` is necessary for the
  140. package `gluon-web-mesh-vpn-fastd`, which adds a UI for this configuration.
  141. In any case, the ``null`` method should always be the first method in the list
  142. if it is supported at all. You should only set `configurable` to `true` if the
  143. configured peers support both the ``null`` method and methods with encryption.
  144. You can set syslog_level from verbose (default) to warn to reduce syslog output.
  145. The `tunneldigger` section is used to define the *tunneldigger* broker list.
  146. **Note:** It doesn't make sense to include both `fastd` and `tunneldigger`
  147. sections in the same configuration file, as only one of the packages *gluon-mesh-vpn-fastd*
  148. and *gluon-mesh-vpn-tunneldigger* should be installed with the current
  149. implementation.
  150. ::
  151. mesh_vpn = {
  152. -- enabled = true,
  153. mtu = 1280,
  154. fastd = {
  155. methods = {'salsa2012+umac'},
  156. -- configurable = true,
  157. -- syslog_level = 'warn',
  158. groups = {
  159. backbone = {
  160. -- Limit number of connected peers from this group
  161. limit = 1,
  162. peers = {
  163. peer1 = {
  164. key = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  165. -- Having multiple domains prevents SPOF in freifunk.net
  166. remotes = {
  167. 'ipv4 "vpn1.alpha-centauri.freifunk.net" port 10000',
  168. 'ipv4 "vpn1.alpha-centauri-freifunk.de" port 10000',
  169. },
  170. },
  171. peer2 = {
  172. key = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  173. -- You can also omit the ipv4 to allow both connection via ipv4 and ipv6
  174. remotes = {'"vpn2.alpha-centauri.freifunk.net" port 10000'},
  175. },
  176. peer3 = {
  177. key = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
  178. -- In addition to domains you can also add ip addresses, which provides
  179. -- resilience in case of dns outages
  180. remotes = {
  181. '"vpn3.alpha-centauri.freifunk.net" port 10000',
  182. '[2001:db8::3:1]:10000',
  183. '192.0.2.3:10000',
  184. },
  185. },
  186. },
  187. -- Optional: nested peer groups
  188. -- groups = {
  189. -- lowend_backbone = {
  190. -- limit = 1,
  191. -- peers = ...
  192. -- },
  193. -- },
  194. },
  195. -- Optional: additional peer groups, possibly with other limits
  196. -- peertopeer = {
  197. -- limit = 10,
  198. -- peers = { ... },
  199. -- },
  200. },
  201. },
  202. tunneldigger = {
  203. brokers = {'vpn1.alpha-centauri.freifunk.net'}
  204. },
  205. bandwidth_limit = {
  206. -- The bandwidth limit can be enabled by default here.
  207. enabled = false,
  208. -- Default upload limit (kbit/s).
  209. egress = 200,
  210. -- Default download limit (kbit/s).
  211. ingress = 3000,
  212. },
  213. }
  214. mesh_on_wan \: optional
  215. Enables the mesh on the WAN port (``true`` or ``false``).
  216. mesh_on_lan \: optional
  217. Enables the mesh on the LAN port (``true`` or ``false``).
  218. poe_passthrough \: optional
  219. Enable PoE passthrough by default on hardware with such a feature.
  220. autoupdater \: package
  221. Configuration for the autoupdater feature of Gluon.
  222. The mirrors are checked in random order until the manifest could be downloaded
  223. successfully or all mirrors have been tried.
  224. ::
  225. autoupdater = {
  226. branch = 'stable',
  227. branches = {
  228. stable = {
  229. name = 'stable',
  230. mirrors = {
  231. 'http://[fdca:ffee:babe:1::fec1]/firmware/stable/sysupgrade/',
  232. 'http://autoupdate.alpha-centauri.freifunk.net/firmware/stable/sysupgrade/',
  233. },
  234. -- Number of good signatures required
  235. good_signatures = 2,
  236. pubkeys = {
  237. 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', -- someguy
  238. 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX', -- someother
  239. }
  240. }
  241. }
  242. }
  243. All configured mirrors must be reachable from the nodes via IPv6. If you don't want to set an IPv6 address
  244. explicitly, but use a hostname (which is recommended), see also the :ref:`FAQ <faq-dns>`.
  245. roles \: optional
  246. Optional role definitions. Nodes will announce their role inside the mesh.
  247. This will allow in the backend to distinguish between normal, backbone and
  248. service nodes or even gateways (if they advertise that role). It is up to
  249. the community which roles to define. See the section below as an example.
  250. ``default`` takes the default role which is set initially. This value should be
  251. part of ``list``. If you want node owners to change the role via config mode add
  252. the package ``gluon-web-node-role`` to ``site.mk``.
  253. The strings to display in the web interface are configured per language in the
  254. ``i18n/en.po``, ``i18n/de.po``, etc. files of the site repository using message IDs like
  255. ``gluon-web-node-role:role:node`` and ``gluon-web-node-role:role:backbone``.
  256. ::
  257. roles = {
  258. default = 'node',
  259. list = {
  260. 'node',
  261. 'test',
  262. 'backbone',
  263. 'service',
  264. },
  265. },
  266. setup_mode \: package
  267. Allows skipping setup mode (config mode) at first boot when attribute
  268. ``skip`` is set to ``true``. This is optional and may be left out.
  269. ::
  270. setup_mode = {
  271. skip = true,
  272. },
  273. legacy \: package
  274. Configuration for the legacy upgrade path.
  275. This is only required in communities upgrading from Lübeck's LFF-0.3.x.
  276. ::
  277. legacy = {
  278. version_files = {'/etc/.freifunk_version_keep', '/etc/.eff_version_keep'},
  279. old_files = {'/etc/config/config_mode', '/etc/config/ffac', '/etc/config/freifunk'},
  280. config_mode_configs = {'config_mode', 'ffac', 'freifunk'},
  281. fastd_configs = {'ffac_mesh_vpn', 'mesh_vpn'},
  282. mesh_ifname = 'freifunk',
  283. tc_configs = {'ffki', 'freifunk'},
  284. wifi_names = {'wifi_freifunk', 'wifi_freifunk5', 'wifi_mesh', 'wifi_mesh5'},
  285. }
  286. Packages
  287. --------
  288. The ``site.mk`` is a Makefile which should define constants
  289. involved in the build process of Gluon.
  290. GLUON_SITE_PACKAGES
  291. Defines a list of packages which should be installed additionally
  292. to the ``gluon-core`` package.
  293. GLUON_RELEASE
  294. The current release version Gluon should use.
  295. GLUON_PRIORITY
  296. The default priority for the generated manifests (see the autoupdater documentation
  297. for more information).
  298. GLUON_REGION
  299. Region code to build into images where necessary. Valid values are the empty string,
  300. ``us`` and ``eu``.
  301. GLUON_LANGS
  302. List of languages (as two-letter-codes) to be included in the web interface. Should always contain
  303. ``en``.
  304. .. _site-config-mode-texts:
  305. Config mode texts
  306. -----------------
  307. The community-defined texts in the config mode are configured in PO files in the ``i18n`` subdirectory
  308. of the site configuration. The message IDs currently defined are:
  309. gluon-config-mode:welcome
  310. Welcome text on the top of the config wizard page.
  311. gluon-config-mode:pubkey
  312. Information about the public VPN key on the reboot page.
  313. gluon-config-mode:novpn
  314. Information shown on the reboot page, if the mesh VPN was not selected.
  315. gluon-config-mode:altitude-label
  316. Label for the ``altitude`` field
  317. gluon-config-mode:altitude-help
  318. Description for the usage of the ``altitude`` field
  319. gluon-config-mode:reboot
  320. General information shown on the reboot page.
  321. There is a POT file in the site example directory which can be used to create templates
  322. for the language files. The command ``msginit -l en -i ../../docs/site-example/i18n/gluon-site.pot``
  323. can be used from the ``i18n`` directory to create an initial PO file called ``en.po`` if the ``gettext``
  324. utilities are installed.
  325. .. note::
  326. An empty ``msgstr``, as is the default after running ``msginit``, leads to
  327. the ``msgid`` being printed as-is. It does *not* hide the whole text, as
  328. might be expected.
  329. Depending on the context, you might be able to use comments like
  330. ``<!-- empty -->`` as translations to effectively hide the text.
  331. Site modules
  332. ------------
  333. The file ``modules`` in the site repository is completely optional and can be used
  334. to supply additional package feeds from which packages are built. The git repositories
  335. specified here are retrieved in addition to the default feeds when ``make update``
  336. it called.
  337. This file's format is very similar to the toplevel ``modules`` file of the Gluon
  338. tree, with the important different that the list of feeds must be assigned to
  339. the variable ``GLUON_SITE_FEEDS``. Multiple feed names must be separated by spaces,
  340. for example::
  341. GLUON_SITE_FEEDS='foo bar'
  342. The feed names may only contain alphanumerical characters, underscores and slashes.
  343. For each of the feeds, the following variables are used to specify how to update
  344. the feed:
  345. PACKAGES_${feed}_REPO
  346. The URL of the git repository to clone (usually ``git://`` or ``http(s)://``)
  347. PACKAGES_${feed}_COMMIT
  348. The commit ID of the repository to use
  349. PACKAGES_${feed}_BRANCH
  350. Optional: The branch of the repository the given commit ID can be found in.
  351. Defaults to the default branch of the repository (usually ``master``)
  352. These variables are always all uppercase, so for an entry ``foo`` in GLUON_SITE_FEEDS,
  353. the corresponding configuration variables would be ``PACKAGES_FOO_REPO``,
  354. ``PACKAGES_FOO_COMMIT`` and ``PACKAGES_FOO_BRANCH``. Slashes in feed names are
  355. replaced by underscores to get valid shell variable identifiers.
  356. Examples
  357. --------
  358. site.mk
  359. ^^^^^^^
  360. .. literalinclude:: ../site-example/site.mk
  361. :language: makefile
  362. site.conf
  363. ^^^^^^^^^
  364. .. literalinclude:: ../site-example/site.conf
  365. :language: lua
  366. i18n/en.po
  367. ^^^^^^^^^^
  368. .. literalinclude:: ../site-example/i18n/en.po
  369. :language: po
  370. i18n/de.po
  371. ^^^^^^^^^^
  372. .. literalinclude:: ../site-example/i18n/de.po
  373. :language: po
  374. modules
  375. ^^^^^^^
  376. .. literalinclude:: ../site-example/modules
  377. :language: makefile
  378. site-repos in the wild
  379. ^^^^^^^^^^^^^^^^^^^^^^
  380. This is a non-exhaustive list of site-repos from various communities:
  381. * `site-ffa <https://github.com/tecff/site-ffa>`_ (Altdorf, Landshut & Umgebung)
  382. * `site-ffac <https://github.com/ffac/site>`_ (Regio Aachen)
  383. * `site-ffbs <https://github.com/ffbs/site-ffbs>`_ (Braunschweig)
  384. * `site-ffhb <https://github.com/FreifunkBremen/gluon-site-ffhb>`_ (Bremen)
  385. * `site-ffda <https://github.com/freifunk-darmstadt/site-ffda>`_ (Darmstadt)
  386. * `site-ffeh <https://github.com/freifunk-ehingen/site-ffeh>`_ (Ehingen)
  387. * `site-fffl <https://github.com/freifunk-flensburg/site-fffl>`_ (Flensburg)
  388. * `site-ffgoe <https://github.com/freifunk-goettingen/site-ffgoe>`_ (Göttingen)
  389. * `site-ffgt-rhw <https://github.com/ffgtso/site-ffgt-rhw>`_ (Guetersloh)
  390. * `site-ffhh <https://github.com/freifunkhamburg/site-ffhh>`_ (Hamburg)
  391. * `site-ffho <https://git.c3pb.de/freifunk-pb/site-ffho>`_ (Hochstift)
  392. * `site-ffhgw <https://github.com/lorenzo-greifswald/site-ffhgw>`_ (Greifswald)
  393. * `site-ffka <https://github.com/ffka/site-ffka>`_ (Karlsruhe)
  394. * `site-ffki <http://git.freifunk.in-kiel.de/ffki-site/>`_ (Kiel)
  395. * `site-fflz <https://github.com/freifunk-lausitz/site-fflz>`_ (Lausitz)
  396. * `site-ffl <https://github.com/freifunk-leipzig/freifunk-gluon-leipzig>`_ (Leipzig)
  397. * `site-ffhl <https://github.com/freifunk-luebeck/site-ffhl>`_ (Lübeck)
  398. * `site-fflg <https://github.com/kartenkarsten/site-fflg>`_ (Lüneburg)
  399. * `site-ffmd <https://github.com/FreifunkMD/site-ffmd>`_ (Magdeburg)
  400. * `site-ffmwu <https://github.com/freifunk-mwu/sites-ffmwu>`_ (Mainz, Wiesbaden & Umgebung)
  401. * `site-ffmyk <https://github.com/FreifunkMYK/site-ffmyk>`_ (Mayen-Koblenz)
  402. * `site-ffmo <https://github.com/ffruhr/site-ffmo>`_ (Moers)
  403. * `site-ffmg <https://github.com/ffruhr/site-ffmg>`_ (Mönchengladbach)
  404. * `site-ffm <https://github.com/freifunkMUC/site-ffm>`_ (München)
  405. * `site-ffhmue <https://github.com/Freifunk-Muenden/site-conf>`_ (Münden)
  406. * `site-ffms <https://github.com/FreiFunkMuenster/site-ffms>`_ (Münsterland)
  407. * `site-neuss <https://github.com/ffne/site-neuss>`_ (Neuss)
  408. * `site-ffniers <https://github.com/ffruhr/site-ffniers>`_ (Niersufer)
  409. * `site-ffnw <https://git.nordwest.freifunk.net/ffnw-firmware/siteconf/tree/master>`_ (Nordwest)
  410. * `site-ffrgb <https://github.com/ffrgb/site-ffrgb>`_ (Regensburg)
  411. * `site-ffrn <https://github.com/Freifunk-Rhein-Neckar/site-ffrn>`_ (Rhein-Neckar)
  412. * `site-ffruhr <https://github.com/ffruhr?utf8=✓&query=site>`_ (Ruhrgebiet, Multi-Communities)
  413. * `site-ffs <https://github.com/freifunk-stuttgart/site-ffs>`_ (Stuttgart)
  414. * `site-fftr <https://github.com/freifunktrier/site-fftr>`_ (Trier)