site.rst 21 KB

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