From: Steve Brown <sbrown@cortland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: YanBo <dreamfly281@gmail.com>,
Andrey Yurovsky <andrey@cozybit.com>,
linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net
Subject: Re: [ath5k-devel] [PATCH] ath5k: add Mesh Point support
Date: Mon, 28 Jul 2008 08:45:34 -0400 [thread overview]
Message-ID: <488DBF6E.10606@cortland.com> (raw)
In-Reply-To: <1217247004.12662.3.camel@johannes.berg>
Johannes Berg wrote:
>> I've been looking at this too. After the "revamp beacon configuration"
>> patch, mesh no longer send beacons. If I revert it, beacons reappear and
>> my two stations are found. I'm using both a b43 & zd1211rw.
>>
>> I believe the problem is in mac80211. It appears that the call to
>> ieee80211_if_config that was previously in ieee80211_open never made it
>> to the new start_mesh routine in the revision. The attached patch seems
>> to revive beacons and both stations are now found. I'm not familiar with
>> the code and wouldn't call this a fix.
>>
>
> Yeah, we talked about it yesterday or the day before, and this seems
> like the right fix, except you say that AP is also broken.
>
> I'll look into everything when I no longer feel hung over from
> travelling for about 18 hours.
>
> johannes
>
I haven't tested AP, just mesh. So far, it's working w/ 3 nodes. In
rereading my post, it wasn't clear which beacons I meant.
Although mesh path timeout seems to default to 5000ms, in my testing it
takes about 50 min. Is this really the timeout that removes a node when
it's beacon is off for this period?
Steve
next prev parent reply other threads:[~2008-07-28 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 20:12 [PATCH] ath5k: add Mesh Point support Andrey Yurovsky
2008-07-18 17:59 ` Nick Kossifidis
2008-07-28 9:09 ` [ath5k-devel] " YanBo
2008-07-28 10:24 ` Steve Brown
2008-07-28 12:10 ` Johannes Berg
2008-07-28 12:45 ` Steve Brown [this message]
2008-07-30 19:27 ` Luis Carlos Cobo
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=488DBF6E.10606@cortland.com \
--to=sbrown@cortland.com \
--cc=andrey@cozybit.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=dreamfly281@gmail.com \
--cc=johannes@sipsolutions.net \
--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 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.