linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 2/3] mac80211: create a STA entry for a WDS interface after receiving a beacon
Date: Wed, 01 Jun 2011 12:53:05 +0200	[thread overview]
Message-ID: <4DE61A11.1070708@openwrt.org> (raw)
In-Reply-To: <1306901843.3867.2.camel@jlt3.sipsolutions.net>

On 2011-06-01 6:17 AM, Johannes Berg wrote:
> On Tue, 2011-05-31 at 22:22 +0200, Felix Fietkau wrote:
>>  On 2011-05-31 10:06 PM, Johannes Berg wrote:
>>  >  On Tue, 2011-05-31 at 21:39 +0200, Felix Fietkau wrote:
>>  >>   On 2011-05-31 9:32 PM, Johannes Berg wrote:
>>  >>   >   On Tue, 2011-05-31 at 21:16 +0200, Felix Fietkau wrote:
>>  >>   >>    When a STA entry is created too early, a lot of essential information
>>  >>   >>    required for rate control is missing.
>>  >>   >
>>  >>   >   I don't understand how you can rely on beacons for WDS.
>>  >>   You usually set up WDS links between APs on the same channel, each
>>  >>   running both a normal AP vif and a WDS vif. The remote AP's beacons are
>>  >>   then used to detect the capabilities of the peer.
>>  >
>>  >  I don't think we can rely on "usually" unless we also enforce that
>>  >  somehow. Otherwise this link will basically be dead. There's nothing
>>  >  that requires you to add WDS to an AP interface only after all.
>>  I don't think using WDS without APs makes any sense. Since WDS alone
>>  does not use beacons or probe requests, there's nothing else that would
>>  ensure that rate information, HT capabilities, etc. get exchanged.
>
> I just don't like the fact that you can create a non-functional WDS
> interface by adding it when there's no AP interface.
Actually, I just noticed that ieee80211_assign_perm_addr forces you to 
use the MAC address of an existing AP interface for a WDS interface, 
same as for an AP VLAN interface. So the requirement to also have an AP 
mode interface is not new.

- Felix

  reply	other threads:[~2011-06-01 10:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 19:16 [PATCH 1/3] mac80211: remove the useless WLAN_STA_WDS station flag Felix Fietkau
2011-05-31 19:16 ` [PATCH 2/3] mac80211: create a STA entry for a WDS interface after receiving a beacon Felix Fietkau
2011-05-31 19:16   ` [PATCH 3/3] mac80211: receive action frames for WDS interfaces Felix Fietkau
2011-05-31 19:31   ` [PATCH 2/3] mac80211: create a STA entry for a WDS interface after receiving a beacon Johannes Berg
2011-05-31 19:46     ` Felix Fietkau
2011-05-31 20:05       ` Johannes Berg
2011-05-31 19:32   ` Johannes Berg
2011-05-31 19:39     ` Felix Fietkau
2011-05-31 20:06       ` Johannes Berg
2011-05-31 20:22         ` Felix Fietkau
2011-06-01  4:17           ` Johannes Berg
2011-06-01 10:53             ` Felix Fietkau [this message]
2011-06-01 11:02               ` Johannes Berg
2011-06-01 11:18                 ` Felix Fietkau
2011-06-01 11:30                   ` Johannes Berg
2011-06-01 11:41                     ` Felix Fietkau
2011-06-01 12:26                       ` Johannes Berg
2011-06-01 12:48                         ` Felix Fietkau
2011-06-06 18:24                           ` John W. Linville

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=4DE61A11.1070708@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).