problem with old prism2.5 based card

ojw at weilerfamily.com ojw at weilerfamily.com
Thu Oct 8 23:07:53 EDT 2009


I'm having issues with a recently reloaded server I use as an access  
point.  The problem is that it appears that the DWL-520 in the linux  
server can receive packets but can't send any.

tcpdump on the linux system looks like this:

19:32:45.658028 arp who-has 192.168.0.1 tell 192.168.0.66
19:32:45.658094 arp who-has 192.168.0.1 tell 192.168.0.66
19:32:45.658104 arp reply 192.168.0.1 is-at 00:05:5d:ee:68:e7

while at the same time doing a ping to the access point IP address  
from a windows box (IP of windows wireless interface is statically  
assigned at 192.168.0.66).  All the windows box shows (using  
wireshark) is the arp who-has packets.

I'm using an old DLink DWL-520 and claims the following from lshw:

              product: Prism 2.5 Wavelan chipset
              vendor: Intersil Corporation
              physical id: 7

I used to be running Redhat 9 (not Fedora Core 9) with kernel  
v2.4.20-8. I was able to run the DWL-520 as an access point by just  
doing this:

/sbin/iwconfig wlan0 essid weiler channel 1 key off
/sbin/ifconfig wlan0 192.168.0.1

and then running the appropriate dhcpd and routing things to get  
connectivity to work.  Now, I'm running Fedora Core 11 with kernel  
2.6.31.2

As far as my system goes, dmesg shows this:

hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x21
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.2
wifi0: Intersil Prism2.5 PCI: mem=0xfeb00000, irq=27
wifi0: registered netdevice wlan0
udev: renamed network interface wlan0 to eth2
eth2: Host AP mode does not support 'Any' essid
prism2: eth2: operating mode changed 3 -> 2
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=00:05:5d:ee:68:e7
wifi0: LinkStatus=2 (Disconnected)
wifi0: LinkStatus: BSSID=44:44:44:44:44:44
wifi0: dropped unencrypted TX data frame (drop_unencrypted=1)
eth2: no IPv6 routers present

I use the following commands to try to set up my access point:

/sbin/iwconfig eth2 mode master
/sbin/iwconfig eth2 essid weiler channel 3 key 1234567890
/sbin/ifconfig eth2 192.168.0.1

then later, when I'm doing the pings, I get a bunch of these:

Virtual device wifi0 asks to queue packet!

At the suggestion of a few other sites, I have many modules  
blacklisted: orinoco, orinoco_pci, hermes, eth1394, p80211, prism2_pci

Here's the grep'ed contents of /var/log/messages:

Oct  8 19:45:28 fred kernel: hostap_pci: Registered netdevice wifi0
Oct  8 19:45:28 fred kernel: wifi0: NIC: id=0x8013 v1.0.0
Oct  8 19:45:28 fred kernel: wifi0: PRI: id=0x15 v1.1.1
Oct  8 19:45:28 fred kernel: wifi0: STA: id=0x1f v1.8.2
Oct  8 19:45:28 fred kernel: wifi0: Intersil Prism2.5 PCI:  
mem=0xfeb00000, irq=27
Oct  8 19:45:28 fred kernel: udev: renamed network interface wlan0 to eth2
Oct  8 19:45:30 fred NetworkManager: <info>  (eth2): driver supports  
SSID scans (scan_capa 0x01).
Oct  8 19:45:30 fred NetworkManager: <info>  (eth2): new 802.11 WiFi  
device (driver: 'hostap_pci')
Oct  8 19:45:30 fred NetworkManager: <info>  (eth2): exported as  
/org/freedesktop/Hal/devices/net_00_05_5d_ee_68_e7
Oct  8 19:45:30 fred NetworkManager: <info>  (eth2): supplicant  
manager state:  down -> idle
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): device state  
change: 1 -> 2
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): bringing up device.
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): preparing device.
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): deactivating  
device (reason: 2).
Oct  8 19:45:35 fred NetworkManager: <WARN>   
nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device  
eth2: Invalid argument
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): device state  
change: 2 -> 3
Oct  8 19:45:35 fred NetworkManager: <info>  (eth2): supplicant  
interface state:  starting -> ready
Oct  8 19:45:36 fred avahi-daemon[1239]: Registering new address  
record for fe80::205:5dff:feee:68e7 on eth2.*.
Oct  8 19:45:38 fred ntpd[1481]: Listening on interface #6 eth2,  
fe80::205:5dff:feee:68e7#123 Enabled

And output of iwconfig looks like this:

wifi0     IEEE 802.11b  ESSID:"weiler"  Nickname:""
           Mode:Master  Frequency:2.422 GHz  Access Point: 00:05:5D:EE:68:E7
           Bit Rate:11 Mb/s   Sensitivity=1/3
           Retry short limit:8   RTS thr:off   Fragment thr:off
           Encryption key:12345-6789-00   Security mode:restricted
           Power Management:off

eth2      IEEE 802.11b  ESSID:"weiler"  Nickname:""
           Mode:Master  Frequency:2.422 GHz  Access Point: 00:05:5D:EE:68:E7
           Bit Rate:11 Mb/s   Sensitivity=1/3
           Retry short limit:8   RTS thr:off   Fragment thr:off
           Encryption key:12345-6789-00   Security mode:restricted
           Power Management:off
           Link Quality:0  Signal level:0  Noise level:0
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:18  Invalid misc:78   Missed beacon:0



One last thing: what's weird is that even though I, at one point,  
tried to set the key to be "off", my windows box still claimed it  
required a key so I set the key as you see above.

Any ideas on what might be wrong?  I figured there's got to be a way  
to get this work since it was working with my RedHat 9 system before.



More information about the HostAP mailing list