This introduces beacon_int and basic_rate (per wifi-device), and
dtim_period and max_listen_int (per wifi-iface) for mac80211. These
configure the beacon interval, basic rate specification, DTIM period
(one DTIM per this many beacon frames), and maximum listen interval
that a STA will be permitted to associate with. All of the new
settings are optional; if they're absent, the existing hostapd (or, in
the case of basic_rate, driver) defaults will be used.
The existing bintval property only used for type adhoc is moved from
wifi-iface to wifi-device, and is renamed to beacon_interval because
bintval isn't a great name. The beacon interval is property of the
wifi-device; while the choice between wifi-device and wifi-iface may
not be relevant with an adhoc network, there's no reason to configure
the same property one way for type adhoc and another for type ap. This
change isn't expected to cause many problems, as bintval was added
recently, in r25111.
Similarly, the list of basic rates, also added for type adhoc in
r25111, is a property of the device and not the interface. Further, it
ought to be represented in UCI as a list, not a string dependent on
the format that iw uses. I’ve moved it onto the device, renamed it to
basic_rate, and made it configurable for APs via hostapd. Finally, I
adapted it to use the same kb/s representation as mcast_rate; there's
precedent for this format in that it's also how madwifi interprets
mcast_rate.
Neither bintval nor basicrates were ever documented in the UCI
wireless configuration page on the wiki. When this change is
committed, I'll update the documentation as needed.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25837 3c298f89-4303-0410-b956-a3cf2f4a3e73
r24503 (trunk) and r24505 (backfire) revised the regulatory rules used
for the ath drivers' world regulatory domains in the 5GHz band by
opening up channels 36, 40, 44, and 48 to being used without the
*_PASSIVE_SCAN and *_NO_IBSS flags set. This was done by breaking
ATH9K_5GHZ_5150_5350 into two REG_RULES. The various struct
ieee80211_regdomains that reference these rules in their reg_rules
fields need to have their n_reg_rules fields updated accordingly.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25418 3c298f89-4303-0410-b956-a3cf2f4a3e73
- split antenna options into rxantenna and txantenna to bring it in line with broadcom and madwifi
- get rid of temporary variables
- follow the documented config protocol for wep keys (option key # + option key# [s:]data)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25116 3c298f89-4303-0410-b956-a3cf2f4a3e73
Add new options 'bintval' (beacon interval), 'basicrates' (basic rates) and
'antenna' (antenna selection) for /etc/config/wireless to be used with
mac80211 drivers.
Enable WEP encryption for IBSS mode.
Patch from: kentarou matsuyama <matsuyama@thinktube.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25111 3c298f89-4303-0410-b956-a3cf2f4a3e73
Add support of mac address filter. Now 'macfilter' and 'maclist' options
can be used with mac80211.
Patch from: kentarou matsuyama <matsuyama@thinktube.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25105 3c298f89-4303-0410-b956-a3cf2f4a3e73
It has been confirmed by Atheros that this PCI bug affects the RX side only,
so we can keep the 128B DMA size for TX.
With this change we can double the thruput of ath5k from 15Mps to 30Mbps.
We have been using this patch since more than 6 month in a production
environment without problems and a significant performance improvement.
It has also been said to fix HW encryption:
http://www.mail-archive.com/ath5k-devel@lists.ath5k.org/msg04311.html
Patch from: kentarou matsuyama <matsuyama@thinktube.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@25104 3c298f89-4303-0410-b956-a3cf2f4a3e73
