Subject: Re: ath(4) packet loss problem
To: NetBSD current-users <current-users@NetBSD.org>
From: David Young <dyoung@pobox.com>
List: current-users
Date: 07/11/2007 16:15:54
On Wed, Jul 11, 2007 at 04:38:00PM -0400, Andreas Wrede wrote:
>
> On Jul 11, 2007, at 15:59 , David Young wrote:
>
> >ifconfig -v ath0 | grep -v ': 0$'
>
> # ifconfig -v ath0 | grep -v ': 0$'
> ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> ssid Planix -frag nwkey 65536:"",
> 0x5a5f2b45f816925fead885174f485f71,0xd4e8eaea44dbee833e922a782a59a9b2,""
> powersave off
> bssid 00:19:e3:33:c7:1b chan 1
> address: 00:02:6f:20:f5:4a
> media: IEEE802.11 autoselect (OFDM12 mode 11g)
> status: active
> input: 531874 packets, 54761325 bytes, 440569 multicasts,
> 155647 errors
> output: 91659 packets, 8982475 bytes, 5 multicasts, 148 errors
> rx from wrong bssid: 915
> rx discard 'cuz dup: 1537
> rx discard 'cuz mcast echo: 17
> rx discard mgt frames: 56
> rx discard ctrl frames: 35
> rx beacon frames: 7041100
> rx element unknown: 14083044
> rx frame chan mismatch: 357
> rx w/ incorrect keyid: 6
> rx seq# violation (TKIP): 32
> tx failed 'cuz no defkey: 7
> active scans started: 7
> inet 10.99.254.240 netmask 0xffff0000 broadcast 10.99.255.255
> inet6 fe80::202:6fff:fe20:f54a%ath0 prefixlen 64 scopeid 0x4
Is it possible to turn off crypto on the AP and on your client, and
try again?
Is your client very near your AP? Within 3 feet? 10 feet?
Dave
--
David Young OJC Technologies
dyoung@ojctech.com Urbana, IL * (217) 278-3933 ext 24