From: Baruch Siach <baruch@tkos.co.il>
To: Javier Cardona <javier@cozybit.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Mesh HWMP: PREQ node queue full
Date: Fri, 29 Jul 2011 10:17:43 +0300 [thread overview]
Message-ID: <20110729071742.GB24030@tarshish> (raw)
In-Reply-To: <CAPjQAd_KCc+TtTMeJmhD8WdqooUHWqttdASDpwB0DdrXfXWkRA@mail.gmail.com>
Hi Javier,
On Thu, Jul 28, 2011 at 11:47:44AM -0700, Javier Cardona wrote:
> Thanks for reporting. Is 02:92:ca:39:48:72 the address of the mesh
> gate or the address of the external proxied node?
This is the MAC address of the mesh gate (i.e. the other AP). What is
"external proxied node"?
baruch
> On Wed, Jul 27, 2011 at 11:51 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > Hi linux-wireless list,
> >
> > I'm testing the mesh capabilities (specifically, MPP) of the latest kernel
> > (3.0). My driver is ath9k on AR9390 chip. My two APs are configured
> > identically as follows:
> >
> > ----- mesh.sh start
> > #!/bin/sh
> >
> > iw dev wlan1 interface add mesh0 type mp mesh_id wavmesh
> > ip link set mesh0 addr $(cat /etc/network/mesh0.mac)
> >
> > brctl addbr br0
> > brctl addif br0 eth0
> > brctl addif br0 mesh0
> >
> > ifconfig mesh0 down up
> > ifconfig eth0 0.0.0.0
> > ifconfig br0 up
> > ----- mesh.sh end
> >
> > When transferring traffic from a machine behind one eth0 to a machine behind
> > the other eth0, I see the following on the console (of both APs, only
> > different MACs):
> >
> > Mesh HWMP: sending PREP to 02:92:ca:39:48:72
> > Mesh HWMP: sending PREQ to 02:92:ca:39:48:72
> > Mesh HWMP: received PREP from 02:92:ca:39:48:72
> > Mesh HWMP: received PREQ from 02:92:ca:39:48:72
> > Mesh HWMP: PREQ is for us
> > Mesh HWMP: replying to the PREQ
> > Mesh HWMP: sending PREP to 02:92:ca:39:48:72
> > mesh_queue_preq: 40 callbacks suppressed
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> > Mesh HWMP: PREQ node queue full
> >
> > Any suggestion?
> >
> > baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2011-07-29 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 6:51 Mesh HWMP: PREQ node queue full Baruch Siach
2011-07-28 18:47 ` Javier Cardona
2011-07-29 7:17 ` Baruch Siach [this message]
2011-08-03 16:34 ` Javier Cardona
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=20110729071742.GB24030@tarshish \
--to=baruch@tkos.co.il \
--cc=javier@cozybit.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