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>
This patch adds the support to run the set_mcast_rate() command on
adhoc and mesh_point vifs. With this command it is possible to tune
the bitrate to use when sending group frames. This command can be used
even if the vifs has already joint the ibss/mesh network.
Signed-off-by: Antonio Quartulli <ordex@autistici.org>
The GET_INTERFACE command receives also the ssid as part of the reply.
This patch makes iw print the ssid together with the other information
when issuing the "iw dev $vif info" command.
Signed-off-by: Antonio Quartulli <ordex@autistici.org>
This patch introduces the "ap-force" argument to the scan command.
This argument instructs mac80211 to trigger the scan even if the
interface is configured as AP and has already started beaconing (the
driver may not support such operation)
Signed-off-by: Antonio Quartulli <ordex@autistici.org>
Sam Leffler [Wed, 17 Oct 2012 19:20:04 +0000 (12:20 -0700)]
iw: add lowpri and flush scan operands
Add lowpri (low priority) and flush operands to the scan cmd to
request the equivalent flags be set in the scan request. Note
these are applied regardless of the feature flags to support
testing drivers that do not implement them.
iw: allow setting mesh proactive tree building mode related parameters
This patch allows the setting of following mesh parameters:
mesh_hwmp_active_path_to_root_timeout
mesh_hwmp_root_interval
mesh_hwmp_confirmation_interval
Also ensure the TU is printed for mesh_hwmp_rann_interval.
Johannes Berg [Fri, 6 Jul 2012 06:50:00 +0000 (08:50 +0200)]
add (optional) hwsim code
As an example, the hwsim code was useful, but for normal
distros it's not. Allow developers to build hwsim code
into the iw binary with "make HWSIM=y".
iw: fix the Makefile for multiple libnl installations
All different versions of libnl can cohexist on a system
(libnl-1, libnl-2, libnl-3.0, libnl-3.1 and libnl-3.2).
When multiple versions are installed only link against
the highest versioned one, otherwise there might be
unpredictable results (including segmentation faults):
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7bd7f7d in genl_unregister () from /usr/lib64/libnl-genl.so.3
(gdb) where
This patch fixes the Makefile to link against only one
of the libraries, the highest version found.
Chun-Yeow Yeoh [Sun, 4 Mar 2012 17:41:46 +0000 (01:41 +0800)]
iw: Add support of setting non-forwarding entity in Mesh
This patch creates a new mesh parameter known as mesh_fwding. Mesh node will become
non-forwarding entity if this parameter is set to 0. By default, it is set as 1.
Gilles Espinasse [Fri, 11 Nov 2011 23:04:38 +0000 (00:04 +0100)]
fix compilation against libnl-3.x
Add configuration to compile against 3.1 and 3.2 without breaking 3.0
That's a bit of mess with version on .pc file and the part which belong or not to the shared lib name.
libnl-genl-3.1 is broken and can't be used
Starting from 3.2.0, I could have used libnl-genl-3.0.pc file like in patch V1 and not hardcode adding libnl-genl-3 into LIBS
I consider this a matter of tast for now, coded like previous versions that can't use that way to code.
Added an echo to display against which libnl version iw is compiled.
That particulary help me to test with various versions because of the mess on .pc file version as libnl>=3.2.0 has again pc file version with 3.0 number.
Removed the version_check part instead of extending blindly for the new versions.
That was mostly dead code because prior check on NLLIBNAME not empty already care.
The only case where that could matter would be using something stupid like
NLLIBNAME=foo make
Compilation tested to work against
- libnl-2.0
- libnl-3.0
- libnl-3.1
- libnl-3.2.0
- libnl-3.2.2