From: Ivo van Doorn <ivdoorn@gmail.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Michael Wu <flamingice@sourmilk.net>,
"John Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] d80211: Add software sequence support
Date: Fri, 16 Feb 2007 15:29:22 +0100 [thread overview]
Message-ID: <200702161529.22717.IvDoorn@gmail.com> (raw)
In-Reply-To: <20070216135827.7d262ae3@griffin.suse.cz>
On Friday 16 February 2007 13:58, Jiri Benc wrote:
> On Fri, 16 Feb 2007 13:25:47 +0100, Ivo van Doorn wrote:
> > On Friday 16 February 2007 13:03, Jiri Benc wrote:
> > > On Thu, 15 Feb 2007 21:57:22 +0100, Jiri Benc wrote:
> > > > Thinking about it more, sdata should be the correct place. It's more
> > > > per-interface thing than per-BSS (although the difference is small in
> > > > this particular case).
> > >
> > > ...and thinking about it even more, that won't work with WDS.
> >
> > You mean storing the sequence counter per-interface won't work,
> > or per-bss?
>
> Both.
>
> When you have a WDS link and some other wireless interface at the same
> time, their source addresses are (in most cases) the same. You want to
> have the sequence control counter shared by them. Actually, it will
> probably work most of time even when they have different counters. The
> situation where it won't work is if you have two virtual interfaces,
> one in STA and second in WDS mode, both connected to the same AP. I
> can't figure out how this particular setup could be useful but it's
> generally not disallowed.
>
> Anyway, using different counter for a WDS interface probably violates
> 802.11 (although it's not much specific in this case). I believe it
> will work in most cases, though.
>
> Any ideas how to solve that?
Are there more situations where it might be important to know
if the WDS interface has to keep in mind that there is a virtual STA interface
on the same network? Because it might be worthwhile to make a check for that
in the creation of the WDS interface (and in the STA interface).
Ivo
next prev parent reply other threads:[~2007-02-16 14:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 13:23 [PATCH v2] d80211: Add software sequence support Ivo van Doorn
2007-02-15 16:42 ` Johannes Berg
2007-02-15 17:41 ` John W. Linville
2007-02-15 18:54 ` Ivo Van Doorn
2007-02-15 19:02 ` Michael Wu
2007-02-15 19:11 ` Jiri Benc
2007-02-15 19:22 ` Michael Wu
2007-02-15 20:04 ` Jouni Malinen
2007-02-15 19:09 ` Jiri Benc
2007-02-15 20:48 ` Michael Wu
2007-02-15 20:57 ` Jiri Benc
2007-02-15 22:18 ` Ivo Van Doorn
2007-02-16 12:03 ` Jiri Benc
2007-02-16 12:25 ` Ivo van Doorn
2007-02-16 12:58 ` Jiri Benc
2007-02-16 14:29 ` Ivo van Doorn [this message]
2007-02-16 21:14 ` Johannes Berg
2007-02-16 22:07 ` Ivo van Doorn
2007-02-16 22:12 ` Johannes Berg
2007-02-19 19:40 ` Jiri Benc
2007-02-19 19:52 ` Johannes Berg
2007-03-10 14:38 ` Ivo van Doorn
2007-03-10 17:51 ` Michael Wu
2007-03-10 19:01 ` Ivo van Doorn
2007-03-10 19:21 ` [PATCH v3] " Ivo van Doorn
2007-03-10 19:32 ` Michael Buesch
2007-03-10 23:25 ` Ivo van Doorn
2007-03-23 17:52 ` Jiri Benc
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=200702161529.22717.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.