linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Brown <sbrown@cortland.com>
To: Keir <keirlawson@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Andrey Yurovsky <andrey@cozybit.com>,
	javier@cozybit.com
Subject: Re: Mesh now completely broken on ath5k, latest git
Date: Tue, 16 Dec 2008 08:22:55 -0500	[thread overview]
Message-ID: <4947ABAF.9060205@cortland.com> (raw)
In-Reply-To: <e27b78a40812160405h2241e1acqa0dc8e593d6ebfad@mail.gmail.com>

Keir wrote:
> Having has no luck with an old rc6 version (basically all plink
> packets were getting lost), I upgraded to the newest git (rc8) however
> now when I run iw dev mesh0 station sump I don't see a single other
> mesh point.  This would imply that presumably beaconing is broken?
>
> Does anyone know a revision for which ath5k is properly working? I am
> yet to find one that works on my system.
>
> Cheers
>
> Keir
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   
Beaconing seems broken by Update PCU code 
dd1c9abd167de9bb9457a57694a1ab5e5801a0c1. After this patch, beacon debug 
says beacons sent, but sniffer sees none.

A snapshot of ath5k prior to this and git 12/10 
(b6d06c9669f27db31a0317fc98fedc8ff1ba4822) works for me with 
hostapd/wpa. It's been running for the past few days.

Mesh beaconing also works. I didn't test two nodes; I only sniffed the 
beacons.

I had to comment out 5GHz in caps.c because of too many channels. It's a 
nl80211 buffer size problem that's been discussed.

Steve



  reply	other threads:[~2008-12-16 13:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 12:05 Mesh now completely broken on ath5k, latest git Keir
2008-12-16 13:22 ` Steve Brown [this message]
2008-12-16 16:07   ` Keir
2008-12-16 18:30     ` Andrey Yurovsky
2008-12-17 10:56       ` Keir
2008-12-17 11:20         ` Michael Renzmann
2008-12-17 18:03         ` Keir
2008-12-17 17:06       ` Nick Kossifidis
2008-12-17 18:04         ` Keir
2008-12-18 14:00           ` Steve Brown
2008-12-18 19:38             ` Bob Copeland
2008-12-18 21:02               ` Steve Brown
2008-12-18 21:48                 ` Bob Copeland
2008-12-18 23:14                   ` Steve Brown
2008-12-19 20:18                   ` Steve Brown
2008-12-19 20:41                     ` Bob Copeland
2008-12-22 22:29                       ` Steve Brown
2008-12-22 22:40                         ` Bob Copeland

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=4947ABAF.9060205@cortland.com \
    --to=sbrown@cortland.com \
    --cc=andrey@cozybit.com \
    --cc=javier@cozybit.com \
    --cc=keirlawson@gmail.com \
    --cc=linux-wireless@vger.kernel.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).