From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Lee <lee-in-berlin@web.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36, rt73usb)
Date: Tue, 26 Oct 2010 07:40:47 +0200 [thread overview]
Message-ID: <201010260740.47692.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <4CC33E83.4020505@web.de>
Hi,
Am Samstag 23 Oktober 2010 schrieb Lee:
> On 22/10/10 01:47, Lee wrote:
> > The test case is as follows: I have eth0 and wlan0 (the interface to an
> > rt37usb device) in a bridge lan0. I have a properly configured hostapd. When I
> > try to connect with a client to my hostapd AP, I can successfully
> > authenticate, but all further packets don't reach the interface of the AP.
> >
> > However, I can see broadcast packets *from* the AP on my client, but not the
> > other way round (DHCP requests from client to AP). To make sure the bug was
> > not specific to broadcast packets, I manually set an IP on my client and tried
> > to ping the AP, but those packets didn't come through, either.
[...]
> I checked vanilla 2.6.36, the bug is still there. Is this a known bug? Does
> anyone care to give me some hints? Are any details needed?
Please try to create a monitor interface on the rt73usb AP after setting it up:
# iw dev wlan0 interface add mon0 type monitor
and run a tcpdump on that (with XX:...:XX replaced by the MAC address of
your client):
# tcpdump -i mon0 "ether src XX:XX:XX:XX:XX:XX"
Do you see any frames from your specific client?
Helmut
next prev parent reply other threads:[~2010-10-26 5:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 23:47 [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36-, rt73usb) Lee
2010-10-23 19:58 ` [regression]AP with hostapd 0.7.3 can't receive packets beyond authentication (2.6.36, rt73usb) Lee
2010-10-25 17:49 ` John W. Linville
2010-10-26 2:04 ` Lee
2010-10-26 5:40 ` Helmut Schaa [this message]
2010-10-26 10:19 ` Johannes Stezenbach
2010-10-26 11:03 ` Johannes Stezenbach
2010-10-26 15:40 ` Johannes Stezenbach
2010-10-28 8:16 ` Lee
2010-10-28 8:20 ` Ivo Van Doorn
2010-10-28 8:23 ` Helmut Schaa
2010-10-28 19:06 ` Lee
2010-10-28 19:54 ` Gertjan van Wingerde
2010-10-28 20:36 ` Ivo Van Doorn
2010-10-28 20:40 ` Gertjan van Wingerde
2010-10-28 22:17 ` Helmut Schaa
2010-10-29 21:39 ` Lee
2010-10-30 12:30 ` Helmut Schaa
2010-11-02 12:50 ` Johannes Stezenbach
2010-11-02 14:46 ` Johannes Stezenbach
2010-11-02 14:58 ` Ivo Van Doorn
2010-11-02 15:05 ` Helmut Schaa
2010-11-02 15:49 ` Johannes Stezenbach
2010-11-03 14:14 ` Johannes Stezenbach
2010-11-03 14:50 ` Ivo Van Doorn
2010-11-03 15:08 ` Johannes Stezenbach
2010-11-03 14:51 ` Ivo Van Doorn
2010-11-03 14:59 ` Johannes Stezenbach
2010-11-03 15:21 ` Helmut Schaa
2010-11-03 14:53 ` Helmut Schaa
2010-10-29 16:17 ` Lee
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=201010260740.47692.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=lee-in-berlin@web.de \
--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).