From: Ivo van Doorn <ivdoorn@gmail.com>
To: Antonio Marques <froz@icix.org>
Cc: Andrey Yurovsky <andrey@cozybit.com>, linux-wireless@vger.kernel.org
Subject: Re: rt2x00 mesh support
Date: Sun, 15 Mar 2009 14:45:01 +0100 [thread overview]
Message-ID: <200903151445.01344.IvDoorn@gmail.com> (raw)
In-Reply-To: <594B4EB2-FE87-4756-B016-C83083EF415B@icix.org>
On Sunday 15 March 2009, Antonio Marques wrote:
> Upon further investigation, beaconing does not work after configuring
> an interface in mesh point mode but running 'iwlist mesh scan'
> triggers something in the driver that enables beaconing.
> After executing this command beacons are generated and correctly
> received at other nodes.
Thats odd, but very interesting :)
Could you enable debugfs and CONFIG_RT2X00_LIB_DEBUGFS and
use the script from http://kernel.org/pub/linux/kernel/people/ivd/tools=
/rt2x00_regdump.sh
to create a register dump before running 'iwlist mesh scan' and afterwa=
rds.
(So basically when beaconing is broken and when it is working).
Thanks,
Ivo
> This behaviour is present using both rt73usb and rt2500pci based card=
s.
> Once beaconing is triggered the interface works as expected and mesh
> peer links are automatically established. I assume this is a bug in =20
> the rt2x00
> driver. Is there anything I can do to help debug this problem?
>=20
> Thanks,
> Antonio Marques
>=20
> On Jan 24, 2009, at 11:40 , Ant=F3nio Marques wrote:
> > Ok. I didn't realize the driver was broken and the issue wasn't =20
> > specific
> > to mesh support. I hope the driver maintainers can solve this soon.
> >
> > Thanks,
> > Antonio Marques
> >
> > On Jan 23, 2009, at 19:02 , Andrey Yurovsky wrote:
> >> Hi Antonio. As I understand it, beaconing is currently broken in
> >> rt2x00 (it used to work in the past). This means that, until the
> >> device can send beacons again, it won't be able to do mesh (or AP =
or
> >> IBSS). However the commit in question at least sets up the driver=
to
> >> support mesh as soon as beaconing works again.
> >>
> >> On Fri, Jan 23, 2009 at 10:58 AM, Antonio Marques <froz@icix.org> =
=20
> >> wrote:
> >>> Hi,
> >>>
> >>> I have been trying to setup a mesh network using the 802.11s =20
> >>> stack, but
> >>> unfortunately the only hardware that I have readily available are=
=20
> >>> rt2x00
> >>> usb dongles and an ath5k mini-pci card. Since support for rt2x00
> >>> driver is listed on o11s.org as being in development, what is the=
=20
> >>> current
> >>> status
> >>> of mesh support for this driver?
> >>>
> >>> I see recent commit activity such as
> >>> fdc26201323eb8ba543ac5624f8d71e55b6f7352,
> >>> "rt2x00: Add mesh support" but I am still unable to establish mes=
h =20
> >>> links
> >>> using
> >>> rt2x00 devices. An rt2x00 device can see the ath5k device =20
> >>> according to
> >>> 'iw dev mesh station dump', but the link state never changes to =20
> >>> ESTAB.
> >>>
> >>> Thanks,
> >>> Antonio Marques
> >>>
> >>>
> >>> --
> >>> To unsubscribe from this list: send the line "unsubscribe linux-=20
> >>> wireless" in
> >>> the body of a message to majordomo@vger.kernel.org
> >>> More majordomo info at http://vger.kernel.org/majordomo-info.htm=
l
> >>>
> >
>=20
>=20
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-15 13:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 18:58 rt2x00 mesh support Antonio Marques
2009-01-23 19:02 ` Andrey Yurovsky
2009-01-24 11:40 ` António Marques
2009-03-15 11:54 ` Antonio Marques
2009-03-15 13:45 ` Ivo van Doorn [this message]
2009-03-16 1:58 ` Pat Erley
2009-03-16 13:29 ` Antonio Marques
2009-03-16 13:22 ` António Marques
2009-03-16 14:58 ` Ivo van Doorn
2009-03-16 19:12 ` Antonio Marques
2009-03-17 9:31 ` Ivo van Doorn
2009-03-17 14:11 ` Johannes Berg
2009-03-17 20:10 ` Johannes Berg
2009-03-17 21:50 ` Ivo van Doorn
2009-03-17 21:53 ` Johannes Berg
2009-03-17 22:04 ` Ivo van Doorn
2009-03-17 22:35 ` Johannes Berg
2009-03-17 23:01 ` Ivo van Doorn
2009-03-17 23:04 ` Johannes Berg
2009-03-18 10:02 ` Ivo van Doorn
2009-03-18 12:26 ` Antonio Marques
2009-03-18 12:48 ` Ivo van Doorn
2009-03-18 13:12 ` Johannes Berg
2009-03-18 13:31 ` Ivo van Doorn
2009-03-18 13:36 ` Johannes Berg
2009-03-19 21:55 ` Antonio Marques
2009-03-17 19:38 ` Antonio Marques
2009-03-17 22:03 ` Ivo van Doorn
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=200903151445.01344.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=andrey@cozybit.com \
--cc=froz@icix.org \
--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).