Difference between revisions of "Mesh/Spectrum"

Jump to navigation Jump to search
500 bytes added ,  05:29, 18 April 2014
 
(2 intermediate revisions by the same user not shown)
Line 28: Line 28:
*157 - 5785 MHz (5765-5805)
*157 - 5785 MHz (5765-5805)
*161 - 5805 MHz (5785-5825)
*161 - 5805 MHz (5785-5825)
:Beware that [https://dev.openwrt.org/ticket/10136 you cannot use channel 165 as part of a HT40+/- channel]


Maximum power output for these channels at 20 or 40 mhz is [http://louise.hallikainen.org/FCC/FccRules/2011/15/407/ 1 watt], with the following caveats:
Maximum power output for these channels at 20 or 40 mhz is [http://louise.hallikainen.org/FCC/FccRules/2011/15/407/ 1 watt], with the following caveats:
Line 149: Line 150:
== 5 GHz ==
== 5 GHz ==


Here are some reasonable settings for a point to point or point to multi-point 5 GHz rooftop node:
Here are some (possibly?) reasonable settings for a point to point or point to multi-point 5 GHz rooftop node:


<pre>
<pre>
Line 156: Line 157:
htmode HT40
htmode HT40
chanbw 20
chanbw 20
txpower  
txpower 20
noscan 1 (?)
</pre>
</pre>
These OpenWRT settings are documented [http://wiki.openwrt.org/doc/uci/wireless#common.options1 here].
I'm not actually sure what the noscan feature does or whether it's a good idea. There's a warning that it will violate regulatory requirements, but I'm not sure if it's related to DFS or if it's something else. - ([[User:Juul|Juul]] ([[User talk:Juul|talk]]))


The ath9k driver does not yet have support for a 802.11n-only mode (also known as greenfield). The closest is 802.11n+a. Apparently you can prevent 802.11a nodes from associating somehow. [http://comments.gmane.org/gmane.linux.drivers.ath9k.devel/10735 source].
The ath9k driver does not yet have support for a 802.11n-only mode (also known as greenfield). The closest is 802.11n+a. Apparently you can prevent 802.11a nodes from associating somehow. [http://comments.gmane.org/gmane.linux.drivers.ath9k.devel/10735 source].

Navigation menu