linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Any /n NICs that support APs and multiple STAs other than ath9k?
Date: Wed, 06 Oct 2010 11:51:39 -0700	[thread overview]
Message-ID: <4CACC53B.4050608@candelatech.com> (raw)
In-Reply-To: <1286390920.3655.402.camel@jlt3.sipsolutions.net>

On 10/06/2010 11:48 AM, Johannes Berg wrote:
> On Wed, 2010-10-06 at 11:45 -0700, Luis R. Rodriguez wrote:
>
>> Your best bet is to test against mac80211_hwsim, that would rule out
>> any hardware. I think Jouni and Johannes have also a way to get the
>> devices to talk to each other. Perhaps some documentation of that on
>> the kernel Documentation/networking/mac80211_hwsim/
>
> You can either use network namespaces, or you can now somehow add local
> routes (Patrick worked on that). But that's only needed if you need to
> test IP connectivity at all between the interfaces, as long as you just
> assoc etc. you don't need that.

Oh, I'm using all of Patrick's stuff, and my application is a traffic
generator, so I have no trouble generating traffic to/from interfaces on
the same system.

That said, we're hitting these problems before we ever try to start
traffic most of the time, so it's not so important.

Thanks,
Ben

>
> johannes


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2010-10-06 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 16:29 Any /n NICs that support APs and multiple STAs other than ath9k? Ben Greear
2010-10-06 18:45 ` Luis R. Rodriguez
2010-10-06 18:48   ` Johannes Berg
2010-10-06 18:51     ` Ben Greear [this message]
2010-10-06 18:49   ` Ben Greear
2010-10-06 18:58     ` Luis R. Rodriguez
2010-10-06 19:08       ` Ben Greear
2010-10-06 19:21         ` Luis R. Rodriguez

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=4CACC53B.4050608@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).