From: Hakan Coskun <coskun@cs.tu-berlin.de>
To: linux-wireless@vger.kernel.org
Subject: Multiple station interfaces with one wifi card
Date: Fri, 6 Aug 2010 20:47:45 +0200 [thread overview]
Message-ID: <46641FB7-7BF7-4BFA-9AF2-C1369840FF84@cs.tu-berlin.de> (raw)
In-Reply-To: <7CE373CC-7FCB-41A0-AC81-06E9893D8BC8@cs.tu-berlin.de>
Hi,
we are doing research in order to study the behaviour of virtual wifi interfaces with channel switching. After a simulative study, we started to perform some real world experiments with ath9k, which is able to run multiple wiphys on top of a card. This is working quite good. Of course there are several restrictions and performance problems, we are working on some scheduling algorithms to improve the operation.
But now to take it a step further, we plan to go for a mac80211 based virtualization, meaning to run multiple vifs in parallel in station mode. The first step is to run them on the same channel, but as expected this is not working, yet. We can create several interfaces with iw, there is no problem. Even scanning is working, but as soon as we want to connect to an open AP we get into trouble. Authentication and association are not working.
mac80211 needs to be extended with additional functionality like ath9k, to cope with multiple associations and channel switching, etc.. The internals of ath9k are clear to us, since the virtualization code is not big, and the patches well documented. We want to adapt them to mac80211, in order allow vifs to connect to APs simultaneously.
How can we track the sequence of operations during the runtime in order to get a better understanding of the mac80211. At the moment, we enabled tracing and debug messages for mac80211, this helps but is not sufficient to follow the functions step by step. We can put a lot of debugging messages into the files, but are there any "best practices" we should follow.
Thanks,
Hakan
prev parent reply other threads:[~2010-08-06 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 19:03 Compat-wireless release for 2010-06-18 is baked Compat-wireless cronjob account
[not found] ` <C2473D7F-D624-48C1-A9C5-46678C5CD489@cs.tu-berlin.de>
[not found] ` <7CE373CC-7FCB-41A0-AC81-06E9893D8BC8@cs.tu-berlin.de>
2010-08-06 18:47 ` Hakan Coskun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46641FB7-7BF7-4BFA-9AF2-C1369840FF84@cs.tu-berlin.de \
--to=coskun@cs.tu-berlin.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox