Hi,
What is the idea behind channel contexts? Is it just to create an
abstraction between the different vifs regarding the channel (each vif
is allowed to operate on its own channel)? In case I want just a single
vif, can I ignore the chanctx (specify that the driver does not support
Hi,
The channel context is mentioned in lots of mails and pieces of code,
but its significance or goal is never mentioned. Could someone please be
so kind to elaborate on this?
I believe the channel context is used to provide some hardware
abstraction towards the driver and mac, such that
On 07/22/2015 07:16 PM, Oleksij Rempel wrote:
Am 22.07.2015 um 18:37 schrieb Rolf Anderegg:
On 16/07/15 13:54, Oleksij Rempel wrote:
Am 13.07.2015 um 13:52 schrieb Rolf Anderegg:
I suspect that there are bandwidth/speed issues when dealing with USB
adapters, but that does not inherently
On 03/13/2015 12:36 PM, Cedric VONCKEN wrote:
My test plateforme is very simple, One sta (with openwrt), one AP and a
computer connected to the AP.
I launch iperf on the sta and power up the AP.
With wireshark I can observe 1 s delay between the frame EAPOL 4/4 and
the arp request sent by the
Hi,
On 03/06/2015 06:20 AM, Marco wrote:
On 03/05/15 06:10, Christian Lamparter wrote:
Hello,
On Wednesday, March 04, 2015 11:02:25 PM ma...@tampabay.rr.com wrote:
Quite a while back after doing an upgrade to the latest (back then)
compat-wireless, I noticed that I was only seeing
On 03/06/2015 05:12 PM, marco wrote:
On Fri, Mar 06, 2015 at 10:34:42AM +0100, wim torfs wrote:
Hi,
Perhaps a silly question, and I'm sure you already covered this, but I need
to ask, just to be sure. Did you enable promiscuous mode to capture the data
packets?
Could you elaborate
If it is the case that the 4-way handshake fails, then I have seen this
issue before. The problem is that messages 1 to 4 are sent with the
previous key. However, right after sending message 4/4, does
wpa_supplicant set the new key. In some cases, such as in a high
throughput environment, this
On 02/20/2015 11:11 AM, Mário Lopes wrote:
Quoting wim torfs wto...@gmail.com:
On 02/19/2015 03:53 PM, Mário Lopes wrote:
Hi everyone.
When using frame injection over monitor interface, with handmade packet
with Radiotap header + QoS + Data, at sender I capture the packet with
tcpdump
On 02/19/2015 03:53 PM, Mário Lopes wrote:
Hi everyone.
When using frame injection over monitor interface, with handmade packet
with Radiotap header + QoS + Data, at sender I capture the packet with
tcpdump and it is equal to the one I sent.
Although, at receiver station, the packet is
I will try to answer your question, please correct me if I'm wrong.
On 01/29/2015 11:55 PM, Rafał Miłecki wrote:
Hi,
I'm looking at deauthentication disassociation with cfg80211 API.
AFAIK both frames can be send by STA as well as AP (according to the
standard). I was looking info few
not use mac80211.
Mwifiex is very much located under drivers/net/wireless; its not in
net/wireless. net/wireless has cfg80211 driver.
Thanks,
Avinash.
From: linux-wireless-ow...@vger.kernel.org
[linux-wireless-ow...@vger.kernel.org] On Behalf Of wim torfs
. This correction has
not been tested, it was discovered during a code review.
Signed-off-by: Wim Torfs wto...@gmail.com
---
diff -uprN linux-3.18.1.orig/net/mac80211/iface.c
linux-3.18.1.patched/net/mac80211/iface.c
--- linux-3.18.1.orig/net/mac80211/iface.c 2014-12-16 18:39:45.0
+0100
12 matches
Mail list logo
