Differences between revisions 2 and 14 (spanning 12 versions)
Revision 2 as of 2015-12-21 19:40:22
Size: 4113
Editor: Drahtseil
Comment: add german Quickstart
Revision 14 as of 2021-01-12 10:40:05
Size: 9435
Editor: fioddor
Comment: Neue Übersetzung.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from de/FreedomBox/Handbuch
#langauage de
<<Include(FreedomBox/Manual, ,from="^##TAG:TRANSLATION-HEADER-START",to="^##TAG:TRANSLATION-HEADER-END")>>
Line 4: Line 8:
<<Include(de/FreedomBox/Einführung, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/Schnelleinstieg, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(
FreedomBox/Manual/GettingHelp, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/ReleaseNotes, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Download, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Introduction, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/QuickStart,
, from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/GettingHelp, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Download, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
Line 10: Line 13:
= Apps =

<<Include(FreedomBox/Manual/Tor, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Deluge, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Transmission, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Shaarli, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/XMPP, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/DynamicDNS, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Roundcube, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/ownCloud, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/PageKite, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/SecureShell, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Mumble, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Privoxy, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Ikiwiki, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Unhosted, , to="## END_INCLUDE")>>
= Anwendungen (Apps) =
<<Include(de/FreedomBox/Manual/bepasty, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Calibre, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/Coturn, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/Deluge, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/ejabberd, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/GitWeb, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/I2P, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Ikiwiki, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Infinoted, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/JSXC, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/MatrixSynapse, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/MediaWiki, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Minetest, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/MiniDLNA, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/MLDonkey, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Mumble, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/OpenVPN, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Privoxy, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Quassel, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Radicale, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Roundcube, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Samba, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Searx, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Shadowsocks, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Sharing, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Syncthing, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/TinyTinyRSS, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Manual/Tor, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Transmission, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Apache_userdir, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/WireGuard, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
Line 28: Line 47:
<<Include(FreedomBox/Manual/Configure, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Users, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Networks, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Upgrades, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Diagnostics, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Firewall, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/DateTime, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Backups, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Bind, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Cockpit, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Configure, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/DateTime, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Diagnostics, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/DynamicDNS, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Firewall, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/LetsEncrypt, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Monkeysphere, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/NameServices, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Networks, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/PageKite, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Performance, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Power, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/SecureShell, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Security, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/ServiceDiscovery, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Storage, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Snapshots, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Upgrades, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Manual/Users, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
Line 37: Line 71:
<<Include(de/FreedomBox/Hardware, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/Cubietruck, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/BeagleBone, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/A20-OLinuXino-Lime2, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/A20-OLinuXino-MICRO, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/APU, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/VirtualBox, , to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Hardware/Debian, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/DreamPlug, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi2, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/USBWiFi, , to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Hardware, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/PioneerEdition, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/A20-OLinuXino-Lime2, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/A20-OLinuXino-MICRO, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/APU, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/Cubietruck, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/Cubieboard2, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/BeagleBone, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/pcDuino3, , to="## END_INCLUDE")>>
<<Include(de/FreedomBox/Hardware/Debian, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/VirtualBox, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/PineA64+, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/BananaPro, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/OrangePiZero, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RockPro64, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/Rock64, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi2, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi3B, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi3B+, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/RaspberryPi4B, , to="## END_INCLUDE")>>
<<Include(FreedomBox/Hardware/USBWiFi, , to="## END_INCLUDE")>>
Line 51: Line 95:

<<Include(FreedomBox/ReleaseNotes, , from="## BEGIN_INCLUDE", to="## END_INCLUDE")>>
Line 87: Line 133:

## END_INCLUDE

<<Include(de/FreedomBox/Portal)>>

----
CategoryFreedomBox

Contents

  1. Smart Router
  2. Private Cloud
  3. Diskussionsforum
  4. Matrix
  5. IRC #freedombox
  6. Email
  7. Hilfe wiedergeben
  8. Herunterladen für Debian
  9. Herunterladen für Hardware bzw. Virtuelle Maschinen
  10. Bepasty (Datei- und Ausschnittteilen)
  11. Calibre (e-Library)
  12. Coturn (VoIP-Helfer)
  13. Deluge (Verteilte Dateifreigabe über BitTorrent)
  14. Ejabberd (Chat Server)
  15. GitWeb (Simple Git Hosting)
  16. I2P (Anonymity Network)
  17. Ikiwiki (Wiki and Blog)
  18. Infinoted (Collaborative text edition with Gobby)
  19. JSXC (Web Chat Client)
  20. Matrix Synapse (Chat Server)
  21. MediaWiki (Wiki)
  22. Minetest (Block Sandbox)
  23. MiniDLNA (Simple Media Server)
  24. Mumble (Voice Chat) Server
  25. OpenVPN (Virtual Private Network)
  26. Privoxy (Web Proxy)
  27. Quassel (Text Chat Client via IRC)
  28. Radicale (Calendar and Addressbook)
  29. Roundcube (Email Client)
  30. Samba (Network File Storage)
  31. Searx (Web Search)
  32. Shadowsocks (Bypass Censorship)
  33. Sharing (File Publishing)
  34. Syncthing (File Synchronization)
  35. Tiny Tiny RSS (News Feed Reader)
  36. Tor (Anonymitätnetzwerk)
  37. Transmission (Distributed File Sharing via BitTorrent)
  38. User Websites
  39. WireGuard (Virtual Private Network)
  40. Backups
  41. BIND (Domain Name Server)
  42. Cockpit (Server Administration)
  43. Configure
  44. Date & Time
  45. Diagnostics
  46. Dynamic DNS Client
  47. Firewall
  48. Let's Encrypt (Certificates)
  49. Monkeysphere
  50. Name Services
  51. Networks
  52. PageKite (Public Visibility)
  53. Performance (System Monitoring)
  54. Power
  55. Secure Shell (SSH) Server
  56. Security
  57. Service Discovery
  58. Storage
  59. Storage Snapshots
  60. Software Updates
  61. Users and Groups
  62. Unterstützte Hardware
  63. Ziel-Hardware
  64. Pioneer Edition FreedomBox
  65. A20 OLinuXino Lime2
  66. A20 OLinuXino MICRO
  67. APU
  68. Cubietruck
  69. Cubieboard 2
  70. Beagle Bone Black
  71. pcDuino3
  72. Debian
  73. VirtualBox
  74. Pine A64+
  75. Banana Pro
  76. Orange Pi Zero
  77. RockPro64
  78. Rock64
  79. Raspberry Pi 2 Model B
  80. Raspberry Pi 3 Model B
  81. Raspberry Pi 3 Model B+
  82. Raspberry Pi 4 Model B
  83. USB Wi-Fi
  84. FreedomBox 23.18 (2023-09-25)
  85. FreedomBox 23.17 (2023-09-11)
  86. FreedomBox 23.16 (2023-08-28)
  87. FreedomBox 23.15 (2023-08-14)
  88. FreedomBox 23.14 (2023-07-31)
  89. FreedomBox 23.13 (2023-07-17)
  90. FreedomBox 23.12 (2023-06-19)
  91. FreedomBox 23.11 (2023-06-05)
  92. FreedomBox 23.10 (2023-05-22)
  93. FreedomBox 23.9 (2023-05-08)
  94. FreedomBox 23.6.2 (2023-05-01)
  95. FreedomBox 23.8 (2023-04-24)
  96. FreedomBox 23.6.1 (2023-04-10)
  97. FreedomBox 23.7 (2023-03-27)
  98. FreedomBox 23.6 (2023-03-13)
  99. FreedomBox 23.5 (2023-02-27)
  100. FreedomBox 23.4 (2023-02-13)
  101. FreedomBox 23.3 (2023-01-30)
  102. FreedomBox 23.2 (2023-01-16)
  103. FreedomBox 23.1 (2023-01-03)
  104. FreedomBox 22.27 (2022-12-19)
  105. FreedomBox 22.26 (2022-12-05)
  106. FreedomBox 22.25 (2022-11-21)
  107. FreedomBox 22.24 (2022-11-07)
  108. FreedomBox 22.23 (2022-10-24)
  109. FreedomBox 22.22.1 (2022-10-16)
  110. FreedomBox 22.22 (2022-10-10)
  111. FreedomBox 22.21.1 (2022-10-01)
  112. FreedomBox 22.21 (2022-09-26)
  113. FreedomBox 22.20 (2022-09-12)
  114. FreedomBox 22.19 (2022-08-29)
  115. FreedomBox 22.18 (2022-08-15)
  116. FreedomBox 22.17 (2022-08-01)
  117. FreedomBox 22.16 (2022-07-18)
  118. FreedomBox 22.15 (2022-07-04)
  119. FreedomBox 22.14.1 (2022-06-27)
  120. FreedomBox 22.14 (2022-06-20)
  121. FreedomBox 22.13 (2022-06-06)
  122. FreedomBox 22.12 (2022-05-23)
  123. FreedomBox 22.11 (2022-05-09)
  124. FreedomBox 22.10 (2022-04-25)
  125. FreedomBox 22.9 (2022-04-11)
  126. FreedomBox 22.8 (2022-03-28)
  127. FreedomBox 22.7 (2022-03-14)
  128. FreedomBox 22.6.1 (2022-03-06)
  129. FreedomBox 22.6 (2022-03-02)
  130. FreedomBox 22.5 (2022-02-14)
  131. FreedomBox 22.4 (2022-01-31)
  132. FreedomBox 22.3 (2022-01-17)
  133. FreedomBox 22.2 (2022-01-11)
  134. FreedomBox 22.1 (2022-01-03)
  135. FreedomBox 21.16 (2021-12-20)
  136. FreedomBox 21.15 (2021-12-06)
  137. FreedomBox 21.14.1 (2021-11-24)
  138. FreedomBox 21.14 (2021-11-22)
  139. FreedomBox 21.13 (2021-11-08)
  140. FreedomBox 21.12 (2021-10-25)
  141. FreedomBox 21.11 (2021-10-11)
  142. FreedomBox 21.10 (2021-09-27)
  143. FreedomBox 21.9 (2021-09-18)
  144. FreedomBox 21.8 (2021-08-30)
  145. FreedomBox 21.7 (2021-08-16)
  146. FreedomBox 21.6 (2021-05-31)
  147. FreedomBox 21.5 (2021-04-19)
  148. FreedomBox 21.4.2 (2021-03-28)
  149. FreedomBox 21.4.1 (2021-03-13)
  150. FreedomBox 21.4 (2021-02-28)
  151. FreedomBox 21.3 (2021-02-11)
  152. FreedomBox 21.2 (2021-02-05)
  153. FreedomBox 21.1 (2021-01-25)
  154. FreedomBox 21.0 (2021-01-11)
  155. FreedomBox 20.21 (2020-12-28)
  156. FreedomBox 20.20.1 (2020-12-19)
  157. FreedomBox 20.20 (2020-12-14)
  158. FreedomBox 20.19 (2020-11-30)
  159. FreedomBox 20.18.1 (2020-11-23)
  160. FreedomBox 20.18 (2020-11-16)
  161. FreedomBox 20.17.1 (2020-11-07)
  162. FreedomBox 20.17 (2020-11-02)
  163. FreedomBox 20.16 (2020-10-19)
  164. FreedomBox 20.15 (2020-10-05)
  165. FreedomBox 20.14.1 (2020-09-23)
  166. FreedomBox 20.14 (2020-09-15)
  167. FreedomBox 20.13 (2020-07-18)
  168. FreedomBox 20.12.1 (2020-07-05)
  169. FreedomBox 20.12 (2020-06-29)
  170. FreedomBox 20.11 (2020-06-15)
  171. FreedomBox 20.10 (2020-06-01)
  172. FreedomBox 20.9 (2020-05-18)
  173. FreedomBox 20.8 (2020-05-04)
  174. FreedomBox 20.7 (2020-04-20)
  175. FreedomBox 20.6.1 (2020-04-11)
  176. FreedomBox 20.6 (2020-04-06)
  177. FreedomBox 20.5.1 (2020-03-26)
  178. FreedomBox 20.5 (2020-03-23)
  179. FreedomBox 20.4 (2020-03-09)
  180. FreedomBox 20.3 (2020-02-24)
  181. FreedomBox 20.2 (2020-02-10)
  182. FreedomBox 20.1 (2020-01-27)
  183. FreedomBox 20.0 (2020-01-13)
  184. FreedomBox 19.24 (2019-12-30)
  185. FreedomBox 19.23 (2019-12-16)
  186. FreedomBox 19.22 (2019-12-02)
  187. FreedomBox 19.21 (2019-11-18)
  188. FreedomBox 19.20 (2019-11-04)
  189. FreedomBox 19.19 (2019-10-21)
  190. FreedomBox 19.18 (2019-10-07)
  191. FreedomBox 19.17 (2019-09-23)
  192. FreedomBox 19.16 (2019-09-09)
  193. FreedomBox 19.15 (2019-08-26)
  194. FreedomBox 19.14 (2019-08-12)
  195. FreedomBox 19.13 (2019-07-29)
  196. FreedomBox 19.12 (2019-07-22)
  197. FreedomBox 19.2.2 (2019-07-17)
  198. FreedomBox 19.2.1 (2019-07-09)
  199. FreedomBox 19.11 (2019-07-08)
  200. FreedomBox 19.10 (2019-06-24)
  201. FreedomBox 19.9 (2019-06-10)
  202. FreedomBox 19.8 (2019-05-27)
  203. FreedomBox 19.7 (2019-05-13)
  204. FreedomBox 19.6 (2019-04-29)
  205. FreedomBox 19.5 (2019-04-15)
  206. FreedomBox 19.4 (2019-04-01)
  207. FreedomBox 19.3 (2019-03-18)
  208. FreedomBox 19.2 (2019-03-02)
  209. FreedomBox 19.1 (2019-02-14)
  210. FreedomBox 19.0 (2019-02-09)
  211. Version 0.49.1 (2019-02-07)
  212. Version 0.49.0 (2019-02-05)
  213. Version 0.48.0 (2019-01-28)
  214. Version 0.47.0 (2019-01-14)
  215. Version 0.46.0 (2018-12-31)
  216. Version 0.45.0 (2018-12-17)
  217. Version 0.44.0 (2018-12-03)
  218. Version 0.43.0 (2018-11-19)
  219. Version 0.42.0 (2018-11-05)
  220. Version 0.41.0 (2018-10-22)
  221. Version 0.40.0 (2018-10-08)
  222. Version 0.39.0 (2018-09-24)
  223. Version 0.38.0 (2018-09-10)
  224. Version 0.37.0 (2018-08-27)
  225. Version 0.36.0 (2018-08-13)
  226. Version 0.35.0 (2018-07-30)
  227. Version 0.34.0 (2018-07-16)
  228. Version 0.33.1 (2018-07-04)
  229. Version 0.33.0 (2018-07-02)
  230. Version 0.32.0 (2018-06-18)
  231. Version 0.31.0 (2018-06-04)
  232. Version 0.30.0 (2018-05-21)
  233. Version 0.29.1 (2018-05-08)
  234. Version 0.29.0 (2018-05-07)
  235. Version 0.28.0 (2018-04-23)
  236. Version 0.27.0 (2018-04-09)
  237. Version 0.26.0 (2018-03-26)
  238. Version 0.25.0 (2018-03-12)
  239. Plinth v0.24.0 (2018-02-26)
  240. Plinth v0.23.0 (2018-02-12)
  241. Plinth v0.22.0 (2018-01-30)
  242. Plinth v0.21.0 (2018-01-15)
  243. Plinth v0.20.0 (2018-01-01)
  244. Plinth v0.19.0 (2017-12-18)
  245. Plinth v0.18.0 (2017-12-04)
  246. Plinth v0.17.0 (2017-11-20)
  247. Plinth v0.16.0 (2017-11-06)
  248. Plinth v0.15.3 (2017-10-20)
  249. Plinth v0.15.2 (2017-09-24)
  250. Plinth v0.15.0 (2017-07-01)
  251. Plinth v0.14.0 (2017-04)
  252. Plinth v0.13.1 (2017-01-22)
  253. Plinth v0.12.0 (2016-12-08)
  254. Plinth v0.11.0 (2016-09-29)
  255. Plinth v0.10.0 (2016-08-21)
  256. Version 0.9.4 (2016-06-24)
  257. Version 0.9 (2016-04-24)
  258. Version 0.8 (2016-02-20)
  259. Version 0.7 (2015-12-13)
  260. Version 0.6 (2015-10-31)
  261. Version 0.5 (2015-08-07)
  262. Version 0.3 (2015-01-20)
  263. Version 0.2 (2014-03-16)
  264. Version 0.1 (2013-02-26)
  265. Quick Links
  266. Welcome to newcomers
  267. Donate
  268. Spread the Word
  269. Feed Us Back (Comment)
  270. Request applications
  271. Translate
  272. Document: User Manual, Website and Wiki, HowTo/demo videos
  273. Assure Quality (Test and Check)
  274. Code
  275. Design
  276. Package Applications
  277. FreedomBox Service (Plinth)
  278. FreedomBox Setup
  279. Freedom Maker

FreedomBox Einführung

FreedomBox ist ein persönlicher Server, der Ihre Privatsphäre schützt. Es ist ein freier Software-Stack, ein Teil des Debian universellen Betriebssystems, das auf vielen Varianten von günstiger und energieeffizienter Hardware installiert werden kann. Die Einfachheit der Installation und des Betriebs einer FreedomBox ist ähnlich der von einem Smartphone.

1. Smart Router

FreedomBox läuft auf einem physischen Computer und kann Ihren Datenverkehr lenken. Es kann zwischen verschiedenen Geräten zu Hause sitzen, wie beispielsweise Mobiltelefone, Laptops, Fernseher und das Internet und ersetzt einen Wireless-Router. Durch das Routen des Datenverkehrs kann FreedomBox Tracking-Anzeigen und bösartige Web-Bugs entfernen, bevor sie überhaupt Ihre Geräte erreichen. FreedomBox kann Ihren Standort verbergen und schützt Ihre Anonymität durch "Onion Routing" Ihres Datenverkehrs über Tor. FreedomBox bietet einen VPN-Server, den Sie verwenden können wenn Sie unterwegs sind, um Ihren Datenverkehr auf nicht vertrauenswürdigen öffentlichen Funknetzen zu verschiedenen Geräten zuhause sicher und geheim zu halten. Es kann auch zusammen mit Ihrem Laptop mitgeführt und dazu verwendet werden, um sich an öffentliche Netze bei der Arbeit, in der Schule oder Büro zu verbinden, um deren Dienste in Anspruch zu nehmen. Es könnte in einem Dorf verwendet werden, um die Kommunikation im ganzen Dorf zu ermöglich. Zukünftig beabsichtigt FreedomBox Unterstützung für alternative Verbindungsmöglichkeiten mit dem Internet zu ermöglichen, wie beispielsweise Mesh Netze.

2. Private Cloud

FreedomBox bietet Dienstleistungen: für Ihren Computer und mobile Geräte in Ihrem Haus und zu Computern und mobilen Geräten von anderen Menschen, die Ihre Freunde sind. FreedomBox bietet Filesharing wie Dropbox, gemeinsame Kalander wie Google oder Yahoo und Foto-Sharing. FreedomBox bietet Instant Messaging und wirklich sichere Sprachkonferenzen, die auf niedriger Bandbreite mit hoher Qualität arbeiten. FreedomBox hat einen Blog und Wiki und lässt Sie so Ihre Informationen veröffentlichen und gemeinsam mit dem Rest der Welt zusammenarbeiten. In Kürze wird ein persönlicher E-Mail-Server und verteiltes Social-Networking mit GNU Social und Diaspora realisiert, die beide Ihre Privatsphäre respektieren als Alternative zu Google Mail und Facebook.

Schnelleinstieg

  1. Die einfachste Methode um ein FreeedomBox zu haben, ist es zu kaufen. Sonst, laden Sie ein FreedomBox Image herunter und installieren Sie es indem Sie den Anweisungen auf Download folgen.

  2. Stecken Sie ein Ende des Ethernetkabels in den Ethernet-Port Ihrer FreedomBox und das andere Ende in Ihren Router.

    • Auf der Dreamplug sollte der eth0-Port (in der Mitte der Box) an den Router angeschlossen werden.
  3. Wenn Ihr Gerät einen zweiten Ethernet-Port hat, können Sie Ihren Computer mit einem weiteren Ethernetkabel direkt daran anschließen.
  4. Starten Sie Ihre FreedomBox.

  5. Beim ersten Booten wird die FreedomBox die Erstinstallation durchführen und dann neu zu starten. Dies kann mehrere Minuten dauern.

  6. Nachdem die FreedomBox neu gestartet wurde, können Sie auf dessen Web-Interface (genannt Plinth) über Ihren Webbrowser zugreifen.

    • Wenn der Computer direkt an die FreedomBox durch einen zweiten (LAN) Ethernet-Port angeschlossen ist, können Sie http://freedombox/ oder http://10.42.0.1/ verwenden.

    • Wenn Ihr Computer mDNS unterstützt (GNU/Linux, Mac OSX und Windows mit installierter mDNS-Software), können Sie http://freedombox.local/ (oder http://der-hostname-den-Sie-bei-der-Installation-verwendet-haben.local/) verwenden.

    • Wenn keine dieser Methoden zur Verfügung steht, müssen Sie die IP-Adresse Ihrer FreedomBox herausfinden. Sie können dazu das "nmap" Programm verwenden:

           nmap -p 80 --open -sV 192.168.0.0/24

      Ihre FreedomBox wird als eine IP-Adresse mit einer offenen TCP-Port 80 unter Verwendung vom Apache-Dienst http auf Debian erscheinen, wie das Beispiel hier zeigt, wo es über http://192.168.0.165 zugänglich ist:

           Nmap scan report for 192.168.0.165
           Host is up (0.00088s latency).
           PORT   STATE SERVICE VERSION
           80/tcp open  http    Apache httpd 2.4.17 ((Debian))
  7. Beim Zugriff auf Plinth wird Sie Ihr Browser warnen, dass er sicher kommuniziert aber dass er das Sicherheitszertifikat für ungültig hält. Dies ist eine Tatsache, die Sie zur Zeit akzeptieren müssen, weil das Zertifikat automatisch auf der Box erzeugt und daher "selbstsigniert" wird (der Browser könnte auch Worte wie "nicht vertrauenswürdig", "nicht privat", "Privatsphäre-Fehler" oder "unbekannter Emittent/Behörde" verwenden). Ihrem Browser mitzuteilen dass Sie dies wissen, wird durch Drücken der Tasten wie "Ich verstehe die Risiken" oder "Ausnahme hinzufügen" erreicht.
  8. Beim ersten Zugriff werden Sie eine Willkommensseite sehen die Sie bittet, einige grundlegende Informationen zum Einrichten der FreedomBox bereitzustellen.

  9. Nach dem Ausfüllen des Formulars werden Sie bei Plinth angemeldet und in der Lage sein, auf Anwendungen und Konfigurationen über diese Schnittstelle zuzugreifen.
  10. Wenn Ihr Computer direkt mit der FreedomBox verbunden ist kann Ihre FreedomBox als Router arbeiten, und Ihnen Zugriff auf das Internet ermöglichen.

Nun können Sie die Apps, die auf der FreedomBox verfügbar sind, ausprobieren.

Hilfe Erhalten

Die FreedomBox-Gesellschaft bietet Instanthilfe durch Forum, Chat und E-Mail. Fühlen Sie sich frei, mitzumachen und, was Sie möchten zu fragen. Wenn Sie erfolgreiche Hilfe erhalten, wägen Sie ab, Ihre Lösung auf der Seite "Fragen und Antworten" einzutragen, damit andere in der Zukunft davon profitieren können.

1. Diskussionsforum

Der einfachste Unterstützungsmittel, ist das Diskussionsforum. Sie können nach Lösungen für bekannte Probleme suchen, oder Hilfe von Gesellschaftsmitwirkenden anfordern, indem Sie Fragen stellen. Dies ist auch der beste Mittel, um Gesellschaftsmitwirkenden von Ihrer FreedomBox-Erfahrung zu informieren.

Um neue Informationen zu veröffentlichen, müssen Sie sich mit Name und E-Mail-Adresse eintragen (Sie dürfen jedoch ein Pseudonym und eine sekundäre E-Mail-Adresse angeben). Sie können sich Themen und Kategorien ansehen oder wenn Sie den Mailinglistenmodus in Ihren Kontoeinstellungen aktivieren, können Sie mit dem Forum durch e-Mail, wie bei einer Mailingliste, interagieren.

2. Matrix

Sie können unserem Matrixraum #freedombox:matrix.org beitreten. Der Raum ist mit dem IRC-Kanal verbunden und speichert den Chat-Verlauf. Wenn Sie noch keinen Client installiert haben, können Sie sich mit Ihrem Webbrowser anmelden. Weitere Optionen finden Sie auf dieser Matrix-Client-Übersichtsseite.

3. IRC #freedombox

Wenn Sie sind mit Internet Relay Chat (IRC) und IRC client vertraut sind, können Sie auch sofortige Online-Hilfe von der Gesellschaft auf dem Kanal #freedombox in irc.debian.org erhalten. Wahrscheinlich dauert es einige Zeit, bis ein Mitglied Ihnen antwortet. Seien Sie geduldig. Eine Reaktion wird eventuell eintreten.

4. Email

FreedomBox-Benutzer und Mitwirkende sind per E-Mail über eine Diskussionsliste erreichtbar. Um eine Frage zu stellen und eine Antwort von der Gesellschaft zu erhalten, registrieren Sie sich bitte auf der Mailinglistenseite, geben Sie Ihre E-Mail-Adresse an und erstellen Sie ein Passwort. Sie können auch Diskussionsarchive lesen . Diese Liste sammelt etwa 700 Leser an.

5. Hilfe wiedergeben

Wenn Sie erfolgreiche Hilfe erhalten, vergessen Sie nicht, Ihre Lösung auf der Seite Fragen und Antworten einzutragen, und erzählen Sie in der Seite Anwendungsfälle, welche Funktionen Sie verwenden. Es könnte anderen helfen, FreedomBox auf eine Weise zu verwenden, die sie sich noch nicht vorgestellt hätten.

Herunterladen und installieren

  • Notitz: Wenn Sie ein FreedomBox Kit gekauft haben, richtet sich dieser Abschnitt nicht an Sie, und Sie dürfen ihn ruhig überlesen. (Es sei denn, Sie wollen explizit ein alternatives Image bauen).

Sie können FreedomBox entweder auf einer der unterstützten Hardware, auf einem Debian System oder einer virtuellen Maschine verwenden.

1. Herunterladen für Debian

Wenn Sie auf Debian installieren, brauchen Sie diese Images nicht herunterladen. Stattdessen lesen Sie bitte die Anleitungen zum Einrichten der FreedomBox auf Debian.

2. Herunterladen für Hardware bzw. Virtuelle Maschinen

2.1. Gerät vorbereiten

Siehe die Hardware-spezifischen Anweisungen, wie Sie Ihr Gerät vorbereiten. Lesen Sie so viele Dokumentationen wie möglich, die Sie im Internet über das ersten Booten und Flashen von USB oder SD-Karten auf Ihrer Hardware finden können.

2.2. Images Herunterladen

Neueste Images für unterstützte Geräte finden Sie hier:

2.3. Heruntergeladene Images Überprüfen

Es ist wichtig die Images die Sie heruntergeladen haben zu überprüfen, um sicherzustellen, dass die Datei nicht während der Übertragung beschädigt wurde und dass es sich in der Tat um die durch FreedomBox Entwickler erstellte Images handelt.

  • Öffnen Sie zunächst ein Terminal und importieren Sie den öffentlichen Schlüssel des FreedomBox Entwicklers, der das Image erstellt hat:

    $ gpg --keyserver x-hkp://pool.sks-keyservers.net --recv-keys 0x36C361440C9BC971
  • Als nächstes überprüfen Sie den Fingerabdruck des öffentlichen Schlüssels:
    $ gpg --fingerprint 0x36C361440C9BC971
    pub   4096R/0C9BC971 2011-11-12
          Key fingerprint = BCBE BD57 A11F 70B2 3782  BC57 36C3 6144 0C9B C971
    uid                  Sunil Mohan Adapa <sunil@medhas.org>
    sub   4096R/4C1D4B57 2011-11-12
  • Schließlich verifizieren Sie Ihr heruntergeladenes Image mit seiner Signatur-Datei .sig. Beispielsweise:

    $ gpg --verify freedombox-unstable-free_2015-12-13_cubietruck-armhf.img.xz.sig freedombox-unstable-free_2015-12-13_cubietruck-armhf.img.xz
    gpg: Signature made Thursday 15 January 2015 09:27:50 AM IST using RSA key ID 0C9BC971
    gpg: Good signature from "Sunil Mohan Adapa <sunil@medhas.org>"
    gpg: WARNING: This key is not certified with a trusted signature!
    gpg:          There is no indication that the signature belongs to the owner.
    Primary key fingerprint: BCBE BD57 A11F 70B2 3782  BC57 36C3 6144 0C9B C971

2.4. Installation

Nach dem Download können Sie das Image verwenden um die unterstützte Hardware (einschließlich virtuelle Maschinen) zu booten. Sie müssen das Image wie folgt auf die Speicherkarte oder den USB-Stick kopieren:

  1. Finden Sie heraus, welches Gerät Ihre Karte tatsächlich ist.
    1. Entnehmen Sie Ihre Karte.
    2. Starten Sie dmesg -w um die Kernel-Meldungen anzuzeigen.

    3. Stecken Sie Ihre Karte ein. Sie sehen Nachrichten wie:
    • [33299.023096] usb 4-6: new high-speed USB device number 12 using ehci-pci
      [33299.157160] usb 4-6: New USB device found, idVendor=058f, idProduct=6361
      [33299.157162] usb 4-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [33299.157164] usb 4-6: Product: Mass Storage Device
      [33299.157165] usb 4-6: Manufacturer: Generic
      [33299.157167] usb 4-6: SerialNumber: XXXXXXXXXXXX
      [33299.157452] usb-storage 4-6:1.0: USB Mass Storage device detected
      [33299.157683] scsi host13: usb-storage 4-6:1.0
      [33300.155626] scsi 13:0:0:0: Direct-Access     Generic- Compact Flash    1.01 PQ: 0 ANSI: 0
      [33300.156223] scsi 13:0:0:1: Direct-Access     Multiple Flash Reader     1.05 PQ: 0 ANSI: 0
      [33300.157059] sd 13:0:0:0: Attached scsi generic sg4 type 0
      [33300.157462] sd 13:0:0:1: Attached scsi generic sg5 type 0
      [33300.462115] sd 13:0:0:1: [sdg] 30367744 512-byte logical blocks: (15.5 GB/14.4 GiB)
      [33300.464144] sd 13:0:0:1: [sdg] Write Protect is off
      [33300.464159] sd 13:0:0:1: [sdg] Mode Sense: 03 00 00 00
      [33300.465896] sd 13:0:0:1: [sdg] No Caching mode page found
      [33300.465912] sd 13:0:0:1: [sdg] Assuming drive cache: write through
      [33300.470489] sd 13:0:0:0: [sdf] Attached SCSI removable disk
      [33300.479493]  sdg: sdg1
      [33300.483566] sd 13:0:0:1: [sdg] Attached SCSI removable disk
    • Im obigen Fall ist die Platte, die neu eingefügten wurde als /dev/sdg verfügbar. Notieren Sie dies sorgfältig und verwenden Sie es in dem Kopierschritt unten.

  2. Entpacken Sie das heruntergeladene Image:
    $ xz -d freedombox-unstable-free_2015-12-13_cubietruck-armhf.img.xz

    Der oben stehende Befehl ist ein Beispiel für das cubietruck Image vom 2015.12.13. Ihre heruntergeladene Datei wird einen anderen Namen haben.

  3. Kopieren Sie das Image auf Ihre Karte. Überprüfen sie dabei alle Schritte sehr genau um sicherzustellen, dass Sie nicht aus Versehen auf den Speicher des Computers (wie /dev/sda) schreiben. Stellen Sie auch sicher, dass Sie diesen Schritt nicht als root durchführen, um zu vermeiden versehentlich Daten auf Ihrer Festplatte durch einen Fehler bei der Identifizierung des Geräts oder einem Fehler während der Eingabe des Befehls zu löschen. USB Sticks und SD-Karten sollten in der Regel für normale Benutzer beschreibbar sein. Wenn Sie nicht über die Berechtigung verfügen, auf die SD-Karte als Benutzer zu schreiben, müssen Sie diesen Befehl als root ausführen. In diesem Fall überprüfen Sie alles dreifach, bevor Sie den Befehl ausführen. Eine weitere Sicherheitsmaßnahme ist, alle externen Festplatten mit Ausnahme der SD-Karte abzuziehen, bevor Sie den Befehl ausführen.

    For example, if your SD card is /dev/sdf as noted in the first step above, then to copy the image, run:

    Zum Beispiel, wenn die SD-Karte /dev/sdf heißt, wie im ersten Schritt oben festgestellt wurde, dann führen Sie folgendes aus, um das Image zu kopieren:

    $ cd build
    $ dd bs=1M if=freedombox-unstable-free_2015-12-13_cubietruck-armhf.img of=/dev/sdf conv=fdatasync

Andere moglichkeit zum kopieren zum SD card, when dd ist nicht for hande.

$ cat freedombox-unstable-free_2015-12-13_cubietruck-armhf.img > /dev/sdf ; sync

Fur MS Windows gibt das programm etcher.

  • Der oben stehende Befehl ist ein Beispiel für das cubietruck Image vom 2015.12.13. Ihre heruntergeladenen Dateinamen wird anders sein.

    Bei der Auswahl des Geräts, verwenden Sie den Laufwerkbuchstaben, wie /dev/sdf, nicht ein nummerisches Ziel, wie /dev/sdf1. Das Gerät ohne Nummer bezieht sich auf die gesamte Vorrichtung, während der Name mit Zahl auf eine bestimmte Partition verweist. Wir wollen das ganze Gerät verwenden. Heruntergeladene Images enthalten alle Informationen über wie viele Partitionen benötigt werden, ihre Größen und Typen. Sie müssen nicht die SD-Karte formatieren oder Partitionen erstellen. Alle Daten auf der SD-Karte werden während des Schreibprozesses gelöscht werden.

    1. Verwenden Sie das Image, indem Sie die SD-Karte oder USB-Platte in das Gerät einsetzen und von ihm starten. Ihr Gerät sollte ebenfalls vorbereitet worden sein (siehe den entsprechenden Abschnitt).

    2. Lesen Sie (den Rest) des Handbuchs für Anweisungen, wie Sie Anwendungen in FreedomBox verwenden.

Anwendungen (Apps)

1. Bepasty (Datei- und Ausschnittteilen)

bepasty-Ikon

Verfügbar seit: Version 20.14

1.1. Was ist Bepasty?

Bepasty ist eine Webanwendung, mit der man grosse Dateien laden und freigeben kann. Man kann auch Text- und Codeausschnitten kleben und freigeben. Benutzer können Vorblicke von Texte, Bilde, Audio, Video und PDF Dateien sich im Webbrowser vorschauen. Man kann ein Ablaufzeit für die Freigegebene Dateien einstellen.

1.2. Bilschirmfoto

Bilschirmfoto von Bepasty

1.3. Passwörter und Erlaubnisse

Bepasty verwendet nur Passwörter (keine Benutzernamen), um Zugriff zu steuern. Der Benutzer kriegt verschiebene Erlaubnisse, je nach Passwort. Man kann folgende Erlaubnisse kombinieren:

  • lesen: Kann eine Datei lesen, wenn man die URL kennt.

  • listen: Alle Dateien auflisten.

  • erschaffen: Eine neue Datei kleben, bzw. aufladen.

  • löschen: Eine Datei löschen.

  • verwalten: Dateie absperren, bzw. entsperren.

Nach der Installation Bepasty ist voreingestellt für folgende Rollen:

  • Schauer: Kann Dateien lesen und auflisten
  • Editor: Kann Dateien lesen, auflisten, erschaffen und löschen
  • Verwalter: Vollberechtigt

Diese Rollen unterstüttzen der Anwendungsfall einer Dateifreigabe unter bekannten, berechtigte Benutzern. Bei Bedarf kann man Bepasty für andere Rolle bzw. Anwendungsfälle wiedereinstellen.

1.4. Verteilung von Passwörte

Standardmässig ist der öffentlichen Zugriff auf None eingestellt, sodass eine Passwort für Zugriff auf Bepasty verlangt wird. Das heisst, dass Sie die Passwörte über andere vorhandene Kommunikationskanäle an die entschprechenden Benutzer vertilen müssen.

Beachten Sie btte, dass Sie wahrscheinlich mehrere verschiedene Passwörte mit dem selben Erlaubnissmenge erstellen möchten. Dies erlaubt jeder Benutzer (bzw Benutzergruppe) eine eigene Passwort zu kriegen. Wenn Sie dann einem bestimmten Benutzer den Zugriff entziehen möchten, können Sie dessen Passwork einfach löschen. Die andere Benutzer bleiben ungetroffen, denn jeder hat seine eigene Passwort.

1.5. Bepasty verwenden

Nach Anmeldung bei Bepasty, wenn Sie erlaubt zu "erschaffen" sind, wird ein grosses Textfeld angeboten in das Sie beliebigen Text kleben können. Sie dürfen auch Dateiname oder Content-Type für dem Inhalt angeben. Wenn Sie auf Senden klicken, wird die Datei erschafft.

Sie können auch Dateie ziehen in den unteren Bereich ablegen, und sie werden sofort aufgeladen. Sie können auch eine Liste erschaffen, um eine Sammlung hochgeladener Dateien zu verfolgen.

Sie können einen maximalen Lebensdauertwert festlegen. Nach Ablauf dieser Zeit wird die Datei gelösch.

Wenn Sie erlaubt zu "listen" sind, wird oben auf der Seite ein Link Alle Elemente Auflisten angezeigt. Dies zeigt alle Dateien an, die erschafft oder aufgeladen wurden.

Wenn Sie erlaubt zu "löschen" oder "verwalten" sind, werden auf der Listenseite neben jeder Datei weitere Aktionen angeboten.

Wenn Sie nur zu "lesen" erlaubt sind, brauchen Sie eine Passwort und eine oder mehrere URLs für vorhandene Dateien, um sie zu lesen,

1.6. Passwortverwaltung

Die Bepasty-Konfigurationseite im FreedomBox Interface erlaubt Sie neue Passwörter zu erstellen und verhandene zu löschen. When Sie eine Passwort erstellen, können Sie die oben beschriebene Berechtigungen kombinieren. Beachten Sie, dass ein Verwalter alle Berechtigungen haben sollte (nicht nur "Verwalter").

Sie können auch ein Kommentar angeben. Es ist empfohlen, sich damit der Zweck des Passwortes, bzw. wer sie es verwenden wird, zu merken.

Man kann auch öffentlichen Zugriff konfigurieren. Damit legt man Standarderlaubnisse, die auch ohne Anmeldung gelten, fest. So kann man festlegen, ob man Dateie über ihre URL lesen darf, oder ob man alle Dateie auflisten und lesen darf.

2. Calibre (e-Library)

calibre app tile in FreedomBox web interface

Available since: version 20.15

calibre is an e-book management solution. You can organize your e-books into collections in calibre known as "libraries". calibre can do e-book format conversion between most of the popular e-book formats. It can also manage metadata of your e-books such as book covers, descriptions, author and publisher information etc.

Moving your calibre library from your desktop to your FreedomBox has the benefit of being able to access your e-books from any device on the local network or through the Internet.

Only users who are members of the calibre group have access to the libraries. You can assign users to this group via the system app users and groups.

You might be familiar with the e-book reader shipped with the calibre application on your desktop. The server version of calibre that's installed on your FreedomBox has a web-based e-book reader with similar look and feel. This allows you to read your e-books from any device with a web browser.

2.1. Managing Libraries

After installation of calibre, a default library called "Library" will be made available. The FreedomBox administrator can add or delete any of the libraries including the default one from the app settings in FreedomBox web interface.

2.2. Access

calibre can be accessed after installation through the web client at https://<my_freedombox_name>/calibre.

3. Coturn (VoIP-Helfer)

Coturn Ikon

Verfügbar seit: Version 20.8

Coturn ist ein Server zur Erleichterung von Audio- bzw. Videoanrufen und Konferenzen durch die Implementierung von TURN- und STUN- Protokollen. WebRTC, SIP und andere Kommunikationsserver können damit einen Anruf zwischen Teilnehmern herstellen, die sonst keine Verbindung zueinander herstellen können.

Es ist nicht, um direkt von Benutzern verwendet zu werden entworfen. Server wie Matrix Synapse müßen mit den auf der Coturn-App-Seite angegebenen Details konfiguriert werden. Abgesehen von Matrix Synapse können Jitsi, Ejabberd, Nextcloud Talk usw. den Coturn-Server für Audio- bzw. Videoanrufe und Konferenzen verwenden. Man braucht nicht die Coturn-Serversoftware auf demselben Rechner wie FreedomBox ausgeführt werden, und externe Komunikationsserver können den von FreedomBox gelieferten Coturn verwenden.

Coturn ist in FreedomBox als fortgeschrittene Anwendung bezeichnet. Das heißt, daß um das Coturn-Ikon im Abteilung "Apps" zu sehen, Sie die Option "Fortgeschrittene Apps und Funktionen anzeigen" unter "Allgemeine Konfiguration" aktivieren müßen.

3.1. Wie funktioniert es

Bei einen Audio- bzw. Videoanruf soll man lieber die Medienströme direkt zwischen beide Seiten leiten. Dies bietet die bestmögliche Latenz (beßere Signalqualität) und vermeidet die Abhängigkeit von einem zentralen Server (Datenschutz). Es läßt sich gut skalieren, denn ein einfacher Chat-Server kann Tausende Anrufen hosten, bei dem der Server nirgends außer beim Anrufseinrichtung mitmacht. Dieser Ansatz funktioniert jedoch wegen der Netzwerkkonfiguration meistens nicht. Den meisten Netzwerkbetutzer ist keine eindeutige IP-Adreße zugewiesen. Sie arbeiten versteckt hinter einem Netzwerkgerät, das für sie Network Address Translation (NAT) ausführt. Das heißt, daß beide Seiten keine Möglichkeit haben, sich gegenseitig zu erreichen.

Als Lösung zu diesem Problem, wurde eine einfache Technik namens STUN eingeführt. Mithilfe eines drittseits STUN-Servers können die Seiten die NAT-Geräte austricksen, um den Datenverkehr zwischen beiden zu übertragen. Leider funktioniert dieser Trick nur in etwa 80% der Fälle. Wenn STUN fehlschlägt, haben die Seiten keine andere Wahl, als ihren Datenverkehr über einen Zwischenserver namens TURN-Server weiterzuleiten. Der ganze Mechanismus, STUN zuerst auszuprobieren und dann auf TURN zurückzugreifen, wird in einem Protokoll namens ICE beschrieben.

Auf FreedomBox bietet Coturn sowohl STUN- als auch TURN-Server. Beide Dienste werden sowohl über TCP als auch über UDP bereitgestellt. Sie werden sowohl auf unverschlüßelten als auch auf verschlüßelten Kanälen (die höhere Erfolgschancen haben) bereitgestellt. Da STUN-Server sehr kostengünstig sind und wenige Servermitteln verbrauchen, braucht man keine Authentifizierung, um sie zu verwenden. Dagegen, TURN-Server benötigen Authentifizierung. Diese Authentifizierung ist stark vereinfacht und erfordert keine Benutzerdatenbankpflege. Ein Server wie Matrix-Synapse, der einen Audio- bzw. Videoanruf zwischen 2 Seiten einrichten soll, generiert einen Benutzernamen und ein Kennwort durch eines gemeinsamen Geheimnis. Wenn die Seiten den TURN-Server verwenden, werden sie anhand dieser Anmeldeinformationen überprüft, da der TURN-Server dieses Geheimnis shon kennt.

Zusammenfaßend, ein Kommunikationsserver muß die URLs der STUN bzw. TURN-Server sowie ein gemeinsames Authentifizierungsgeheimnis für TURN kennen. Danach steuert er die korrekte Verwendung von STUN bzw. TURN-Servern während des Einrichtens von Audio- bzw. Videoanrufen zwischen beide Seiten. Die Coturn-App auf FreedomBox bietet genau diese Informationen, die dann beim Einstellung eines Kommunikationsservers verwendet werden können, unabhängig davon, ob er auf derselben FreedomBox oder auf einem anderen Server ausgeführt wird.

3.2. Einstellung von Matrix Synapse

Der Matrix Synapse-Server kann in FreedomBox für die Verwendung des Coturn TURN bzw. STUN-Servers eingestellt werden. In der Zukunft, wenn Sie Matrix Synapse installieren, wird FreedomBox automatisch Coturn installieren und seine Parameter in Matrix Synapse einstellen. Um Matrix Synapse einzustellen, bearbeiten Sie die Datei /etc/matrix-synapse/homeserver.yaml mit den folgenden Zeilen

turn_uris: [ "stun:myfreedombox.example.org:3478?transport=udp", "stun:myfreedombox.example.org:3478?transport=tcp", "turn:myfreedombox.example.org:3478?transport=udp", "turn:myfreedombox.example.org:3478?transport=tcp" ]
turn_shared_secret: "my-freedombox-provided-secret"
turn_user_lifetime: 86400000
turn_allow_guests: True

Der Wert für turn_shared_secret wird als static-auth-secret in der Datei /etc/coturn/freedombox.conf angegeben

Starten Sie anschließend den Matrix-Synapse-Server neu, indem Sie die Matrix-Synapse Anwendung deaktivieren und wieder aktivieren.

3.3. Portweiterleitung

Wenn sich Ihre FreedomBox hinter einem Router befindet, müßen Sie die Portweiterleitung auf Ihrem Router einrichten. Sie sollten die folgenden Ports für Coturn weiterleiten:

  • UDP 3478
  • TCP 3478
  • UDP 3479
  • TCP 3479
  • UDP 5349
  • TCP 5349
  • UDP 5350
  • TCP 5350
  • UDP 49152-50175
  • TCP 49152-50175

4. Deluge (Verteilte Dateifreigabe über BitTorrent)

Deluge Ikon

Verfügbar seit: Version 0.5

4.1. Was ist Deluge?

Deluge ist ein BitTorrent-Netzknoten (Client sowohl als Server, beide gleichzeitig).

BitTorrent ist ein Kommunikationsprotokoll für Peer-to-Peer (P2P) Freigabe von Dateien.

  • Es ist nicht anonym; Sie sollen davon ausgehen, daß andere sehen können, welche Dateien Sie freigeben.

  • Diese Technologie eignet sich am besten für große, beliebte Dateien

In FreedomBox sind zwei BitTorrent-Webknoten verfügbar: Transmission und Deluge. Sie haben ähnliche Funktionen, aber wahrscheinlich mögen Sie eine lieber als der anderen.

Deluge ist ein leichter BitTorrent-Client, der hochgradig konfigurierbar ist. Zusätzliche Funktionen können durch die Einrichtung von Erweiterungen (Plugins) hinzugefügt werden.

4.2. Bildschirmfoto

Deluge Web UI

4.3. Ersteinrichtung

Nach der Einstellung, setzen Sie Ihren Browser auf https://<Ihre Freedombox>/deluge, um auf Deluge zuzugreifen. Sie müssen ein Passwort eingeben, um sich anzumelden:

Deluge Login

Das ursprüngliche Passwort lautet "deluge". Bei erster Anmeldung, fragt Deluge, ob Sie das Passwort ändern möchten. Sie sollen es in etwas ändern, das schwerer zu erraten ist.

Dann, wird Ihnen der Verbindungsmanager angezeigt. Klicken Sie auf den ersten Eintrag (Offline - 127.0.0.1:58846). Klicken Sie dann auf "Daemon starten", um den Deluge-Dienst zu starten, der im Hintergrund ausgeführt wird.

Deluge Connection Manager (Offline)

Nun sollte es "Online" zeigen. Klicken Sie auf "Verbinden", um die Einrichtung zu vervollständigen.

Deluge Verbindungsmanager (Online)

An diesem Punkt können Sie Deluge verwenden. Sie können weitere Einstellungen verändern oder eine Torrent-Datei bzw. URL hinzufügen.

5. Ejabberd (Chat Server)

ejabberd icon

Available since: version 0.3

5.1. What is ejabberd?

Ejabberd is a chat server which uses the Extensible Messaging and Presence Protocol (XMPP).

5.2. What is XMPP?

XMPP is a federated server-client protocol for Instant Messaging. This means that users who have accounts on one server, can talk to users that are on another server.

XMPP can also be used for voice and video calls, if supported by the clients.

Currently FreedomBox offers both, a server (ejabberd) and a web client (JSXC) from its web interface.

5.3. Privacy

With XMPP, there are two ways that conversations can be secured:

  1. TLS: This secures the connection between the client and server, or between two servers. This should be supported by all clients and is highly recommended.
  2. End-to-end: This secures the messages sent from one client to another, so that even the server cannot see the contents. The latest and most convenient protocol is called OMEMO, but it is only supported by a few clients. There is another protocol called OTR that may be supported by some clients that lack OMEMO support. Both clients must support the same protocol for it to work.

5.4. Setting the Domain Name

For XMPP to work, your FreedomBox needs to have a Domain Name that can be accessed over the network.

If you only need the local network (LAN) users to chat with each other you can invent your domain name, but if you want users from the internet to join your rooms you need a public domain name. You can read more about obtaining a Domain Name in the Dynamic DNS section of this manual.

Once you have a Domain Name, you can tell your FreedomBox to use it by setting the Domain Name in the System Configuration.

Note: After changing your Domain Name, the Chat Server (XMPP) page may show that the service is not running. After a minute or so, it should be up and running again.

Please note that PageKite does not support the XMPP protocol at this time.

5.5. Registering FreedomBox users to use XMPP

Currently, all users created through FreedomBox will be able to login to the XMPP server. You can add new users through the System module Users and Groups. It does not matter which Groups are selected for the new user.

5.6. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for XMPP:

  • TCP 5222 (client-to-server)
  • TCP 5269 (server-to-server)

5.7. Compatible clients

  • FreedomBox provides a web client: JSXC.

  • XMPP clients are available for various desktop and mobile platforms. FreedomBox links to the download sources of some of them. Feel free to include more here (needs free registration). We'll notice and might list them in FreedomBox.

    XMPP clients

5.7.1. FreedomBox webclient

For maximum simplicity FreedomBox provides a web client: JSXC. No need for your users to install additional software on their side. They'll be able to just use their browser. This is usually the first choice for new and eventual users.

5.7.2. Mobile clients

You can download an XMPP client for your smartphone or tablet among the ones listed below.

5.7.2.1. Conversations (Android)

Conversations is an Android XMPP client with videochat support available on F-Droid or the Play Store. In addition to text messaging, you can use Conversations to send images and have group chats.

Conversations - First screen Conversations - Login Conversations - Add contacts

From left to right: (1) First screen - (2) Login screen - (3) Add contacts.

When first starting the Conversations app, you will be asked whether you want to create a new account or if you want to use an existing account. Choose "I already have an account" (1)

With ejabberd installed, the FreedomBox provides an XMPP account for every FreedomBox user. Additional (non-admin) FreedomBox user accounts can be created under System > Users and Groups.

Once logged into a FreedomBox/XMPP account (2), the Conversation app provides a + button that brings up a few choices to contact other people (3).

5.7.2.2. Movim (Android)

Movim is a free software XMPP client with videochat support for Android available on F-Droid.

5.7.2.3. ChatSecure (iOS)

ChatSecure is a free software XMPP client with videochat support available from the App Store.

5.7.2.4. Monal (iOS)

Monal is a free software XMPP client with videochat support available from the App Store.

5.7.2.5. Siskin (iOS)

Siskin is a free software XMPP client with videochat support available from the App Store.

5.7.3. Desktop clients

5.7.3.1. Gajim (Windows, MacOS, Linux)

Gajim is a XMPP open-source client for the desktop, available for Windows, MacOS and Linux. This application is available in Debian, and for other operating systems you can download it from this page and find instructions about installation.

Gajim - First screen Gajim - Login Gajim - Main Window

From left to right: (1) First screen - (2) Login screen - (3) Main window

A popup shows up right after you start Gajim for the first time (1), asking you to either login to your XMPP (FreedomBox) account or to register for a new account. When you choose to login, after clicking "Forward", you will be asked a Jabber ID and a password (2): you have to enter your FreedomBox account and password here.

Finally, after logging in successfully, you will see the main Gajim screen (3). From there, you can add a contact (Account > Add contact...) then you can start a conversation (Gajim > Start chat).

5.7.3.2. Dino (Linux)

Dino is another XMPP free software client for the desktop. It is available for https://github.com/dino/dino/wiki/Distribution-Packages.

Dino - First screen Dino - Login Dino - Start a conversation

From left to right: (1) First screen - (2) Login screen - (3) Start conversation

When first starting Dino after installation, click on the Setup account button. You will be then asked your JID: this is your FreedomBox account. Enter it then click Next (2). Alternatively, you can click on Create account if you don't have a FreedomBox account.

Once you have logged in, you will be able to either start a conversation with one of your XMPP contacts or to join a channel (3).

5.7.3.3. Movim (Linux)

Movim is a free software XMPP client with videochat support for Linux. The project provides an unofficial Debian package.

5.7.3.4. Monal (MacOS)

Monal is a free software XMPP client with videochat support available from the Mac App Store.

5.8.1. Ejabberd

5.8.2. Clients' sites

5.8.3. XMPP Protocol

6. GitWeb (Simple Git Hosting)

Gitweb icon

Available since: version 19.19

6.1. What is Git

Git is a distributed version-control system for tracking changes in source code during software development. GitWeb provides a web interface to Git repositories. You can browse history and content of source code, use search to find relevant commits and code. You can also clone repositories and upload code changes with a command-line Git client or with multiple available graphical clients. And you can share your code with people around the world.

To learn more on how to use Git visit Git tutorial.

6.2. Managing the repositories

After installation of GitWeb, a new repository can be created. It can be marked as private to limit access.

6.3. Access

GitWeb can be accessed after installation e.g. by the web client through https://<my_freedombox_name>/gitweb.

6.4. HTTP basic auth

GitWeb on FreedomBox currently supports HTTP(S) remotes only (i.e. not SSH). To avoid having to enter the password each time you pull/push to the repository, you can edit your remote to include the credentials.

Example: https://username:password@my.freedombox.rocks/gitweb/myrepo

Your username and password will be encrypted. Someone monitoring the network traffic will notice the domain name only.

Note: If using this method, your password will be stored in plain text in the local repository's .git/config file. For this reason, you should create a FreedomBox user who has only access to the gitweb and never use an admin account.

For GNOME users (Advanced)

GNOME "Passwords and Keys" utility can be used to store the username and password. See this StackOverflow Answer for details on how to do it.

6.5. Mirroring

Though your repositories are primarily hosted on your own FreedomBox, you can configure a repository on another Git hosting system like GitLab as a mirror.

6.6. Enabling/Disabling Features

In FreedomBox, some of the default features of gitweb have been changed:

  • Enabled: Blame feature to show what revision and author last modified each line of a file
  • Enabled: Pickaxe feature to list the commits that introduced or removed a given string
  • Enabled: Highlight feature to perform syntax highlighting on blobs
  • Disabled: Snapshot feature that provides a download of a compressed tar file for a given revision (due to high resource usage).

These features can be changed on a per-repository bases by an administrator by editing the git configuration file for the repository on FreedomBox. See manual page for gitweb.conf(5) for more details on syntax and features. For example, to re-enable the snapshot feature on myrepo repository, login to a FreedomBox terminal via SSH or web console as administrator and edit the file /var/lib/git/myrepo/config to contain the following section:

[gitweb]
snapshot = tgz

7. I2P (Anonymity Network)

I2P icon

7.1. About I2P

The Invisible Internet Project is an anonymous network layer intended to protect communication from censorship and surveillance. I2P provides anonymity by sending encrypted traffic through a volunteer-run network distributed around the world.

7.2. Services Offered

The following services are offered via I2P in FreedomBox by default. Additional services may be available when enabled from I2P router console that can be launched from FreedomBox web interface.

  • Anonymous Internet browsing: I2P can be used to browse Internet anonymously. For this, configure your browser (preferable a Tor Browser) to connect to I2P proxy. This can be done by setting HTTP proxy and HTTPS proxy to freedombox.local (or your FreedomBox's local IP address) and ports to 4444 and 4445 respectively. This service is available only when you are reaching FreedomBox using local network (networks in internal zone) and not available when connecting to FreedomBox from the Internet. One exception to this is when you connect to FreedomBox's VPN service from Internet you can still use this service.

  • Reaching eepsites: I2P network can host websites that can remain anonymous. These are called eepsites and end with .i2p in their domain name. For example, http://i2p-projekt.i2p/ is the website for I2P project in the I2P network. eepsites are not reachable using a regular browser via regular Internet connection. To browse eepsites, your browser needs to be configured to use HTTP, HTTPS proxies as described above. This service is available only when you are reaching FreedomBox using local network (networks in internal zone) and not available when connecting to FreedomBox from the Internet. One exception to this is when you connect to FreedomBox's VPN service from Internet you can still use this service.

  • Anonymous torrent downloads: I2PSnark, an application for anonymously downloading and sharing files over the BitTorrent network is available in I2P and enabled by default in FreedomBox. This application is controlled via a web interface that can be launched from 'Anonymous torrents' section of I2P app in FreedomBox web interface or from the I2P router console interface. Only logged-in users belonging to 'Manage I2P application' group can use this service.

  • IRC network: I2P network contains an IRC network called Irc2P. This network hosts the I2P project's official IRC channel among other channels. This service is enabled by default in FreedomBox. To use it, open your favourite IRC client. Then configure it to connect to host freedombox.local (or your FreedomBox's local IP address) with port number 6668. This service is available only when you are reaching FreedomBox using local network (networks in internal zone) and not available when connecting to FreedomBox from the Internet. One exception to this is when you connect to FreedomBox's VPN service from Internet you can still use this service.

  • I2P router console: This is the central management interface for I2P. It shows the current status of I2P, bandwidth statistics and allows modifying various configuration settings. You can tune your participation in the I2P network and use/edit a list of your favourite I2P sites (eepsites). Only logged-in users belonging to 'Manage I2P application' group can use this service.

8. Ikiwiki (Wiki and Blog)

Ikiwiki icon

Avaiable since: version 0.5

8.1. What is Ikiwiki?

Ikiwiki converts wiki pages into HTML pages suitable for publishing on a website. It provides particularly blogging, podcasting, calendars and a large selection of plugins.

8.2. Creating a wiki or blog

You can create a wiki or blog to be hosted on your FreedomBox through the Wiki & Blog (Ikiwiki) page in FreedomBox. The first time you visit this page, it will ask to install packages required by Ikiwiki.

After the package install has completed, select the "Create Wiki or Blog" button. ikiwiki: Manage

You can select the type to be Wiki or Blog. Also type in a name for the wiki or blog, and the username and password for the wiki's/blog's admin account. Then click Update setup and you will see the wiki/blog added to your list. Note that each wiki/blog has its own admin account. ikiwiki: Manage

8.3. Accessing your wiki or blog

Your wikis and blogs are listed in the Ikiwiki app. Clicking on your site's name will bring you to its start page.

ikiwiki: Manage

From here, if you click Edit or Preferences, you will be taken to a login page. To log in with the admin account that you created before, select the Other tab, enter the username and password, and click Login.

8.4. User login through SSO

Besides the wiki/blog admin, other FreedomBox users can be given access to login and edit wikis and blogs. However, they will not have all the same permissions as the wiki admin. They can add or edit pages, but cannot change the wiki's configuration.

To add a wiki user, go to the Users and Groups page in FreedomBox (under System configuration, the gear icon at the top right corner of the page). Create or modify a user, and add them to the wiki group. (Users in the admin group will also have wiki access.)

To login as a FreedomBox user, go to the wiki/blog's login page and select the Other tab. Then click the "Login with HTTP auth" button. The browser will show a popup dialog where you can enter the username and password of the FreedomBox user.

8.5. Adding FreedomBox users as wiki admins

  1. Login to the site, using the admin account that was specified when the site was created.
  2. Click "Preferences", then "Setup".
  3. Under "main", in the "users who are wiki admins", add the name of a user on the FreedomBox.

  4. (Optional) Under "auth plugin: passwordauth", uncheck the "enable passwordauth?" option. (Note: This will disable the old admin account login. Only SSO login using HTTP auth will be possible.)
  5. At the bottom of the page click "Save Setup".
  6. Click "Preferences", then "Logout".
  7. Login as the new admin user using "Login with HTTP auth".

8.6. Avoiding Spam

By default, every wiki page also has a "Discussion" page, which can be edited anonymously, without logging in. To avoid spam, you may want to disable the Discussion feature all together, by unchecking the "enable Discussion pages?" option in the setup.

8.7. Theming

  1. Login to the site, using the admin account that was specified when the site was created.
  2. Click "Preferences", then "Setup".
  3. Under "web plugin: theme", check "enable theme?"
  4. Right under the checkbox, type in the name of the desired theme. You can choose from the following officially supported themes:
    • actiontabs - mobile friendly
    • blueview - non-mobile friendly
    • goldtype - non-mobile friendly
    • monochrome - mobile friendly
  5. At the bottom of the page click "Save Setup".

For your changes to become visible, you might have to delete your browser's cache or wait a few minutes and refresh your ikiwiki's page.

It is also possible to install user-contributed themes from ikiwiki's Theme Market. Please note, that this requires additional technical knowledge.

9. Infinoted (Collaborative text edition with Gobby)

Infinoted icon

Available since: version 0.5

infinoted is a server for Gobby, a collaborative text editor.

To use it, download Gobby, desktop client and install it. Then start Gobby and select "Connect to Server" and enter your FreedomBox's domain name.

9.1. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for infinoted:

  • TCP 6523

10. JSXC (Web Chat Client)

JSXC icon

Available since: version 0.11.0

JSXC is a web chat client. It can be used to join compatible chat servers.

FreedomBox offers both parties, a server (ejabberd) and a web client (JSXC), from its web interface.

10.1. Technical Specifications

JSXC features the XMPP over BOSH protocol and is implemented in HTML5.

XMPP is a federated server-client protocol for Instant Messaging. This means that users who have accounts on one server, can talk to users that are on another server.

XMPP can also be used for voice and video calls, if supported by the clients.

10.2. Installation

You can install JSXC through its icon in the Apps section of FreedomBox web interface. The ejabberd (XMPP server) icon also offers to launch the web client (and installs JSXC if not yet installed).

10.3. Usage

After the JSXC module install completes, the JSXC can be accessed through its icon in the Apps section of FreedomBox web interface. The ejabberd (XMPP server) icon also offers to launch the web client. Both will redirect you to https://<your freedombox>/plinth/apps/xmpp/jsxc/.

To use it, you need to input the domain name of the server to connect to. It will automatically check the BOSH server connection to the given domain name as you type it.

JSXC not connecting

JSXC connecting

Videoconferencing and file transfer features are offered by JSXC but don't seem to work in FreedomBox yet.

10.4. Port Forwarding

If your FreedomBox is behind a router and you want to connect to other servers, you will need to set up port forwarding on your router. You should forward the following ports for XMPP:

  • TCP 5222 (client-to-server)

11. Matrix Synapse (Chat Server)

Matrix Synapse icon

Available since: version 0.14.0

11.1. What is Matrix?

Matrix is an open protocol for interoperable, decentralized, real-time communication over IP. Synapse is the reference implementation of a Matrix server. It can be used to setup instant messaging on FreedomBox to host chat rooms with end-to-end encrypted communication and audio/video calls. Matrix Synapse is a federated application where chat rooms can exist on any server and users from any server in the federated network can join them. Learn more about Matrix.

11.2. How to access your Matrix Synapse server?

We recommend the Element client to access the Matrix Synapse server. You can download Element for desktops. Mobile applications for Android and iOS are available from their respective app stores.

11.3. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Matrix:

  • TCP 8448

11.4. Setting up Matrix Synapse on your FreedomBox

To enable Matrix Synapse, first navigate to the Chat Server (Matrix Synapse) page and install it. Matrix needs a valid domain name to be configured. After installation, you will be asked to configure it. You will be able to select a domain from a drop down menu of available domains. Domains are configured using System -> Configure page. After configuring a domain, you will see that the service is running. The service will be accessible on the configured FreedomBox domain. Currently, you will not be able to change the domain once is it configured.

Your router has to be configured to forward port 8448.

All the registered users of your FreedomBox will have their Matrix IDs as @username:domain. If public registration is enabled, also your chosen client can be used to register a user account.

11.5. Setting up Audio/Video calls

The Matrix Synapse server is only responsible for establishing calls between participants in rooms. Matrix clients such as Element are actually responsible for the transfer of the audio/video traffic. Element supports calling in both one-to-one conversations and in groups.

For one-to-one conversations, Element tries to make a peer-to-peer connection between the two participants. This works when both the participants are using Element on computers with a public IP address or if they're on the same network. If both the participants are behind different NAT devices, establishing a direct peer-to-peer connection between them will not be possible. This problem can be solved by configuring Matrix Synapse with a STUN/TURN server. FreedomBox provides an app called Coturn for this purpose. FreedomBox doesn't automatically install Coturn on installing Matrix Synapse. However, as soon as Coturn app is installed, FreedomBox automatically configures Matrix Synapse to use it for audio/video calls. It is possible to override this configuration with a different STUN/TURN server in the web interface.

For calling groups with more than two participants (i.e. not one-on-one conversations), Element uses an external Jitsi Meet instance. Element uses jitsi.riot.im as its default Jitsi Meet instance. If the Matrix Synapse server is configured to use a different Jitsi Meet instance as the default, Element will use it instead for all users on that server.

11.6. Federating with other Matrix instances

You will be able to interact with any other person running another Matrix instance. This is done by simply starting a conversation with them using their matrix ID which is of the format @their-username:their-domain. You can also join rooms which are in another server and have audio/video calls with contacts on other server.

11.7. Memory usage

The Synapse reference server implemented in Python is known to be quite RAM hungry, especially when loading large rooms with thousands of members like #matrix:matrix.org. It is recommended to avoid joining such rooms if your FreedomBox device only has 1 GiB RAM or less. Rooms with up to a hundred members should be safe to join. The Matrix team is working on a new implementation of the Matrix server written in Go called Dendrite which might perform better in low-memory environments.

Some large public rooms in the Matrix network are also available as IRC channels (e.g. #freedombox:matrix.org is also available as #freedombox on irc.debian.org). It is better to use IRC instead of Matrix for such large rooms. You can join the IRC channels using Quassel.

11.8. Advanced usage

  1. If you wish to create a large number of users on your Matrix Synapse server, use the following commands on a remote shell as root user:
    • cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1 | sed "s+^+registration_shared_secret: +" > /etc/matrix-synapse/conf.d/registration_shared_secret.yaml
      chmod 600 /etc/matrix-synapse/conf.d/registration_shared_secret.yaml
      chown matrix-synapse:nogroup /etc/matrix-synapse/conf.d/registration_shared_secret.yaml
      systemctl restart matrix-synapse
      register_new_matrix_user -c /etc/matrix-synapse/conf.d/registration_shared_secret.yaml
  2. If you wish to see the list of users registered in Matrix Synapse, the following as root user:
    • apt install sqlite3
      echo 'select name from users' | sqlite3 /var/lib/matrix-synapse/homeserver.db  
  3. If you wish to create a community in Matrix Synapse, a Matrix user with server admin privileges is needed. In order to grant such privileges to username run the following commands as root user:

    • sudo apt install sqlite3
      echo "UPDATE users SET admin=1 WHERE name='@username:domainname'" | sudo sqlite3 /var/lib/matrix-synapse/homeserver.db  

12. MediaWiki (Wiki)

MediaWiki icon

Available since: version 0.20.0

12.1. About MediaWiki

MediaWiki is the software that powers the Wikimedia suite of wikis.

Read more about MediaWiki on Wikipedia

12.2. MediaWiki on FreedomBox

MediaWiki on FreedomBox is configured to be publicly readable and privately editable. Only logged in users can make edits to the wiki. This configuration prevents spam and vandalism on the wiki.

12.2.1. User management

Users can be created by the MediaWiki administrator (user "admin") only. The "admin" user can also be used to reset passwords of MediaWiki users. The administrator password, if forgotten can be reset anytime from the MediaWiki app page in web interface.

12.2.2. Use cases

MediaWiki is quite versatile and can be put to many creative uses. It also comes with a lot of plugins and themes and is highly customizable.

12.2.2.1. Personal Knowledge Repository
  • MediaWiki on FreedomBox can be your own personal knowledge repository. Since MediaWiki has good multimedia support, you can write notes, store images, create checklists, store references and bookmarks etc. in an organized manner. You can store the knowledge of a lifetime in your MediaWiki instance.

12.2.2.2. Community Wiki
  • A community of users can use MediaWiki as their common repository of knowledge and reference material. It can used as a college notice board, documentation server for a small company, common notebook for study groups or as a fan wiki like wikia.

12.2.2.3. Personal Wiki-based Website
  • Several websites on the internet are simply MediaWiki instances. MediaWiki on FreedomBox is read-only to visitors. Hence, it can be adapted to serve as your personal website and/or blog. MediaWiki content is easy to export and can be later moved to use another blog engine.

12.2.3. Editing Wiki Content

The MediaWiki installation on FreedomBox ships with two kinds of editors - WikiText editor and !Visual editor.

12.2.3.1. WikiText Editor
  • This editor is for editing the wiki directly in MediaWiki's markup language. It has a toolbar for common options like Bold, Italics etc. Click on the Advanced section for more options like Headings, bullet lists etc.

mediawiki-toolbar.png

12.2.3.2. Visual Editor
  • MediaWiki's VisualEditor extension provides a WYSIWYG interface to editing wiki pages. This extension is bundled with MediaWiki from 1.35 and is enabled by default from FreedomBox 21.9.

    Since this is essentially a rich-text editor, knowledge of MediaWiki's markup language is not required. To use advanced features not available in the VisualEditor (yet), switch back to source editing.

VisualEditor.png

12.2.3.3. Other Formats
  • You don't have to necessarily learn the MediaWiki formatting language. You can write in your favorite format (Markdown, Org-mode, LaTeX etc.) and convert it to the MediaWiki format using Pandoc.

12.2.3.4. Image Uploads
  • Image uploads have been enabled since FreedomBox version 0.36.0. You can also directly use images from Wikimedia Commons using a feature called Instant Commons.

12.2.4. Customization

12.2.4.1. Skins

MediaWiki's default skin is usually Vector. The default skin set by FreedomBox is Timeless.

Vector is a skin best-suited for viewing on desktop browsers. It is not suitable for mobile screen sizes. Wikimedia sites host a separate mobile site. It is not worth hosting a separate mobile site for small MediaWiki installations like those on FreedomBox. Using a mobile-friendly skin like Timeless is a cheaper way of solving the problem.

Administrators can choose a default skin from the app configuration. Users of the site also have the choice of viewing it with a different skin.

13. Minetest (Block Sandbox)

Minetest icon

Available since: version 0.9

Minetest is a multiplayer infinite-world block sandbox. This module enables the Minetest server to be run on this FreedomBox, on the default port (30000). To connect to the server, a Minetest client is needed.

13.1. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Minetest:

  • UDP 30000

13.2. Install and enable mods

After SSHing into your FreedomBox server, install (unzip or git clone) mods in /var/games/minetest-server/.minetest/mods (for example, for the mobs_animal mod, you'd have the new /var/games/minetest-server/.minetest/mods/mobs_animal/ directory).

To enable a mod, first restart minetest:

sudo systemctl restart minetest-server.service

This will update the world config file, located in /var/games/minetest-server/.minetest/worlds/world/world.mt, with a line related to the added mod. Set that line from false to true in order to enable the new mod in your minetest instance. For example:

load_mod_mobs_animal = true

After that, save your changes, restart minetest one more time, then you should be all set.

14. MiniDLNA (Simple Media Server)

MiniDLNA icon

Available since: version 19.23

MiniDLNA is a media server with the aim to be compliant with DLNA/UPnP clients.

Note: This service is available only on networks configured as "internal" zone. It is not available when connected via OpenVPN.

14.1. What is UPnP/DLNA?

Universal plug & play is a set of networking protocols that allow devices within a network such as PCs, TVs, printers etc. to seamlessly discover each other and establish communication for data sharing. It is zero configuration protocol and requires only a media server and a media player that are compliant with the protocol.

DLNA is derived from UPnP as a form of standardizing media interoperability. It forms a standard/certification which many consumer electronics conform to.

14.2. Setting up MiniDLNA on your FreedomBox

To install/enable the media server you need to navigate at MiniDLNA page and enable it. The application is intended to be available in the internal (home) network and therefore it requires a network interface configured for internal traffic.

After installation a web page becomes available on https://<your-freedombox>/_minidlna. It includes information for how many files the server is detecting, how many connections exist etc. This is very useful if plugging external disks with media to check if the new media files are detected properly. If that is not happening, disabling and enabling the server will fix it.

14.3. Using MiniDLNA to play media on your devices

Any DLNA compliant device or media player should be able to automatically detect, browse and play media from MiniDLNA on FreedomBox. The following devices and media players have been tested:

  • GNOME Videos: Videos is the default media player on the popular GNU/Linux desktop environment GNOME. Open Videos, switch to 'Channels'. You should see a channel named 'freedombox: minidlna'. You will be able to browse and play media from it.

  • VLC media player: VLC is a very popular media player for GNU/Linux, Android, Windows and macOS. Open VLC and click on 'View -> Playlist'. In the playlist sidebar that appears, select 'Universal Plug'n'Play'. You should see an item named 'freedombox: minidlna'. You should be able to browse and play media from it.

  • Kodi: Kodi is a popular media centre software with user interface designed for Televisions. Open Kodi, goto 'System -> Service settings -> UPnP/DLNA' and 'Enable UPnP support'. Then visit 'Home -> Videos -> Files -> Add videos... -> Browse -> UPnP devices'. You should see 'freedombox: minidlna'. Select it and choose 'OK'. Then choose 'OK in the 'Add video source' dialog. From now on, you should see 'freedombox: minidlna' in 'Videos -> Files' section. You should be able to browse and play media from it. See Kodi documentation for more information.

  • Roku: Roku is an appliance connected to a TV for playing Internet streaming services. Many TVs also have Roku built into them. In Roku interface, find a channel called 'Roku Media Player' and open it. You should see an item called 'freedombox: minidlna'. You should be able to browse and play media from it.

  • Rhythmbox: Rhythmbox is the default audio player on the popular GNU/Linux desktop environment GNOME. Open Rhythmbox and ensure that the side pane is open by clicking on 'Application menu -> View -> Side Pane'. In the side pane you should see 'freedombox:minidlna' under the 'Shared' section. You should be able to browse and play audio files from it. Video files will not show up.

14.4. Supported media formats

MiniDLNA supports a wide variety of video and audio file formats.

  • Video: Files ending with .avi, .mp4, .mkv, .mpg, .mpeg, .wmv, .m4v, .flv, .mov, .3gp, etc.

  • Audio: Files ending with .mp3, .ogg, .flac, .wav, .pcm, .wma, .fla, .aac, etc.

  • Image: Files ending with .jpg, .jpeg

  • Playlist: Files ending with .m3u, .pls

  • Captions: Files ending with .srt, .smi

Notably, it does not support the following file extensions. Renaming the file to a known extension seems to work in most cases.

  • Video: Files ending with .webm

In addition to file format support from MiniDLNA, your media player or device needs to support the audio/video codecs with which the media has been encoded. MiniDLNA does not have the ability to translate files into a codec understood by the player. If you face problems with media playback, use the VLC player to find the codecs used in the media and the check your device or media player documentation on whether the codecs are supported.

14.5. File systems for external drives

If using an external drive that is used also from a Windows system the preferred filesystem should be NTFS. NTFS will keep Linux file permissions and UTF8 encoding for file names. This is useful if file names are in your language.

15. Mumble (Voice Chat) Server

Mumble icon

Available since: version 0.5

15.1. What is Mumble?

Mumble is a voice chat software. Primarily intended for use while gaming, it is suitable for simple talking with high audio quality, noise suppression, encrypted communication, public/private-key authentication by default, and "wizards" to configure your microphone for instance. A user can be marked as a "priority speaker" within a channel.

15.2. Using Mumble

FreedomBox includes the Mumble server. Clients are available for desktop and mobile platforms. Users can download one of these clients and connect to the server.

15.3. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Mumble:

  • TCP 64738
  • UDP 64738

15.4. Managing Permissions

A super user in Mumble has the ability to create administrator accounts who can in turn manage groups and channel permissions. This can be done after logging in with the username "SuperUser" using the super user password. See Mumble Guide for information on how to do this. The SuperUser password can be set through the FreedomBox interface.

16. OpenVPN (Virtual Private Network)

OpenVPN icon

Available since: version 0.7

16.1. What is OpenVPN?

OpenVPN provides to your FreedomBox a virtual private network service. You can use this software for remote access, site-to-site VPNs and Wi-Fi security. OpenVPN includes support for dynamic IP addresses and NAT.

16.2. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for OpenVPN:

  • UDP 1194

16.3. Setting up

  1. In FreedomBox apps menu, select Virtual Private Network (OpenVPN) and click Install.

  2. After the module is installed, there is an additional setup step that may take a long time to complete. Click "Start setup" to begin.

    OpenVPN service page

  3. Wait for the setup to finish. This could take a while.
  4. Once the setup of the OpenVPN server is complete, you can download your profile. This will download a file called <USER>.ovpn, where <USER> is the name of a FreedomBox user. Each FreedomBox user will be able to download a different profile. Users who are not administrators can download the profile from home page after login.

  5. The ovpn file contains all the information a vpn client needs to connect to the server.
  6. The downloaded profile contains the domain name of the FreedomBox that the client should connect to. This is picked up from the domain configured in 'Config' section of 'System' page. In case your domain is not configured properly, you may need to change this value after downloading the profile. If your OpenVPN client allows it, you can do this after importing the OpenVPN profile. Otherwise, you can edit the .ovpn profile file in a text editor and change the 'remote' line to contain the WAN IP address or hostname of your FreedomBox as follows.

    client
    remote mybox.freedombox.rocks 1194
    proto udp

16.4. Troubleshooting

If your network doesn't support IPv6, you might have to remove the following line from your OpenVPN client configuration. This is especially in cases where your server supports IPv6 but client does not thus confusing the OpenVPN client on which protocol to use.

proto udp6

To connect via IPv4, ensure that the following line is present.

proto udp

16.5. Browsing Internet after connecting to VPN

After connecting to the VPN, the client device will be able to browse the Internet without any further configuration. However, a pre-condition for this to work is that you need to have at least one Internet connected network interface which is part of the 'External' firewall zone. Use the networks configuration page to edit the firewall zone for the device's network interfaces.

16.6. Usage

16.6.1. On Android/LineageOS

  1. Visit FreedomBox home page. Login with your user account. From home page, download the OpenVPN profile. The file will be named username.ovpn.

    • OpenVPN Download Profile

  2. Download an OpenVPN client such as OpenVPN for Android. F-Droid repository is recommended. In the app, select import profile.

    • OpenVPN App

  3. In the select profile dialog, choose the username.opvn file you have just downloaded. Provide a name for the connection and save the profile.

    • OpenVPN import profile

  4. Newly created profile will show up. If necessary, edit the profile and set the domain name of your FreedomBox as the server address.

    • OpenVPN profile created

      OpenVPN edit domain name

  5. Connect by tapping on the profile.
    • OpenVPN connect

      OpenVPN connected

  6. When done, disconnect by tapping on the profile.
    • OpenVPN disconnect

16.6.2. On Debian

Install an OpenVPN client for your system

$ sudo apt install openvpn

Open the ovpn file with the OpenVPN client.

$ sudo openvpn --config /path/to/<USER>.ovpn

If you use Network Manager, you can create a new connection by importing the file:

$ sudo apt install network-manager-openvpn-gnome
$ sudo nmcli connection import type openvpn file /path/to/<USER>.ovpn

If you get an error such as configuration error: invalid 1th argument to “proto” (line 5) then edit the .ovpn file and remove the line proto udp6.

16.7. Checking if you are connected

16.7.1. On Debian

  1. Try to ping the FreedomBox or other devices on the local network.

  2. Running the command ip addr should show a tun0 connection.

  3. The command traceroute freedombox.org should show you the ip address of the VPN server as the first hop.

16.8. Accessing internal services

After connecting to OpenVPN, you will be able to access FreedomBox services that are only meant to be accessed on internal networks. This is in addition to being able to access external services. This can be done by using the IP address 10.91.0.1 as the host name for these services (for example, use smb://10.91.0.1 instead of smb://freedombox.local to access Samba shares).

The following services are known to work:

Some services are known not to work at this time:

17. Privoxy (Web Proxy)

Privoxy icon

Available since: version 0.1

A web proxy acts as a filter for incoming and outgoing web traffic. Thus, you can instruct any computer in your network to pass internet traffic through the proxy to remove unwanted ads and tracking mechanisms.

Privoxy is a software for security, privacy, and accurate control over the web. It provides a much more powerful web proxy (and anonymity on the web) than what your browser can offer. Privoxy "is a proxy that is primarily focused on privacy enhancement, ad and junk elimination and freeing the user from restrictions placed on his activities" (source: Privoxy FAQ).

17.1. Screencast

Watch the screencast on how to setup and use Privoxy in FreedomBox.

17.2. Setting up

  1. In FreedomBox, install Web Proxy (Privoxy)

    Privoxy Installation

  2. Adapt your browser proxy settings to your FreedomBox hostname (or IP address) with port 8118. Please note that Privoxy can only proxy HTTP and HTTPS traffic. It will not work with FTP or other protocols.

    Privoxy Browser Settings

  3. Go to page http://config.privoxy.org/ or http://p.p. If Privoxy is installed properly, you will be able to configure it in detail; if not you will see an error message.

  4. If you are using a laptop that occasionally has to connect through other routers than yours with the FreedomBox and Privoxy, you may want to install a proxy switch add-on that allows you to easily turn the proxy on or off.

17.3. Advanced Users

The default installation should provide a reasonable starting point for most. There will undoubtedly be occasions where you will want to adjust the configuration, that can be dealt with as the need arises.

  1. Plan first:
    • While using Privoxy, you can see its configuration details and documentation at http://config.privoxy.org/ or http://p.p.

    • The Quickstart is a good starting point to read on how to define own blocking and filtering rules.

    • Read carefully the manual, especially this security warning:

      • Access to the editor can not be controlled separately by "ACLs" or HTTP authentication, so that everybody who can access Privoxy can modify its configuration for all users. This option is not recommended for environments with untrusted users. Note that malicious client side code (e.g Java) is also capable of using the actions editor and you shouldn't enable this options unless you understand the consequences and are sure your browser is configured correctly.

  2. Only when you are ready, perform the changes:
    1. To enable changing these configurations, you first have to change the value of enable-edit-actions in /etc/privoxy/config to 1.

    2. Now you find an EDIT button on the configuration screen in http://config.privoxy.org/.

18. Quassel (Text Chat Client via IRC)

Quassel icon

Available since: version 0.8

Quassel is an IRC application that is split into two parts, a "core" and a "client". This allows the core to remain connected to IRC servers, and to continue receiving messages, even when the client is disconnected. FreedomBox can run the Quassel core service keeping you always online and one or more Quassel clients from a desktop or a mobile device can be used to connect and disconnect from it.

18.1. Why run Quassel?

Many discussions about FreedomBox are being done on the IRC-Channel irc://irc.debian.org/freedombox. If your FreedomBox is running Quassel, it will collect all discussions while you are away, such as responses to your questions. Remember, the FreedomBox project is a worldwide project with people from nearly every time zone. You use your client to connect to the Quassel core to read and respond whenever you have time and are available.

18.2. How to setup Quassel?

  • Within FreedomBox's web interface

    1. select Applications

    2. go to IRC Client (Quassel) and

    3. install the application and make sure it is enabled

      Quassel Installation

    4. now your Quassel core is running

18.3. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Quassel:

  • TCP 4242
  • Example configuration in router:
    • Quassel_PortForwarding_en_v01.png

18.4. Clients

Clients to connect to Quassel from your desktop and mobile devices are available.

18.4.1. Desktop

In a Debian system, you can e.g. use quassel-client. The following steps describe how to connect Quassel Client with Quassel Core running on a FreedomBox. The first time you do this connection, Quassel Core will be initialized too.

  1. Launch Quassel Client. You will be greeted with a wizard to Connect to Core.

    • Connect to Core

  2. Click the Add button to launch Add Core Account dialog.

    • Add Core Account

  3. Fill any value in the Account Name field. Fill proper DNS hostname of your FreedomBox in Hostname filed. Port field must have the value 4242. Provide the username and password of the account you wish to create to connect to the Quassel Core in the User and Password fields. Choose Remember if don't wish to be prompted for a password every time you launch Quassel client.

  4. After pressing OK in the Add Core Account dialog, you should see the core account in the Connect to Core dialog.

    • Connect to Core

  5. Select the newly created core account and select OK to connect to it.

  6. If this is the first time you are connecting to this core. You will see an Untrusted Security Certificate warning and need to accept the server certificate.

    • Untrusted Security Certificate

  7. Select Continue. Then you will be asked if you wish to accept the certificate permanently. Select Forever.

    • Untrusted Security Certificate

  8. If this Quassel Core has not been connected to before, you will then see a Core Configuration Wizard. Select Next.

    • Core Configuration Wizard

  9. In the Create Admin User page, enter the username and password you have used earlier to create the core connection. Select Remember password to remember this password for future sessions. Click Next.

    • Create Admin User Page

  10. In the Select Storage Backend page, select SQLite and click Commit.

    • Select Storage Backend

  11. The core configuration is then complete and you will see a Quassel IRC wizard to configure your IRC connections. Click Next.

    • Welcome Wizard

  12. In Setup Identity page next, provide a name and multiple nicknames. This is how you present yourself to other users on IRC. It is not necessary to give your real world name. Multiple nicknames are useful as fallback nicknames when the first nickname can't be used for some reason. After providing the information click Next.

    • Setup Identity

  13. In Setup Network Connection page next, provide a network name of your choice. Next provide a list of servers to which Quassel Core should connect to in order to join this IRC network (such as irc.debian.org:6667).

    • Setup Network Connection

  14. Select the server in the servers list and click Edit. In the Server Info dialog, set the port 6697 (consult your network's documentation for actual list of servers and their secure ports) and click Use SSL. Click OK. This is to ensure that communication between your FreedomBox and the IRC network server is encrypted.

    • Server Info Server Info SSL

  15. Back in the Setup Network Connection dialog, provide a list of IRC channels (such as #freedombox) to join upon connecting to the network. Click Save & Connect.

    • Setup Network Connection

  16. You should connect to the network and see the list of channels you have joined on the All Chats pane on the left of the Quassel Client main window.

    • Quassel Main Window

  17. Select a channel and start seeing messages from others in the channel and send your own messages.

18.4.2. Android

For Android devices you may use e.g. Quasseldroid from F-Droid

  • enter core, username etc. as above
    • Quasseldroid.png

By the way, the German verb quasseln means talking a lot, to jabber.

19. Radicale (Calendar and Addressbook)

Radicale icon

Available since: version 0.9

With Radicale, you can synchronize your personal calendars, ToDo lists, and addressbooks with your various computers, tablets, and smartphones, and share them with friends, without letting third parties know your personal schedule or contacts.

19.1. Why should I run Radicale?

Using Radicale, you can get rid of centralized services like Google Calendar or Apple Calendar (iCloud) data mining your events and social connections.

19.2. How to setup Radicale?

First, the Radicale server needs to be activated on your box.

  • Within FreedomBox Service:

    1. select Apps

    2. go to Radicale (Calendar and Addressbook) and

    3. install the application. After the installation is complete, make sure the application is marked "enabled" in the FreedomBox interface. Enabling the application launches the Radicale CalDAV/CardDAV server.

    4. define the access rights:
      • Only the owner of a calendar/addressbook can view or make changes
      • Any user can view any calendar/addressbook, but only the owner can make changes
      • Any user can view or make changes to any calendar/addressbook

Note, that only users with a FreedomBox login can access Radicale.

Radicale-Plinth.png

If you want to share a calendar with only some users, the simplest approach is to create an additional user-name for these users and to share that user-name and password with them.

Radicale provides a basic web interface, which only supports creating new calendars and addressbooks. To add events or contacts, an external supported client application is needed.

radicale_web.png

  • Creating addressbook/calendar using the web interface
    • Visit https://IP-address-or-domain-for-your-server/radicale/

    • Log in with your FreedomBox account

    • Select "Create new addressbook or calendar"
    • Provide a title and select the type
    • Optionally, provide a description or select a color
    • Click "Create"
    • The page will show the URL for your newly created addressbook or calendar

Now open your client application to create new calendar and address books that will use your FreedomBox and Radicale server. The Radicale website provides an overview of supported clients, but do not use the URLs described there; FreedomBox uses another setup, follow this manual. Below are the steps for two examples:

  • Example of setup with Evolution client:
    • Calendar
      1. Create a new calendar
      2. For "Type," select "CalDAV"
      3. When "CalDAV" is selected, additional options will appear in the dialogue window.
      4. URL: https://IP-address-or-domain-for-your-server. Items in italics need to be changed to match your settings.

      5. Enable "Use a secure connection."
      6. User: USERNAME. Your Freedombox user-name.

      7. Click on "Find Calendars"
      8. Enter your password and select a calendar

        Evolution-new-calendar.png

    • TODO/Tasks list: Adding a TODO/Tasks list is basically the same as a calendar.
    • Contacts
      • Follow the same steps described above and replace CalDAV with WebDAV.

19.3. Synchronizing over Tor

In FreedomBox, setting up a calendar with Radicale over Tor is the same as over the clear net. Here is a short summary:

  1. When logged in to FreedomBox interface over Tor, click on Radicale, and at the prompt provide your FreedomBox user name and password.

  2. In the Radicale web interface, log in using your FreedomBox user name and password.

  3. Click on "Create new address book or calendar", provide a title, select a type, and click "Create".
  4. Save the URL, e.g., https://ONION-ADDRESS-FOR-YOUR-SERVER.onion/radicale/USERNAME/CALENDAR-CODE/. Items in italics need to be changed to match your settings.

These instructions are for Thunderbird/Lightning. Note that you will need to be connected to Tor with the Tor Browser Bundle.

  1. Open Thunderbird, install the Torbirdy add-on, and restart Thunderbird. (This may not be necessary.)
  2. In the Lightning interface, under Calendar/Home in the left panel right click with the mouse and select "New calendar".
  3. Select the location of your calendar as "On the Network".
  4. Select CalDAV and for the location copy the URL, e.g., https://ONION-ADDRESS-FOR-YOUR-SERVER.onion/radicale/USERNAME/CALENDAR-CODE/. Items in italics need to be changed to match your settings.

  5. Provide a name, etc. Click "Next". Your calendar is now syncing with your FreedomBox over Tor.

  6. If you have not generated a certificate for your FreedomBox with "Let's Encrypt", you may need to select "Confirm Security Exception" when prompted.

19.4. Synchronizing with your Android phone

There are various Apps that allow integration with the Radicale server. This example uses DAVx5, which is available e.g. on F-Droid. If you intend to use ToDo-Lists as well, the compatible app OpenTasks has to be installed first.

Follow these steps for setting up your account with the Radicale server running on your FreedomBox.

  1. Install DAVx5
  2. Create a new account on DAVx5 by clicking on the floating + button.
  3. Select the second option as shown in the first figure below and enter the base url as https://<your.freedombox.address>/radicale/username/ (don't miss the / at the end). DAVx5 will be able to discover both CalDAV and WebDAV accounts for the user.

  4. Follow this video from DAVx5 FAQ to learn how to migrate your existing contacts to Radicale.

Synchronizing contacts

  1. Click on the hamburger menus of CalDAV and CardDAV and select either "Refresh ..." in case of existing accounts or "Create ..." in case of new accounts (see the second screenshot below).
  2. Check the checkboxes for the address books and calendars you want to synchronize and click on the sync button in the header. (see the third screenshot below)

DAVx5 account setup DAVx5 refresh DAVx5 account sync

19.5. Advanced Users

19.5.1. Sharing resources

Above was shown an easy way to create a resource for a group of people by creating a dedicated account for all. Here will be described an alternative method where two users User1 and User2 are granted access to a calendar. This requires SSH-access to the FreedomBox.

  1. create a file /etc/radicale/rights

    • [friends_calendar]
      user: ^(User1|User2)$
      collection: ^.*/calendar_of_my_friends.ics$
      permission: rw
      
      # Give write access to owners
      [owner-write]
      user: .+
      collection: ^%(login)s/.+$
      permission: rw
    • [friends_calendar] is just an identifier, can be any name.

    • The [owner-write] section makes sure that owners have access to their own files

  2. edit file /etc/radicale/config and make the following changes in section [rights]

    • [rights]
      type = from_file
      file = /etc/radicale/rights
  3. Restart the radicale server or the FreedomBox

19.5.2. Importing files

If you are using a contacts file exported from another service or application, it should be copied to: /var/lib/radicale/collections/user/contact file name.vcf.

20. Roundcube (Email Client)

Roundcube icon

Available since: version 0.5

20.1. What is Roundcube?

Roundcube is a browser-based multilingual email client with an application-like user interface. Roundcube is using the Internet Message Access Protocol (IMAP) to access e-mail on a remote mail server. It supports MIME to send files, and provides particularly address book, folder management, message searching, and spell checking.

Roundcube app can be used to read and send emails in one of the two ways: using an email account you have elsewhere (other than FreedomBox), like in Riseup or in Gmail, or an account on FreedomBox. The latter is possible if an email server app, such as Postfix/Dovecot/Rspamd, is setup and enabled on FreedomBox. At present, Roundcube can only be setup for one of these two ways. This is controlled by the Use only the local mail server option in Roundcube app configuration page.

20.2. Email privacy

In the first case, you only get privacy over your drafts. Once you send the email, a copy will reside in the external services (Riseup, Gmail, etc) unless you explicitly remove it. In any case, your traffic transits through them.

In the second (self-hosted) case, your mail copies reside on your FreedomBox server. But you only keep privacy as long as the recipient also uses a private system and doesn't disclose your content.

20.3. Using Roundcube

After Roundcube is installed, it can be accessed at https://<your freedombox>/roundcube. Enter your username and password. The username for many mail services will be the full email address such as exampleuser@example.org and not just the username like exampleuser. Enter the address of your email service's IMAP server address in the Server field. You can try providing your domain name here, such as example.org for email address exampleuser@example.org and if this does not work, consult your email provider's documentation for the address of the IMAP server. Using encrypted connection to your IMAP server is strongly recommended. To do this, prepend 'imaps://' at the beginning of your IMAP server address. For example, imaps://imap.example.org.

Logging into your IMAP server

20.4. Using Gmail with Roundcube

If you wish to use Roundcube with your Gmail account, you need to first enable support for password based login in your Google account preferences. This is because Gmail won't allow applications to login with a password by default. To do this, visit Google Account preferences and enable Less Secure Apps. After this, login to Roundcube by providing your Gmail address as Username, your password and in the server field use imaps://imap.gmail.com.

Logging into Gmail

21. Samba (Network File Storage)

Samba icon

Available since: version 19.22

Samba lets you have shared folders over the local network that can be used from multiple computers running different operating systems. We refer to these shared folders as "shares".

You can have a personal folder shared between your own devices (Home share), a folder shared with a trusted group (Group share) or one that is shared with every device on the network (Open share).

Samba lets you to treat a share as if it's a local folder on your computer. However, shares are available only on the local network.

To learn more about Samba, please refer to the user documentation on their wiki.

21.1. Using Samba

After installation, you can choose which disks to use for sharing. Enabled shares are accessible in the file manager on your computer at location \\freedombox (on Windows) or smb://freedombox.local (on Linux and Mac). There are three types of shares you can choose from:

Open share - accessible to everyone in your local network.
Group share - accessible only to FreedomBox users who are in the freedombox-share group.
Home share - every user in the freedombox-share group can have their own private space.

21.1.1. Connecting from an Android device

To access Samba shares on an Android device, install "Android Samba Client" from F-Droid or Google Play. Enter smb://freedombox.local/<disk> as the share path in the app. Your shared folders should then be visible in the file manager app. Samba shares can also be used by VLC for Android which automatically discovers them.

21.1.2. Connecting from a macOS device

  • Open a Finder window on your Mac.
  • Use Go -> Connect to Server... from the file menu or press the shortcut Cmd+K to open the Connect To Server dialog.

  • Enter the address of your Samba share, e.g. smb://192.168.0.105/disk and click Connect.

21.2. Integration with other apps

Transmission app on FreedomBox provides a setting to allow downloads to be saved directly to a Samba share.

If you want to make available files synchronized with Syncthing through Samba you need to make sure you synchronize in a Samba share folder. Additionally in order to make Syncthing shares available in Samba Open share or Group share you will need to ensure you click "Permissions > Ignore" button under the "Advanced" tab in folder you wish in the Syncthing web UI. This will ensure that the files will be writable through Samba.

21.3. Comparison with other apps

21.3.1. Syncthing

Syncthing maintains a copy of the shared folder on each device that it is shared with. Samba maintains only one copy on your FreedomBox device.

Syncthing can synchronize your shared folders between devices over the Internet. Samba shares are only available on the local network.

Since Syncthing is primarily a synchronization solution, it has features like conflict resolution and versioning. Samba has only copy of the file, so it doesn't need such features. For example, if two people are editing a spreadsheet stored on a Samba share, the last one to save the file wins.

22. Searx (Web Search)

Searx icon

Available since: version 0.24.0

22.1. About Searx

Searx is a metasearch engine. A metasearch engine aggregates the results from various search engines and presents them in a unified interface.

Read more about Searx on their official website.

22.2. Screenshot

Searx Screenshot

22.3. Screencast

Searx installation and first steps (14 MB)

22.4. Why use Searx?

22.4.1. Personalization and Filter Bubbles

Search engines have the ability to profile users and serve results most relevant to them, putting people into filter bubbles, thus distorting people's view of the world. Search engines have a financial incentive to serve interesting advertisements to their users, increasing their chances of clicking on the advertisements.

A metasearch engine is a possible solution to this problem, as it aggregates results from multiple search engines thus bypassing personalization attempts by search engines.

Searx avoids storing cookies from search engines as a means of preventing tracking and profiling by search engines.

22.4.2. Advertisement filtering

Searx filters out advertisements from the search results before serving the results, thus increasing relevance the of your search results and saving you from distractions.

22.4.3. Privacy

Searx uses HTTP POST instead of GET by default to send your search queries to the search engines, so that anyone snooping your traffic wouldn't be able to read your queries. The search queries wouldn't stored in browser history either.

Note: Searx used from Chrome browser's omnibar would make GET requests instead of POST.

22.5. Searx on FreedomBox

  • Searx on FreedomBox uses Single Sign On. This means that you should be logged in into your FreedomBox in the browser that you're using Searx.

  • SearX is easily accessible via Tor.
  • Searx can be added as a search engine to the Firefox browser's search bar. See Firefox Help on this topic. Once Searx is added, you can also set it as your default search engine.

  • Searx also offers search results in csv, json and rss formats, which can be used with scripts to automate some tasks.

23. Shadowsocks (Bypass Censorship)

Shadowsocks icon

Available since: version 0.18.0

23.1. What is Shadowsocks?

Shadowsocks is a tool for securely forwarding network requests to a remote server. It consists of two parts: (1) a Shadowsocks server, and (2) a Shadowsocks client with a SOCKS5 proxy.

Shadowsocks can be used to bypass Internet filtering and censorship. This requires that the Shadowsocks server is in a location where it can freely access the Internet, without filtering.

Your FreedomBox can run a Shadowsocks client which can connect to a Shadowsocks server. It will also run a SOCKS5 proxy. Local devices can connect to this proxy, and their data will be encrypted and proxied through the Shadowsocks server.

Alternatively, your FreedomBox can run a Shadowsocks server, that allows Shadowsocks clients to connect to it. Clients' data will be encrypted and proxied through this server.

23.2. Using Shadowsocks?

Shadowsocks can be used as follows:

  • Shadowsocks Client (a FreedomBox) is in a region where some parts of the Internet are blocked or censored.

  • Shadowsocks Server (a different FreedomBox, or another server) is in a different region, which doesn't have these blocks.

  • The FreedomBox running Shadowsocks Client provides SOCKS proxy service on the local network for other devices to make use of its Shadowsocks connection to the server.

Shadowsocks connection diagram

23.3. Configuring your FreedomBox for Shadowsocks Client

To enable Shadowsocks Client, first navigate to the Shadowsocks Client (Bypass Censorship) page, and install it.

Server: the Shadowsocks server is not this FreedomBox's IP or URL; rather, it will be another server or VPS that has been configured as a Shadowsocks server. There are also some public Shadowsocks servers listed on the web, but be aware that whoever operates the server can see where requests are going, and any non-encrypted data will be visible to them.

To use Shadowsocks Client after setup, set the SOCKS5 proxy URL in your device, browser or application to http://freedombox_address:1080/

23.4. Configuring your FreedomBox for Shadowsocks Server

To enable Shadowsocks Server, first navigate to the Shadowsocks Server (Help Others Bypass Censorship) page, and install it.

Note: In general, a FreedomBox should be set up as either a Shadowsocks Server, or a Shadowsocks Client, but not both!

For Shadowsocks Clients to connect to your server, they will need to know your domain name, the password, and the encryption method.

23.4.1. Port Forwarding

If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports for Shadowsocks Server:

  • TCP 8388
  • UDP 8388

24. Sharing (File Publishing)

Sharing icon

Available since: version 0.25

24.1. What Is Sharing App?

Sharing app allows you to share content over the web. Shared content can be individual files or whole directories.

The content can be shared publicly or restricted to the users of listed allowed groups. Allowed users will be able to access the shared content from their web browser at https://your_freedombox/share/content_name. Users not belonging to any of the allowed groups won't see or access the content through this mechanism.

24.2. Setting Up Shares

For the users to access the content through their browser it must exist and have a share. A share is an entry in the Sharing app relating:

  • the Name (an thereby the URL) with which the users will ask for the content,
  • the Disk Path of the content to be served and
  • the sharing mode. On restricted mode, it also has the list of allowed groups.

Many shares can coexist in the same server.

Only admins can create, edit or remove shares. They'll find the Sharing app in the Apps section of FreedomBox web interface. Sharing app is an easy to use web application with an evident interface.

Each share has its own sharing mode (public or restricted) setting. Only groups recognized by FreedomBox service can be combined in the list of allowed groups. Groups created in the CLI won't be offered by the Sharing app.

24.3. Providing/Updating Content

The content can be created before or after the share is created and they can be updated independently.

The content doesn't need to be provided by an admin either. Any user with write access to the share's disk path can create or update it.

Multiple shares might point to the same content.

If you are user of FreedomBox and your admin refuses to create shares for you, and you don't need to restrict the access to your content, you still can fall back to the User Websites mechanism or the P2P networks (Deluge or Transmission for Torrent) to publish your files.

24.4. Technicalities

Sharing will share the content using the built-in Apache web server.

25. Syncthing (File Synchronization)

Syncthing icon

Available since: version 0.14

With Syncthing installed on your FreedomBox, you can synchronize content from other devices to your FreedomBox and vice-versa. For example, you can keep the photos taken on your mobile phone synchronized to your FreedomBox.

Users should keep in mind that Syncthing is a peer-to-peer synchronization solution, not a client-server one. This means that the FreedomBox isn't really the server and your other devices clients. They're all devices from Syncthing's perspective. You can use Syncthing to synchronize your files between any of your devices. The advantage that FreedomBox provides is that it is a server that's always running. Suppose you want your photos on your phone to be synchronized to your laptop, if you simply sync the photos to the FreedomBox, the laptop can get them from the FreedomBox whenever it comes online the next time. You don't have to be worried about your other devices being online for synchronization. If your FreedomBox is one of the devices set up with your Syncthing shared folder, you can rest assured that your other devices will eventually get the latest files once they come online.

After installation follow the instructions in the getting started of the Syncthing project. Syncthing allows individual folders to be selectively shared with other devices. Devices must be paired up before sharing by scanning QR codes or entering the device ids manually. Syncthing has a discovery service for easily identifying the other devices on the same network having Syncthing installed.

In order to access to the web client of the Syncthing instance running on your FreedomBox, use the path /syncthing. This web client is currently only accessible to the users of the FreedomBox that have administrator privileges, though it might be accessible to all FreedomBox users in a future release.

Syncthing web interface

Syncthing has android apps available on the F-Droid and Google Play app stores. Cross-platform desktop apps are also available.

To learn more about Syncthing, please visit their official website and documentation.

25.1. Synchronizing over Tor

Syncthing should automatically sync with your FreedomBox even if it is only accessible as a Tor Onion Service.

If you would like to proxy your Syncthing client over Tor, set the all_proxy environment variable:

$ all_proxy=socks5://localhost:9050 syncthing

For more information, see the Syncthing documentation on using proxies.

25.2. Avoiding Syncthing Relays

Syncthing uses dynamic connections by default to connect with other peers. This means that if you are synchronizing over the Internet, the data might have to go through public Syncthing relays to reach your devices. This doesn't take advantage of the fact that your FreedomBox has a public IP address.

When adding your FreedomBox as a device in other Syncthing clients, set the address like "tcp://<my.freedombox.domain>" instead of "dynamic". This allows your Syncthing peers to directly connect to your FreedomBox avoiding the need for relays. It also allows for fast on-demand syncing if you don't want to keep Syncthing running all the time on your mobile devices.

25.3. Using Syncthing with other applications

25.3.1. Password Manager

Password managers that store their databases in files are suitable for synchronization using Syncthing. The following example describes using a free password manager called KeePassXC in combination with Syncthing to serve as a replacement for proprietary password managers that store your passwords in the cloud.

KeePassXC stores usernames, passwords etc. in files have the .kdbx extension. These kdbx files can be stored in a Syncthing shared folder to keep them synchronized on multiple machines. Free software applications which can read this file format are available for both desktop and mobile. You typically have to just point the application at the .kdbx file and enter the master password to access your stored credentials. For example, the same kdbx file can be accessed by using KeePassXC on desktop and KeePassDX on Android. KeePassXC can also be used to fill credentials into login fields in the browser by installing a browser extension.

26. Tiny Tiny RSS (News Feed Reader)

Tiny Tiny RSS icon

Available since: version 0.9

Tiny Tiny RSS is a news feed (RSS/Atom) reader and aggregator, designed to allow reading news from any location, while feeling as close to a real desktop application as possible.

Any user created through FreedomBox web interface will be able to login and use this app. Each user has their own feeds, state and preferences.

26.1. Using the Web Interface

When enabled, Tiny Tiny RSS will be available from /tt-rss path on the web server. Any user created through FreedomBox will be able to login and use this app.

Tiny Tiny RSS

26.1.1. Adding a new feed

1. Go to the website you want the RSS feed for and copy the RSS/Atom feed link from it.

Selecting feeds

2. Select "Subscribe to feed.." from the Actions dropdown.

Subscribe to feed

3. In the dialog box that appears, paste the URL for copied in step 1 and click the Subscribe button.

Subscription dialog box

Give the application a minute to fetch the feeds after clicking Subscribe.

In some websites, the RSS feeds button isn't clearly visible. In that case, you can simply paste the website URL into the Subscribe dialog (step 3) and let TT-RSS automatically detect the RSS feeds on the page.

You can try this now with the homepage of WikiNews

As you can see in the image below, TT-RSS detected and added the Atom feed of WikiNews to our list of feeds.

WikiNews feed added

If you don't want to keep this feed, right click on the feed shown in the above image, select Edit feed and click Unsubscribe in the dialog box that appears.

Unsubscribe from a feed

26.1.2. Importing your feeds from another feed reader

In your existing feed reader, find an option to Export your feeds to a file. Prefer the OPML file format if you have to choose between multiple formats. Let's say your exported feeds file is called Subscriptions.opml

Click on the Actions menu at the top left corner and select Preferences. You will be taken to another page.

Select the second tab called Feeds in the top header. Feeds has several sections. The second one is called OPML. Select it.

OPML feeds page

To import your Subscriptions.opml file into TT-RSS,

  1. Click Browse and select the file from your file system

  2. Click Import my OPML

After importing, you'll be taken to the Feeds section that's above the OPML section in the page. You can see that the feeds from your earlier feed reader are now imported into Tiny Tiny RSS. You can now start using Tiny Tiny RSS as your primary feed reader.

In the next section, we will discuss setting up the mobile app, which can let you read your feeds on the go.

26.2. Using the Mobile App

The official Android app from the Tiny Tiny RSS project works with FreedomBox's Tiny Tiny RSS Server. The older TTRSS-Reader application is known not to work.

To configure, first install the application, then in the setting page, set URL as https://<your.freedombox.address>/tt-rss-app/. Set your user name and password in the Login details as well as HTTP Authentication details. If your FreedomBox does not have a valid HTTPS certificate, then in settings request allowing any SSL certificate and any host.

Tiny Tiny RSS Tiny Tiny RSS Tiny Tiny RSS Tiny Tiny RSS Tiny Tiny RSS

26.3. RSS Bridge

RSS Bridge can be used with Tiny Tiny RSS to generate Atom/RSS links for websites that don't provide one.

27. Tor (Anonymitätnetzwerk)

Tor Ikon

Verfügbar seit: Version 0.3

27.1. Was ist Tor?

Tor ist ein Servernetzwerk, die von Freiwilligen betrieben wird. Benutzer dieser Server können ihre Privatsphäre und Sicherheit beim Surfen im Internet verbessern. Sie und Ihre Freunde können über das Tor-Netzwerk auf Ihre FreedomBox zugreifen, ohne deren IP-Adresse zu verraten. Wenn Sie die Tor-Anwendung auf Ihrer FreedomBox aktivieren, können Sie Remotedienste (Chat, Wiki, Dateifreigabe usw.) anbieten, ohne Ihren Standort anzuzeigen. Diese Anwendung bietet Ihnen einen beßeren Schutz als ein öffentlicher Webserver, denn Sie werden an weniger aufdringlichen Agente im Web ausgesetzt.

27.2. Anonymsurfen mit Tor

Tor Browser ist die empfohlene Methode, um mit Tor im Internet zu surfen. Sie können den Tor-Browser von https://www.torproject.org/projects/torbrowser.html herunterladen und den Anweisungen auf dieser Site folgen, um ihn zu installieren und rennen.

27.3. Zugriff auf Ihren FreedomBox mit dem Tor Onion Service

Der Tor Onion Service bietet eine Möglichkeit, auf Ihre FreedomBox zuzugreifen, auch wenn sie sich hinter einem Router, einer Firewall oder einem CGNAT befindet (d.h. Ihr Internetdienstanbieter stellt keine öffentliche IPv4-Adresse für Ihren Router bereit).

Um den Tor Onion Service zu aktivieren, gehen Sie erstmal zur Seite Anonymitätnetzwerk (Tor). (Wenn Sie es nicht sehen, klicken Sie oben links auf der Seite auf das FreedomBox-Logo, um zur Apps-Hauptseite zu gelangen.) Aktivieren Sie auf der Seite Anonymitätnetzwerk (Tor) unter Konfiguration die Option "Tor Onion Service aktivieren", und klicken Sie dann auf Setup aktualisieren. Tor wird neu konfiguriert und wiedergestartet werden.

Nach einer Weile wird die Seite aktualisiert und unter Status wird eine Tabelle mit der .onion-Adresse des Onion Service angezeigt. Kopieren Sie die ganze Adresse (mit der Endung .onion) und fügen Sie sie in das Adressfeld des Tor-Browsers ein. Sie sollten dann auf Ihre FreedomBox zugreifen können. (Möglicherweise wird eine Zertifikatwarnung angezeigt, denn FreedomBox'sches Zertifikat ist selbstsigniert.)

Tor Einstellung - FreedomBox

Heutzutage können nur HTTP (Port 80), HTTPS (Port 443) und SSH (Port 22) über den auf der FreedomBox konfigurierten Tor Onion Service zugegriffen werden.

27.4. Apps, die über Tor zugreifbar sind

Folgende Apps lassen sich über Tor zugreiffen. Beachten Sie, daß diese Liste nicht vollständig ist.

27.5. Ein Tor-Relais betreiben

Tor ist standardmäßig, als Brückenrelais eingestellt. Die Relais- oder Brückenoption kann man über die Tor-Konfigurationsseite in FreedomBox abschalten.

Unten, bei der Tor-Seite in FreedomBox gibt es eine Liste der vom Tor-Relais verwendeten Ports. Wenn Ihre FreedomBox sich hinter einem Router befindet, müssen Sie die Portweiterleitung auf Ihrem Router konfigurieren, um diese Ports über das öffentliche Internet zugreifbar zu lassen.

Die Anforderungen für den Betrieb eines Relais sind im Tor Relay Guide aufgegeben . Das heißt:

  • Es wird empfohlen, daß für ein Relais mindestens 16 Mbit/s (Mbps) Auf- sowohl als Herunterwärts-Bandbreite für Tor verfügbar sind. Mehr desto besser.
  • Es ist erforderlich, daß ein Tor-Relay mindestens 100 GByte ausgehenden und eingehenden Datenverkehrs pro Monat verwenden darf.
  • Für ein Nicht-Ausgang-Relais mit <40 Mbit/s wird es empfohlen, daß mindestens 512 MB RAM verfügbar sind; Ein schnelleren Relais, sollte mindestens 1 GB RAM haben.

27.6. (Fortgeschrittene) Verwendung als SOCKS-Proxy

FreedomBox bietet einen Tor SOCKS-Port, mit dem andere Anwendungen eine Verbindung herstellen können um ihren Verkehr über das Tor-Netzwerk zu leiten. Dieser Port ist an alle Schnittstellen zugänglich, die die internen Firewall-Zone zugewiesen sind. Setzen Sie SOCKS Host auf die IP-Adresse der internen Netzwerkverbindung und Stellen Sie den SOCKS-Port auf 9050 ein, um die Anwendung einzustellen.

27.6.1. Beispiel mit Firefox

Ihr Webbrowser kann so eingestellt werden, daß er das Tor-Netzwerk für alle Surfen-Aktivität verwendet wird. Dies ermöglicht die Umgehung der Zensur und versteckt auch Ihre IP-Adresse von Websites während des regelmäßigen Surfens. Für Anonymität wird TorBrowser empfohlen.

Stellen Sie Ihre lokale FreedomBox-IP-Adresse und Ihren Port 9050 als SOCKS v5-Proxy in Firefox ein. Es gibt Erweiterungen, mit denen der Proxy einfach ein- und ausgeschaltet werden kann.

Firefox mit Tor SOCKS proxy einstellen

Mit konfigurierten SOCKS-Proxy können Sie nun direkt auf Onion-URLs aus Firefox zugreifen. FreedomBox selbst hat eine Onion-v3-Adresse, mit der Sie eine Verbindung über das Tor-Netzwerk herstellen können. (Bemerken Sie sie für Notfallgelegenheiten).

27.7. Umgehung der Tor-Zensur

Wenn Ihr ISP versucht, den Tor-Verkehr zu blockieren, können Sie Tor-Bridge-Relais verwenden, um eine Verbindung zum Tor-Netzwerk herzustellen

1. Erhalten Sie die Bridge-Konfiguration aus der Tor BridgeDB

Tor BridgeDB

2. Fügen Sie die Zeilen wie unten gezeigt zu Ihrer FreedomBox Tor-Konfiguration hinzu.

Eistellungseite für Tor

28. Transmission (Distributed File Sharing via BitTorrent)

Transmission icon

Available since: version 0.5

28.1. What is Transmission ?

Transmission is a BitTorrent node (both, client and server at the same time).

BitTorrent is a communications protocol for peer-to-peer (P2P) file sharing.

  • It is not anonymous; you should assume that others can see what files you are sharing.

  • This technology works best for big, popular files.

There are two BitTorrent web nodes available in FreedomBox: Transmission and Deluge. They have similar features, but you may prefer one over the other.

Transmission is a lightweight BitTorrent client that is well known for its simplicity and a default configuration that "Just Works".

28.2. Screenshot

Transmission Web Interface

28.3. Using Transmission

After installing Transmission, it can be accessed at https://<your freedombox>/transmission. Transmission uses single sign-on from FreedomBox, which means that if you are logged in on your FreedomBox, you can directly access Transmission without having to enter the credentials again. Otherwise, you will be prompted to login first and then redirected to the Transmission app.

28.4. Tips

28.4.1. Transferring Downloads from the FreedomBox

  1. Transmission's downloads directory can be added as a shared folder in the Sharing app. You can then access your downloads from this shared folder using a web browser.

  2. (Advanced) If you have the ssh access to your FreedomBox, you can use sftp or scp to browse the downloads directory using a suitable file manager or web browser:

28.5. Port Forwarding

If your FreedomBox is behind a router you optionally might want to set up port forwarding on your router in order to improve communication with other peers. You should forward the following ports for Transmission:

  • TCP 51413 (or your configured peer listening port)

28.6. Using Remote Apps

In addition to using the web interface to control Transmission on FreedomBox, desktop and mobile apps may also be used. List of tested clients and their platforms are listed on the app page in FreedomBox web interface. When configuring these clients the URL to connect must be /transmission-remote/rpc and the port must be 443.

29. User Websites

Available since: version 0.9.4

29.1. What is User Websites?

User websites is a standard location for webservers to allow host users to expose static files on the filesystem as a website to the local network and/or the internet according to the network and firewall setup.

The standard webserver in FreedomBox is Apache and this is implemented by means of a specific Apache module.

29.2. Screenshot

29.3. Using User Websites

The module is always enabled and offers no configuration from the FreedomBox web interface. There is no configuration or status page shown for this module in the FreedomBox web interface.

To serve documents, place the files in the designated directory in a FreedomBox user's home directory in the filesystem.

This directory is: public_html

Thus the absolute path for the directory of a user named fbx with home directory in /home/fbx will be /home/fbx/public_html. User websites will serve documents placed in this directory when requests for documents with the URI path "~fbx" are received. For the the example.org domain thus a request for the document example.org/~fbx/index.html will transfer the file in /home/fbx/public_html/index.html.

29.4. Creating public_html folder and uploading documents

29.4.1. Visually from Linux

Linux standard desktop file managers use to support remote filesystem access through SFTP out of the box. Among others, Gnome's Nautilus, KDE/Plasma's Dolphin and XFCE's Thunar do so. This standarization allows for very easy, similar and straightforward procedures:

  1. Connect with the file manager to your FreedomBox:

    • Gnome's Nautilus:
      1. To lauch Nautilus you can seek its archive icon, or search ether its name or the word "file".
      2. At the bottom of the left pane you'll find an option "+ Other locations".
      3. It leads you to a list of locations. Find "freedombox SFTP server" (english literal for all desktop languages). Click on it.

      4. The first time you'll be asked for your user and password. Enter your FreedomBox user and its password. The dialog will also offer you some options to remember it for some time.

    • Plasma file manager AKA Dolphin:
      1. Click on the location bar at the top of the window.
      2. Input ftp://freedombox.local

      3. The first time you'll be asked for your user and password. Enter your FreedomBox user and its password. The dialog will also offer you some option to remember it.

    • XFCE's Thunar:
      1. Type this into the browser bar: sftp://username@freedombox.local, replacing the 'username' placeholder with your actual FreedomBox username.

      2. I guess the first time you'll be asked for your password. Enter your FreedomBox user's password.

  2. You should be shown FreedomBox filesystem. Enter the home folder and then enter you user's subfolder.

  3. If there's no public_html folder, create it: right mouse button click, etc.

  4. Drag your file(s) and drop it/'em into the public_html folder.

  5. You should now be able to navigate your browser to the corresponding url and see the files.

29.4.2. Visually from Other Plattforms

If you want to use graphical free software clients, install:

Their usage will be similar to that described for Linux desktops.

29.4.3. With a Command Line Interface (CLI)

Usually any Unix system, including Linux in all (most) of its flavours and Mac, provide the standard utilities ssh, scp and sftp. FreeDOS provides SSH2DOS. No need to install anything. It's already there!

Examples:

Connect to FreedomBox via SSH:

  1. (replacing username with a valid FreedomBox user name and freedombox.local with your FreedomBox's domain name or IP):

    $ ssh username@freedombox.local
  2. If your data is ok and your FreedomBox reachable, the first time you'll be asked to confirm its signature.

  3. Then you'll be asked for the password of your FreedomBox user.

  4. Then you'll be shown the welcome banner with the FreedomBox's buttefly logo in ASCII art (painted with characters).

  5. The prompt changes to username@freedombox:~$.

Once connected create your website folder with:

  • username@freedombox:~$ mkdir ~/public_html

...or one for another user:

  1. use the sudo prefix like

    username@freedombox:~$ sudo mkdir /home/<the_other_user>/public_html
    , and introduce your password.
  2. When you create a folder, by default it belongs to you no matter where it is created. Thus you'll then need to set its ownership to the other user:

    username@freedombox:~$ sudo chown <the_other_user>:<the_other_user> /home/<the_other_user>/public_htm
  3. Better check it before you disconnect that `public_html' is listed among the contents of the other user's home folder.
    username@freedombox:~$ ls -l /home/<the_other_user>
    ...
    drwxr-xr-x  2 <the_other_user> <the_other_user>   4096 jan 29 17:39  public_html
    ...

    . The name of the other user must appear twice in the public_html line and its permissions should be drwxr-xr-x.

Then any user can upload their files to their respective folders with any of the graphical clients. Ask them to check it.

It is a good security practice to exit instead of to just wait for the connection to time out:

  • username@freedombox:~$ exit

If then you want to also upload the web content through the command line you can

$ scp path/to/files username@freedombox.local:public_html/

. It will ask your password in FreedomBox. You should then be able to navigate your browser to the corresponding url and see the files.

Learn more about ssh, scp and sftp with $ man ssh, $ man scp and $ man sftp.

30. WireGuard (Virtual Private Network)

alt="WireGuard icon"

30.1. About WireGuard

WireGuard is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It can be a useful replacement for IPSec or OpenVPN.

30.2. Installation

You can install wireguard from the Apps section of the FreedomBox web interface.

30.3. Usage

  • Point-to-point tunnel
  • VPN client with default route

30.4. Configuration - Debian Peers

Note: These steps are handled automatically on FreedomBox. So you only need to follow these steps on any Debian clients that will connect to FreedomBox, or Debian servers that FreedomBox will connect to.

30.5. Configuration - Mobile Clients

WireGuard has a user space implementation for mobile devices available via the WireGuard app - available for Android and iOS (a full list of supported operating systems is available here).

The client can be configured in several ways:

30.5.1. Alternative A - Create configuration manually

This is self-explanatory, you actually create the config on the mobile device then transfer the relevant keys to the server's config.

30.5.2. Alternative B - Create configuration from archive

Here you have to create a .zip archive of the client configuration file, transfer it to the device then import it into the app.

30.5.3. Alternative C - Import by reading a QR code (most secure method)

The mobile client as of version 0.0.20180724 supports QR code based input.

qrencode can be used to generate qr codes, even in a terminal/console using UTF8 characters.

The syntax is:

# qrencode -t ansiutf8 < client.conf

This will generate a QR code that is readable by the mobile client.

The advantage of this approach is that there is no need to transfer sensitive information via data channels that can potentially be compromised and there is no need for any additional software.

System

1. Backups

FreedomBox includes the ability to backup and restore data, preferences, configuration and secrets from most of the applications. The Backups feature is built using Borg backup software. Borg is a deduplicating and compressing backup program. It is designed for efficient and secure backups. This backups feature can be used to selectively backup and restore data on an app-by-app basis. Backed up data can be stored on the FreedomBox machine itself or on a remote server. Any remote server providing SSH access can be used as a backup storage repository for FreedomBox backups. Data stored remotely may be encrypted and in such cases remote server cannot access your decrypted data.

1.1. Notes for Specific App Backups

Unless otherwise noted here, backup of an app's data will include its configuration, secrets and other data.

App/Feature

Notes

Deluge

Does not include downloaded/seeding files

MiniDLNA

Does not include the data in the shared folders

Networks

No plans currently to implement backup

Samba

Does not include the data in the shared folders

Sharing

Does not include the data in the shared folders

Snapshot

Only configuration, does not include snapshot data

Syncthing

Does not include data in the shared folders

Transmission

Does not include downloaded/seeding files

Users

Backup of user accounts is planned

1.2. How to install and use Backups

Step 1

Backups: Step 1

Step 2

Backups: Step 2

Step 3

Backups: Step 3

Step 4

Backups: Step 4

Step 5

Backups: Step 5

Step 6

Backups: Step 6

Step 7

Backups: Step 7

2. BIND (Domain Name Server)

BIND enables you to publish your Domain Name System (DNS) information on the Internet, and to resolve DNS queries for your user devices on your network.

Currently, on FreedomBox, BIND is only used to resolve DNS queries for other machines on local network. It is also incompatible with sharing Internet connection from FreedomBox.

Note: This service is available only on networks configured as "internal" zone. It is not available when connected via OpenVPN.

2.1. Using BIND

When BIND is enabled, that does not automatically mean that anything is using it. The following can be configured:

  • FreedomBox can be configured to use the local BIND service for its own DNS lookups.

  • Clients on the Local Area Network can be configured to use the FreedomBox's BIND service for their DNS lookups.

The FreedomBox can be set to use its own BIND service for DNS lookups through Networks:

  1. Go to System page, and then select Networks.
  2. Select the "FreedomBox WAN" connection and press Edit.

  3. Under "IPv4 Addressing Method", there is a field "DNS Server". Set it to 127.0.0.1.

  4. Press "Edit Connection" at the bottom to save the changes.
  5. Restart the FreedomBox from the user drop-down menu.

3. Cockpit (Server Administration)

Cockpit is a server manager that makes it easy to administer GNU/Linux servers via a web browser. On a FreedomBox, controls are available for many advanced functions that are not usually required. A web based terminal for console operations is also available.

It can be accessed by any user on your FreedomBox belonging to the admin group. Cockpit is only usable when you have proper domain name setup for your FreedomBox and you use that domain name to access Cockpit. See the Troubleshooting section for more information.

Use cockpit only if you are an administrator of GNU/Linux systems with advanced skills. FreedomBox tries to coexist with changes to system by system administrators and system administration tools like Cockpit. However, improper changes to the system might causes failures in FreedomBox functions.

3.1. Using Cockpit

Install Cockpit like any other application on FreedomBox. Make sure that Cockpit is enabled after that.

cockpit-enable.png

Ensure that the user account on FreedomBox that will used for Cockpit is part of the administrators group.

cockpit-admin-user.png

Launch the Cockpit web interface. Login using the configured user account. Be sure to check the box to "reuse my password for privileged tasks", otherwise you will not be able to perform various tasks such as configuring raid, or editing users, once logged in.

cockpit-login.png

Start using cockpit.

cockpit-system.png

Cockpit is usable on mobile interfaces too.

cockpit-mobile.png

3.2. Features

The following features of Cockpit may be useful for advanced FreedomBox users.

3.2.1. System Dashboard

Cockpit has a system dashboard that

  • Shows detailed hardware information
  • Shows basic performance metrics of a system
  • Allows changing system time and timezone
  • Allows changing hostname. Please use FreedomBox UI to do this

  • Shows SSH server fingerprints

cockpit-system.png

3.2.2. Viewing System Logs

Cockpit allows querying system logs and examining them in full detail.

cockpit-logs.png

3.2.3. Managing Storage

Cockpit allows following advanced storage functions:

  • View full disk information
  • Editing disk partitions
  • RAID management

cockpit-storage1.png

cockpit-storage2.png

3.2.4. Networking

Cockpit and FreedomBox both rely on NetworkManager to configure the network. However, Cockpit offers some advanced configuration not available on FreedomBox:

  • Route configuration
  • Configure Bonds, Bridges, VLANs

cockpit-network1.png

cockpit-network2.png

cockpit-network3.png

3.2.5. Services

Cockpit allows management of services and periodic jobs (similar to cron).

cockpit-services1.png

cockpit-services2.png

3.2.6. Web Terminal

Cockpit offers a web based terminal that can be used perform manual system administration tasks.

cockpit-terminal.png

3.3. Troubleshooting

Cockpit requires a domain name to be properly setup on your FreedomBox and will only work when you access it using a URL with that domain name. Cockpit will not work when using IP address in the URL. Using freedombox.local as the domain name also does not work. For example, the following URLs will not work:

https://192.168.0.10/_cockpit/
https://freedombox.local/_cockpit/

Starting with FreedomBox version 19.15, using .local domain works. You can access Cockpit using the URL https://freedombox.local/_cockpit/. The .local domain is based on your hostname. If your hostname is mybox, your .local domain name will be mybox.local and the Cockpit URL will be https://mybox.local/_cockpit/.

To properly access Cockpit, use the domain name configured for your FreedomBox.Cockpit will also work well when using a Tor Onion Service. The following URLs will work:

https://mybox.freedombox.rocks/_cockpit/
https://exampletorhs.onion/_cockpit/

The reason for this behaviour is that Cockpit uses WebSockets to connect to the backend server. Cross site requests for WebSockets must be prevented for security reasons. To implement this, Cockpit maintains a list of all domains from which requests are allowed. FreedomBox automatically configures this list whenever you add or remove a domain. However, since we can't rely on IP addresses, they are not added by FreedomBox to this domain list. You can see the current list of allowed domains, as managed by FreedomBox, in /etc/cockpit/cockpit.conf. You may edit this, but do so only if you understand web security consequences of this.

4. Configure

Configure has some general configuration options:

4.1. Hostname

  • Hostname is the local name by which other devices on the local network can reach your FreedomBox. The default hostname is freedombox.

4.2. Domain Name

4.3. Webserver Home Page

Once some other app is set as the home page, you can only navigate to the FreedomBox Service by typing https://myfreedombox.rocks/plinth/ into the browser.
/freedombox can also be used as an alias to /plinth

  • You can set any web application, Ikiwiki wikis and blogs or Apache's default index.html page as the web server home page. Since release 20.20 you can also select a user's website among those users who have created their public_html directory.

  • Tip: Bookmark the URL of FreedomBox Service before setting the home page to some other app.

5. Date & Time

This network time server is a program that maintains the system time in synchronization with servers on the Internet.

You can select your time zone by picking a big city nearby (they are sorted by Continent/City) or select directly the zone with respect to GMT (Greenwich Mean Time).

DateTime.png

6. Diagnostics

The system diagnostic test will run a number of checks on your system to confirm that applications and services are working as expected.

Just click Run Diagnostics. This may take some minutes.

7. Dynamic DNS Client

7.1. What is Dynamic DNS?

In order to reach a server on the Internet, the server needs to have permanent address also known as the static IP address. Many Internet service providers don't provide home users with a static IP address or they charge more providing a static IP address. Instead they provide the home user with an IP address that changes every time the user connects to the Internet. Clients wishing to contact the server will have difficulty reaching the server.

Dynamic DNS service providers assist in working around a problem. First they provide you with a domain name, such as 'myhost.example.org'. Then they associate your IP address, whenever it changes, with this domain name. Then anyone intending to reach the server will be to contact the server using the domain name 'myhost.example.org' which always points to the latest IP address of the server.

For this to work, every time you connect to the Internet, you will have to tell your Dynamic DNS provider what your current IP address is. Hence you need special software on your server to perform this operation. The Dynamic DNS function in FreedomBox will allow users without a static public IP address to push the current public IP address to a Dynamic DNS Server. This allows you to expose services on FreedomBox, such as ownCloud, to the Internet.

7.2. GnuDIP vs. Update URL

There are two main mechanism to notify the Dynamic DNS server of your new IP address; using the GnuDIP protocol and using the Update URL mechanism.

If a service provided using update URL is not properly secured using HTTPS, your credentials may be visible to an adversary. Once an adversary gains your credentials, they will be able to replay your request your server and hijack your domain.

On the other hand, the GnuDIP protocol will only transport a salted MD5 value of your password, in a way that is secure against replay attacks.

7.3. Using the GnuDIP protocol

  1. Register an account with any Dynamic DNS service provider. A free service provided by the FreedomBox community is available at https://ddns.freedombox.org .

  2. In FreedomBox UI, enable the Dynamic DNS Service.

  3. Select GnuDIP as Service type, enter your Dynamic DNS service provider address (for example, ddns.freedombox.org) into GnuDIP Server Address field.

    Dynamic DNS Settings

  4. Fill Domain Name, Username, Password information given by your provider into the corresponding fields.

7.4. Using an Update URL

This feature is implemented because the most popular Dynamic DNS providers are using Update URLs mechanism.

  1. Register an account with a Dynamic DNS service provider providing their service using Update URL mechanism. Some example providers are listed in the configuration page itself.
  2. In FreedomBox UI, enable the Dynamic DNS service.

  3. Select other Update URL as Service type, enter the update URL given by your provider into Update URL field.

  4. If you browse the update URL with your Internet browser and a warning message about untrusted certificate appears, then enable accept all SSL certificates. WARNING: your credentials may be readable here because man-in-the-middle attacks are possible! Consider choosing a better service provider instead.

  5. If you browse the update URL with your Internet browser and the username/password box appears, enable use HTTP basic authentication checkbox and provide the Username and Password.

  6. If the update URL contains your current IP address, replace the IP address with the string <Ip>.

7.5. Checking If It Works

  1. Make sure that external services you have enabled such as /jwchat, /roundcube and /ikiwiki are available on your domain address.
  2. Go to the Status page, make sure that the NAT type is detected correctly. If your FreedomBox is behind a NAT device, this should be detected over there (Text: Behind NAT). If your FreedomBox has a public IP address assigned, the text should be "Direct connection to the Internet".

  3. Check that the last update status is not failed.

7.6. Recap: How to create a DNS name with GnuDIP

  1. Access to GnuIP login page (answer Yes to all pop ups)

  2. Click on "Self Register"
  3. Fill the registration form (Username and domain will form the public IP address [username.domain])
  4. Take note of the username/hostname and password that will be used on the FreedomBox app.

  5. Save and return to the GnuDIP login page to verify your username, domain and password (enter the datas, click login).
  6. Login output should display your new domain name along with your current public IP address (this is a unique address provided by your router for all your local devices).
  7. Leave the GnuDIP interface and open the Dynamic DNS Client app page in your FreedomBox.

  8. Click on "Set Up" in the top menu.
  9. Activate Dynamic DNS
  10. Choose GnuDIP service.
  11. Add server address (ddns.freedombox.org)
  12. Add your fresh domain name (username.domain, ie [username].freedombox.rocks)
  13. Add your fresh username (the one used in your new IP address) and password
  14. Add your GnuDIP password
  15. Fill the option with https://ddns.freedombox.org/ip/ (try this url in your browser, you will figure out immediately)

8. Firewall

Firewall is a network security system that controls the incoming and outgoing network traffic. Keeping a firewall enabled and properly configured reduces risk of security threat from the Internet.

The operation of the firewall in FreedomBox web interface is automatic. When you enable a service it is automatically permitted in the firewall and when you disable a service it is automatically disabled in the firewall. For services which are enabled by default on FreedomBox, firewall ports are also enabled by default during the first run process.

Firewall

Firewall management in FreedomBox is done using FirewallD.

8.1. Interfaces

Each interface is needs to be assigned to one (and only one) zone. If an interface is not assigned any zone, it is automatically assigned external zone. Whatever rules are in effect for a zone, those rules start to apply for that interface. For example, if HTTP traffic is allowed in a particular zone, then web requests will be accepted on all the addresses configured for all the interfaces assigned to that zone.

There are primarily two firewall zones used. The internal zone is meant for services that are provided to all machines on the local network. This may include services such as streaming media and simple file sharing. The external zone is meant for services that are provided publicly on the Internet. This may include services such as blog, website, email web client etc.

For details on how network interfaces are configured by default, see the Networks section.

8.2. Opening Custom Ports

Cockpit app provides advanced management of firewall. Both FreedomBox and Cockpit operate over firewalld and are hence compatible with each other. In particular, Cockpit can be used to open custom services or ports on FreedomBox. This is useful if you are manually running your own services in addition to the services provided by FreedomBox on the same machine.

firewalld-cockpit.png

8.3. FreedomBox Ports/Services

The following table attempts to document the ports, services and their default statuses in FreedomBox. If you find this page outdated, see the Firewall status page in FreedomBox interface.

Service

Port

External

Enabled by default

Status shown in FreedomBox

Managed by FreedomBox

Minetest

30000/udp

{*}

{X}

(./)

(./)

XMPP Client

5222/tcp

{*}

{X}

(./)

(./)

XMPP Server

5269/tcp

{*}

{X}

(./)

(./)

XMPP Bosh

5280/tcp

{*}

{X}

(./)

(./)

NTP

123/udp

{o}

(./)

(./)

(./)

FreedomBox Web Interface (Plinth)

443/tcp

{*}

(./)

(./)

{X}

Quassel

4242/tcp

{*}

{X}

(./)

(./)

SIP

5060/tcp

{*}

{X}

(./)

(./)

SIP

5060/udp

{*}

{X}

(./)

(./)

SIP-TLS

5061/tcp

{*}

{X}

(./)

(./)

SIP-TLS

5061/udp

{*}

{X}

(./)

(./)

RTP

1024-65535/udp

{*}

{X}

(./)

(./)

SSH

22/tcp

{*}

(./)

(./)

{X}

mDNS

5353/udp

{o}

(./)

(./)

(./)

Tor (Socks)

9050/tcp

{o}

{X}

(./)

(./)

Obfsproxy

<random>/tcp

{*}

{X}

(./)

(./)

OpenVPN

1194/udp

{*}

{X}

(./)

(./)

Mumble

64378/tcp

{*}

{X}

(./)

(./)

Mumble

64378/udp

{*}

{X}

(./)

(./)

Privoxy

8118/tcp

{o}

{X}

(./)

(./)

JSXC

80/tcp

{*}

{X}

{X}

{X}

JSXC

443/tcp

{*}

{X}

{X}

{X}

DNS

53/tcp

{o}

{X}

{X}

{X}

DNS

53/udp

{o}

{X}

{X}

{X}

DHCP

67/udp

{o}

(./)

{X}

{X}

Bootp

67/tcp

{o}

{X}

{X}

{X}

Bootp

67/udp

{o}

{X}

{X}

{X}

Bootp

68/tcp

{o}

{X}

{X}

{X}

Bootp

68/udp

{o}

{X}

{X}

{X}

LDAP

389/tcp

{o}

{X}

{X}

{X}

LDAPS

636/tcp

{o}

{X}

{X}

{X}

8.4. Manual operation

See FirewallD documentation for more information on the basic concepts and comprehensive documentation.

8.4.1. Enable/disable firewall

To disable firewall

service firewalld stop

or with systemd

systemctl stop firewalld

To re-enable firewall

service firewalld start

or with systemd

systemctl start firewalld

8.4.2. Modifying services/ports

You can manually add or remove a service from a zone.

To see list of services enabled:

firewall-cmd --zone=<zone> --list-services

Example:

firewall-cmd --zone=internal --list-services

To see list of ports enabled:

firewall-cmd --zone=<zone> --list-ports

Example:

firewall-cmd --zone=internal --list-ports

To remove a service from a zone:

firewall-cmd --zone=<zone> --remove-service=<service>
firewall-cmd --permanent --zone=<zone> --remove-service=<interface>

Example:

firewall-cmd --zone=internal --remove-service=xmpp-bosh
firewall-cmd --permanent --zone=internal --remove-service=xmpp-bosh

To remove a port from a zone:

firewall-cmd --zone=internal --remove-port=<port>/<protocol>
firewall-cmd --permanent --zone=internal --remove-port=<port>/<protocol>

Example:

firewall-cmd --zone=internal --remove-port=5353/udp
firewall-cmd --permanent --zone=internal --remove-port=5353/udp

To add a service to a zone:

firewall-cmd --zone=<zone> --add-service=<service>
firewall-cmd --permanent --zone=<zone> --add-service=<interface>

Example:

firewall-cmd --zone=internal --add-service=xmpp-bosh
firewall-cmd --permanent --zone=internal --add-service=xmpp-bosh

To add a port to a zone:

firewall-cmd --zone=internal --add-port=<port>/<protocol>
firewall-cmd --permanent --zone=internal --add-port=<port>/<protocol>

Example:

firewall-cmd --zone=internal --add-port=5353/udp
firewall-cmd --permanent --zone=internal --add-port=5353/udp

8.4.3. Modifying the zone of interfaces

You can manually change the assignment of zones of each interfaces after they have been autuomatically assigned by the first boot process.

To see current assignment of interfaces to zones:

firewall-cmd --list-all-zones

To remove an interface from a zone:

firewall-cmd --zone=<zone> --remove-interface=<interface>
firewall-cmd --permanent --zone=<zone> --remove-interface=<interface>

Example:

firewall-cmd --zone=external --remove-interface=eth0
firewall-cmd --permanent --zone=external --remove-interface=eth0

To add an interface to a zone:

firewall-cmd --zone=<zone> --add-interface=<interface>
firewall-cmd --permanent --zone=<zone> --add-interface=<interface>

Example:

firewall-cmd --zone=internal --add-interface=eth0
firewall-cmd --permanent --zone=internal --add-interface=eth0

9. Let's Encrypt (Certificates)

A digital certificate allows users of a web service to verify the identity of the service and to securely communicate with it. FreedomBox can automatically obtain and setup digital certificates for each available domain. It does so by proving itself to be the owner of a domain to Let's Encrypt, a certificate authority (CA).

Let's Encrypt is a free, automated, and open certificate authority, run for the public's benefit by the Internet Security Research Group (ISRG). Please read and agree with the Let's Encrypt Subscriber Agreement before using this service.

9.1. Why using Certificates

The communication with your FreedomBox can be secured so that it is not possible to intercept the content of the web pages viewed and about the content exchanged.

9.2. How to setup

  1. If your FreedomBox is behind a router, you will need to set up port forwarding on your router. You should forward the following ports:

    • TCP 80 (http)
    • TCP 443 (https)
  2. Make the domain name known:
    • In Configure insert your domain name, e.g. MyWebName.com

      Let's Encrypt

  3. Verify the domain name was accepted
  4. Go to the Certificates (Let's Encrypt) page, and complete the module install if needed. Then click the "Obtain" button for your domain name.
    • After some minutes a valid certificate is available

      Let's Encrypt

  5. Verify in your browser by checking https://MyWebName.com

    • Let's Encrypt Certificate

Screencast: Let's Encrypt

9.3. Using

The certificate is valid for 3 months. It is renewed automatically and can also be re-obtained or revoked manually.

With running diagnostics the certificate can also be verified.

10. Monkeysphere

This application is no longer available in FreedomBox.

With Monkeysphere, an OpenPGP key can be generated for each configured domain serving SSH. The OpenPGP public key can then be uploaded to the OpenPGP keyservers. Users connecting to this machine through SSH can verify that they are connecting to the correct host. For users to trust the key, at least one person (usually the machine owner) must sign the key using the regular OpenPGP key signing process. See the Monkeysphere SSH documentation for more details.

Monkeysphere can also generate an OpenPGP key for each Secure Web Server (HTTPS) certificate installed on this machine. The OpenPGP public key can then be uploaded to the OpenPGP keyservers. Users accessing the web server through HTTPS can verify that they are connecting to the correct host. To validate the certificate, the user will need to install some software that is available on the Monkeysphere website.

11. Name Services

Name Services provides an overview of ways the box can be reached from the public Internet: domain name, Tor Onion Service, and Pagekite. For each type of name, it is shown whether the HTTP, HTTPS, and SSH services are enabled or disabled for incoming connections through the given name.

12. Networks

This section describes how networking is setup by default in FreedomBox and how you can customize it. See also the Firewall section for more information on how firewall works.

12.1. Default setup

In a fresh image of FreedomBox, network is not configured at all. When the image is written to an SD card and the device boots, configuration is done. During first boot, FreedomBox setup package detects the networks interfaces and tries to automatically configure them so that FreedomBox is available for further configuration via the web interface from another machine without the need to connect a monitor. Automatic configuration also tries to make FreedomBox useful, out of the box, for the most important scenarios FreedomBox is used for.

There are two scenarios it handles: when is a single ethernet interface and when there are multiple ethernet interfaces.

12.1.1. Single ethernet interface

When there is only single ethernet interface available on the hardware device, there is not much scope for it to play the role of a router. In this case, the device is assumed to be just another machine in the network. Accordingly, the only available interface is configured to be an internal interface in automatic configuration mode. This means that it connects to the Internet using the configuration provided by a router in the network and also makes all (internal and external) of its services available to all the clients on this network.

network_single.png

12.1.2. Multiple ethernet interface

When there are multiple ethernet interfaces available on the hardware device, the device can act as a router. The interfaces are then configured to perform this function.

The first network interface is configured to be an WAN or external interface in automatic configuration mode. This means that it connects to the Internet using network configuration provided by the Internet Service Provider (ISP). Only services that are meant to be provided across the entire Internet (external services) will be exposed on this interface. You must plug your Internet connection into the port of this ethernet interface. If you wish to continue to have your existing router manage the Internet connection for you, then plug a connection from your router to the port on this interface.

The remaining network interfaces are configured for the clients of a router. They are configured as LAN or internal interfaces in shared configuration mode. This means that all the services (both external and internal) services are provided to who ever connects on this interface. Further, the shared mode means that clients will be able to receive details of automatic network connection on this interface. Specifically, DHCP configuration and DNS servers are provided on this interface. The Internet connection available to the device using the first network interface will be shared with clients using this interface. This all means that you can connect your computers to this network interface and they will get automatically configured and will be able to access the Internet via the FreedomBox.

Currently, it is not very clear which interface will be come the WAN interface (and the remaining being LAN interfaces) although the assignment process is deterministic. So, it take a bit of trail and error to figure out which one is which. In future, for each device, this will be well documented.

12.1.3. Wi-Fi configuration

All Wi-Fi interfaces are configured to be LAN or internal interfaces in shared configuration mode. They are also configured to become Wi-Fi access points with following details.

  • Name of the access point will be FreedomBox plus the name of the interface (to handle the case where there are multiple of them).

  • Password for connecting to the interface will be freedombox123.

12.2. Internet Connection Sharing

Although the primary duty of FreedomBox is to provide decentralized services, it can also act like a home router. Hence, in most cases, FreedomBox connects to the Internet and provides other machines in the network the ability to use that Internet connection. FreedomBox can do this in two ways: using a shared mode connection or using an internal connection.

When an interface is set in shared mode, you may connect your machine directly to it. This is either by plugging in an ethernet cable from this interface to your machine or by connecting to a Wi-Fi access point. This case is the simplest to use, as FreedomBox automatically provides your machine with the necessary network configuration. Your machine will automatically connect to FreedomBox provided network and will be able to connect to the Internet given that FreedomBox can itself connect to the Internet.

Sometimes the above setup may not be possible because the hardware device may have only one network interface or for other reasons. Even in this case, your machine can still connect to the Internet via FreedomBox. For this to work, make sure that the network interface that your machine is connecting to is in internal mode. Then, connect your machine to network in which FreedomBox is present. After this, in your machine's network configuration, set FreedomBox's IP address as the gateway. FreedomBox will then accept your network traffic from your machine and send it over to the Internet. This works because network interfaces in internal mode are configured to masquerade packets from local machines to the Internet and receive packets from Internet and forward them back to local machines.

12.3. Customization

The above default configuration may not be fit for your setup. You can customize the configuration to suit your needs from the Networks area in the 'setup' section of the FreedomBox web interface.

12.3.1. PPPoE connections

If your ISP does not provide automatic network configuration via DHCP and requires you to connection via PPPoE. To configure PPPoE, remove any network connection existing on an interface and add a PPPoE connection. Here, optionally, provide the account username and password given by your ISP and activate the connection.

12.3.2. Connect to Internet via Wi-Fi

By default Wi-Fi devices attached during first boot will be configured as access points. They can be configured as regular Wi-Fi devices instead to connection to a local network or an existing Wi-Fi router. To do this, click on the Wi-Fi connection to edit it. Change the mode to Infrastructure instead of Access Point mode and IPv4 Addressing Method to Automatic (DHCP) instead of Shared mode. Then the SSID provided will mean the Wi-Fi network name you wish to connect to and passphrase will be the used to while making the connection.

12.3.2.1. Problems with Privacy Feature

NetworkManager used by FreedomBox to connect to the Wi-Fi networks has a privacy feature that uses a different identity when scanning for networks and when actually connecting to the Wi-Fi access point. Unfortunately, this causes problems with some routers that reject connections from such devices. Your connection won't successfully activate and disconnect after trying to activate. If you have control over the router's behaviour, you could also turn off the feature causing problem. Otherwise, the solution is to connect with a remote shell using SSH or Cockpit, editing a file /etc/NetworkManager/NetworkManager.conf and adding the line wifi.scan-rand-mac-address=no in the [device] section. This turns off the privacy feature.

Edit a file:

$ sudo nano /etc/NetworkManager/NetworkManager.conf

Add the following:

[device]
wifi.scan-rand-mac-address=no

Then reboot the machine.

12.3.3. Adding a new network device

When a new network device is added, network manager will automatically configure it. In most cases this will not work to your liking. Delete the automatic configuration created on the interface and create a new network connection. Select your newly added network interface in the add connection page.

  • Then set firewall zone to internal and external appropriately.

  • You can configure the interface to connect to a network or provide network configuration to whatever machine connects to it.
  • Similarly, if it is a Wi-Fi interface, you can configure it to become a Wi-FI access point or to connect to an existing access points in the network.

12.3.4. Configuring a mesh network

FreedomBox has rudimentary support for participating in BATMAN-Adv based mesh networks. It is possible to either join an existing network in your area or create a new mesh network and share your Internet connection with the rest of the nodes that join the network. Currently, two connections have to be created and activated manually to join or create a mesh network.

12.3.4.1. Joining a mesh network

To join an existing mesh network in your area, first consult the organizers and get information about the mesh network.

  1. Create a new connection, then select the connection type as Wi-Fi. In the following dialog, provide the following values:

    Field Name

    Example Value

    Explanation

    Connection Name

    Mesh Join - BATMAN

    The name must end with 'BATMAN' (uppercase)

    Physical Interface

    wlan0

    The Wi-Fi device you wish to use for joining the mesh network

    Firewall Zone

    External

    Since you don't wish that participants in mesh network to use internal services of FreedomBox

    SSID

    ch1.freifunk.net

    As provided to you by the operators of the mesh network. You should see this as a network in Nearby Wi-Fi Networks

    Mode

    Ad-hoc

    Because this is a peer-to-peer network

    Frequency Band

    2.4Ghz

    As provided to you by the operators of the mesh network

    Channel

    1

    As provided to you by the operators of the mesh network

    BSSID

    12:CA:FF:EE:BA:BE

    As provided to you by the operators of the mesh network

    Authentication

    Open

    Leave this as open, unless you know your mesh network needs it be otherwise

    Passphrase

    Leave empty unless you know your mesh network requires one

    IPv4 Addressing Method

    Disabled

    We don't want to request IP configuration information yet

    Save the connection. Join the mesh network by activating this newly created connection.
  2. Create a second new connection, then select the connection type as Generic. In the following dialog, provide this following values:

    Field Name

    Example Value

    Explanation

    Connection Name

    Mesh Connect

    Any name to identify this connection

    Physical Interface

    bat0

    This interface will only show up after you successfully activate the connection in first step

    Firewall Zone

    External

    Since you don't wish that participants in mesh network to use internal services of FreedomBox

    IPv4 Addressing Method

    Auto

    Mesh networks usually have a DHCP server somewhere that provide your machine with IP configuration. If not, consult the operator and configure IP address setting accordingly with Manual method

    Save the connection. Configure your machine for participation in the network by activating this connection. Currently, this connection has to be manually activated every time you need to join the network. In future, FreedomBox will do this automatically. You will now be able reach other nodes in the network. You will also be able to connect to the Internet via the mesh network if there is an Internet connection point somewhere in mesh as setup by the operators.

12.3.4.2. Creating a mesh network

To create your own mesh network and share your Internet connection with the rest of the nodes in the network:

  1. Follow the instructions as provided above in step 1 of Joining a mesh network but choose and fix upon your own valid values for SSID (a name for you mesh network), Frequency Band (usually 2.4Ghz), Channel (1 to 11 in 2.4Ghz band) and BSSID (a hex value like 12:CA:DE:AD:BE:EF). Create this connection and activate it.

  2. Follow the instructions as provided above in step 2 of Joining a mesh network but select IPv4 Addressing Method as Shared. This will provide automatic IP configuration to other nodes in the network as well as share the Internet connection on your machine (achieved using a second Wi-Fi interface, using Ethernet, etc.) with other nodes in the mesh network.

Spread the word about your mesh network to your neighbors and let them know the parameters you have provided when creating the network. When other nodes connect to this mesh network, they have to follow steps in Joining a mesh network but use the values for SSID, Frequency Band and Channel that you have chosen when you created the mesh network.

12.4. Advanced Network Operations

Cockpit provides many advanced networking features over those offered by FreedomBox. Both FreedomBox and Cockpit operate over Network Manager and are hence compatible with each other. Some of the functions provided by Cockpit include:

  • Set the maximum transmission unit (MTU) for a network connection
  • Change the hardware address (MAC address) of a network interface
  • Add more DNS servers and configure routing of a network connection
  • Creating bonded devices for highly available network interfaces
  • Creating bridge devices to join network interfaces for aggregating separate networks
  • Manage VLAN for creating virtual partitions in the physical network

networks-cockpit.png

12.5. Manual Network Operation

FreedomBox automatically configures networks by default and provides a simplified interface to customize the configuration to specific needs. In most cases, manual operation is not necessary. The following steps describe how to manually operate network configuration in the event that a user finds FreedomBox interface to insufficient for task at hand or to diagnose a problem that FreedomBox does not identify.

On the command line interface:

For text based user interface for configuring network connections:

nmtui

To see the list of available network devices:

nmcli device

To see the list of configured connections:

nmcli connection

To see the current status of a connection:

nmcli connection show '<connection_name>'

To see the current firewall zone assigned to a network interface:

nmcli connection show '<connection_name>' | grep zone

or

firewall-cmd --zone=internal --list-all
firewall-cmd --zone=external --list-all

To create a new network connection:

nmcli con add con-name "<connection_name>" ifname "<interface>" type ethernet
nmcli con modify "<connection_name>" connection.autoconnect TRUE
nmcli con modify "<connection_name>" connection.zone internal

To change the firewall zone for a connection:

nmcli con modify "<connection_name>" connection.zone "<internal|external>"

For more information on how to use nmcli command, see its man page. Also for a full list of configuration settings and type of connections accepted by Network Manager see:

https://developer.gnome.org/NetworkManager/stable/ref-settings.html

To see the current status of the firewall and manually operate it, see the Firewall section.

13. PageKite (Public Visibility)

13.1. What is PageKite?

PageKite makes local websites and services publicly accessible immediately without creating yourself a public IP address. It does this by tunneling protocols such as HTTPS or SSH through firewalls and NAT. Using PageKite requires an account on a PageKite relay service. One such service is https://pagekite.net.

A PageKite relay service will allow you to create kites. Kites are similar to domain names, but with different advantages and drawbacks. A kite can have a number of configured services. PageKite is known to work with HTTP, HTTPS, and SSH, and may work with some other services, but not all.

13.2. Using PageKite

  1. Create an account on a PageKite relay service.

  2. Add a kite to your account. Note your kite name and kite secret.
  3. In FreedomBox, go to the "Configure PageKite" tab on the Public Visibility (PageKite) page.

  4. Check the "Enable PageKite" box, then enter your kite name and kite secret. Click "Save settings".

  5. On the "Standard Services" tab, you can enable HTTP and HTTPS (recommended) and SSH (optional).
    • HTTP is needed to obtain the Let's Encrypt certificate. You can disable it later.
  6. On the Certificates (Let's Encrypt) page, you can obtain a Let's Encrypt certificate for your kite name.

14. Performance (System Monitoring)

Available since: version 20.9.7

Performance app allows you to collect, store and view information about utilization of the hardware. This can gives you basic insights into usage patterns and whether the hardware is overloaded by users and services.

Performance metrics are collected by Performance Co-Pilot and can be viewed using the Cockpit app. When this system app is installed and enabled, cockpit's graphs shows the past (up to one year at a time).

performance-one-week.png

15. Power

To restart or shut down FreedomBox, click the user dropdown menu on the top right of the page. After you select "Restart" or "Shut Down", you will be asked to confirm.

16. Secure Shell (SSH) Server

16.1. What is Secure Shell?

FreedomBox runs openssh-server server by default allowing remote logins from all interfaces. If your hardware device is connected to a monitor and a keyboard, you may login directly as well. Regular operation of FreedomBox does not require you to use the shell. However, some tasks or identifying a problem may require you to login to a shell.

16.2. Setting Up A User Account

16.2.1. FreedomBox First Log In: Admin Account

When creating an account in FreedomBox's web interface for the first time, this user will automatically have administrator capabilities. Admin users are able to log in using ssh (see Logging In below) and have superuser privileges via sudo.

16.2.2. Default User Account

  • Note: If you can access FreedomBox's web interface, then you don't need to do this. You can use the user account created in FreedomBox's web interface to connect to SSH.

The pre-built FreedomBox images have a default user account called "fbx". However the password is not set for this account, so it will not be possible to log in with this account by default.

There is a script included in the freedom-maker program, that will allow you to set the password for this account, if it is needed. To set a password for the "fbx" user:

1. Decompress the image file.

2. Get a copy of freedom-maker from https://salsa.debian.org/freedombox-team/freedom-maker/.

3. Run sudo ./bin/passwd-in-image <image-file> fbx.

4. Copy the image file to SD card and boot device as normal.

The "fbx" user also has superuser privileges via sudo.

16.3. Logging In

16.3.1. Local

To login via SSH, to your FreedomBox:

$ ssh fbx@freedombox

Replace fbx with the name of the user you wish to login as. freedombox should be replaced with the hostname or IP address of you FreedomBox device as found in the Quick Start process.

fbx is the default user present on FreedomBox with superuser privileges. Any other user created using FreedomBox and belonging to the group admin will be able to login. The root account has no password set and will not be able to login. Access will be denied to all other users.

fbx and users in admin group will also be able to login on the terminal directly. Other users will be denied access.

If you repeatedly try to login as a user and fail, you will be blocked from logging in for some time. This is due to libpam-abl package that FreedomBox installs by default. To control this behavior consult libpam-abl documentation.

16.3.2. SSH over Tor

If in FreedomBox you have enabled onion services via Tor, you can access your FreedomBox using ssh over Tor. On a GNU/Linux computer, install netcat-openbsd.

$ sudo apt-get install netcat-openbsd

Edit ~/.ssh/config to enable connections over Tor.

$ nano ~/.ssh/config

Add the following:

Host *.onion
  user USERNAME
  port 22
  ProxyCommand nc -X 5 -x 127.0.0.1:9050 %h %p

Replace USERNAME with, e.g., an admin username (see above).

Note that in some cases you may need to replace 9050 with 9150.

Now to connect to the FreedomBox, open a terminal and type:

$ ssh USERNAME@ADDRESS.onion

Replace USERNAME with, e.g., an admin username, and ADDRESS with the onion service address for your FreedomBox.

16.3.3. SSH Over Pagekite

If in FreedomBox you are using Pagekite to expose services to the Internet, you can access your FreedomBox using SSH over Pagekite. On a GNU/Linux computer install netcat-openbsd.

$ sudo apt-get install netcat-openbsd

Edit ~/.ssh/config to enable connections over Pagekite.

$ nano ~/.ssh/config

Add the following:

Host *.pagekite.me
  CheckHostIP no
  ProxyCommand /bin/nc -X connect -x %h:443 %h %p

Now to connect to FreedomBox, open a terminal and type:

$ ssh USERNAME@KITENAME.pagekite.me

Replace USERNAME with, e.g., an admin username, and KITENAME with your kite name provided by pagekite.net as configured in FreedomBox.

16.4. Becoming Superuser

After logging in, if you want to become the superuser for performing administrative activities:

$ sudo su

Make a habit of logging in as root only when you need to. If you aren't logged in as root, you can't accidentally break everything.

16.5. Changing Password

To change the password of a user managed by FreedomBox's web interface, use the change password page. However, the fbx default user is not managed by FreedomBox's web interface and its password cannot be changed through it.

To change password on the terminal, log in to your FreedomBox as the user whose password you want to change. Then, run the following command:

$ passwd

This will ask you for your current password before giving you the opportunity to set a new one.

17. Security

Press the Show security report button to see a report including the following:

  • Number of security vulnerabilities in installed version of FreedomBox.

  • Number of security vulnerabilities for each installed app.
  • Whether each installed app supports security sandboxing.
  • For each enabled app, the security sandbox coverage as a percentage.

17.1. Configuration

When the Restrict console logins option is enabled, only users in the admin group will be able to log in via console, secure shell (SSH) or graphical login. When this option is disabled, any user with an account on FreedomBox will be able to log in. They may be able to access some services without further authorization. This option should only be disabled if all the users of the system are well trusted. If you wish to use your FreedomBox machine also as a desktop and allow non-admin users to login via GUI, this option must be disabled. You can define the list of users belonging to admin group in the Users section.

Security.png

18. Service Discovery

Service discovery allows other devices on the network to discover your FreedomBox and services running on it. If a client on the local network supports mDNS, it can find your FreedomBox at <hostname>.local (for example: freedombox.local).

It also allows FreedomBox to discover other devices and services running on your local network.

Service discovery is not essential and works only on internal networks. It may be disabled to improve security especially when connecting to a hostile local network.

18.1. Troubleshooting

18.1.1. Unable to reach <hostname>.local

If <hostname>.local is not able to be reached, you may simply need to disable and re-enable the Service Discovery feature in FreedomBox. To do this, go to System -> Service Discovery, slide the toggle to the left position to disable it (it turns grey), followed by sliding it back to the right to re-enable it (it turns blue).

To do this you obviously need other means to reach your FreedomBox than <hostname>.local. See the Quick Start Guide for those.

19. Storage

Storage allows you to see the storage devices attached to your FreedomBox and their disk space usage.

FreedomBox can automatically detect and mount removable media like USB flash drives. They are listed under the Removable Devices section along with an option to eject them.

If there is some free space left after the root partition, the option to expand the root partition is also available. This is typically not shown, since expanding the root partition happens automatically when the FreedomBox starts up for the first time.

Storage.png

19.1. Advanced Storage Operations

Cockpit provides many advanced storage features over those offered by FreedomBox. Both FreedomBox and Cockpit operate over Udisks2 storage daemon and are hence compatible with each other. Some of the functions provided by Cockpit include:

  • Format a disk or partition with a fresh filesystem
  • Add, remove partitions or wipe the partition table
  • Create and unlock encrypted file systems
  • Create and manage RAID devices

storage-cockpit.png

20. Storage Snapshots

Snapshots allows you to create filesystem snapshots, and rollback the system to a previous snapshot.

  • Note: This feature requires a Btrfs filesystem. All of the FreedomBox stable disk images use Btrfs.

Snapshots

There are three types of snapshots:

  • boot: Taken when the system boots up
  • Software Installation (apt): Taken when software is installed or updated
  • Timeline: Taken hourly, daily, weekly, monthly, or yearly

The Timeline and Software Installation snapshots can be turned on or off, and you can limit the number of each type of Timeline snapshot. You can also set a percentage of free disk space to be maintained.

21. Software Updates

FreedomBox can automatically install security updates. On the Update page of the System section in FreedomBox web interface you can turn on automatic updates. This feature is enabled by default and there is no manual action necessary. It is strongly recommended that you have this option enabled to keep your FreedomBox secure.

Updates are performed every day at night according to you local time zone. You can set the time zone with Date & Time. If you wish to shutdown FreedomBox every day after use, keep it running at night once a week or so to let the automatic updates happen. Alternatively, you can perform manual updates as described below.

Note that once the updates start, it may take a long time to complete. During automatic update process that runs every night or during manual update process, you will not be able to install apps from FreedomBox web interface.

update.png

21.1. When Will I Get the Latest Features?

Although updates are done every day for security reasons, latest features of FreedomBox will not propagate to all the users. The following information should help you understand how new features become available to users.

Stable Users: This category of users include users who bought the FreedomBox Pioneer Edition, installed FreedomBox on a Debian stable distribution or users who downloaded the stable images from freedombox.org. As a general rule, only security updates to various packages are provided to these users. One exception to this rule is where FreedomBox service itself is updated when a release gains high confidence from developers. This means that latest FreedomBox features may become available to these users although not as quickly or frequently as testing users. If an app is available only in testing distribution but not in stable distribution, then that app will show up in the web interface but will not be installable by stable users. Some apps are also provided an exception to the rule of "security updates only" when the app is severely broken otherwise. Every two years, a major release of Debian stable happens with the latest versions of all the software packages and FreedomBox developers will attempt to upgrade these users to the new release without requiring manual intervention.

Testing Users: This category of users include users who installed FreedomBox on a Debian testing distribution or users who downloaded the testing images from freedombox.org. Users who use Debian testing are likely to face occasional disruption in the services and may even need manual intervention to fix the issue. As a general rule, these users receive all the latest features and security updates to all the installed packages. Every two weeks, a new version of FreedomBox is released with all the latest features and fixes. These releases will reach testing users approximately 2-3 days after the release.

Unstable Users: This category of users include users who installed FreedomBox on a Debian unstable distribution or users who downloaded the unstable images from freedombox.org. Users who use Debian unstable are likely to face occasional disruption in the services and may even need manual intervention to fix the issue. As a general rule, these users receive all the latest features to all the installed packages. Every two weeks, a new version of FreedomBox is released with all the latest features and fixes. Theses releases will reach unstable users on the day of the release. Only developers, testers and other contributors to the FreedomBox project should use the unstable distribution and end users and advised against using it.

21.2. Manual Updates from Web Interface

To get updates immediately and not wait until the end of the day, you may want to trigger updates manually. You can do this by pressing the Update now button in Manual update tab for Update page in System section. Note that this step is not necessary if you have enabled Auto-updates as every night this operation is performed automatically.

When installing apps you may receive an error message such as

Error installing packages: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem

This is typically caused by shutting down FreedomBox while it is installing apps, while performing daily updates or during some other operations. This situation can be rectified immediately by running manual update.

21.3. Manual Updates from Terminal

Some software packages may require manual interaction for updating due to questions related to configuration. In such cases, FreedomBox updates itself and brings in new knowledge necessary to update the package by answering configuration questions. After updating itself, FreedomBox acts on behalf of the user and updates the packages by answering the questions. Until FreedomBox has a chance to update the package, such packages should not be be updated manually. The manual update triggered from the web interface is already mindful of such packages and does not update them.

In some rare situations, FreedomBox itself might fail to update or the update mechanism might fall into a situation that might need manual intervention from a terminal. To perform manual upgrades on the terminal, login into FreedomBox on a terminal (if you have monitor and keyboard connected), via a web terminal (using FreedomBox/Manual/Cockpit) or using a remote secure shell (see Secure Shell section). Then run the following commands:

$ sudo su -
Password: <enter user password here>
# dpkg --configure -a
# apt update
# apt -f install
# unattended-upgrade --debug
# apt install freedombox
# apt update

If apt update asks for a confirmation to change Codename or other release information, confirm yes. If during update of freedombox package, if a question about overwriting configuration files is asked, answer to install new configuration files from the latest version of the package. This process will upgrade only packages that don't require configuration file questions (except for freedombox package). After this, let FreedomBox handle the upgrade of remaining packages. Be patient while new releases of FreedomBox are made to handle packages that require manual intervention.

If you want to go beyond the recommendation to upgrade all the packages on your FreedomBox and if you are really sure about handling the configuration changes for packages yourself, run the following command:

$ apt full-upgrade

21.4. Auto-Update to Next Stable Release

FreedomBox can automatically update itself when there is a new stable release of Debian. This update feature is recommended, and enabled by default for stable systems. Note that it also requires "Enable auto-update" to be enabled, and that there is 5 GB free space on the root partition.

In some special cases, such as advanced customization made to the system, the automatic update could fail. If you wish, you can disable it on the System -> Update page, by clearing the “Enable auto-update to next stable release” checkbox.

If you decide to stay on an older release, you should check DebianReleases#Production_Releases to see how long it will be supported by Debian security team. Note that older releases will not have new versions of FreedomBox, even through backports.

21.5. Manual Update to Next Stable Release

Auto-update is recommended for most users. However if you want to do the update manually, here are some tips:

  • Take backups of your apps' data before performing the update.
  • Create a system snapshot before you begin.
  • General instructions for upgrading Debian distribution are available.

  • Some packages are known to have prompts during upgrade, due to modified conffiles. It is recommended not to upgrade these packages manually, but rather to allow FreedomBox to handle their upgrade automatically. This applies to the following packages:

    • bind9
    • firewalld
    • janus
    • minetest-server
    • minidlna
    • mumble-server
    • radicale
    • roundcube-core
    • tt-rss

22. Users and Groups

You can grant access to your FreedomBox for other users. Provide the Username with a password and assign a group to it. Currently the groups

  • admin
  • bit-torrent
  • calibre
  • ed2k
  • feed-reader
  • freedombox-share
  • git-access
  • i2p
  • minidlna
  • syncthing
  • web-search
  • wiki

are supported.

The user will be able to log in to services that support single sign-on through LDAP, if they are in the appropriate group.

Users in the admin group will be able to log in to all services. They can also log in to the system through SSH and have administrative privileges (sudo).

A user's groups can also be changed later.

It is also possible to set an SSH public key which will allow this user to securely log in to the system without using a password. You may enter multiple keys, one on each line. Blank lines and lines starting with # will be ignored.

The interface language can be set for each user individually. By default, the language preference set in the web browser will be used.

A user's account can be deactivated, which will temporarily disable the account.

Hardware

FreedomBox zielt darauf ab, ein Unterhaltungselektronik-Gerät zu sein, das einfach zu installieren, zu unterhalten und zu verwenden ist. Das Projekt zielt nicht darauf ab, ein spezielles Gerät zu realisieren. Statt dessen planen wir existierende Hardware zu unterstützen/anzupassen.

Zusätzlich zur Unterstützung verschiedener Single-Board-Computer und anderer Geräte, unterstützt FreedomBox auch die Installation in einer virtuellen Maschine. Auch kann jede Debian-Maschine in eine FreedomBox durch die Installation des freedombox-setup Paket umgewandelt werden. Siehe das Handbuch für weitere Details.

1. Unterstützte Hardware

1.1. Empfohlene Hardware

FreedomBox Danube Edition
FreedomBox - Danube Edition
(basierend auf Cubietruck)

BeagleBone Black
BeagleBone Black

A20 OLinuXino Lime2
A20 OLinuXino Lime2

A20 OLinuXino MICRO
A20 OLinuXino MICRO

PC Engines APU
PC Engines APU

Debian
Debian

VirtualBox
VirtualBox

.

.

.

1.2. Auch Funktionierende Hardware

Diese Hardware funktioniert, ist aber nicht empfohlen aufgrund von Freiheits-, Kosten-Nutzen- oder anderer Bedenken:

Raspberry Pi 2
Raspberry Pi 2

Hinweis: Da FreedomBox noch in der Entwicklung ist, bedeutet Unterstützte Hardware, dass FreedomBox Images für die genannte Hardware realisiert werden und mindestens ein Entwickler berichtet hat, dass sie in ihren Grundfunktionen arbeitet.

2. Ziel-Hardware

2.1. Liste der Ziel-Hardware

Obwohl sich das Projekt auf die Unterstützung von bestimmten Geräten konzentriert, versuchen wir eine möglichst breite Vielzahl an Hardware zu unterstützen, die für die FreedomBox geeignet ist. Werfen Sie einen Blick auf die Liste der unterstützen Hardware für weitere Unterstützung.

2.2. Hardware Unterstützung hinzufügen

Wenn Sie Entwickler sind, sollten Sie erwägen, Hardware-Unterstützung für Ihr Gerät beizutragen, indem Sie Freedom Maker und FreedomBox Setup anpassen.

3. Pioneer Edition FreedomBox

Pioneer FreedomBox Home Servers are produced and sold by Olimex, a company which specializes in Open Source Hardware (OSHW). The kit includes pocket-sized server hardware, an SD card with the operating system pre-installed, and a backup battery which can power the hardware for 4-5 hours in case of outages. It sells for 69 euro. An optional storage add-on for high capacity hard disk (HDD) or solid-state drive (SSD) is also available from Olimex. By purchasing this product, you also support the FreedomBox Foundation's efforts to create and promote its free and open source server software.

Pioneer Edition FreedomBox Home Server Kit

3.1. Product Features

The Pioneer Edition FreedomBox Home Server Kit includes all the hardware needed for launching a FreedomBox home server on an Olimex A20-OLinuXino-LIME2 board:

  • the A20-OlinuXino-LIME2,

  • a custom metal case with a laser-engraved FreedomBox logo,

  • a high-speed 32GB micro SD card with the FreedomBox software pre-installed,

  • a backup battery,
  • a power adapter, and
  • an Ethernet cable.
  • an optional storage add-on for hard disk (HDD) or solid-state drive (SSD)

3.2. Recommended Hardware

This is the hardware recommended for all users who just want a turn-key FreedomBox, and don't want to build their own one.

(Building your own FreedomBox means some technical stuff like choosing and buying the right components, downloading the image and preparing the SD card).

3.3. Availability

The Pioneer Edition FreedomBox Home Server is the first commercially available version of FreedomBox.

3.4. Hardware Specifications

Pioneer Edition FreedomBox Home Server is based on A20-OLinuXino-LIME2 Rev.G.

  • Open Source Hardware (OSHW): Yes

  • CPU: Allwinner A20, ARM Cortex-A7 @ 1GHz dual-core
  • RAM: 1 GiB DDR3
  • Storage: 32GB class 10+ microSD card pre-loaded with FreedomBox

  • SATA: 1 SATA port 2.6 compliant 3Gb/s
  • USB: 2 USB 2.0 Hi-Speed host ports
  • Battery: 3.3V Li-Po, 1400mAh (4-5 hours of backup without additional devices connected via USB)
  • Ethernet: 10/100/1000, RJ45 (1 meter cable included)
  • Power adapter: 110-220 V input, 5V output, EU style (with optional UK or US sockets)
  • Power consumption: 1.5W and 5W depending on load (0.3A to 1A current)
  • Box: Custom metallic box with FreedomBox decal

Further information:

The kits run entirely on Free Software. They work with Kernel and u-boot from Debian repositories. Even the boot firmware in ROM called BROM is free software (GPLV2+).

3.5. Storage Add-on

You can order a storage add-on along with the Pioneer Edition FreedomBox Home Server. The storage add-on is a SATA disk drive enclosure case optionally with a hard disk or solid-state drive of size 128GB to 2000GB. If you have already purchased the Home Server without the add-on, you can order the add-on separately.

  • Olimex Store

  • Price: 9 EUR (without the hard disk, only for the case, you need to add your own HDD/SSD to it)
  • Price: 42 EUR (with 128GB Solid-State Drive)
  • Price: 69 EUR (with 512GB Solid-State Drive)
  • Price: 42 EUR (with 320GB Hard Disk)
  • Price: 53 EUR (with 500GB Hard Disk)
  • Price: 64 EUR (with 1000GB Hard Disk)
  • Price: 86 EUR (with 2000GB Hard Disk)

3.6. Download

The kits come with an SD card pre-loaded with FreedomBox. There's NO need to download images.

However, if you wish to reset your devices to a pristine state, then you can do so with the image provided. Follow the instructions on the download page to create a FreedomBox SD card and boot the device. Make sure to download the Pioneer Edition images. These SD card images are meant for use with the on-board SD card slot and won't work when used with a separate SD card reader connected via USB.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

3.7. Build Image

FreedomBox images for this hardware can be built using Freedom Maker.

3.8. Known Issues

  • The image that shipped with the kits uses a slightly modified u-boot from Debian and not stock Debian like the rest of FreedomBox. So, if you wish to get the source code, please use the FreedomBox team's u-boot repository.

3.9. Obtaining Source Code

After you purchase and receive your Pioneer Edition FreedomBox, you may want to obtain the source code of the software running in it. Continue reading this section for instructions.

FreedomBox is fully free software and you can obtain the source code to study, modify and distribute improvements.

3.9.1. From within FreedomBox

FreedomBox is made up of several software programs and you can obtain the source code to any of them. These instructions are similar to obtaining and building source code for Debian since FreedomBox is a pure blend of Debian. Using this process you can obtain the source code to the exact version of the package you are currently using in FreedomBox.

  1. To see the list of software packages installed on your FreedomBox, run the following in a terminal:

    dpkg -l
  2. To obtain the source code for any of those programs, then run:
    apt source <package_name>

    This requires that the file /etc/apt/sources.list file contains the information about the source code repositories. These are present by default on all FreedomBox images. If you have installed FreedomBox using a package from Debian, you need to ensure that source repositories are added in the file.

  3. To build the package from source code, first install its dependencies
    apt build-dep <package_name>

    Switch to the source directory created by the apt source command:

    cd <source_directory>
    Then build the package
     dpkg-buildpackage -rfakeroot -uc
  4. Install the package:
     dpkg -i ../<built_package>.deb

3.9.2. Other Ways to Obtain Source Code

  1. Source code for any of the packages can be browsed and searched using the web interface at sources.debian.org. For example, see the plinth package.

  2. Source code and pre-built binary package for any version of a package including historic versions can be obtained from snapshot.debian.org. For example, see the plinth package.

  3. You can also obtain the links to upstream project homepage, upstream version control, Debian's version control, changelog, etc. from the Debian tracker page for a project at tracker.debian.org. For example, see the tracker page for plinth package.

  4. You can build and install a package from its Debian's version control repository. For example,
     git clone https://salsa.debian.org/freedombox-team/freedombox.git
     cd freedombox
     apt build-dep .
     dpkg-buildpackage -rfakeroot -uc
     dpkg -i ../freedombox*.deb

3.9.3. Building Disk Images

You can also build FreedomBox disk images for various hardware platforms using the freedom-maker tool. This is also available as a Debian package and source code for it may be obtained using the above methods. Build instructions for creating disk images are available as part of the source code for freedom-maker package.

FreedomBox disk images are built and uploaded to official servers using automated Continuous Integration infrastructure. This infrastructure is available as source code too and provides accurate information on how FreedomBox images are built.

3.9.4. U-boot on Pioneer Edition Images

There is one minor exception to the u-boot package present on the hardware sold as FreedomBox Home Server Kits Pioneer Edition. It contains an small but important fix that is not part of Debian sources. The fork of the Debian u-boot source repository along with the minor change done by the FreedomBox is available as a separate repository. We expect this change to be available in upstream u-boot eventually and this repository will not be needed. This package can be built on a Debian armhf machine as follows (cross compiling is also possible, simply follow instructions for cross compiling Debian packages):

apt install git git-buildpackage
git clone https://salsa.debian.org/freedombox-team/u-boot.git
cd u-boot
pbuilder create --distribution=buster
gbp buildpackage --git-pbuilder

The u-boot Debian package will be available in u-boot-sunxi*.deb. This package will contain

mkdir temp
dpkg -x u-boot-suxi*.deb temp
unxz <lime2_image_built_with_freedom_maker>
dd if=temp/usr/lib/u-boot/A20-OLinuXino-Lime2/u-boot-sunxi-with-spl.bin of=<lime2.img> seek=8 bs=1k conv=notrunc

The resulting image will have the modified u-boot in it.

3.10. Power and reset buttons

The Pioneer Edition Kit has 3 undocumented buttons for RESET, BOOT, and POWER. They are legacy features originally designed to be used with Android operating system but are useful in particular cases.

Pioneer Edition Undocumented buttons

Warning: Excessive force will break the buttons. The three buttons are not intended to be pushed regularly, which is why they are fragile and not easily to push.

More details in our Forum.

4. A20 OLinuXino Lime2

A20 OLinuXino Lime2

Olimex's A20 OLinuXino Lime2 is a fully Open Source Hardware (OSHW) single board computer. This means that the designer is actively helping people using the platform for their own designs, and supports them in adding hardware functionality and production advice. This is a part of freedom that is often overlooked, but very much aligned with the FreedomBox goals. It uses the Allwinner A20 Dual Core ARM processor.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

4.1. Similar Hardware

The following similar hardware will also work well with FreedomBox.

4.2. Download

FreedomBox SD card images are available for this device. Follow the instructions on the download page to create a FreedomBox SD card and boot the device. These SD card images are meant for use with the on-board SD card slot and won't work when used with a separate SD card reader connected via USB.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

4.3. Availability

  • Price: 45 EUR (A20 OLinuXino Lime2)
  • Price: 55 EUR (A20 OLinuXino Lime2 4GB)
  • Olimex Store

4.4. Hardware

  • Open Source Hardware (OSHW): Yes

  • CPU: Allwinner A20, ARM Cortex-A7 @ 1GHz dual-core
  • RAM: 1 GiB DDR3
  • Storage: 4 GB NAND flash built-in (only on 4GB model), 1x microSD slot
  • Architecture: armhf
  • Ethernet: 10/100/1000, RJ45
  • WiFi: None, use a USB WiFi device

  • SATA: 1x port

4.5. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

  • Boot Firmware: BROM (GPLV2+)

4.6. Known Issues

5. A20 OLinuXino MICRO

A20 OLinuXino MICRO

Olimex's A20 OLinuXino MICRO is a fully Open Source Hardware (OSHW) single board computer. This means that the designer is actively helping people using the platform for their own designs, and supports them in adding hardware functionality and production advice. This is a part of freedom that is often overlooked, but very much aligned with the FreedomBox goals. It uses the Allwinner A20 Dual Core ARM processor.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

5.1. Similar Hardware

The following similar hardware will also work well with FreedomBox.

5.2. Download

FreedomBox MicroSD card images are available for this device. Follow the instructions on the download page to create a FreedomBox MicroSD card and boot the device. These MicroSD card images are meant for use with the on-board MicroSD card slot and won't work on the SD card slot or when using a separate MicroSD card reader connected via USB.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

5.3. Availability

  • Price: 50 EUR (A20 OLinuXino MICRO)
  • Price: 63 EUR (A20 OLinuXino MICRO 4GB)
  • Olimex Store

5.4. Hardware

  • Open Source Hardware (OSHW): Yes

  • CPU: Allwinner A20, ARM Cortex-A7 @ 1GHz dual-core
  • RAM: 1 GiB DDR3
  • Storage: 4 GB NAND flash built-in (only on 4GB model), 1x microSD slot
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: None, use a USB WiFi device

  • SATA: 1x port

5.5. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

  • Boot Firmware: BROM (GPLV2+)

5.6. Known Issues

  • Not visible on local network
  • When booting the 'stable' image (made on 2017-06-18) the board does not automatically get an IP address from the router's DHCP server over ethernet. Booting the 'testing' image (2018-06) the board does get an IP address. Tested on MICRO hardware revision J. see also: https://www.olimex.com/forum/index.php?topic=5839.msg24167#msg24167

6. APU

PC Engines APU 1D

PC Engines APU 1D is a single board computer with 3 Gigabit ethernet ports, a powerful AMD APU and Coreboot firmware. FreedomBox images built for AMD64 machines are tested to work well for it.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

6.1. Similar Hardware

Although untested, the following similar hardware is also likely to work well with FreedomBox.

6.2. Download

FreedomBox disk images for this hardware are available. Follow the instructions on the download page to create a FreedomBox SD card, USB disk, SSD or hard drive and boot into FreedomBox. Pick the image meant for all amd64 machines.

An alternative to downloading these images is to install Debian on the APU and then install FreedomBox on it.

6.3. Networking

The first network port, the left most one in the above picture, is configured by FreedomBox to be an upstream Internet link and the remaining 2 ports are configured for local computers to connect to.

6.4. Availability

6.5. Hardware

  • Open Hardware: No
  • CPU: AMD G series T40E

  • RAM: 2 GB DDR3-1066 DRAM
  • Storage: SD card, External USB
  • Architecture: amd64
  • Ethernet: 3 Gigabit Ethernet ports
  • WiFi: None, use a USB WiFi device

  • SATA: 1 m-SATA and 1 SATA

6.6. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

  • Boot firmware: Coreboot

7. Cubietruck

7.1. FreedomBox Danube Edition

FreedomBox Danube Edition

FreedomBox Danube Edition is a custom casing around Cubietruck and an SSD-hard drive.

7.2. Cubietruck / Cubieboard3

Cubietruck (Cubieboard3) is a single board computer with very good performance compared to many other boards. FreedomBox images are built for this device.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

7.3. Download

FreedomBox SD card images are provided for this hardware. These SD card images are meant for use with the on-board SD card slot and do not work when used with a separate SD card reader connected via USB.

An alternative to downloading these images is to install Debian on the Cubietruck and then install FreedomBox on it.

7.4. Availability

Cubietruck / Cubieboard3

7.5. Hardware

  • Open Hardware: No
  • CPU: Allwinner A20, ARM Cortex-A7 @ 1GHz dual-core
  • RAM: 2 GiB DDR3 @ 480 MHz
  • Storage: 8 GB NAND flash built-in, 1x microSD slot
  • Architecture: armhf
  • Ethernet: 10/100/1000, RJ45
  • WiFi: Broadcom BCM4329/BCM40181 (no free WiFi drivers + firmware available)

  • SATA: 1x 2.0 port

7.6. Non-Free Status

  • Non-free blobs required: ?
  • WiFi: no free WiFi drivers + firmware available

7.7. Known Issues

  • The on-board WiFi does not work with free software. A separate USB WiFi device is recommended.

8. Cubieboard 2

Cubieboard 2

The Cubieboard 2 is a single board computer based on the Allwinner A20 processor. It doesn't require any non-free firmware to run FreedomBox, and Wifi capability can be added via a USB adaptor if needed. This board is available in two versions, one with on-board flash and a microSD slot, and a version with two microSD card slots.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

8.1. Download

FreedomBox SD card images are available for this device. Follow the instructions on the download page to create a FreedomBox SD card and boot the device.

8.2. Availability

8.3. Hardware

  • CPU: ARM Cortex A7 Dual-Core
  • RAM: 1GB DDR3 @960M
  • Storage: 4GB internal NAND flash, up to 64GB on uSD slot
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: None, use a USB WiFi device

  • SATA: Yes

8.4. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

9. Beagle Bone Black

Beagle Bone Black

Beagle Bone Black (Revision C.1) is an Open Source Hardware (OSHW) single board computer. This means that the designer is actively helping people using the platform for their own designs, and supports them in adding hardware functionality and production advice. This is a part of freedom that is often overlooked, but very much aligned with the FreedomBox goals. FreedomBox images are built and tested for this device.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

9.1. Download

FreedomBox SD card images are available for this device. Follow the instructions on the download page to create a FreedomBox SD card and boot the device.

Note: This image is for BeagleBone Black (Revision C.1) only. It will not work on the BeagleBone Green, and also not on the Revisions A & B.

An alternative to downloading these images is to install Debian on the BeagleBone and then install FreedomBox on it.

9.2. Availability

9.3. Hardware

  • Open Source Hardware (OSHW): Yes

  • CPU: AM335x 1GHz ARM Cortex-A8

  • RAM: 512MB DDR3L 800 Mhz
  • Storage: Onboard 4GB, 8bit Embedded MMC and microSD
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: None, use a USB WiFi device

  • SATA: None

9.4. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

10. pcDuino3

LinkSprite pcDuino3S

LinkSprite pcDuino3S is a single board computer running on Allwinner A20 and sold with a good case. FreedomBox images are built and tested for this device.

Note: The FreedomBox logo is simply a sticker on top of device brought from store.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

10.1. Similar Hardware

Although untested, the following similar hardware is also likely to work well with FreedomBox.

10.2. Download

FreedomBox disk images for this hardware are available. Follow the instructions on the download page to create a FreedomBox SD card, USB disk, SSD or hard drive and boot into FreedomBox. Pick the image meant for pcduino3.

An alternative to downloading these images is to install Debian on the APU and then install FreedomBox on it.

10.3. Availability

10.4. Hardware

  • Open Hardware: No
  • CPU: AllWinner A20 SoC, 1GHz ARM Cortex A7 Dual Core

  • RAM: 1 GB
  • Storage: SD card, 4 GB onboard flash
  • Architecture: armhf
  • Ethernet: 10/100 Mbps
  • WiFi: Built-in WiFi requires non-free firmware, use a USB WiFi device instead

  • SATA: 1 SATA host socket

10.5. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Requires non-free firmware

  • Boot Firmware: BROM (GPLV2+)

Include: Nothing found for "## BEGIN_INCLUDE"!

11. Debian

FreedomBox ist ein "pure blend" von Debian. Dies bedeutet dass alles von FreedomBox in den Debian Paketen zur Verfügung steht. Es bedeutet auch, dass jedes Gerät das mit Debian läuft in eine FreedomBox umgewandelt werden kann.

Diese Seite beschreibt den Prozess wie man FreedomBox auf einem Debian-System installiert. Aktuell arbeitet FreedomBox auf Debian Testing (Stretch) und Unstable (Sid).

Setzen Sie eine frische Debian Installation ein

Die Installation der FreedomBox verändert Ihr Debian System in umfangreicher und wichtiger Weise. Dies beinhaltet die Installing einer Firewall und die Neuerstellung von Server Zertifikaten. Es ist deshalb empfohlen dass Sie FreedomBox auf einem frischen/neuen Debian System installieren anstatt auf einem existierenden Setup.

nutzen Sie "fbx" als Login-Nname

Wenn Sie eine erstes Benutzerkonto erstellen, nutzen Sie "fbx" als Login-Name. (Sobald der FreedomBox Setup abgeschlossen ist werden alle Benutzerkonten außer "fbx" durch pam_access ausgesperrt werden. Dies beeinflusst auch den sudo Zugriff.)

11.1. Auf Debian installieren

  1. Beachten Sie den Abschnitt zur Fehlerbehebung weiter unten; er enthält Tips und Work-arounds die bei der Installation hilfreich sein können.
  2. Installieren Sie Debian 10 (Buster) oder Unstable (Sid) auf Ihre Hardware.

  3. Aktualisieren Sie Ihre Paketliste.
    $ sudo apt-get update
  4. Installieren Sie das freedombox Package.

    $ sudo DEBIAN_FRONTEND=noninteractive apt-get install freedombox
  5. Während der Installation Sie bekommen einen Geheimkode, dass man bei der Konfigurationsprozess zufügen braucht. Zeichnen Sie dies auf. Der Geheimkode kann später im Datei /var/lib/plinth/firstboot-wizard-secret gelesen werden.

  6. Nach dem zweiten Neustart können Sie beginnen Ihre FreedomBox zu benutzen.

11.2. Fehlerbehebungen

  1. FreedomBox unterstützt keine Netzwerkkonfiguration über /etc/network/interfaces und sie wird keine non-loopback Interfaces die dort definiert sind unterstützen. (Siehe Fehler #797614.) Zukünftige Versionen von freedombox-setup werden diese Datei automatisch leeren; für den Moment editieren Sie sie per Hand und stellen sicher dass sie nur folgendes enthält:

    auto lo
    iface lo inet loopback

    Wenn Sie den Installationsprozess bereits abgeschlossen haben ohne diesen Schritt durchzuführen, müssen Sie jetzt die Datei /etc/network/interfaces entsprechend anpassen und den Rechner neustarten. Anschließend werden die Netzwerke die durch den setup Schritt oben definiert worden sind konfiguriert werden. Netzwerk-Schnittstellen werden dann in der Firewall-Zone internal oder external stehen. Dies ist wesentlich damit das FreedomBox Web-Interface von anderen Geräten im Netzwerk erreichbar ist. Man kann die Netzwerkverbindungen über das nmtui Kommando, falls nötig, bearbeiten.

12. VirtualBox

VirtualBox

This page will help you get started with using FreedomBox on a virtual machine using VirtualBox. While VirtualBox images are primarily used for testing and development, they can also be used for regular use if you have spare resources on one of your machines. This setup is useful if:

  • You don't own one of the supported hardware devices.

  • You don't use Debian GNU/Linux as your operating system.
  • You don't want to disturb your Debian installation to try out FreedomBox.

Prebuilt FreedomBox images for VirtualBox are routinely made available in VirtualBox's own VDI image file format. They contain a Debian GNU/Linux operating system and an installation of FreedomBox with all dependencies ready to run on any OS supported by VirtualBox (Windows, Linux, Macintosh, and Solaris).

A more adventurous alternative to downloading one of these images is to install Debian on VirtualBox and then install FreedomBox on it.

VirtualBox itself is available from https://www.virtualbox.org/ (or your distribution's package manager).

12.1. Download

Follow the instructions on the download page to download and verify a VirtualBox image. The latest images are available on freedombox.org.

12.2. Creating a Virtual Machine

  1. Decompress the downloaded VDI image (tool for Windows, Mac).

  2. Create a new VM in the VirtualBox UI with OS type Linux and Version Debian (32/64-bit according to the downloaded image).

VirtualBox Name and OS dialog

  1. In the Hard disk dialog choose Use an existing virtual hard disk file and select the .vdi file you extracted in step 1.

VirtualBox Hard disk dialog

  1. When created, go to the virtual machine's Settings -> [Network] -> [Adapter 1]->[Attached to:] and choose the network type your want the machine to use according to the explanation in Network Configuration below. The recommended type is the Bridged adapter option, but be aware that this exposes the FreedomBox's services to your entire local network.

VirtualBox recommended network setting

Note: It is important to make sure that you have provided the correct network interface in the above step. For example, if the virtual machine is running on a laptop connected to a Wi-Fi network, then the wireless interface (starts with wlp) must be chosen as shown in the screenshot.

12.3. First Boot

When satisfied with the VM settings click the start button in the VirtualBox UI and your new FreedomBox will boot.

The console of the VM will show the textual screen below when finished booting, from here most interaction with FreedomBox will be through the web interface in a browser.

FreedomBox console after booting successfully

If everything went well so far, you should be able to access the web interface of FreedomBox by pointing a browser on the host machine to https://freedombox.local.

In case freedombox.local cannot be resolved, you need to find out your FreedomBox's IP address as described in Finding out the IP address of the virtual machine. Then access this IP from a web browser which is on the same network as the VM (for example, the host). If all is well, you are now presented with a welcome message and invited to complete the first boot process.

FreedomBox welcomes you to the first boot

This mainly consist of creating an administrative user for the system.

12.4. Using

See the FreedomBox usage page for more details.

You can log in to the Debian GNU/Linux system as the user created during FreedomBox first boot on the VirtualBox console or remotely via ssh.

After logging in, you can become root with the command sudo su.

12.5. Build Image

If you wish to build your own images instead of downloading available images, it can be done using Freedom Maker.

12.6. Tips & Troubleshooting

12.6.1. Network Configuration

VirtualBox provides many types of networking options. Each has its advantages and disadvantages. For more information about how various networking types work in VirtualBox, see VirtualBox's networking documentation. https://www.virtualbox.org/manual/ch06.html

For a simple setup, it is recommended that you use a single network interface in your guest machine. This will make the first boot script automatically configure that interface as an internal network with automatic network configuration. Inside the guest machine, the networking is configured automatically and all the services are made available on this network interface. For more information on how networks are configured by default in FreedomBox, see Networks section.

What remains is to make those services available to the host machine or to other machines in the network. You must then choose one of the following types of networking for the network interface on your guest machine. To set a particular type of network for the guest's network adapter, go to the guest VM's settings then the network options and then select the adapter you wish to configure. There, set the network type from the available list of networks.

  1. First and the recommended option is to use the Bridged type of network. This option exposes the guest machine to the same network that host network is connected to. The guest obtains network configuration information from a router or DHCP server on the network. The guest will appear as just another machine in the network. A major advantage of this of setup is that the host and all other machines in the network will be able to access the services provided by guest without requiring any further setup. The only drawback of this approach is that if the host is not connected to any network, the guest's network will remain unconfigured making it inaccessible even from the host.

  2. Second method is Host only type of networking. With a guest's network interface configured in this manner, it will only be accessible from the host machine. The guest will not able access any other machine but the host, so you do not have internet access on the guest. All services on the guest are available to the host machine without any configuration such as port forwarding.

  3. The third option is to use the NAT type of network. This the networking type that VirtualBox assigns to a freshly created virtual machine. This option works even when host is not connected to any network. The guest is automatically configured and is able to access the internet and local networks that host is able to connect to. However, the services provided by the guest require port forwarding configuration setup to be available outside.

    To configure this go to VM settings -> [Network] -> [Adapter] -> [Port Forwarding]. Map a port such as 2222 from host to guest port 22 and you will be able to ssh into FreedomBox from host machine as follows:

     ssh -p 2222 fbx@localhost

    Map 4443 on host to 443 on the guest. This make FreedomBox HTTPS service available on host using the URL https://localhost:4443/ You will need to add a mapping for each such services from host to guest.

  4. The final option is to create two network interfaces, one host only and one NAT type. This way you can access the guest without any additional configuration, and you have internet access on the guest. The guest will be invisible to any other machines on the network.

Summary of various network types:

-

Guest accessible from other machines

Guest accessible from host

Works without port forwarding

Works without host connected to network

Guest has internet access

Bridged

(./)

(./)

(./)

{X}

(./)

Host only

{X}

(./)

(./)

(./)

{X}

NAT

(./)

(./)

{X}

(./)

(./)

NAT and Host

{X}

(./)

(./)

(./)

(./)

12.6.2. Finding out the IP address of the virtual machine

This depends on the network configuration you chose. With a bridged adapter, your virtual machine gets its IP address from the DHCP server of your network, most likely of your Router. You can try the first couple of IP addresses or check your router web interface for a list of connected devices.

If you chose host-only adapter, the IP address is assigned by the DHCP server of your VirtualBox network. In the VirtualBox Manager, go to File -> Preferences -> Network -> Host-only Networks. You can see and edit the DHCP address range there, typically you get assigned addresses close to the Lower Address Bound.

Another possibility of finding the IP address is to login via the VirtualBox Manager (or similar software). The FreedomBox images do not have any default user accounts, so you need to set an initial user and password using the passwd-in-image script.

See also QuickStart for instructions on how to scan your network to discover the IP of the VM.

12.6.3. Networking Problems with macchanger

The package macchanger can cause network problems with VirtualBox. If you have a valid IP address on your guest's host network adapter (like 192.168.56.101) but are not able to ping or access the host (like 192.168.56.1), try uninstalling macchanger:

$ dpkg --ignore-depends=freedombox-setup --remove macchanger 

You might have to manually remove the script /etc/network/if-prep-up/macchanger. If Debian complains about unmet dependencies when you use a package manager (apt-get, aptitude, dpkg), try to remove 'macchanger' from the dependencies of 'freedombox-setup' in the file /var/lib/dpkg/status.

12.6.4. Mounting Images Locally

If you want to mount images locally, use the following to copy built images off the VirtualBox:

$ mkdir /tmp/vbox-img1 /tmp/vbox-root1
$ vdfuse -f freedombox-unstable_2013.0519_virtualbox-i386-hdd.vdi /tmp/vbox-img1/
$ sudo mount -o loop /tmp/vbox-img1/Partition1 /tmp/vbox-root1
$ cp /tmp/vbox-root1/home/fbx/freedom-maker/build/freedom*vdi ~/
$ sudo umount /tmp/vbox-root1
# $ sudo umount /tmp/vbox-img1 # corruption here.

12.6.5. Fixing the time after suspend and resume

The virtual machine loses the correct time/date after suspending and resuming. One way to fix this is to create a cron-job that restarts the time service ntp. You can add a crontab entry as root to restart ntp every 15 minutes by typing 'crontab -e' and adding this line:

*/15 * *   *   *     /etc/init.d/ntp restart

Do not restart this service too often as this increases the load of publicly and freely available NTP servers.

12.6.6. UUID collision in VB

Whenever this happens VirtualBox shows following error message: Cannot register the hard disk A with UUID ... because a hard disk B with UUID ... already exists in the media registry

Creating several VMs from the same image causes collisions due to ID's (hostname, IP, UUID, etc) that are expected to be universally unique. Most can be handeled operating the running VM. But VirtualBox complains before that (at the very creation of the VM) about the hard disk's UUID. This is usual stuff when you develop/test e.g. FreedomBox.

You can change a clone's UUID in the terminal as follows:

$ VBoxManage internalcommands sethduuid path/to/the/hd/vdi/file

13. Pine A64+

Pine 64+

Pine A64+ is an affordable single board computer with good performance.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

13.1. Similar Hardware

  • Both 1GB and 2GB versions of Pine A64+ are supported with the same FreedomBox image.

  • There is a separate Pine A64-LTS image.

13.2. Download

FreedomBox SD card images for this hardware are available. Follow the instructions on the download page to create a FreedomBox SD card and boot into FreedomBox. Pick the image meant for Pine A64+.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

13.3. Availability

13.4. Hardware

  • Open Source Hardware (OSHW): No
  • CPU: Allwinner A64, Quad-core ARM Cortex A53 64-bit processor
  • RAM: 3 variants - 512 MB (not recommended), 1 GB and 2 GB (recommended)
  • Storage: SD card, eMMC (module sold separately but not tested with FreedomBox)

  • Architecture: arm64
  • Ethernet: Gigabit Ethernet port
  • Battery: Supports battery backup using a Li-Po battery
  • WiFi: None, use a USB WiFi device

  • SATA: None

13.5. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

14. Banana Pro

Banana Pro

LeMaker Banana Pro is an updated version of its predecessor Banana Pi.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

14.1. Download

FreedomBox SD card images for this hardware are available. Follow the instructions on the download page to create a FreedomBox SD card and boot into FreedomBox. Pick the image meant for Banana Pro.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

14.2. Hardware

  • Open Source Hardware (OSHW): No
  • CPU: Allwinner A20, Dual-core ARM Cortex A7 processor
  • RAM: 3 variants - 1 GB
  • Storage: SD card
  • Architecture: armhf
  • Ethernet: 10/100/1000 Mbps
  • Battery: No
  • WiFi: WiFi 802.11 b/g/n 2.4GHz (not tested with FreedomBox)

  • SATA: SATA 2.0 (2.5 inch SSD or HDD recommended)

14.3. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Unknown

15. Orange Pi Zero

Orange Pi Zero

Orange Pi Zero is a single board computer available at very low price. It uses the Allwinner H2 SoC, and has 256MB/512MB DDR3 SDRAM. It doesn't require any non-free firmware to run FreedomBox. However, the onboard Wi-Fi module needs proprietary firmware to work. The board is available in two versions: with 256MB RAM and 512MB RAM. The version with 512 MB RAM is recommended for FreedomBox. Even then, FreedomBox is expected to gracefully run only a small number of services.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

15.1. Download

FreedomBox SD card images are available for this device. Follow the instructions on the download page to create a FreedomBox SD card and boot the device.

15.2. Availability

15.3. Hardware

  • CPU: ARM Cortex-A7 Quad-Core (Allwinner H2)
  • RAM: 256MB/512MB DDR3 SDRAM
  • Storage: Up to 32GB on uSD slot, 2MB SPI Flash
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: Onboard 802.11 b/g/n, use a USB WiFi device

15.4. Non-Free Status

  • Non-free blobs required: No (without Wi-Fi)
  • Wi-Fi: no free Wi-Fi drivers + firmware available

16. RockPro64

RockPro64

Pine64's RockPro64 is a powerful single board computer. It uses the Rockchip RK3399 Hexa Core ARM64 processor. FreedomBox images are built and tested for this device.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

16.1. Download

Before downloading and using FreedomBox you need to ensure that latest u-boot based firmware is installed into the SPI flash chip. See instructions on how to write u-boot firmware into SPI flash. The gist is that you download and write an image to an SD card. Boot with SD card and wait for white LED blinking to stop. After that power off, remove the SD card and proceed with FreedomBox download.

FreedomBox images meant for all "arm64" hardware work well for this device. However, u-boot firmware must be present in SPI flash (or on a separate SD card, which is not explained here). Follow the instructions on the download page to create a FreedomBox SD card and boot the device. These images also work well for onboard eMMC, USB 2.0 and USB 3.0 disk drives. The process for preparing USB disk drives is same as for an SD card. For eMMC, boot the board using any OS and then write the image to the eMMC similar to writing to SD card.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

16.2. Availability

16.3. Hardware

  • Open Source Hardware (OSHW): No
  • CPU: Rockchip RK3399 SOC (2x Cortex A72@1.8Ghz, 4x Cortex A53@1.4Ghz)

  • GPU: Mali T860 MP4 GPU
  • RAM: 2 GiB or 4 GiB LPDDR4
  • Storage: eMMC module slot, microSD slot, 16 MiB SPI Flash
  • USB: 2x USB 2.0, 1x USB 3.0, 1x USB-C
  • Expansion slot: 1x PCIe 4x slot (NVMe disks, etc.)
  • Architecture: arm64
  • Ethernet: 10/100/1000, RJ45
  • WiFi: None, use a USB WiFi device

16.4. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

16.5. Known Issues

  • FreedomBox on NVMe disk has not been tested.

17. Rock64

Rock64

Pine64's Rock64 is a powerful single board computer. It uses the Rockchip RK3328 Quad Core ARM64 processor. FreedomBox images are built and tested for this device.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

17.1. Download

Before downloading and using FreedomBox you need to ensure that latest u-boot based firmware is installed into the SPI flash chip. Download the latest u-boot to write to SPI flash and then see instructions on how to write u-boot firmware into SPI flash. The gist is that you download and write an image to an SD card. Boot with SD card and wait for white LED to blink continuously. After that power off remove SD card and proceed with FreedomBox download.

FreedomBox images meant for all "arm64" hardware work well for this device. However, u-boot firmware must present in SPI flash (or on a separate SD card, which is not explained here). Follow the instructions on the download page to create a FreedomBox SD card and boot the device. These images also work well for eMMC disk which an optional attachment to this board and disk drives in USB 2.0 ports (but not in the USB 3.0 port). The process for preparing them is same as for an SD card.

An alternative to downloading these images is to install Debian on the device and then install FreedomBox on it.

17.2. Availability

  • Price: 25 USD (1GB)
  • Price: 35 USD (2GB)
  • Price: 45 USD (4GB)
  • Pine64 Store

17.3. Hardware

  • Open Source Hardware (OSHW): No
  • CPU: Rockchip RK3328 Quad-Core SOC (4x Cortex A53 @ 1.5Ghz)
  • GPU: Mali 450MP2
  • RAM: 1 GiB or 2 GiB or 4 GiB LPDDR3
  • Storage: eMMC module slot, microSD slot, 16 MiB SPI Flash
  • USB: 2x USB 2.0, 1x USB 3.0
  • Architecture: arm64
  • Ethernet: 10/100/1000, RJ45
  • WiFi: None, use a USB WiFi device

17.4. Non-Free Status

  • Non-free blobs required: No
  • WiFi: Not available

17.5. Known Issues

  • FreedomBox does not work when booted from USB 3.0 port (but works from eMMC, SD card or USB 2.0 disk).

  • FreedomBox does not work when booted form the top USB 2.0 port with some u-boot firmware versions (the one listed above). It only works with the bottom USB 2.0 port (the one closer to the board).

18. Raspberry Pi 2 Model B

Raspberry Pi 2

Raspberry Pi 2 (Model B ) is a popular single board computer developed with the intention of promoting teaching of basic computer science in schools. It is a successor to Raspberry Pi Model B+ with much faster processor and more RAM. FreedomBox images are built and tested for it.

Please do not expect any output on a monitor connected via HDMI to this device as it does not display anything beyond the message 'Starting kernel...'. See the Quick Start page to access and control your FreedomBox from network.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

18.1. Download

FreedomBox SD card images for this hardware are available. Follow the instructions on the download page to create a FreedomBox SD card and boot into FreedomBox.

18.2. Availability

18.3. Hardware

  • Open Hardware: No
  • CPU: 900 MHz quad-core ARM Cortex-A7
  • RAM: 1 GB
  • Storage: MicroSD card slot
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: None, use a USB WiFi device

  • SATA: None

18.4. Non-Free Status

  • Non-free blobs required: boot firmware
  • WiFi: Not available

19. Raspberry Pi 3 Model B

Raspberry Pi 3 Model B

Raspberry Pi 3 Model B is a popular single board computer developed with the intention of promoting teaching of basic computer science in schools. It is a successor to Raspberry Pi 2 Model B with a 64-bit processor and on-board Wi-Fi. FreedomBox "stable" and "testing" images are available for Raspberry Pi 3 Model B.

Please do not expect any output on a monitor connected via HDMI to this device as it does not display anything beyond the message 'Starting kernel...'. See the Quick Start page to access and control your FreedomBox from network.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

19.1. Download

FreedomBox SD card images for this hardware are available. Download the "stable" or "testing" image for Raspberry Pi 3 Model B. Follow the instructions on the download page to create a FreedomBox SD card and boot into FreedomBox.

19.2. Availability

19.3. Hardware

  • Open Hardware: No
  • CPU: 1.2GHz 64-bit quad-core ARMv8 CPU
  • RAM: 1 GB
  • Storage: MicroSD card slot
  • Architecture: armhf
  • Ethernet: 10/100, RJ45
  • WiFi: 802.11n but requires non-free firmware, instead use a USB WiFi device

  • SATA: None

19.4. Non-Free Status

  • Non-free blobs required: boot firmware
  • WiFi: Requires non-free firmware

20. Raspberry Pi 3 Model B+

Raspberry Pi 3 Model B+

Raspberry Pi 3 Model B+ is a popular single board computer developed with the intention of promoting teaching of basic computer science in schools. It is a successor to Raspberry Pi 3 Model B with better Ethernet and a 5Ghz Wi-Fi. FreedomBox "stable" and "testing" images are available for Raspberry Pi 3 Model B+.

Please do not expect any output on a monitor connected via HDMI to this device as it does not display anything beyond the message 'Starting kernel...'. See the Quick Start page to access and control your FreedomBox from network.

Important: Read general advice about hardware before building a FreedomBox with this single board computer.

20.1. Download

FreedomBox SD card images for this hardware are available. Download the "stable" or "testing" image for Raspberry Pi 3 Model B+. Follow the instructions on the download page to create a FreedomBox SD card and boot into FreedomBox.

20.2. Availability

20.3. Hardware

  • Open Hardware: No
  • CPU: 1.4GHz 64-bit quad-core ARMv8 CPU
  • RAM: 1 GB
  • Storage: MicroSD card slot
  • Architecture: armhf
  • Ethernet: 10/100/1000, RJ45
  • WiFi: 802.11ac but requires non-free firmware, instead use a USB WiFi device

  • SATA: None

20.4. Non-Free Status

  • Non-free blobs required: boot firmware
  • WiFi: Requires non-free firmware

21. Raspberry Pi 4 Model B

Raspberry Pi 4 Model B

Raspberry Pi 4 Model B is a popular single board computer developed with the intention of promoting teaching of basic computer science in schools. It is a successor to Raspberry Pi 3 Model B+ with better processor and ability to drive multiple displays. Both stable and "testing" images are available for Raspberry Pi 4 Model B.

21.1. Download

FreedomBox SD card images for this hardware are available. Download the "stable" or "testing" image for Raspberry Pi 4 Model B. Follow the instructions on the download page to create a FreedomBox SD card or USB drive and boot into FreedomBox.

21.2. Booting from USB

MicroSD cards are notouriously slow and prone to be corrupted. SD card corruption means that a high read/write load or a sudden power outage can make render your card unusable. It is therefore strongly recommended that you use a USB drive for your root partition. To be able to do that, you have to follow these preliminary steps:

  1. Download and install the Raspberry Pi Imager.

  2. Insert a microSD card to your computer.
  3. Open the Raspberry Pi Imager

    3.1 Select CHOOSE OS >> Misc utility images >> Bootloader >> USB Boot

    3.2 From CHOOSE STORAGE select your microSD card

    3.3 Click on WRITE

  4. After the writing was succesful, you should eject the card.
  5. Insert the newly created card into your Raspberry Pi and boot up the device. If it is connected to a monitor, you will see a green screen. Let your device rest for a minute, after which you can disconnect it from power and eject the card from the Raspberry Pi. It can now boot from USB.
  6. Final step: write your FreedomBox image into your USB device, then connect it to your Raspberry Pi. Make sure you did not leave your microSD card in the Raspberry Pi.

Please note that steps 1. to 5. only need to be done once.

21.3. Build Image

FreedomBox images for this hardware can be built using Freedom Maker. Use the target 'raspberry64' to build the image for this board.

21.4. Availability

21.5. Hardware

  • Open Hardware: No
  • CPU: Broadcom BCM2711 SOC (4x Cortex-A72@1.5GHz)

  • RAM: 2 GB or 4GB or 8 GB
  • Storage: MicroSD card slot or USB drive
  • USB: 2x USB 2.0, 2x USB 3.0, USB Type-C power supply
  • Architecture: arm64
  • Ethernet: 10/100/1000, RJ45
  • WiFi: 802.11ac but requires non-free firmware, instead use a USB WiFi device

  • SATA: None

21.6. Non-Free Status

  • Non-free blobs required: boot firmware
  • WiFi: Requires non-free firmware

22. USB Wi-Fi

FreedomBox works on many single board computers. However, many of these boards do not have built-in Wi-Fi capabilities. Even when Wi-Fi capability is available, non-free proprietary firmware is required to make them work.

A solution to the problem is to plug-in a USB Wi-Fi device into one of the available USB ports. There are many such devices available which do not require non-free firmware to work. The following is a list of such devices that work with FreedomBox devices. Some devices based on these chips have tested to work well with FreedomBox including functions such as access point mode.

22.1. Firmware Installation

The free firmware for these devices is not packaged in Debian yet. You can manually download and install the firmware as follows:

sudo su [enter password]
cd /lib/firmware
wget https://www.thinkpenguin.com/files/ath9k-htc/version-1.4-beta/htc_9271.fw
wget https://www.thinkpenguin.com/files/ath9k_firmware_free-version/htc_7010.fw

22.2. Resources

The following are the release notes for each FreedomBox version.

23. FreedomBox 23.18 (2023-09-25)

  • *: Fix all typing hint related errors
  • development: Make passing mypy checks mandatory
  • development: Perform backports tests on bookworm instead of bullseye
  • ikiwiki: Disable discussion pages by default for new wiki/blog
  • locale: Update translations for Bulgarian
  • middleware: Add new middleware to handle common errors like DB busy
  • upgrades: Fix detecting apt over tor during upgrade
  • wordpress: Use absolute path in service file

24. FreedomBox 23.17 (2023-09-11)

  • locale: Update translations for Czech, Dutch, Spanish, Swedish, Turkish, Ukrainian

25. FreedomBox 23.16 (2023-08-28)

25.1. Highlights

  • openvpn: Renew server/client certificates
  • openvpn: Correctly set expiry of server/client certs to 10 years

25.2. Other Changes

  • backups: Remove use of length_is template function
  • django: Remove use of X-XSS-Protection header
  • locale: Update translations for Czech, Norwegian Bokmål, Swedish
  • networks, samba: Fix tests setting firewall zone
  • openvpn: Ensure that re-running setup works as expected
  • openvpn: Fix app not installing on Debian testing
  • openvpn: Minor refactoring in setting up easy-rsa
  • openvpn: Use config file instead of env vars for easy-rsa
  • sso: Switch to django-axes >= 5.0

  • sso: Use POST method for logout
  • users, networks: Use the autofocus HTML attribute sparingly

26. FreedomBox 23.15 (2023-08-14)

  • debian: Add Swedish translation for debconf
  • locale: Update translations for Dutch, German, Spanish, Turkish, Ukrainian

27. FreedomBox 23.14 (2023-07-31)

27.1. Highlights

  • app: Implement advanced option to rerun app setup
  • torproxy: Add separate app for Tor Proxy
  • upgrades: Use codename in apt preferences

27.2. Other Changes

  • HACKING: Add instructions for container on Raspberry Pi
  • bepasty: Don't enable app when setup is rerun
  • bind: Don't enable app when setup is rerun
  • ci: Add mypy static type check
  • container: Add support for retrieving GPG keys using wget
  • container: Update for bookworm images
  • deluge: Don't enable app when setup is rerun
  • ejabberd: Don't enable app when setup is rerun
  • firewall: Add diagnostic check for backend
  • firewall: Add diagnostic check for passthroughs
  • firewall: Add diagnostic for default zone
  • gitweb: Don't enable app when setup is rerun
  • ikiwiki: Don't enable app when setup is rerun
  • infinoted: Don't enable app when setup is rerun
  • janus: Don't enable app when setup is rerun
  • jsxc: Don't enable app when setup is rerun
  • kvstore: Optionally, don't throw exception when deleting key
  • locale: Update translations for Dutch
  • mediawiki: Don't enable app when setup is rerun
  • minetest: Don't enable app when setup is rerun
  • openvpn: Don't enable app when setup is rerun
  • performance: Don't enable app when setup is rerun
  • privoxy: Don't enable app when setup is rerun
  • quassel: Don't enable app when setup is rerun
  • radicale: Don't enable app when setup is rerun
  • rssbridge: Don't enable app when setup is rerun
  • shaarli: Don't enable app when setup is rerun
  • sharing: Don't enable app when setup is rerun
  • tor, torproxy: Export settings from old to new app
  • tor, torproxy: Update description for info on services provided
  • tor: tests: Make functional test check for running service
  • ttrss: Don't enable app when setup is rerun
  • upgrades: Use codename for unattended-upgrades origin pattern
  • users: Add diagnostic checks for nsswitch config
  • users: Add diagnostics check for nslcd config
  • wireguard: Don't enable app when setup is rerun
  • zoph: Don't enable app when setup is rerun

28. FreedomBox 23.13 (2023-07-17)

  • container: Add support for ARM64 containers
  • HACKING: Instructions for macOS on Apple Silicon
  • locale: Update translations for German, Spanish, Turkish, Ukrainian

29. FreedomBox 23.12 (2023-06-19)

29.1. Highlights

  • packages: Purge packages on uninstall
  • gitweb: Fix issue with service startup when gitweb is not enabled
  • mediawiki: Increment version to run update.php automatically

29.2. Other Changes

  • deluge: Utilize purging of packages and don't remove explicitly
  • locale: Update translations for Czech, Dutch, Spanish, Turkish, Ukrainian
  • mediawiki: Utilize purging of packages and don't remove explicitly
  • roundcube: Clarify description for local mail only option
  • samba: Remove additional configuration files on uninstall
  • searx: Fix typo in method name
  • shaarli: Utilize purging of packages and don't remove explicitly
  • uninstall: Remove experimental warning

30. FreedomBox 23.11 (2023-06-05)

30.1. Highlights

  • *: Fix icons not present in the generated .deb
  • shadowsocksserver: Add separate app for Shadowsocks server

30.2. Other Changes

  • apache: Fix failure during app update
  • apache: Use drop-in config component for /etc files
  • bepasty: Use drop-in config component for /etc files
  • calibre: Use drop-in config component for /etc files
  • cockpit: Use drop-in config component for /etc files
  • config: Add new component for managing drop-in /etc/ config files
  • debian/install: Add new place in /usr to keep drop-in config files
  • deluge: Use drop-in config comonents for /etc files
  • ejabberd: Use drop-in config component for /etc files
  • email: Use drop-in config component for /etc files
  • gitweb: Use drop-in config component for /etc files
  • i2p: Use drop-in config component for /etc files
  • ikiwiki: Use drop-in config component for /etc files
  • janus: Use drop-in config component for /etc files
  • letsencrypt: Use drop-in config component for /etc files
  • matrixsynapse: Use drop-in config component for /etc files
  • mediawiki: Use drop-in config component for /etc files
  • minidlna: Use drop-in config component for /etc files
  • networks: Use drop-in config component for /etc files
  • pagekite: Drop the config file for forcing use of Debian certs
  • privacy: Use drop-in config component for /etc files
  • radicale: Use drop-in config component for /etc files
  • roundcube: Use drop-in config component for /etc files
  • rssbridge: Use drop-in config component for /etc files
  • searx: Use drop-in config component for /etc files
  • security: Use drop-in config component for /etc files
  • sharing: Use drop-in config component for /etc files
  • ssh: Use drop-in config component for /etc files
  • sso: Use drop-in config component for /etc files
  • syncthing: Use drop-in config component for /etc files
  • transmission: Use drop-in config component for /etc files
  • ttrss: Use drop-in config component for /etc files
  • upgrades: Use drop-in config component for /etc files
  • users: Use drop-in config component for /etc files
  • wordpress: Use drop-in config component for /etc files

31. FreedomBox 23.10 (2023-05-22)

  • *: Move modules-enabled files to /usr/share
  • locale: Update translations for Dutch, Portuguese, Spanish, Turkish, Ukrainian
  • doc/dev: Set language code explicitly in Sphinx configuration
  • gitweb: Disable gpg signing in tests

32. FreedomBox 23.9 (2023-05-08)

32.1. Highlights

  • transmission: Allow remote UIs to connect
  • ttrss: Allow apps to use /tt-rss URL instead of separate one

32.2. Other Changes

  • apache: Reload apache using component if config changes
  • debian: Follows policy v4.6.2
  • debian: Update copyright years
  • doc/dev: Update copyright year
  • help: Add information on obtaining source code
  • locale: Update translations for Japanese
  • mediawiki: Make a utility method public
  • mediawiki: Make retrieving list of supported languages robust
  • mediawiki: Simplify retrieving the default language
  • minidlna: Resize icon and export to PNG also
  • service: Remove reference to managed_services in a message
  • storage: Handle mount error properly
  • theme: Move icons to app folders
  • tor: Check if Hidden service is version 3
  • tor: Only diagnose relay ports if feature enabled
  • tor: Rename Hidden service to Onion service
  • transmission: Add Tremotesf to list of client apps
  • ttrss: Don't show app in enabled list of apps if install fails
  • ttrss: Update list of clients
  • ttrss: Use the apache component to restart apache on config change
  • uninstall: Fix issue with uninstall of apps that have no backup
  • zoph: Don't fail at showing app view during uninstall

33. FreedomBox 23.6.2 (2023-05-01)

  • upgrades: Check apt result during dist-upgrade
  • locale: Update translations for Bulgarian, Ukrainian

34. FreedomBox 23.8 (2023-04-24)

34.1. Highlights

  • coturn: Prevent package removal when roundcube is uninstalled
  • datetime: Re-implement backup/restore for timezone
  • gitweb: Disable snapshot feature

34.2. Other Changes

  • HACKING: Force pip to install packages to system environment
  • bepasty: When uninstalling, remove all data and configuration
  • calibre: Remove libraries during uninstallation
  • ci: Force pip install for functional tests
  • coturn: When uninstalling, remove all data and configuration
  • datetime: Use unique component ID for related daemon
  • deluge: When uninstalling, remove all data and configuration
  • gitweb: When uninstalling, remove all data and configuration, remove repositories
  • gitweb: Make globally configured features overridable per-repository
  • gitweb: Simplify handling shortcut for front page
  • ikiwiki: When uninstalling, remove all data and configuration
  • infinoted: When uninstalling, remove all data and configuration
  • locale: Update translations for Bulgarian, French, Ukrainian
  • matrixsynapse: When uninstalling, remove all data and configuration
  • mediawiki: When uninstalling, remove all data and configuration
  • mediawiki: Fix broken view on Bullseye due to language selection
  • openvpn: When uninstalling, remove all data and configuration
  • roundcube: When uninstalling, remove all data and configuration
  • rssbridge: When uninstalling, remove all data and configuration
  • samba: When uninstalling, remove all data and configuration
  • searx: When uninstalling, remove all data and configuration
  • searx: Simplify handling shortcut for front page
  • shaarli: When uninstalling, remove all data and configuration
  • shadowsocks: When uninstalling, remove all data and configuration
  • sharing: When uninstalling, remove all data and configuration
  • syncthing: When uninstalling, remove all data and configuration
  • syncthing: Remove unused pathlib import so job code-quality can pass
  • tests: Don't error during collection if selenium is not installed
  • tests: functional: Make install script work for Bullseye
  • tests: functional: Remove handling for custom enable/disable buttons
  • tests: functional: Update detecting page changes
  • tor: When uninstalling, remove all data and configuration
  • ttrss: When uninstalling, remove all data and configuration
  • upgrades: Check apt result during dist-upgrade
  • wordpress: When uninstalling, remove all data and configuration

35. FreedomBox 23.6.1 (2023-04-10)

  • coturn: Prevent package removal when roundcube is uninstalled
  • datetime: Re-implement backup/restore for timezone
  • gitweb: Disable snapshot feature
  • gitweb: Make globally configured features overridable per-repository
  • locale: Update translations for Bulgarian, French

36. FreedomBox 23.7 (2023-03-27)

36.1. Highlights

  • matrixsynapse: Add token based registration verification
  • mediawiki: Allow setting site language code

36.2. Other Changes

  • container: Fix resizing disk image containing multiple partitions
  • container: Force pip to install packages to system environment
  • container: Increase wait time to accommodate slower architectures
  • locale: Update translations for Bulgarian
  • tests: functional: Fix setting first ethernet connection as internal

37. FreedomBox 23.6 (2023-03-13)

  • /etc/issue: Update message to reflect that all users can login
  • ci: Force pip to install packages to system environment
  • datetime: Use timedatectl to read current timezone
  • samba: Make sure shares are not accessible from the internet
  • ttrss: Fix failing backup

38. FreedomBox 23.5 (2023-02-27)

  • mediawiki: Fix app view error
  • locale: Update translations for Albanian, Bulgarian, Czech, Dutch, German, Spanish, Swedish, Turkish, Ukrainian
  • samba: tests: Fix enable share view test

39. FreedomBox 23.4 (2023-02-13)

39.1. Highlights

  • ejabberd: Fix making call connections when using TURN
  • matrixsynapse: Disable verification to fix public registrations
  • snapshot: Fix issue with snapshot rollbacks

39.2. Other Changes

  • app: Add backup and restore menu items to toolbar menu
  • backups: Allow selecting a single app from URL when creating backup
  • config: Drop RuntimeMaxUse=5% for journal logging

  • dynamicdns: Skip uninstall test
  • ejabberd: Add Monal and Siskin for iOS and remove ChatSecure

  • email: Redirect to the app page if roundcube isn't installed
  • ikiwiki: Re-run setup for each site after restore
  • locale: Update translations for Bulgarian, Spanish
  • matrixsynapse: Minor refactor in getting/setting public registrations
  • matrixsynapse: Add python3-psycopg2 to packages
  • matrixsynapse: Use yaml.safe_load
  • searx: Add libjs-bootstrap to packages
  • snapshot: Fix mounting /.snapshots subvolume and use automounting
  • templates: Show better title for 404 page
  • uninstall: Fix spelling in warning message
  • vagrant: Drop unnecessary script that deletes sqlite file
  • vagrant: Hide the vagrant-script directory
  • vagrant: Mount source in /freedombox instead of /vagrant
  • vagrant: Switch to /freedombox before running service with alias

40. FreedomBox 23.3 (2023-01-30)

  • config: Fix showing the value of the default home page
  • email: Revert workaround for error on finishing uninstall
  • firewalld: Allow upgrade to version 2*
  • gitweb: tests: Skip tests using git when git is not installed
  • locale: Update translations for Bulgarian
  • tests: functional: Fix submitting forms with notifications present
  • tor: Also use Aptsources822 augeas lens
  • tor: Remove workaround for old Augeas bug
  • upgrades: Add augeas lens for Deb822 apt sources
  • views: Use dedicated view when showing an app with operations

41. FreedomBox 23.2 (2023-01-16)

  • locale: Update translations for Albanian, Bulgarian
  • ssh: Add sudo to allowed groups
  • upgrades: Stop quassel during dist upgrade

42. FreedomBox 23.1 (2023-01-03)

42.1. Highlights

  • package: Don't uninstall packages that are in use by other apps
  • tor: Add onion location to apache

42.2. Other Changes

  • email: Workaround an issue with error on finishing uninstall
  • gitweb: Run git commands as a web user
  • janus: Allow upgrade to 1.1
  • locale: Update translations for Galician, Spanish
  • operation: tests: Fix warning when test helpers start with 'Test'
  • zoph: Add explicit dependency on default-mysql-server

43. FreedomBox 22.27 (2022-12-19)

43.1. Highlights

  • minidlna: Fix incorrect marking for firewall local protection
  • zoph, wordpress: Add conflicts on libpam-tmpdir

43.2. Other Changes

  • container: Drop free tag from image URLs
  • d/control: Don't recommend libpam-tmpdir
  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, German, Turkish, Ukrainian
  • package, email: Move conflicting package removal to framework
  • snapshot: Fix showing unsupported message on non-btrfs filesystems
  • tests: functional: Set timeout to 3 hours
  • upgrades: dist-upgrade: Don't change apt security line
  • users: tests: Fix privileged tests
  • wordpress: Redirect Webfinger queries

44. FreedomBox 22.26 (2022-12-05)

44.1. Highlights

  • ejabberd: Enable mod_http_upload
  • security: Remove restricted access setting and configuration
  • ssh: Restrict logins to groups root, admin and freedombox-ssh

44.2. Other Changes

  • calibre: Add protection to local service using firewall
  • deluge: Add protection to local service using firewall
  • email: Add protection to local service using firewall
  • firewall: Create a mechanism for protecting local services
  • firewall: Introduce component for local service protection
  • i2p: Add protection to local service using firewall
  • i2p: Remove donation URL that is no longer available
  • minidlna: Add protection to local service using firewall
  • searx: Ensure that socket is only reachable by Apache and root
  • ssh: Add checkbox to remove login group restrictions
  • syncthing: Add protection to local service using firewall
  • transmission: Add protection to local service using firewall

45. FreedomBox 22.25 (2022-11-21)

  • email: Add fail2ban jail for dovecot
  • email: Fix creation of aliases for security@ and usenet@

46. FreedomBox 22.24 (2022-11-07)

46.1. Highlights

  • locale: Update translations for Bulgarian, French, German, Norwegian Bokmål

46.2. Other Changes

  • debian/lintian-overrides: Fix mismatch patterns and new messages
  • minetest: Handle upgrade from 5.3.0 to 5.6.1
  • storage: Drop skip_recommends
  • upgrades: Add documentation link to upgrades service file
  • upgrades: Update list of holds during dist upgrade

47. FreedomBox 22.23 (2022-10-24)

47.1. Highlights

  • letsencrypt: Fix regression with comparing certificate
  • rssbridge: Add option to allow public access

47.2. Other Changes

  • locale: Update translations for Bulgarian, Hungarian, Swedish
  • storage: Handle file systems on non-physical devices
  • upgrades: Allow FreedomBox vendor when adding backports

  • upgrades: Skip unattended-upgrade in dist-upgrade

48. FreedomBox 22.22.1 (2022-10-16)

  • debian: tests: Fix PYTHONPATH
  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, Turkish, Ukrainian
  • privacy: Remove unused import, fix pipeline

49. FreedomBox 22.22 (2022-10-10)

49.1. Highlights

  • privacy: Add new system app for popularity-contest
  • matrix: Add fail2ban jail

49.2. Other Changes

  • *: Use privileged decorator for actions
  • action_utils: Drop support for non-systemd environments
  • action_utils: Drop unused progress requests from apt-get
  • actions: Allow actions to be called by other users
  • actions: Allow nested and top-level actions
  • actions: Drop unused superuser_run and related methods
  • actions: Implement getting raw output from the process
  • actions: Use separate IPC for communicating results
  • apache: Fix logs still going into /var/log files
  • bind: Drop enabling DNSSEC (deprecated) as it is always enabled
  • config: Drop ability to set hostname on systems without systemd
  • config: Drop legacy migration of Apache homepage settings
  • fail2ban: Make fail2ban log to journald
  • firewall: Drop showing running status
  • locale: Update translations for Albanian, Czech, Norwegian Bokmål, Russian, Swedish, Ukrainian
  • minidlna: Use the exposed URL for diagnostic test
  • openvpn: Drop RSA to ECC migration code and two-step setup
  • privacy: Set vendor as FreedomBox for dpkg and popularity-contest

  • searx: Show status of public access irrespective of enabled state
  • templates: Update HTML meta tags for better description and app-name
  • tests: Add fixture to help in testing privileged actions
  • wordpress: Update fail2ban filter

50. FreedomBox 22.21.1 (2022-10-01)

  • locale: Update translations for Bulgarian, Ukrainian
  • notification: Don't fail when formatting message strings

51. FreedomBox 22.21 (2022-09-26)

  • janus: Enable systemd sandboxing
  • locale: Update translations for Albanian, Bulgarian, Czech, Danish, Dutch, French, German, Greek, Hungarian, Indonesian, Italian, Latvian, Lithuanian, Norwegian Bokmål, Persian, Polish, Portuguese, Russian, Serbian, Slovenian, Spanish, Swedish, Turkish, Ukrainian
  • mediawiki: Add powered by freedombox logo
  • wordpress: Add fail2ban filter and jail
  • wordpress: Disable readme.html, xmlrpc.php, wp-cron.php

52. FreedomBox 22.20 (2022-09-12)

52.1. Highlights

  • matrixsynapse: Allow matrix-synapse >= 1.65 to install successfully

52.2. Other Changes

  • backups: Use generic form template for create and schedule views
  • backups: tests: functional: Find forms more accurately
  • bepasty: Use generic form template for add password view
  • bepasty: tests: functional: Minor refactor for form submission
  • calibre: tests: functional: Find forms more specifically
  • d/maintscript: remove tahoe and mldonkey apache conf files
  • debian: Add Italian debconf translation
  • ejabberd: tests: functional: Ensure jsxc is installed
  • firewall: Allow upgrade from any version to 1.2.*
  • first_boot: tests: functional: Find form more specifically
  • gitweb: Fix issue with page not refreshing during uninstall
  • gitweb: Use generic form template for create/edit repository
  • gitweb: tests: functional: Find forms more accurately
  • ikiwiki: tests: functional: Find forms more accurately
  • locale: Update translations for Chinese (Simplified), Czech, French, Italian, Turkish
  • samba: Ignore mounted files when listing mounts
  • samba: Update client apps information
  • shaarli: tests: functional: Specify setup form submission button
  • sharing: tests: functional: Find forms more accurately
  • snapshot: tests: functional: Minor refactoring for form submission
  • sso: tests: functional: Find forms more accurately
  • templates: form: Specify a form class for use with functional tests
  • tests: functional: Assert app is not installed after uninstallation
  • tests: functional: Force specifying form to submit more accurately
  • tests: functional: Wait for installation to complete fully
  • users: tests: functional: Find forms more accurately
  • version: Compare Debian package version numbers
  • wordpress: tests: functional: Find forms more specifically
  • zoph: tests: functional: Simplify finding the form to submit

53. FreedomBox 22.19 (2022-08-29)

53.1. Highlights

  • jsxc: Allow disabling the app
  • app: Add a menu item to trigger uninstallation

53.2. Other Changes

  • app: Add API to uninstall an app
  • avahi: Don't disable after tests
  • backups: Use AppView for the main app page

  • container: Display help message when no args are passed
  • container: Show default values in command help
  • d/control: Break ufw as we use firewalld
  • debian: Update Spanish translation template
  • diagnostics: Use AppView for app page

  • ejabberd: Set hostname for test that relies on it
  • forms: Implement form for uninstallation
  • janus: Convert action to privileged
  • janus: Handle upgrades to 1.0.*
  • letsencrypt: Use AppView for app page

  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, French, German, Spanish, Turkish, Ukrainian
  • names: Use AppView for app page

  • networks: Use AppView for app page

  • operation: Factor out template code into a separate file
  • operation: Show operations on app page in addition to setup page
  • package: Implement low-level methods for uninstalling
  • package: Implement uninstall in Package component
  • power: Use AppView for app page

  • security: Use AppView for app page

  • setup: Drop check for already running operation
  • setup: Implement operation to uninstall an app
  • snapshot: Use AppView for app page

  • tests: Make functional.is_available check faster
  • tests: functional: Add install/uninstall test for all apps
  • tor: Use AppView and Operation for app page

  • ttrss: Add donation url
  • upgrades: Add button to test dist-upgrade in development mode
  • upgrades: Hold janus during dist-upgrade
  • views: Implement a view to uninstall an app

54. FreedomBox 22.18 (2022-08-15)

54.1. Highlights

  • networks: Remove DNSSEC diagnostics
  • setup: Allow starting installation when package manager is busy
  • setup: Fix issue with immediate refresh after installation

54.2. Other Changes

  • *: Add setup method on all apps that don't have it
  • *: Drop module level app property
  • *: Make force upgrading part of app rather than a module
  • *: Make setup method part of App class for all apps
  • app: Drop optimization that skips setup process
  • backups: tests: Mark need for Django database during API tests
  • container: Add IdentitiesOnly option to SSH

  • container: Ignore flake8 error 'line too long' in bash script text
  • coturn: Fix link to ejabberd in description
  • doc: dev: Document previously undocumented components
  • ejabberd: Fix showing the status messages
  • locale: Update translations for Bulgarian, Czech, Dutch, French, German, Turkish, Ukrainian
  • matrixsynapse: Fix showing the status messages
  • notification: Pass full context when rendering body template
  • operation: Add module to manage threaded operations
  • package: Run installation operation using app_id instead of module
  • setup: Drop setup_helper and use the new Operation API
  • sharing: Add installing and enable/disable like other apps
  • sharing: tests: functional: Fix a flaky test by waiting
  • ssh: tests: functional: Keep service enabled after tests
  • storage: Fix enumerating partitions without mount points

55. FreedomBox 22.17 (2022-08-01)

55.1. Highlights

  • help: Add "How can I help?" section to Contribute page

55.2. Other Changes

  • locale: Update translations for Chinese (Simplified), Dutch, French, German, Turkish
  • wordpress: Don't install php-ssh2

56. FreedomBox 22.16 (2022-07-18)

56.1. Highlights

  • cockpit: Reconfigure to allow any origin
  • rssbridge: New app to generate RSS feeds for websites

56.2. Other Changes

  • apache: Also configure to serve on /freedombox
  • apache: Merge old configuration files into a better location
  • apache: Redirect all logs to systemd journal
  • cockpit: Depend on apache and setup after it
  • cockpit: Use decorator for privileged actions
  • config: Add option to set logging mode: none/volatile/persistent
  • config: Set volatile logging by default
  • debian: Follows policy version 4.6.1
  • debian: Update copyright year
  • gitweb: Switch default branch name to main for new repositories
  • janus: Change short description to "Video Room"
  • locale: Update translations for Bulgarian, Chinese (Simplified), French, Russian, Ukrainian
  • privoxy: Restrict to private IPs, prevent access over the internet
  • privoxy: Use privileged decorator for actions
  • roundcube: Add fail2ban jail
  • roundcube: Configure to log to journald
  • roundcube: Use privileged to simplify actions
  • rssbridge: Add functional tests
  • rssbridge: Fix flake8 errors
  • rssbridge: Whitelist all bridges by default

57. FreedomBox 22.15 (2022-07-04)

57.1. Highlights

  • backups: Add options to keep sshfs shares responsive
  • backups: Unmount repositories before and after backup
  • users: create home directories for newly created users

57.2. Other Changes

  • *: pylint: Avoid calling super() with arguments
  • *: pylint: Don't inherit from 'object'
  • *: pylint: Drop unnecessary 'pass' statements
  • *: pylint: Explicitly specify encoding when open a file
  • *: pylint: Suppress unused argument warnings
  • ci: Use compatible versions of Selenium and Splinter
  • locale: Update translations for Bulgarian, Russian, Ukrainian
  • mediawiki: Add regex validator to the domain field
  • mediawiki: Remove Buster specific code not needed in Bullseye
  • mediawiki: Remove wgLogo as it is not needed in Bullseye
  • pyproject.toml: Ignore some refactoring messages with pylint
  • static: js: css: Make multiple select fields work with Django 4.0
  • tests: functional: Simplify GitLabCI configuration
  • upgrades: Hold packages one at a time
  • upgrades: Re-add workaround for grub
  • views: Add a comment about change in Django 4.0

58. FreedomBox 22.14.1 (2022-06-27)

58.1. Highlights

  • matrixsynapse: Allow new dependency to be installed from backports

58.2. Other Changes

  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, German, Turkish
  • actions: Note that privileged actions can't output to stdout
  • mumble: Backup/restore the configuration file
  • mumble: Don't set the root channel name unless it is changed
  • mumble: Use privileged decorator for superuser actions
  • mumble: tests: Add functional tests for setting the passwords

59. FreedomBox 22.14 (2022-06-20)

59.1. Highlights

  • ejabberd: Allow domains to be added or removed
  • mumble: Allow setting a password that is required to join the server
  • mediawiki: Add option to change the site name

59.2. Other Changes

  • actions: Add a decorator for marking superuser actions
  • doc: dev: Use and recommend new privileged actions
  • ejabberd: Automatically use coturn
  • janus: Improve description about coturn
  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, French, German, Russian, Turkish
  • tests: Add a dummy parameter for middlewares for Django 4.0
  • translation: Don't use session for storing lang pref in Django 4.0
  • transmission: Simplify actions using the privileged decorator
  • users: Fix deleting user LDAP entry with Django 4.0

60. FreedomBox 22.13 (2022-06-06)

60.1. Highlights

  • email: Make app available for all users (even without advanced flag)
  • janus: Add new app for lightweight WebRTC server
  • wordpress: Allow installing/updating plugins and themes

60.2. Other Changes

  • email: Add description about ISP and domain limitations
  • locale: Added Latvian translation
  • locale: Update translation for Bulgarian, Chinese (Simplified), Czech, Dutch, German, Russian, Swedish, Turkish
  • mumble: Allow changing root channel name
  • tests: functional: Add jobs for bullseye-backports
  • tests: functional: Integrate into Salsa CI
  • transmission: Add redirects to avoid 409 conflict
  • wordpress: tests: Continue past language selection screen
  • wordpress: tests: Fix writing title for new post in newer versions

61. FreedomBox 22.12 (2022-05-23)

61.1. Highlights

  • *: Show Learn More... links in frontpage with description
  • mediawiki: Serve hidden service over http for .onion domains

61.2. Other Changes

  • apache: Allow URL diagnostics to work with redirects
  • firewall: Show service name in port forwarding info table
  • frontpage: Allow showing links to manual pages
  • frontpage: Reuse app header template for showing app description
  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, French, German, Norwegian Bokmål, Turkish
  • mediawiki: Add stricter sandbox rules for jobrunner service
  • mediawiki: Fix URL diagnostics with redirects involved
  • ssh, bind: Show 'Learn More...' links
  • tor: Show port forwarding information in consistent way
  • tt-rss: Fix description about user access

62. FreedomBox 22.11 (2022-05-09)

62.1. Highlights

  • email: Fix userdb lookups with LDAP
  • matrixsynapse: Allow new dependencies to be installed from backports

62.2. Other Changes

  • HACKING: Improve documentation on how to run tests
  • container: Show executed commands when setting up/running tests
  • locale: Update translations for Bulgarian, Danish, French, Hungarian, Norwegian Bokmål, Polish, Russian, Ukrainian
  • mediawiki: Check if admin password is at least 10 characters long
  • mediawiki: Handle password rejection from MediaWiki

  • samba: Fix functional tests when user is not logged in at start
  • tests: functional: Get rid of dependency on xvfb
  • transmission: Improve description

63. FreedomBox 22.10 (2022-04-25)

  • locale: Update translations for Bulgarian, Czech, Dutch, German, Greek, Russian, Swedish, Turkish
  • sharing: Allow spaces in path strings

64. FreedomBox 22.9 (2022-04-11)

64.1. Highlights

  • minetest: Allow alternate name for 3d armor mod
  • upgrades: Use python3-typing-extensions from bullseye-backports

64.2. Other Changes

  • calibre: Fix description of allowable library names
  • locale: Add new Arabic translation
  • locale: Update translations for Arabic, Bulgarian, Czech, Dutch, French, German, Hungarian, Turkish
  • plinth: Add forum link to footer

65. FreedomBox 22.8 (2022-03-28)

65.1. Highlights

  • network: Fix showing wifi connection

65.2. Other Changes

  • calibre: explain correct name format for new library
  • ikiwiki: add packages that are necessary
  • locale: Updated translations for Chinese (Simplified), French, Russian
  • upgrades: Allow backports from src:freedombox

66. FreedomBox 22.7 (2022-03-14)

  • locale: Update translations for French, Hungarian, Spanish

67. FreedomBox 22.6.1 (2022-03-06)

  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, German, Turkish

68. FreedomBox 22.6 (2022-03-02)

68.1. Highlights

  • email: Enable as an advanced app

68.2. Other Changes

  • dynamicdns: Fix adding null domain into configuration
  • email: Add backup/restore component
  • email: Add basic functional tests
  • email: Add front page shortcut, update name and description
  • email: Add more special-use IMAP folders, set autoexpunge to 60days
  • email: Add shortcut for non-admin users to manage their aliases
  • email: Add various documentation links for future readability
  • email: Allow re-running setup
  • email: Backup/restore aliases and mailboxes
  • email: Depend on and run redis server
  • email: Implement adding common aliases for first admin user
  • email: List all listening ports of the daemons
  • email: Narrowly match just rspamd's spam header
  • email: Open firewall port for managesieve protocol
  • email: Revert to LDAP auth as pam does not allow non-admin users
  • email: Set an icon from Tango project
  • email: Setup rspamd configuration to include FreedomBox config

  • email: Tweak client auto-configuration file
  • email: Update donation URL to rspamd donation URL
  • email: aliases: Drop ability to enable/disable aliases
  • email: clients: Make Thunderbird URLs language independent
  • email: dkim: Implement setting up DKIM signing keys
  • email: dns: Show table for desired DNS entries
  • email: postfix: Fix priority for authentication directives
  • email: postfix: use inline map for TLS SNI maps
  • email: rspamd: Log to journald via syslog
  • email: rspamd: Simplify installing configuration
  • locale: Update translations for Bulgarian, Chinese (Simplified), Czech, Dutch, German, Hungarian, Russian, Swedish, Telugu, Turkish, Ukrainian
  • minidlna: add iOS VLC client
  • samba: add iOS VLC client

69. FreedomBox 22.5 (2022-02-14)

69.1. Highlights

  • dynamicdns: Replace ez-ipupdate
    • Drop NAT detection as it is no longer used
    • Drop about page and merge into description
    • Drop tabs and use single page
    • Rewrite configuration handling and update using URL

69.2. Other Changes

  • app: Add component to store enabled state of an app in kvstore
  • backups: Implement backup/restore of key/value settings
  • locale: Update translations for Albanian, Bulgarian, Chinese (Simplified), Czech, Dutch, German, Hungarian, Russian, Spanish, Swedish, Turkish, Ukrainian
  • minetest: Reduce the number of configuration update messages
  • tests: functional: Add plugin for HTML reports
  • tt-rss: Restrict access to feed-reader group in "/tt-rss-app"

  • users: Fix typo in description

70. FreedomBox 22.4 (2022-01-31)

70.1. Highlights

  • coturn: Use wildcard listening address to fix startup issues
  • sso, users: Redirect to home page after logout

70.2. Other Changes

  • apache: Don't redirect to HTTPS for .onion domains
  • apache: Don't set HSTS for .onion domain
  • cockpit: Explicitly redirect to HTTPS as needed for WebSockets

  • doc: Fail when downloading images from Debian wiki fails
  • email_server: Drop showing diagnostics/repair and roundcube config
  • email_server: Drop some unused code
  • locale: Update translations for Bulgarian, Dutch, French, German, Hungarian, Russian, Swedish, Ukrainian
  • matrixsynapse: Add FluffyChat to client list

  • mldonkey: Drop app not available in Debian Bullseye and Bookworm
  • power: Add a link to power app in the system menu
  • roundcube: Add setting for local connection only
  • shaarli: Add android app to description
  • shaarli: Add backup component
  • shaarli: Add functional tests
  • snapshots: Clarify that snapshots are take during updates too
  • tests: functional: Implement a workaround for issue with screenshots
  • users: Clarify help message for authorization password
  • wireguard: tests: Add functional tests

71. FreedomBox 22.3 (2022-01-17)

71.1. Highlights

  • upgrades: Allow matrix's new dependency to be installed
  • sso: Adjust URL to CAPTCHA page needed by Django security fix

71.2. Other Changes

  • container: Avoid a warning that interactive mode is intended
  • help: tests: Fix functional test to check for status logs
  • locale: Update translations for Chinese (Simplified), Czech, Dutch, German, Hungarian, Turkish
  • sso: Add missing captcha/rate limiting on SSO login
  • tests: functional: Fix setting domain name with active notifications
  • tt-rss: Allow published articles to be publicly available

72. FreedomBox 22.2 (2022-01-11)

72.1. Highlights

  • debian, setup.py: Add dependency on python3-tomli
  • help: Fix failing setup when manual directory is not available

72.2. Other Changes

  • backups: Correct spelling of encryption protocols
  • i2p: Fix grammar in description
  • ikiwiki: Initialize shortcuts during post-init setup
  • locale: Update translations for Chinese (Simplified), Czech, Dutch, German, Hungarian, Italian, Swedish, Turkish
  • mumble: Change description to include iOS client app
  • networks: Fix reference to an option
  • openvpn: Add link to IOS app
  • radicale: Update Thunderbird URLs
  • transmission: Fix capitalization
  • wireguard: Fix spelling

73. FreedomBox 22.1 (2022-01-03)

73.1. Highlights

  • package: Add diagnostic to check if a package is the latest version

73.2. Other Changes

  • backups: Capitalize 'SSH' in template
  • config, upgrades: Specify submit button for tests
  • datetime: Explicitly list systemd-timesyncd as a dependency
  • locale: Update translations for Chinese (Traditional), Czech, Dutch, Hungarian, Norwegian Bokmål, Spanish, Swedish
  • storage: Skip tests if not enough disk space is available
  • upgrades: Relabel from 'Update' to 'Software Update'

74. FreedomBox 21.16 (2021-12-20)

74.1. Highlights

  • datetime: Fix checking when timesyncd will run on a system

74.2. Other Changes

  • cockpit, ejabberd: Make 'name' optional in Signal handlers
  • diaspora: Drop app that was never finished
  • email_server:
    • Adjust TLS configuration parameters
    • Fix issue with handling domain removal
    • Include postfix package in packages list
    • Re-implement TLS configuration
    • Rename dovecot TLS configuration file for consistency
  • letsencrypt: Handle cert setup when an app wants all domains
  • locale: Update translations for Chinese (Simplified), Chinese (Traditional), Czech, French, German, Swedish, Turkish
  • monkeysphere, tahoe-lafs: Drop unused apps
  • roundcube: Allow upgrades by avoiding configuration file change
  • tests: Fix app name in pytest.skip statement
  • tests: functional: Skip MLDonkey app
  • upgrades: Cleanup dist upgrade steps specific to bullseye release
  • upgrades: Refactor dist upgrade process

75. FreedomBox 21.15 (2021-12-06)

75.1. Highlights

  • dynamicdns: Update URLs to the new dynamic DNS server
  • firewall: Allow configuration upgrade to version 1.0.x
  • shaarli: Enable app (only available in testing and unstable)

75.2. Other Changes

  • *: Drop module level depends declaration
  • *: Drop module level package_conflicts and use component API
  • *: Drop unused manual_page at module level
  • *: Drop use of managed_packages and rely on Packages component
  • *: Drop use of managed_services, rely on Daemon component
  • *: Drop use of module level is_essential flag
  • *: Drop use of module level version
  • *: Drop use of unnecessary managed_paths
  • *: Use the App's state management API
  • actions/letsencrypt: Drop use of managed_paths and use LE component
  • actions/service: Drop unused list action
  • actions/service: Drop use of managed_services for Daemon component
  • actions: Get list of packages from Packages components
  • app: Introduce API for managing setup state of the app
  • app: Introduce API to setup an app
  • bind: Drop alias handling unnecessary in >= Bullseye

  • daemon: Add new component to hold information about related daemons
  • doc/dev: Drop discussion on managed_paths
  • doc/dev: Drop reference to module level depends declaration
  • doc/dev: Remove mention of managed_services
  • doc/dev: Remove outdated reference to init() at module level
  • doc/dev: Update documentation to not refer to managed_packages
  • email_server: Merge domain configuration with app view
  • email_server: Simplify domain configuration form
  • first_boot: Drop use of loaded_modules and use App.list
  • forms: Fix regression with TLS domain form in quassel and tt-rss
  • letsencrypt: On domain removal, don't revoke certificate, keep it
  • locale: Update translations for Czech, German, Norwegian Bokmål
  • main: List apps instead of modules
  • middleware, views: Reduce use of setup_helper
  • module_loader, app: Move app init to app module
  • package: Add parameter to specify skipping package recommendations
  • package: Implement installing packages in the component
  • package: Introduce component API for package conflicts
  • packages: Move checking for unavailable packages to component
  • security: Drop use of loaded_modules and use App.list
  • security: Drop use of managed_services in security report
  • security: Get the list of packages from Packages component
  • setup: Drop unused API for app's state management
  • setup: List dependencies for apps instead of modules
  • setup: Run setup on apps instead of modules
  • setup: Use apps instead of modules to determine running first setup
  • setup: Work on apps instead of modules for force upgrade
  • tests: Add 'domain' mark for apps that add/remove domains
  • web_server: Drop use of loaded_modules and use App.list

76. FreedomBox 21.14.1 (2021-11-24)

  • config: Add packages component to a re-add zram-tools dependency

77. FreedomBox 21.14 (2021-11-22)

77.1. Highlights

  • tt-rss: Allow selection of a domain name

77.2. Other Changes

  • *: Split app initialization from app construction
  • app: Introduce separate method for post initialization operations
  • datetime: Avoid error when systemctl is not available
  • debian: Fail build if no module dependencies found
  • locale: Update translations for Swedish, Turkish, Ukrainian
  • main: Drop initializing Django when listing dependencies

78. FreedomBox 21.13 (2021-11-08)

78.1. Highlights

  • avahi, samba: Use systemd sandboxing
  • components: Introduce new component - Packages
  • security: Properly handle sandbox analysis of timer units

78.2. Other Changes

  • email_server (not enabled yet):
    • Add buttons for managing aliases, domains, spam
    • Authenticate using PAM instead of LDAP
    • Delivery mail to /var/mail instead of home directory
    • Don't use user IDs when performing lookups
    • Drop hash DB and use sqlite3 directly
    • Use Django forms and views
  • locale: Update translations for German, Swedish, Turkish, Ukrainian
  • tests: Use BaseAppTests for functional tests of most apps

  • utils: Fix ruamel.yaml deprecation warnings

79. FreedomBox 21.12 (2021-10-25)

  • locale: Update translations for Bulgarian, Czech, French, German, Turkish, Ukrainian
  • middleware: Don't show setup view to non-admin users
  • performance: Add backup support (no data)
  • storage: Pass optional mount point to partition expansion
  • storage: tests: Fix tests for expanding disk partitions
  • tests: Add BaseAppTests class for common functional tests

80. FreedomBox 21.11 (2021-10-11)

80.1. Highlights

  • ttrss: Fix daemon not running sometimes on startup

80.2. Other Changes

  • *: Always pass check= argument to subprocess.run()
  • *: Convert all functional tests to python format
  • *: Move all systemd service files from /lib to /usr
  • calibre: Run service only if when installed
  • d/control: Allow building with python interpreter of any arch
  • d/rules: Don't install and enable other systemd service files
  • d/rules: Don't use setup.py to invoke tests, invoke directly instead
  • email: Manage known installation conflicts
  • locale: Update translation for Bulgarian, Ukrainian
  • package: Add functions for removing packages
  • performance: Cleanup code meant for cockpit version < 235

  • pyproject.toml: Merge contents of .converagerc
  • pyproject.toml: Merge contents of pytest.ini
  • settings: Choose password hashing complexity suitable for SBCs
  • setup: Show and remove conflicts before installation
  • sso, translation: Help set language cookie when user logins in
  • storage: tests: functional: Fix tests always getting skipped
  • tests: Add some missed marks for functional tests
  • tests: Add tests for action utilities
  • tests: Improve handling of tests skipped by default
  • tests: help: Add help view tests
  • translation: Always set language cookie when switching language
  • ttrss: Add systemd security hardening to daemon
  • ttrss: tests: functional: Make subscription faster
  • user: Accommodate Django 3.1 change for model choice iteration
  • users: Help set language cookie when user profile is edited
  • wordpress: Run service only if when installed and configured

81. FreedomBox 21.10 (2021-09-27)

81.1. Highlights

  • locale: Update translations for German, Italian, Swedish, Turkish, Ukrainian

81.2. Other Changes

  • Use Django gettext functions instead of ugettext
  • Use allow/denylist instead white/blacklist in comments
  • Use django.urls.re_path() instead of its alias url()
  • Various isort fixes
  • pyproject: Make isort consistent across execution environments
  • settings: Set Django auto field type explicitly
  • signals: Drop provider args when creating Signal object
  • sso: Update usage of OpenSSL crypt signing API
  • tests: Convert functional tests to python format
  • tests: Introduce fixtures to make it easy to test actions
  • tests: Show warning when app not available
  • tests: Use common fixtures for testing actions module
  • tests: Use newer splinter API for finding links
  • views: Update utility for checking URL safety

82. FreedomBox 21.9 (2021-09-18)

82.1. Highlights

  • mediawiki: Backup and restore uploaded files
  • mediawiki: Enable a subset of default extensions

82.2. Other Changes

  • apache: Update security settings
    • Drop support for GnuTLS
    • Drop support for SSLv3, TLSv1 and TLSv1.1
    • Enable and prioritize HTTP/2 protocol
    • Setup Mozilla recommended configuration
  • locale: Update translations for Bulgarian, Chinese (Simplified), Dutch, Persian, Russian, Swedish, Turkish, Ukrainian
  • mediawiki: Handle upgrade for 1.35
  • mediawiki: Switch to MediaWiki 2020 logo

  • plinth: remove diagnose command
  • Add workaround for Django 3.2 with captcha 0.5.6

83. FreedomBox 21.8 (2021-08-30)

83.1. Highlights

  • wordpress: New app to manage a WordPress site/blog

83.2. Other Changes

  • d/control: Drop wireless-tools as recommends
  • email: Basic app to manage an email server
    • - Email server app is currently disabled by default, so it is not yet visible in the interface.
  • locale: Update translations for Norwegian Bokmål, Ukrainian
  • security: Remove display of past vulnerabilities

84. FreedomBox 21.7 (2021-08-16)

84.1. Highlights

  • ttrss: Allow upgrade to version 21

84.2. Other Changes

  • locale: Update translations for Albanian, Bengali, Chinese (Simplified), German, Indonesian, Norwegian Bokmål, Ukrainian, Vietnamese
  • action_utils: Use flag to indicate freedombox package has been held
  • debian: Ensure fuse gets replaced by fuse3

85. FreedomBox 21.6 (2021-05-31)

85.1. Highlights

  • locale: Add Sinhala language
  • locale: Add Vietnamese language
  • backups: Change submit button to fix translation issues

85.2. Other Changes

  • locale: Update translations for Chinese (Simplified), Chinese (Traditional), Dutch, French, German, Hungarian, Indonesian, Japanese, Portuguese, Sinhala, Swedish, Telugu, Turkish, Vietnamese

86. FreedomBox 21.5 (2021-04-19)

86.1. Highlights

  • ejabberd: Add STUN/TURN configuration
  • locale: Add Albanian language

86.2. Other Changes

  • Update copyright year
  • action_utils: Introduce utility for masking services
  • ci: Merge with Salsa CI pipeline
  • config, dynamicdns, pagekite: Remove incorrect use of str
  • config: Convert entered domain name to lower case
  • config: Disable rsyslog and syslog forwarding
  • config: Fix tests related to user home directory
  • config: Install and configure zram for swap
  • container script: Must convert env. var. string to a Path object
  • container: Work in the absence of systemd in PATH
  • container: distribution as environment variable
  • coturn: Mention ejabberd in app description
  • coturn: Validate TURN URIs if provided in form
  • debian: Add coverage to autopkgtest
  • deluge, mldonkey, syncthing, transmission: Depend on nslcd.service
  • deluge: Fix daemon user not in freedombox-share group after installation
  • diagnostics: Use lock to protect results
  • docs: Add filename to code snippets in tutorial
  • docs: Add missing imports in tutorial
  • docs: Add some troubleshooting information
  • docs: Generate developer documentation
  • docs: Improve Developer Documentation index page
  • docs: Set the version attribute as required instead of optional

  • dynamicdns: Convert entered domain name to lower case
  • dynamicdns: Wait after changing domain name in tests
  • first_boot: Use session to verify first boot welcome step
  • letsencrypt: Always return a diagnostics result
  • locale: Update translations for Albanian, Chinese (Simplified), Dutch, German, Greek, Indonesian, Polish, Spanish, Swedish, Turkish
  • pagekite: Convert entered kite name to lower case
  • security: Clarify vulnerability count and provide link to more info
  • security: Ensure that fail2ban is not re-enabled on version increment
  • security: Increment app version to reload fail2ban
  • security: Move fail2ban default configuration to this app
  • ssh, apache: Make fail2ban use systemd journald backend by default
  • users: Fix unit test failures when LDAP is empty

87. FreedomBox 21.4.2 (2021-03-28)

87.1. Highlights

  • firstboot: Use session to verify first boot welcome step

87.2. Other Changes

  • locale: Update translations for German, Greek, Indonesian, Turkish
  • manual: Update Contributing and Matrix Synapse pages

88. FreedomBox 21.4.1 (2021-03-13)

88.1. Highlights

  • deluge, mldonkey, syncthing, transmission: Ensure nslcd is running before the service is started
  • deluge: Fix daemon user not in freedombox-share group after installation

88.2. Other Changes

  • config: Fix tests related to user home directory
  • locale: Update translations for Dutch, German, Greek, Polish, Spanish, Swedish, Turkish

89. FreedomBox 21.4 (2021-02-28)

89.1. Highlights

  • matrix-synapse: Auto configure STUN/TURN using coturn server

89.2. Other Changes

  • coturn: Add new component for usage of coturn by other apps
  • coturn: Minor refactor view to use utility to generate URIs
  • coturn: Remove advanced flag, make app visible to all
  • locale: Update translations for Dutch, French, German, Hungarian, Italian, Lithuanian, Norwegian Bokmål, Swedish, Turkish
  • matrix-synapse: Update description to talk about TURN configuration
  • plinth: Disable start rate limiting for service
  • ui: Fix buttons jumping on click in snapshots page
  • upgrades: Disable searx during dist-upgrade

90. FreedomBox 21.3 (2021-02-11)

90.1. Highlights

  • zoph: Add new app to organize photos
    • Only available in Debian testing (bullseye) due to issues in buster.

90.2. Other Changes

  • locale: Update translations for Dutch, Greek, Spanish, Swedish, Turkish
  • sharing: Improve shares group access description
  • upgrades: Add 10 minute delay before apt update
  • upgrades: Disable apt snapshots during dist upgrade
  • upgrades: Only check free space bytes before dist upgrade

91. FreedomBox 21.2 (2021-02-05)

91.1. Highlights

  • calibre: Fix freedombox.local inaccessible after enabling app
  • matrix-synapse: Install python3-psycopg2 from backports

91.2. Other Changes

  • backups: schedule: tests: Fix failures due to long test run
  • jsxc: Fix issues with jQuery >= 3.5.0

  • locale: Update translations for Bengali, Dutch, French, German, Hungarian, Italian, Polish, Russian, Spanish, Swedish, Turkish
  • mediawiki: Fix app installation process doesn't display status information
  • mediawiki: Set default logo to mediawiki.png
  • minidlna: Implement force upgrading from older version
  • minidlna: Minor refactor of media directory handling
  • plinth: Show running spinner when app installation is in progress
  • radicale: Allow older 2.x release to upgrade to 3.x
  • roundcube: Allow upgrade to 1.4.*
  • tests: Update functional tests default config
  • upgrades: Add notifications for dist upgrade
  • upgrades: Increment version for MatrixSynapse 1.26

92. FreedomBox 21.1 (2021-01-25)

92.1. Highlights

  • backups: Add scheduled backups for each location

92.2. Other Changes

  • container script: Various improvements
  • locale: Update translations for Bulgarian, Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, French, Galician, German, Greek, Gujarati, Hindi, Hungarian, Italian, Lithuanian, Norwegian Bokmål, Persian, Polish, Portuguese, Russian, Serbian, Slovenian, Spanish, Swedish, Turkish, Ukrainian
  • networks: Change connection type to a radio button
  • networks: Hide deactivate/remove buttons for primary connections
  • networks: Prevent unintended changes to primary connection.
  • networks: Separate the delete button and color it differently
  • networks: Use radio buttons for network modes
  • performance: Fix web client link to Cockpit
  • plinth: Fix disable daemon when service alias is provided
  • setup: Enable essential apps that use firewall
  • syncthing: Create LDAP group name different from system group
  • syncthing: Hide unnecessary security warning
  • tahoe: Disable app
  • ui: New style for select all checkbox
  • upgrades: Require at least 5 GB free space for dist upgrade

93. FreedomBox 21.0 (2021-01-11)

93.1. Highlights

  • apache2: Allow downloads in openvpn and backups with latest browsers

93.2. Other Changes

  • locale: Update translations for Dutch, French, German, Hungarian, Polish, Spanish, Swedish, Turkish
  • app: Add locked flag
  • app: component: Add app_id and app properties
  • app: info: Move client validation to info component
  • backups: Add new component for backup and restore
  • backups: Don't open a new window for downloading backups
  • dev-container: 'up' command: Show banner also when container is already running
  • dev-container: Add command to print container IP address
  • dev-container: Add subcommand to run tests
  • doc: dev: Update the tutorial to reflect latest API/code
  • ejabberd: functional tests: Wait until the jsxc buddy list is loaded
  • functional tests: Make tests compatible with pytest-bdd v4.0
  • functional-tests: Fix installation errors in install.sh script
  • gitweb: Add functional tests for git-access group
  • gitweb: tests: functional: Fix test failures in localized environment
  • mumble: Updated mumla and removed plumble from clients list
  • openvpn: Don't show running status on download profile button
  • plinth: Fix daemon is enabled check when service alias is provided
  • radicale: Fix backup and restore of configuration
  • tests: functional: Improve creating users in tests
  • transmission: Show port forwarding information
  • transmission: Update description
  • upgrades: Add service for dist upgrade
  • upgrades: Ensure freedombox package is upgraded during dist upgrade
  • upgrades: Hold tt-rss during dist upgrade, if available
  • upgrades: Install python3-systemd for unattended-upgrades
  • upgrades: Restart FreedomBox service at end of dist-upgrade

  • upgrades: Use full path to searx action script
  • users: Skip action script tests if LDAP is not set up

94. FreedomBox 20.21 (2020-12-28)

94.1. Highlights

  • apache: Create snake oil certificate if not exists
    • Fixes an issue when installing FreedomBox on Hetzner Cloud's Debian image

  • calibre: Fix link to manual page

94.2. Other Changes

  • deluge: Require user to be in bit-torrent group to access
  • locale: Update translations for German, Hungarian, Polish, Russian, Spanish, Swedish
  • security: Fix access denied for user daemon from cron
  • upgrades: Allow grub-pc upgrade without reinstalling grub
  • upgrades: Update searx search engines during dist upgrade
  • users: Remove timeout when creating Samba user

95. FreedomBox 20.20.1 (2020-12-19)

95.1. Highlights

  • config: Skip homepage test on buildd
  • ui: Migrate from bootstrap 3 to bootstrap 4

95.2. Other Changes

  • apache: Disallow all inline styling in sandbox settings
  • gitweb: Make functional tests compatible with pytest-bdd v4.0
  • javascript: Fix disabled submit buttons when navigating back to a page
  • locale: Update translations for Dutch, German, Turkish
  • ui: Adopt a consistent and new table style

96. FreedomBox 20.20 (2020-12-14)

96.1. Highlights

  • config: Add user websites as choices for homepage config
  • templates: Make toggle button responsive

96.2. Other Changes

  • apache: Add app name for diagnostics
  • diagnostics: Improve exception handling in app diagnostics
  • diagnostics: Show app name and fallback to app id if not exist
  • locale: Update translations for Dutch, French, German, Portuguese, Spanish, Swedish, Turkish
  • mumble: Implement force upgrade for 1.3.*
  • snapshot: Check that / is a btrfs subvolume before setup
  • upgrades: Hold mumble-server during dist upgrade

97. FreedomBox 20.19 (2020-11-30)

97.1. Highlights

  • openvpn: Create user group "vpn"
  • upgrades: Add first boot step to run initial update

97.2. Other Changes

  • bepasty: Apply translation to autogenerated comments
  • locale: Update translations for Bengali, Dutch, German, Spanish
  • networks: Apply translation to a tooltip
  • samba: Show toggle buttons and share names
  • snapshots: Translate snapshot types (field description)
  • upgrades: Fix sources list for dist upgrade from buster
  • upgrades: Hold freedombox package during dist upgrade

98. FreedomBox 20.18.1 (2020-11-23)

  • locale: Update translations for Dutch, French, German, Italian, Norwegian Bokmål, Spanish, Swedish, Turkish
  • sso: Fix regression in auth-pubtkt configuration

99. FreedomBox 20.18 (2020-11-16)

99.1. Highlights

  • openvpn: Support Elliptic Curve Cryptography (ECC)
    • If you are already using OpenVPN, you can migrate to ECC to improve speed and security. Visit the OpenVPN page in the FreedomBox interface to perform the one-time migration, and to re-download the client profiles.

99.2. Other Changes

  • dynamicdns: Handle IPv6
  • locale: Update translations for Dutch, French, German, Italian, Spanish
  • openvpn: Cleanup easyrsa 2 to 3 upgrade code
  • openvpn: Remove explicit setup step

100. FreedomBox 20.17.1 (2020-11-07)

  • ci: Fix flake8 errors
  • debian: Rename source package to freedombox
  • locale: Update translations for German, Italian, Turkish
  • pubtkt: Fix Python format language errors

101. FreedomBox 20.17 (2020-11-02)

101.1. Highlights

  • locale: Add Chinese (Traditional) translation
  • mediawiki: Add action to set domain name
  • upgrades: Add a setting to enable dist upgrade

101.2. Other Changes

  • apache: setup uwsgi by default
  • backups: i18n: Mark form success messages for translation
  • locale: Update translations for Danish, French, German, Italian, Norwegian Bokmål, Polish, Russian, Spanish, Swedish, Telugu, Turkish
  • mediawiki: Ensure password file is not empty
  • networks: css: Make button wider in network list
  • networks: i18n: Mark string for translation on delete page
  • networks: i18n: Mark various strings for translation
  • notifications: i18n: Mark app names and extra data for translation
  • package: i18n: Mark progress status strings for translation
  • upgrades: Disable the option when not able to dist upgrade

102. FreedomBox 20.16 (2020-10-19)

102.1. Highlights

  • app: Add donation buttons on app pages
  • updates: Eliminate delay and better status for manual upgrade

102.2. Other Changes

  • calibre: Update group description to reflect 'using' app
  • diagnostics: Lazy format all diagnostic test strings properly
  • diagnostics: Show low system memory notifications
  • help: Link to updates page when new version is available
  • locale: Update translations for Chinese (Simplified), French, Greek, Norwegian Bokmål, Russian, Slovenian, Spanish, Swedish, Turkish
  • notifications: Show severity level on every notification
  • upgrades: Add status section showing version and upgrade status

103. FreedomBox 20.15 (2020-10-05)

103.1. Highlights

  • calibre: Add new e-book library app
  • mumble: configure letsencrypt component
  • upgrades: Detect and upgrade to next stable release

103.2. Other Changes

  • bepasty: Change default permissions to 'read'
  • container: Assign virtual network interface to trusted firewall zone
  • container: Handle edge cases with container update
  • coturn: Don't handle certificates if not installed
  • debian/control: Add sshpass as build dependency
  • doc: Before fetching, drop all old to cleanup deleted pages/images
  • doc: dev: Link to list of potential apps from tutorial