From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?=22Lorna_Gonz=E1lez=22?= Date: Thu, 11 Nov 2010 16:06:34 +0100 Subject: [ath9k-devel] ath9k: Virtual interface as AP In-Reply-To: <1288253027.23270.9.camel@jm-desktop> References: <20101028074721.191890@gmx.net> <1288253027.23270.9.camel@jm-desktop> Message-ID: <20101111150634.288980@gmx.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Hello I finally got a station an a virtual AP working on the same channel using the setup below. I made some test sending TCP through iperf between the AP and the station and the VAP to a station associated with it. Using an AP operating with Ieee802.11n, an atheros AR928X and without virtual interfaces I get a max throughput of 50 MBits/s. As soon as I start using my desired setup, the thoughput of the station is about 15 MBits/s... I actually need to make the rate fixed using iwconfig to get this max. Otherwise the traffic is sent at 1 MBit/s. Can someone please tell me how is the behaviour of the rate control in case of virtual interfaces on mac80211? Thanks in advanced Lorna Gonz?lez. -------- Original-Nachricht -------- > Datum: Thu, 28 Oct 2010 11:03:47 +0300 > Von: Jouni Malinen > An: "\\"Lorna Gonz?lez"" > CC: "ath9k-devel at lists.ath9k.org" > Betreff: Re: [ath9k-devel] ath9k: Virtual interface as AP > On Thu, 2010-10-28 at 00:47 -0700, "Lorna Gonz?lez" wrote: > > After trying to build two virtual interfaces, one as a STA and another > one as AP on mac80211 with an AR928X, creating a new interface with: > > > > iw phy phy0 interface add wlan1 type __ap > > > > I got a new interface called wlan1_rename, the one I used to build the > AP interface. > > > But no other stations are able to see this Virtual AP and no more frames > are sent from the VAP. > > How did you set the MAC addresses on the interfaces? Based on a quick > test, I was able to get hostapd running on the interface created with > the command above at least when not changing the address on the created > interface. A station was able to see the AP and associate. Then I > changed the MAC address of the original interface by setting locally > administered bit (02:) and I was able to associate it as a > station to an AP that was running on the same channel. The ping from the > virtual AP interface was still going through. > > Just keep in mind that not all combinations will work as far as key > setup is concerned. In other words, you may be able to get associated > with multiple interfaces, but the data frames may not get through if the > driver is not yet ready to the setup you tested. These will be > eventually addressed for most cases, but for now, you may also want to > experiment with nohwcrypt=1 if you see something that could be caused by > this. > > - Jouni > > -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl