krombel/site-ffmuc
1
0
Fork 0
forked from remote/site-ffmuc
Code Issues 4 Pull Requests 1 Releases Wiki Activity

ssid vs. mesh_ssid (mentioned in #7).. Accedently hit the wrong line. fixed

Browse Source
This commit is contained in:
Frieder Griesshammer
2014-06-18 11:24:30 +02:00
parent ceb1942bae
commit 80c07ae320
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
site.conf
View File

@@ -45,8 +45,8 @@
http://en.wikipedia.org/wiki/IEEE_802.11#Regulatory_domains_and_legal_compliance http://en.wikipedia.org/wiki/IEEE_802.11#Regulatory_domains_and_legal_compliance
wifi24: Wifi settings for 2.4 GHz frequency devices wifi24: Wifi settings for 2.4 GHz frequency devices
wifi5: Wifi settings for 5 GHz frequency devices wifi5: Wifi settings for 5 GHz frequency devices
sub: sub
ssid: Wifi name shown to the user ssid: Wifi name shown to the user (We recommend %site_code%.freifunk.net)
channel: Wifi channel to use channel: Wifi channel to use
htmode: Specifies the channel width in 802.11n and 802.11ac mode, possible values are: htmode: Specifies the channel width in 802.11n and 802.11ac mode, possible values are:
HT20 (single 20MHz channel), HT20 (single 20MHz channel),
@@ -54,7 +54,7 @@
HT40+ (2x 20MHz channels, primary/control channel is lower, secondary channel is above). HT40+ (2x 20MHz channels, primary/control channel is lower, secondary channel is above).
VHT20 / VHT40 / VHT80 / VHT160 (channel width in 802.11ac, extra channels are picked according to the specification) VHT20 / VHT40 / VHT80 / VHT160 (channel width in 802.11ac, extra channels are picked according to the specification)
http://wiki.openwrt.org/doc/uci/wireless#common.options (-> htmode) http://wiki.openwrt.org/doc/uci/wireless#common.options (-> htmode)
mesh_ssid: SSID of the mesh-interface, an ugly SSID prevent clients from connecting (We recommend %site_code%.freifunk.net) mesh_ssid: SSID of the mesh-interface, an ugly SSID prevent clients from connecting (We recommend not to change this)
mesh_bssid: BSSID of the mesh-interface mesh_bssid: BSSID of the mesh-interface
mesh_mcast_rate: multicast rate of the mesh-interface mesh_mcast_rate: multicast rate of the mesh-interface
]] ]]
@@ -81,11 +81,12 @@
--[[ Next-Node --[[ Next-Node
next_node: Howto reach the node you are currently connected to next_node: Howto reach the node you are currently connected to
The node will always be reachable at that address, and it's the same on all nodes. Because next_node packets are redirected within the node itself, there will be no conflicts.
sub sub
ip4: IPv4 Address to use ip4: IPv4 Address to use
ip6: IPv6 Address to use ip6: IPv6 Address to use
mac: MAC Address to use mac: MAC Address to use
(TODO: What is the purpose of this MAC-Adress here?) (TODO: What is the purpose of this MAC-Address here?)
]] ]]
next_node = { next_node = {
ip4 = '10.130.0.1', ip4 = '10.130.0.1',