Add auto parameter to set distance command in order to enable ACK timeout
estimation algorithm (dynack). Dynack is automatically disabled setting valid
value for coverage class. Currently dynack is supported just by ath9k
This patch is based on "configure dynack through mac80211/cfg80211 stack"
patchset sent on linux-wireless
Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Allow user to configure frequency and channel type during
mesh join command.
Signed-off-by: Ashok Nagarajan <ashok.dragon@gmail.com> Signed-off-by: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
v2: use chandef similar to IBSS (Johannes)
v4: make the mesh join command more self-explanatory (Bob Copeland) Signed-off-by: Johannes Berg <johannes.berg@intel.com>
iw: embrace the Developer Certificate of Origin for contributions
The Linux kernel started to embrace a light weight development contribution
agreement process called the Developer Certificate of Origin (DCO) circa
2004. Attorneys all over the planet have conferred a lot of respect and
appreciation for this document and it provides a light weight alternative to
cumbersome and controversial Contribution License Agreements (CLAs).
Similar to streamlining FOSS licenses we also all stand to gain from
streamlining a light weight contribution agreement process for development
and in light of this the the Linux Foundation recently has made the DCO a
standalone project [0] so that any FOSS project under any FOSS license can
take advantage of the same gains. The motivation and intent is documented
only currently on my blog post [1].
Lets take advantage of the new shiny DCO and embrace it for contributions.
NOTE: Contributions before this commit that still included a Signed-off-by
line (presumably out of habit of typing -s with git commands) aren't
necessarily covered by this agreement.
Ilan Peer [Thu, 14 Nov 2013 07:15:34 +0000 (09:15 +0200)]
iw: Use NL80211_FREQUENCY_ATTR_NO_IR channel attribute
Align iw with the change in nl80211.h where NL80211_FREQUENCY_ATTR_NO_IBSS
and NL80211_FREQUENCY_ATTR_PASSIVE_SCAN were replaced by
NL80211_FREQUENCY_ATTR_NO_IR.
In case both NL80211_FREQUENCY_ATTR_NO_IR and __NL80211_FREQUENCY_ATTR_NO_IBSS
are set, assume that a new kernel is used and use the NO_IR notation,
otherwise use the previous notation.
This change requires nl80211.h with the new definitions
Simon Wunderlich [Tue, 12 Nov 2013 17:31:58 +0000 (18:31 +0100)]
iw: add support for 5 and 10 MHz channels in IBSS mode
5/10 MHz requires to send the frequency information as chandef instead
of the the old channel type, therfore send the chandef next the channel
type (the latter is still used for old kernels).
Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de> Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Don't get iw version from git if there is no .git/
The version.sh script should only try to get the version from git if the
source actually resides in a git repository, i.e. .git/ exists. Doing
otherwise in a non-git source repo results in git ascending until it
finds a .git directory, which will cause problems in some source-based
distributions ( https://bugs.gentoo.org/show_bug.cgi?id=482334 ).
Bruno Randolf [Thu, 26 Sep 2013 16:45:45 +0000 (17:45 +0100)]
iw: sync frequency to channel mapping with kernel
Use ieee80211_frequency_to_channel() and ieee80211_channel_to_frequency() as in
the current kernel. This is necessary to properly print the channel numbers for
4.9GHz channels which can be used in Japan.
User can configure the peer link expiration time with a
new mesh parameter, mesh_plink_timeout. This parameter
sets the expiration time, in seconds, for peer links.
After this time, the peer link is expired. This means the
inactive STA is removed from the list of peers and is not
considered a peer again unless it re-peers.
Amitkumar Karwar [Fri, 28 Jun 2013 19:53:45 +0000 (12:53 -0700)]
iw: add coalesce support
User can configure multiple coalesce rules using 'iw coalesce
enable <config-file>' command. The setting can be cleared using
'iw coalesce disable' command. 'iw coalesce show' displays current
configuration.
Amitkumar Karwar [Fri, 28 Jun 2013 19:53:44 +0000 (12:53 -0700)]
iw: use updated structures and enums for packet pattern
They are renamed in new nl80211.h so that they can be used for
new feature. This patch uses those updated structures and enums
to make the code look nicer.
John W. Linville [Wed, 26 Jun 2013 15:07:40 +0000 (11:07 -0400)]
iw: fix incorrect bit shifting in print_ht_mcs
iw-3.10/util.c:569:result_independent_of_operands –
"mcs[10] >> 8" is 0 regardless of the values of its operands. This occurs as the bitwise first operand of '&'.
This seems more like what was intended...
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Johannes Berg [Thu, 2 May 2013 07:29:10 +0000 (09:29 +0200)]
update version to 3.10
It seems I forgot to release 3.9 when that kernel was starting,
so there's little point in doing it now. The 3.10 merge window
has opened and wireless features are finalized, so this version
of iw matches what will be supported in 3.10.
Johannes Berg [Thu, 2 May 2013 07:22:58 +0000 (09:22 +0200)]
fix "iw phy#0 info"
Ben Greear reported that on a kernel that doesn't have the split
(and therefore filtered) wiphy dump feature, "iw phy#0 info" was
reporting data for all devices, rather than just one. This was a
result of using the split/filtered dump rather than a simple get
on "older" kernels (before 3.10!)
Fix this by checking the kernel feature before getting the data.
Small update, found while verifying against the standard.
Thanks
Jörg
The results of a boring train ride:
- Decode some IEs sent by other traveller's devices
+ IBSS ATIM window
+ TPC report
+ Old ERP IE (802.11g D4.0)
- Tiny whitespace fix
- Add Unit 'TUs' to beacon interval.
v2: TPC: Link margin element is not used in beacons
In case this project requires a sob: Signed-off-by: Joerg Mayer <jmayer@loplof.de> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Johannes Berg [Thu, 14 Feb 2013 15:32:53 +0000 (16:32 +0100)]
iw: support split wiphy dump
This adds support for the new split wiphy dump,
it only uses it for "iw list", not for "info"
though, so far. Using it for "info" would mean
querying the kernel capability first and then
using get/dump (with filter) depending on that.
Marco Porsch [Fri, 18 Jan 2013 12:05:32 +0000 (13:05 +0100)]
iw: add support for link-specific mesh power modes
The different power modes of links towards neighbor STA can be
read using
iw <dev> station get
-or-
iw <dev> station dump
The different power modes shown are:
- mesh local PS mode
- mesh peer PS mode
- mesh non-peer PS mode
where the local PS mode is "our" mode towards the neighbor, the
peer PS mode is the neighbor's mode towards us, and the non-peer
PS mode is the neighbor's non-peer PS mode as indicated in
beacons and management frames.
The local PS mode can be modified for each neighbor using
iw <dev> station set <mac-addr> mesh_power_mode
<active|light|deep>
Signed-off-by: Marco Porsch <marco@cozybit.com> Signed-off-by: Ivan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>
Marco Porsch [Fri, 18 Jan 2013 12:05:31 +0000 (13:05 +0100)]
iw: add default mesh Power Mode and Awake Window to mesh config
The default mesh power mode is the power mode that will be
assigned to newly established peer links.
The awake window is the duration the local STA will stay awake
after sending its own beacon in PS mode.
Both values can be modified as part of the mesh params.
Signed-off-by: Marco Porsch <marco@cozybit.com> Signed-off-by: Ivan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>