From: Tim Sutinen (tim_at_sutinen.com)
Date: 2002-08-28 08:10:36 UTC
My D-Link DWL-520 is having a problem associating with my access point (ap
has no access controls - fully open system). It used to work just fine, for
about a month, then something happened and it no longer associates with it.
I have tried both the hostap_pci driver and many different versions of the
wlan-ng driver.
Ad-Hoc mode works well (with either hostap_pci or prism2_pci).
This box is running SuSE 8.0.
This is what I am doing:
modprobe hostap_pci
gives this output in /var/log/messages:
Aug 28 00:39:54 home kernel: hostap_pci: hostap_pci.c 0.0.0 2002-05-19 (SSH
Communications Security Corp, Jouni Malinen)
Aug 28 00:39:54 home kernel: hostap_pci: (c) SSH Communications Security Corp <jkm_at_ssh.com> Aug 28 00:39:54 home kernel: PCI: Found IRQ 4 for device 00:0d.0 Aug 28 00:39:55 home kernel: hostap_pci: Registered netdevice wlan0 Aug 28 00:39:55 home kernel: prism2_hw_init() Aug 28 00:39:55 home kernel: prism2_hw_config: initialized in 19800 iterations Aug 28 00:39:55 home kernel: wlan0: NIC: id=0x8013 v1.0.0 Aug 28 00:39:55 home kernel: wlan0: PRI: id=0x15 v1.0.5 Aug 28 00:39:55 home kernel: wlan0: STA: id=0x1f v1.3.4 Aug 28 00:39:55 home kernel: wlan0: Intersil Prism2.5 PCI: mem=0xcddff000, irq=4 Aug 28 00:40:03 home /etc/hotplug/net.agent[1474]: No HW description found ... exiting
iwconfig wlan0 mode managed essid SOLO_1 gives this output in /var/log/messages:
Aug 28 00:45:43 home kernel: prism2: wlan0: operating mode changed 3 -> 2 Aug 28 00:45:43 home kernel: wlan0: INFO - fid=0x0293 - len=2 type=0xf200 Aug 28 00:45:43 home kernel: LinkStatus=2 (Disconnected) Aug 28 00:45:43 home kernel: wlan0: INFO - fid=0x0294 - len=2 type=0xf200 Aug 28 00:45:43 home kernel: LinkStatus=2 (Disconnected)
ifup wlan0
gives this output in /var/log/messages:
Aug 28 00:49:20 home kernel: wlan0: prism2_open Aug 28 00:49:20 home kernel: wlan0: TXEXC - fid=0x0121 - status=0x0004 ([Discon]) tx_control=000c Aug 28 00:49:20 home kernel: retry_count=0 tx_rate=0 fc=0x0108 (Data::0) Aug 28 00:49:20 home kernel: addr1=00:00:00:00:00:00 addr2=00:05:5d:ee:61:7faddr3=33:33:ff:ee:61:7f Aug 28 00:49:21 home kernel: wlan0: TXEXC - fid=0x0137 - status=0x0004 ([Discon]) tx_control=000c
and then hundreds of these:
Aug 28 00:53:33 home kernel: wlan0: INFO - fid=0x031d - len=2 type=0xf200
Aug 28 00:53:33 home kernel: LinkStatus=6 (Association failed)
iwconfig output looks like this:
wlan0 IEEE 802.11-DS ESSID:"SOLO_1" Nickname:"suse"
Mode:Managed Frequency:2.412GHz Access Point: 44:44:44:44:44:44
Bit Rate:2Mb/s Tx-Power:0 dBm Sensitivity=1/3 Retry min limit:8 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/92 Signal level:-69 dBm Noise level:-90 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:2197 Missed beacon:0
from my laptop (works, with a Lucent WaveLan PC Card) iwconfig output gives this:
eth1 IEEE 802.11-DS ESSID:"SOLO_1" Nickname:"vaio" Mode:Managed Frequency:2.412GHz Access Point: 00:40:96:48:FD:3F
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Power Management:off Link Quality:13/92 Signal level:-82 dBm Noise level:-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:5 Tx excessiveretries:136 Invalid misc:0 Missed beacon:0
Again, Ad-Hoc between these two computers works just fine. Would anyone have a clue what I could be doing wrong?
Thanks
Tim