New profile for Fürstenwalde. At the moment we use parts of the Berlin-
infrastructure. Thus I have not changed the ip-address-related things.
Signed-off-by: Martin Hübner <martin.hubner@web.de>
[reword and rewrap commit message]
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
The mesh_network option is used to check the user input. The wizard
checks if the input ip address is part of the mesh_network. We use
multiple /16 networks. There is no support for multiple ranges so we the
10.0.0.0/8.
For reference the ip list:
https://wiki.freifunk.net/IP-Netze
Signed-off-by: Philipp Borgers <borgers@mi.fu-berlin.de>
After some discussion in our meetings and on the maling list we decided to
change the SSID to a fixed one.
Signed-off-by: Hannes Fuchs <hannes.fuchs@gmx.org>
- 31C3: this was used back in 2014, looking forward for new the congress
- seefeld: died in march 2013 ... (as per note on their Wiki-page)
Signed-off-by: Sven Roederer devel-sven@geroedel.de
these patches are used by the berlin-freifunk-community since 2014
- change ssid
(563c955a19)
- remove obsolete olsr defaults
(4558f8c88a)
- use intern-chXX.freifunk.net as ssid scheme for adhoc
(6ce8f59082)
- add mcast_rate
(e90753ed04)
(0185677372)
- add wifi_device and *_iface for 5GHz
(5823e89a3d)
- remove owm_api and mapserver key from community profile
(d4ee2e1bce)
- add two ipv6 nameservers
(83df6ab771)
- change default dhcp leasetime to 5 minutes
(b38af129e0)
- remove non existent freifunk community profiles (Berlin)
(6c49443bde)
Signed-off-by: Sven Roederer <freifunk@it-solutions.geroedel.de>
- Freifunk Aachen now uses Gluon
- In addition, the old IP space has already been reallocated for other
communities, so the information here is definitely outdated.
Signed-off-by: David Kolossa <david.kolossa@posteo.de>
The SSID freiburg.freifunk.net is used as the VAP-SSID so we have to use sth. different for the ad-hoc SSID..
ATM 02:d1:11:37:fc:38 - why not using 02:CA:FF:EE:BA:BE...
