How can I mass deploy in the Freifunk Network?
- Clear folder
tmp/images. - Generate images for every location you want to update
- Use
mass-update.shwhile you are connected to the Freifunk Network. It will automatically connect via ssh to all routers and install the new firmware.
Automatic Updates for wiki.freifunk.net
By default all articles that follow the convention will be updated automatically when config changes get merged into the main branch. To add this option to your wikiarticle add a section called "Konfiguration" and replace all values that you want to automatically change as you can see in this example-article. If you want to add a new location you can start with this template.
Wikiupdater expects an article or a redirect to the article at wiki.freifunk.net/Berlin:Standorte:$LOCATION where $LOCATION is the location name defined in your file at locations/$LOCATION.yml. You can manually run this update by using --tags wiki in a ansible config run. If you dont need the config files generated you can skip it by adding --skip-tags
Hosting your own service ( inside FreiFunk )
You need to host your service on a separate device like your old computer. to make it reachable within Freifunk define a static IP Address in the config file of your location like this:
[...]
assignments:
foo-core: 1
foo-service: 2You could choose an existing network like mgmt or define a extra one. Just make sure it doesn't have inbound_filtering: true set.
Set the corresponding static IP on your separate device. It will be reachable via the IP Address or via its internal Domain foo-service.ff.
If you encounter problems with reaching the local services make sure to check if you are connected via a VPN or have a different DNS configured.
Freifunk Berlin uses a public routable IPv6 Addressroom within its network. We can open the firewall to let traffic in. After you finished these steps you can reach your service via IPv6 from all over the world.
- Make sure your router doesnt block incoming traffic e.g. the subnetwork doesnt have
inbound_filtering - Add the following to
group_vars/role_gateway/general.yml
inbound_allow:
- name: Rule Description (mandatory)
dst: Destination IP (mandatory)
src: Source IP
proto: [tcp, udp, icmp.]
src_port:
dst_port: 22-
Update the Firewall of the Gateways
Note: This can only be done by the maintainers of the bbb
-
Check your separate device for its IPv6 Address (starting with 2001:) - it is reachbale now.
Note: IPv6 Addresses are handed out via SLAAC and might not be static. Define a static Address so it doesnt change over time