linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Lee <lee-in-berlin@web.de>, 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 13:03:32 +0200	[thread overview]
Message-ID: <20101026110332.GA3982@sig21.net> (raw)
In-Reply-To: <201010260740.47692.helmut.schaa@googlemail.com>

On Tue, Oct 26, 2010 at 07:40:47AM +0200, Helmut Schaa wrote:
> 
> 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):

ip link set up dev mon0

> # tcpdump -i mon0 "ether src XX:XX:XX:XX:XX:XX"
> 
> Do you see any frames from your specific client?

On the client I run:

zzz:~# ping 172.28.120.1
PING 172.28.120.1 (172.28.120.1) 56(84) bytes of data.
>From 172.28.120.2 icmp_seq=1 Destination Host Unreachable
>From 172.28.120.2 icmp_seq=2 Destination Host Unreachable
>From 172.28.120.2 icmp_seq=3 Destination Host Unreachable

On AP I get:

# tcpdump -i mon0 "ether src 00:15:61:xx:xx:xx"
tcpdump: WARNING: mon0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on mon0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 65535 bytes
00:02:51.398953 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] Data IV: 56 Pad 20 KeyID 0
00:02:51.497845 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] 
00:02:52.415053 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] Data IV: 57 Pad 20 KeyID 0
00:02:53.414897 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] 
00:02:53.415135 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] Data IV: 58 Pad 20 KeyID 0
00:02:53.513661 48.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] 
00:02:54.415042 48.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] Data IV: 59 Pad 20 KeyID 0
00:02:54.415671 36.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] Data IV: 59 Pad 20 KeyID 0
00:02:54.513572 48.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] 
00:02:55.430725 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] Data IV: 5a Pad 20 KeyID 0
00:02:56.430702 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] 
00:02:56.430942 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] Data IV: 5b Pad 20 KeyID 0
00:02:56.529433 48.0 Mb/s 2447 MHz 11g -46dB signal antenna 1 [bit 14] 
00:02:57.249028 1.0 Mb/s 2447 MHz 11b -44dB signal antenna 1 [bit 14] Probe Request (foo) [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit][|802.11]
00:02:57.350169 48.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] 
00:02:57.350402 24.0 Mb/s 2447 MHz 11g -44dB signal antenna 1 [bit 14] 
00:02:57.350582 18.0 Mb/s 2447 MHz 11g -42dB signal antenna 1 [bit 14] 
...


(The client is sending ARP requests but not getting answer:
zzz:~# tcpdump -p -i wlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes
13:00:35.740957 ARP, Request who-has 172.28.120.1 tell 172.28.120.2, length 28
13:00:36.740924 ARP, Request who-has 172.28.120.1 tell 172.28.120.2, length 28
13:00:37.740926 ARP, Request who-has 172.28.120.1 tell 172.28.120.2, length 28
)

The station is using rt3070 usb dongle, AP is D-Link DWL-G122 rt73usb dongle.


Johannes

  parent reply	other threads:[~2010-10-26 11:03 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 [this message]
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=20101026110332.GA3982@sig21.net \
    --to=js@sig21.net \
    --cc=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).