From: Adam Baker <linux@baker-net.org.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: rt2500pci, infinite calls to rt2x00mc_configure_filter
Date: Sat, 29 Mar 2008 23:45:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20080329T232927-720@post.gmane.org> (raw)
In-Reply-To: 200803291801.17068.IvDoorn@gmail.com
Ivo van Doorn <ivdoorn@...> writes:
> Could you enable debugfs and use the tools here:
> http://www-user.rhrk.uni-kl.de/~nissler/rt2x00/index.html
>
> To create a dump of the frames as they are actually send out from the driver
> to the hardware including the status report. This will tell if rt2x00 is
> actually bringing the frame to the hardware correctly.
>
I think you've got that back to front - If I'm reading the
thread correctly the suspicion is the data is being transmitted
correctly by the remote end and is being lost somehere between
the rt2500pci antenna and user space.
The tools would still be helpful to see if a packet is being
received by the hardware and lost in the stack (maybe it doesn't
like something about the received packet) or if it is not even
getting as far as the rt2x00 driver.
> > this is the flag status when running hostapd; as printed with
> > printk(KERN_INFO "rt2500pci filter_flags: %d\n",
> > rt2x00dev->packet_filter);
> >
> > rt2500pci filter_flags: 2
> > rt2500pci MAC changed: 00:0c:f6:14:05:19
>
> Packet filter flags of 2 sounds a bit restrictive.
>
> Johannes, for Master mode shouldn't the following flags be set as well:
> FIF_PROMISC_IN_BSS
> FIF_CONTROL
>
Ivo,
Don't forget that there was no response to the request for someone to test
if broadcast packets were received in monitor mode on the older hardware
so if the filter flags don't select multicast traffic we could be losing
broadcast traffic too. I'm not sure if the stack will be reporting any
active multicast groups in AP mode. (For the benefit of others the only
reason normal broadcast traffic was working was because there was always a
multicast group present, Ivo's request is linked below.)
http://sourceforge.net/mailarchive/forum.php?thread_name=200803031921.41634.IvDoorn%40gmail.com&forum_name=rt2400-devel
next prev parent reply other threads:[~2008-03-29 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 14:34 rt2500pci, infinite calls to rt2x00mc_configure_filter Bas Hulsken
2008-03-29 14:53 ` Ivo van Doorn
2008-03-29 16:42 ` Bas Hulsken
2008-03-29 17:01 ` Ivo van Doorn
2008-03-29 23:45 ` Adam Baker [this message]
2008-03-30 13:15 ` Bas Hulsken
2008-03-30 13:27 ` Ivo van Doorn
2008-03-30 16:32 ` Bas Hulsken
2008-03-30 16:49 ` Mattias Nissler
2008-03-31 12:01 ` Johannes Berg
2008-03-31 12:51 ` Ivo van Doorn
2008-03-31 12:56 ` Johannes Berg
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=loom.20080329T232927-720@post.gmane.org \
--to=linux@baker-net.org.uk \
--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).