All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Rossi <rossi.f@inwind.it>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: ath5k: problems during the connection to a sitecom AP
Date: Sat, 15 Nov 2008 02:07:11 +0100	[thread overview]
Message-ID: <200811150207.12084.rossi.f@inwind.it> (raw)

I'm testing the ath5k driver (wireless-testing v2.6.28-rc4-5172-gc1a847c) with 
my 3com 3CRDAG675 PCI card (atheros AR5212). I can try alternatively two 
different access points (both configured with WEP + hidden SSID), the 
procedure I use is the same but the results are different.

Here are the commands used:

modprobe ath5k
ifconfig ath0 192.168.1.2 up
iwconfig ath0 key <MYKEY>
iwconfig ath0 ap <AP_MAC>
iwconfig ath0 essid <MY_ESSID>


*** 3com AP ***
With this one I can associate without problems at the first try (SSID not 
broadcast + WEP encryption):

ath5k_pci 0000:00:0b.0: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 
10
ath5k_pci 0000:00:0b.0: registered as 'phy1'
phy1: Selected rate control algorithm 'minstrel'
ath5k phy1: Atheros AR5212 chip found (MAC: 0x56, PHY: 0x41)
ath5k phy1: RF5112B multiband radio found (0x36)
udev: renamed network interface wlan0 to ath0
ath0: direct probe to AP <AP_MAC> try 1
ath0 direct probe responded
ath0: authenticate with AP <AP_MAC>
ath0: authenticated
ath0: associate with AP <AP_MAC>
ath0: RX AssocResp from <AP_MAC> (capab=0x421 status=0 aid=4)
ath0: associated
phy1: Allocated STA <AP_MAC>
phy1: Inserted STA <AP_MAC>
ath0: switched to short barker preamble (BSSID=<AP_MAC>)
ath0: switched to short slot (BSSID=<AP_MAC>)

*** Sitecom AP ***
With this one I'm able to associate only when the SSID is broadcast (with or 
without encryption). Moreover the association process isn't successful at 
first try (like for the 3com AP) and the link quality is very bad. An example 
of ping statistics is the following

629 packets transmitted, 527 received, 16% packet loss, time 711605ms
rtt min/avg/max/mdev = 6.332/6303.120/151334.339/18133.729 ms, pipe 114

and it's common to get the following error message (transmission buffer 
saturated?):

ping: sendmsg: No buffer space available

When I disable the SSID I can't associate anymore to the AP, the only debug 
messages are the following:

ath5k_pci 0000:00:0b.0: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 
10
ath5k_pci 0000:00:0b.0: registered as 'phy12'
phy12: Selected rate control algorithm 'minstrel'
ath5k phy12: Atheros AR5212 chip found (MAC: 0x56, PHY: 0x41)
ath5k phy12: RF5112B multiband radio found (0x36)
udev: renamed network interface wlan0 to ath0

How can I debug to provide more details (e.g. using debugfs)?

Thank you for any help,
Fabio

             reply	other threads:[~2008-11-15  1:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15  1:07 Fabio Rossi [this message]
2008-11-17 20:20 ` ath5k: problems during the connection to a sitecom AP Fabio Rossi
2008-11-17 20:23   ` Johannes Berg
2008-11-19 21:00     ` Fabio Rossi
2008-11-20  6:40       ` Johannes Berg
2008-11-18 15:48   ` Bob Copeland
2008-11-19 22:15     ` Fabio Rossi
2008-11-21 20:22       ` Bob Copeland
2008-11-22 16:33         ` Fabio Rossi
2008-11-24  8:31           ` Holger Schurig
2008-11-25  0:08             ` Fabio Rossi
2008-11-24  8:25         ` Holger Schurig
  -- strict thread matches above, loose matches on Subject: below --
2008-11-24  9:35 rossi.f

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=200811150207.12084.rossi.f@inwind.it \
    --to=rossi.f@inwind.it \
    --cc=ath5k-devel@lists.ath5k.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.