From: Lee <lee-in-berlin@web.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
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: Thu, 28 Oct 2010 10:16:08 +0200 [thread overview]
Message-ID: <4CC93148.7090308@web.de> (raw)
In-Reply-To: <201010260740.47692.helmut.schaa@googlemail.com>
On 26/10/10 07:40, Helmut Schaa wrote:
> 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
Yes. I can see this:
# tcpdump -i mon0 "ether host 00:1F:3B:79:41:6F"
10:09:31.193127 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Probe Request () [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit][|802.11]
10:09:31.193360 1.0 Mb/s [bit 15] Probe Response (<MY_AP>) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 11, PRIVACY[|802.11]
10:09:40.952828 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Probe Request () [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit][|802.11]
10:09:40.952986 1.0 Mb/s [bit 15] Probe Response (<MY_AP>) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 11, PRIVACY[|802.11]
10:09:40.963821 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Probe Request (<MY_AP>) [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit][|802.11]
10:09:40.963906 1.0 Mb/s [bit 15] Probe Response (<MY_AP>) [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] CH: 11, PRIVACY[|802.11]
10:09:42.739932 1.0 Mb/s 2462 MHz 11b -78dB signal antenna 1 [bit 14] Authentication (Open System)-1: Succesful
10:09:42.740120 1.0 Mb/s [bit 15] Authentication (Open System)-2:
10:09:42.742538 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Assoc Request (<MY_AP>) [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit][|802.11]
10:09:42.742726 1.0 Mb/s [bit 15] Assoc Response AID(2) : PRIVACY : Succesful[|802.11]
10:09:42.744261 1.0 Mb/s [bit 15] EAPOL key (3) v2, len 95
10:09:42.771053 1.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14]
10:09:42.788163 1.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
10:09:42.844416 1.0 Mb/s [bit 15] EAPOL key (3) v2, len 95
10:09:42.849396 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] EAPOL key (3) v1, len 117
10:09:42.849864 1.0 Mb/s [bit 15] EAPOL key (3) v2, len 207
10:09:42.854022 1.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] EAPOL key (3) v1, len 95
10:09:42.893532 1.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 1 Pad 20 KeyID 0
10:09:42.987625 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14]
10:09:43.079505 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14]
10:09:43.358335 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 2 Pad 20 KeyID 0
10:09:44.198308 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 3 Pad 20 KeyID 0
10:09:44.359547 1.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 4 Pad 20 KeyID 0
10:09:44.377797 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 5 Pad 20 KeyID 0
10:09:44.425039 2.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 6 Pad 20 KeyID 0
10:09:44.446283 1.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 7 Pad 20 KeyID 0
10:09:44.692999 2.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 8 Pad 20 KeyID 0
10:09:44.943957 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 9 Pad 20 KeyID 0
10:09:45.004451 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: a Pad 20 KeyID 0
10:09:45.144803 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: b Pad 20 KeyID 0
10:09:45.458125 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: c Pad 20 KeyID 0
10:09:45.997789 2.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: d Pad 20 KeyID 0
10:09:46.177139 5.5 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: e Pad 20 KeyID 0
10:09:47.491055 5.5 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: f Pad 20 KeyID 0
10:09:48.210438 5.5 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 10 Pad 20 KeyID 0
10:09:48.367412 5.5 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 11 Pad 20 KeyID 0
10:09:50.769904 2.0 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14]
10:09:50.861516 2.0 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14]
10:09:51.007367 5.5 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 12 Pad 20 KeyID 0
10:09:52.377411 5.5 Mb/s 2462 MHz 11b -74dB signal antenna 1 [bit 14] Data IV: 13 Pad 20 KeyID 0
10:10:03.013402 5.5 Mb/s 2462 MHz 11b -76dB signal antenna 1 [bit 14] Data IV: 14 Pad 20 KeyID 0
However, on wlan0 I don't see anything beyond the EAPOL packets.
Temporarily turning off WPA encryption let me successfully connect to my AP.
Lee
next prev parent reply other threads:[~2010-10-28 8:16 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
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 [this message]
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=4CC93148.7090308@web.de \
--to=lee-in-berlin@web.de \
--cc=helmut.schaa@googlemail.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;
as well as URLs for NNTP newsgroup(s).