On Sun, Aug 1, 2010 at 3:21 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 08/01/2010 01:56 PM, Ryszard wrote: >> >> Hey Florian, >> >> thanks for the help on this! Ben/Patrick, if you rebase the patches >> for this functionality, i'm more than happy and willing to do userland >> testing on this to move it along. >> >> regs >> >> On 1 August 2010 19:37, Florian Fainelli<florian@xxxxxxxxxxx> wrote: >>> >>> Hi, >>> >>> Le Sunday 1 August 2010 03:53:13, Ryszard a écrit : >>>> >>>> Hi all, >>>> >>>> i'm working on a project that requires i can create multiple access >>>> points on the one bit of hardware. After an insane amount of googling >>>> and reading the lists the closest i've been able to come up with is >>>> something along the lines of: >>>> iw dev wlan0 interface add vap0 type __ap >>>> iw dev wlan0 interface add vap1 type __ap >>>> >>>> then using macchanger to assign unique mac addresses. >>>> >>>> I've also seen something from March 2009 >>>> (http://lwn.net/Articles/321690/) that hints at the functionality >>>> available with the ath9k which gave me a bit of hope! >>>> >>>> My question is, is it possible to create multiple virtual access >>>> points with my hardware ( Atheros Communications Inc. AR5413 802.11abg >>>> ) and the ath5k/mac80211 drivers (or is there some other method to >>>> achieve what i'm after) ? i'm not too fussed about different >>>> channels, but different SSID's and WPA keys are a requirement for the >>>> project. >>> >>> There is support for creating virtual interfaces using iw and ath5k here: >>> http://www.candelatech.com/oss/vsta.html >>> >>> I really wish someone could submit this mainline, unfortunately it is >>> pretty >>> hard to isolate the commits in this tree which are implementing virtual >>> interfaces support. >>> >>> Ben, Patrick, could you rebase your patches on top of wireless-testing >>> and >>> send them for review/testing? > > You would not believe how hard it is to keep up with the wireless tree. > Last time, > by the time we had something stable, upstream had changed too much to merge. This is why you should not do your development outside of wireless-testing. If you are doing development on a stable kernel tree then you will likely run into huge issues. You should do development on wireless-testing.git, always rebase when John has a new update, and break your changes out into a small changes as possible. If you follow these basic rules I believe you will likely have better luck with keeping your code up to date. Luis -- 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
