linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Sergey Ryazanov <ryazanov.s.a@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Per sta interfaces in WDS (4-address) mode
Date: Wed, 22 Aug 2012 22:28:44 +0200	[thread overview]
Message-ID: <503540FC.9030408@openwrt.org> (raw)
In-Reply-To: <20120820111321.71c6f07e@mj>

On 2012-08-20 5:13 PM, Pavel Roskin wrote:
> On Sun, 19 Aug 2012 21:51:27 +0400
> Sergey Ryazanov <ryazanov.s.a@gmail.com> wrote:
> 
>> Hello dear all,
>> 
>> please tell me, why in the WDS mode, the stack creates a new interface
>> for each WDS station, and this interface hostapd adds to the parent AP
>> interface bridge? Why we couldn't simply pass this frames via AP
>> interface?
> 
> You may want to use a completely different IP address and netmask on the
> WDS interface.  Using the AP interface would take away that option.
> 
> hostapd is not a part of the kernel.  It should be possible not to add
> WDS interfaces to the bridge.
It's not just that. If the WDS station communication were done over the
AP interface, mac80211 would have to keep a table of which MAC address
is reachable behind which WDS station, which is something that the
bridge layer is supposed to do.
I've seen such a design mistake in various drivers, and I've seen the
weird quirks that this usually produces in more complex network
topologies ;)

- Felix


  reply	other threads:[~2012-08-22 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-19 17:51 Per sta interfaces in WDS (4-address) mode Sergey Ryazanov
2012-08-20 15:13 ` Pavel Roskin
2012-08-22 20:28   ` Felix Fietkau [this message]
2012-08-23  6:49     ` Sergey Ryazanov

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=503540FC.9030408@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=ryazanov.s.a@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).