linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 1/3] mac80211: Include sequence number in IBSS and Mesh beacons
Date: Wed, 9 Jul 2008 15:38:09 +0200	[thread overview]
Message-ID: <200807091538.09387.mb@bu3sch.de> (raw)
In-Reply-To: <200807091511.45779.IvDoorn@gmail.com>

On Wednesday 09 July 2008 15:11:45 Ivo van Doorn wrote:
> Currently only beacons generated in AP mode have the software
> sequence number inserted. This means IBSS and Mesh mode are broken
> for all hardware that require software sequence numbers.

Does software seq numbering even work at all?
What about packets that get sent between the driver requested the
beacon and the driver does actually queue it?

> Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
> ---
>  net/mac80211/tx.c |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/net/mac80211/tx.c b/net/mac80211/tx.c
> index 359cb36..0e7e1f3 100644
> --- a/net/mac80211/tx.c
> +++ b/net/mac80211/tx.c
> @@ -1876,6 +1876,8 @@ struct sk_buff *ieee80211_beacon_get(struct ieee80211_hw *hw,
>  		hdr->frame_control = IEEE80211_FC(IEEE80211_FTYPE_MGMT,
>  						  IEEE80211_STYPE_BEACON);
>  
> +		ieee80211_include_sequence(sdata, hdr);
> +
>  		num_beacons = &ifsta->num_beacons;
>  	} else if (ieee80211_vif_is_mesh(&sdata->vif)) {
>  		/* headroom, head length, tail length and maximum TIM length */
> @@ -1896,6 +1898,9 @@ struct sk_buff *ieee80211_beacon_get(struct ieee80211_hw *hw,
>  			cpu_to_le16(local->hw.conf.beacon_int);
>  		mgmt->u.beacon.capab_info = 0x0; /* 0x0 for MPs */
>  
> +		ieee80211_include_sequence(sdata,
> +					   (struct ieee80211_hdr *)skb->data);
> +
>  		pos = skb_put(skb, 2);
>  		*pos++ = WLAN_EID_SSID;
>  		*pos++ = 0x0;



-- 
Greetings Michael.

  parent reply	other threads:[~2008-07-09 13:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 13:11 [PATCH 0/3] rt2x00 update Ivo van Doorn
2008-07-09 13:11 ` [PATCH 1/3] mac80211: Include sequence number in IBSS and Mesh beacons Ivo van Doorn
2008-07-09 13:12   ` [PATCH 2/3] rt2x00: Add support for CTS protection in rt2x00lib Ivo van Doorn
2008-07-09 13:12     ` [PATCH 3/3] rt2x00: Reorganize beacon handling Ivo van Doorn
2008-07-09 13:14   ` [PATCH 1/3] mac80211: Include sequence number in IBSS and Mesh beacons Johannes Berg
2008-07-09 13:38   ` Michael Buesch [this message]
2008-07-09 13:41     ` Johannes Berg
2008-07-09 14:04     ` Ivo van Doorn
2008-07-09 13:58       ` Johannes Berg
2008-07-09 14:57         ` Ivo van Doorn
2008-07-09 14:49           ` Johannes Berg
2008-07-09 14:00       ` Michael Buesch
2008-07-09 14:05         ` Johannes Berg
2008-07-09 14:37           ` Ivo van Doorn
2008-07-09 14:48             ` Johannes Berg
2008-07-09 15:08               ` Ivo van Doorn
2008-07-09 15:15                 ` Michael Buesch
2008-07-09 15:36                   ` Ivo van Doorn
2008-07-09 15:33                     ` Johannes Berg
2008-07-09 15:48                       ` Ivo van Doorn
2008-07-09 15:49                         ` Johannes Berg
2008-07-09 15:55                           ` Johannes Berg
2008-07-09 16:12                             ` Ivo van Doorn
2008-07-09 17:42                               ` Johannes Berg
2008-07-09 18:12                                 ` Ivo van Doorn
2008-07-09 18:07                                   ` Johannes Berg
2008-07-09 16:08                           ` Ivo van Doorn
2008-07-09 16:07                             ` Johannes Berg
2008-07-09 15:16                 ` Johannes Berg
2008-07-09 15:12             ` Michael Buesch
2008-07-14 18:49   ` 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=200807091538.09387.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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).