linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WDS vs. multi-channel operation
Date: Mon, 06 Aug 2012 17:06:39 +0200	[thread overview]
Message-ID: <1344265599.4807.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <501FDC87.1000204@openwrt.org>

On Mon, 2012-08-06 at 17:02 +0200, Felix Fietkau wrote:

> >> If you're going to require them to be bound to an AP though, where's the
> >> difference to the current 4-addr AP_VLAN behaviour? It seems with that
> >> you could actually implement a bound-to-AP-WDS entirely in userspace
> >> since there's no requirement to actually go through the auth/assoc
> >> sequence for hostapd to add the station entry?
> > 
> > Oh and if you actually do need WDS-type interfaces, maybe their role
> > should change to be virtual like AP_VLAN-type interfaces?

> The difference between WDS and 4-addr AP_VLAN is that WDS is AP<->AP,
> not AP<->STA. I guess it would be possible to write some code to create
> AP VLANs + station entries for remote APs based on cooked monitor mode
> based discovery or some form of mgmt frame exchange.

I was thinking just pre-configure it as you have to anyway now?

johannes


  reply	other threads:[~2012-08-06 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 13:36 WDS vs. multi-channel operation Johannes Berg
2012-08-05 17:12 ` Felix Fietkau
2012-08-05 17:21   ` Johannes Berg
2012-08-05 17:22     ` Johannes Berg
2012-08-06 15:02       ` Felix Fietkau
2012-08-06 15:06         ` Johannes Berg [this message]
2012-08-06 15:13           ` Felix Fietkau
2012-08-06 15:23             ` Johannes Berg

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=1344265599.4807.2.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).