On 05/07/2014 02:01 AM, Johannes Berg wrote:
On Tue, 2014-05-06 at 10:56 -0700, Ben Greear wrote:
But, it seems if I have another vif up, it will fail, even if that
vif is (should be?) using the exact same frequency.
./local/sbin/iw phy wiphy0 interface add moni0 type monitor
./local/sbin/ip link set dev moni0 up
./local/sbin/iw dev moni0 set freq 5180 80 5210
-> yields error:
command failed: Device or resource busy (-16)
You can't set the monitor frequency if you're using the hardware for
something else already. We could potentially allow that if the chandefs
are compatible, but that's getting into really messy territory so I'm
not sure I want to go there - if for example the other interface
switches bandwidth or even channel the monitor would usually simply
follow around.
Ok, as long as I know why then the failure is not so concerning.
Another question: if I create a monitor interface first, and
successfully set it's frequency, what do I need to do to allow
a station to move to a different frequency later?
Thanks,
Ben
johannes
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
