DWL-520+ and ACX100 drivers

[amhso]

I recently had the latest acx100 drivers installed on my box (slackware 10.2, kernel 2.6.13). I configured it to my access point with the correct key and information in /etc/rc.d/rc.wireless.conf, and added the correct access point MAC address to /etc/rc.d/rc.inet1.conf. Even though I do have an IP address, packets seem not to transfer correctly at all, thus I don't have any sort of connection. I used the following to get an IP:
dhcpcd killall
dhcpcd wlan0
ifconfig eth0 down <<<<<Brings down my LAN wired interface
ifconfig wlan0 up

Although i have an IP assigned to me, /var/log/syslog report errors an error about authentication. I have used this card in windows and it worked with WEP. I get (in /var/log/syslog):

Nov 3 21:32:43 alex kernel: acx_timer: status = 3
Nov 3 21:32:43 alex kernel: resend association request (attempt 8).
Nov 3 21:32:43 alex kernel: Sending association request, awaiting response! NOT ASSOCIATED YET.
Nov 3 21:32:43 alex kernel: association: requesting caps 0x0001, ESSID STA886F48
Nov 3 21:32:43 alex kernel: <acx_set_timer> Elapse = 2500000
Nov 3 21:32:43 alex kernel: Association FAILED: peer station sent response status code 12: "Association denied due to reason outside the scope of 802.11b standard. TRANSLATION: peer station may have MAC filtering enabled or assoc to wrong AP (BUG), FIX IT!"!

This repeats over and over again, not just when trying to establish a connection.

Some more info:

iwconfig:

root@alex:/home/amhso# iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11b+ ESSID:"home" Nickname:"alex"
Mode:Managed Frequency:2.417 GHz Access Point: 00:11:95:38:47:DB
Bit Rate=11 Mb/s Tx-Power=18 dBm Sensitivity=176/255
Retry min limit:7 RTS thr:off
Encryption key:1234-5678-9D Security mode:restricted
Power Management:off
Link Quality=67/100 Signal level=54/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

ifconfig:

root@alex:~# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5040 (4.9 Kb) TX bytes:5040 (4.9 Kb)

wlan0 Link encap:Ethernet HWaddr 00:01:23:45:67:89
inet addr:192.168.0.107 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::201:23ff:fe45:6789/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8392 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1418120 (1.3 Mb) TX bytes:3245 (3.1 Kb)
Interrupt:5 Base address:0xd000

And lsmod:

root@alex:~# lsmod
Module Size Used by
snd_pcm_oss 46240 0
snd_mixer_oss 15872 1 snd_pcm_oss
ipv6 225600 8
uhci_hcd 29584 0
ehci_hcd 29704 0
sis_agp 6148 1
shpchp 91364 0
i2c_sis630 6924 0
i2c_sis96x 4868 0
i2c_core 16656 2 i2c_sis630,i2c_sis96x
ohci_hcd 18436 0
snd_intel8x0 27968 1
snd_ac97_codec 75388 1 snd_intel8x0
snd_pcm 75016 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 19716 1 snd_pcm
snd 45572 8 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_co dec,snd_pcm,snd_timer
soundcore 6880 1 snd
snd_page_alloc 7556 2 snd_intel8x0,snd_pcm
sis900 18176 0
mii 4608 1 sis900
acx_pci 140420 0
firmware_class 7424 1 acx_pci
nvidia 3703688 0
evdev 7296 0
agpgart 28616 2 sis_agp,nvidia
psmouse 29956 0
reiserfs 223216 2


EDIT: Modified for to be more informative

[banzaikai]

Can you log in with WEP turned off on the router/WAP? If so, then it's your WEP settings. If not, it's your card/driver.

One thing to check: With WEP, you can have a "generated" key, and a "direct" key. The first uses a "key phrase" to generate the actual key, and the latter is the key. I like to use the latter, to make sure the algorithm that generates the key from the phrase isn't what's messing things up. And that's where it gets fun...

Since the key is input using hexadecimal, you get to use the letters A-F. This makes it fun to pick out keys that can be easily remembered: ACED, FACE, FADE, F1D0, or F00D. Have fun with it. If you're an "Animal House" fan, then try "F000DF1647" (Food fight!).

So, turn off the WEP at the router/WAP, and see what happens. If you can connect, then make sure you're using the right type of key value.

BTW, your IP is assigned "in the clear", just the data is WEPped. Once a link is established, the two then negotiate the WEP key and go from there. If you get an IP from the router/WAP's DHCP, then it's probably seeing your card, just not doing anything with it, which leads us back to WEP settings.

Also, if this is a router you're trying to connect to, then check to make sure that the MAC address of the card is in the MAC Filters (Allowed) in the wireless security tab. I had a Dickens of a time with a card before I realized I hadn't done this, and it worked just fine once added. My bad.

banzai "MAC daddy" kai

[amhso]

all the lan filters are off, meaning the router allows any to come in, as long as the ip is between 192.168.0.0 and 192.168.0.199.

I am pretty sure the key is correct, but i have a question about open and restricted security settings. in windows, i have the choices open and shared. is restricted the same as "shared"?

[banzaikai]

IIRC, Windows refers to the key as a shared one, open if it's not used, and "Direct" or "Manual" key should be the third option. Make sure it's not refering to resources (files, printers), unless you do want to allow that using smb/samba. And what, exactly, do you mean by "In Windows..."? This should be at the router's login/setup screen, which is OS independent. Just browse to 192.168.0.1, input username and password, and tab through the router's setup. If you have WEP enabled on the router, it must be enabled on the DWL-520. If it's disabled, then no WEP should be used on the card. For security purposes, most routers will only allow setup to be accessed with a direct cable connection (not wireless).

Now, what do you mean "any addy between 192.168.0.0 and 192.168.0.199"? I thought you were using DHCP from the router, which should have a setting as to where it'll start the DHCP assignments (Linksys defaults to 192.168.1.100-150). Also, most routers reserve 192.168.0.0-1 for the router login/gateway/DMZ, so the "lowest" you'd want to set this is 192.168.0.2, but you do want to have room for any static IPs, so having your DHCP start at 100 is about right.

Your original post stated you had an IP assigned to you - was this static or dynamic? If static, try using an IP between 2 and 99, if dynamic (DHCP), then it should show up as 100-150.

BTW, what router do you have? Linksys typically uses x.x.1.x, where D-Link uses x.x.0.x. Make sure you've got the right numbers in there. Post your output from /sbin/ifconfig.

banzai "D-Linksys" kai

[amhso]

WEP is enabled and i am using. By "in windows" i meant that the driver on windows is configured that way. I can access my router of wireless, although it can be set to only allow cable connections. Where would i find the "direct" and "manual" options?

The open/restricted is in the encryption type settings, and I will be using samba/smb for printers and files.

The router auto assigns the ip's to the computers (once a week). So it is dynamic. I always get an ip between 192.168.0.100-150 . My router is x.x.0.x, as it is D-link.

We may siwtch to static, but at the moment we're sticking with dynamic.

Ifconfig before i do the commands and get my ip. (The router wont give me an ip for cable AND wireless connection)

eth0 Link encap:Ethernet HWaddr 00:D0:09:DB:E9:F4
inet addr:192.168.0.105 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:9ff:fedb:e9f4/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:391 errors:0 dropped:0 overruns:0 frame:0
TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:109343 (106.7 Kb) TX bytes:16549 (16.1 Kb)
Interrupt:11 Base address:0xd400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1150 (1.1 Kb) TX bytes:1150 (1.1 Kb)

wlan0 Link encap:Ethernet HWaddr 00:01:23:45:67:89
inet6 addr: fe80::201:23ff:fe45:6789/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:472 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:106249 (103.7 Kb) TX bytes:140 (140.0 b)
Interrupt:5 Base address:0xd000

[banzaikai]

Okay, some basics:

Both the WAP (router) and client's card must be set to the same settings. If the router is "open", it means anyone and their pets can log in. If you don't want to have the FBI knocking on your door because your neighbor just got done downloading "stuff" off your connection, then you'll have to restrict the access...

Step A: MAC address filtering. This is a simple table entered into the router's memory that lists all the MAC addresses of the cards you don't mind using the router. Anything else is rejected. Of course, anyone can "sniff" this number when you're logged in, and clone it, so it's not foolproof.

After re-reading your posts, I saw this: Association FAILED: peer station sent response status code 12: "Association denied due to reason outside the scope of 802.11b standard. TRANSLATION: peer station may have MAC filtering enabled or assoc to wrong AP (BUG), FIX IT!"!
Which tells me you need to double-check the "Advanced -> Filters" setting to make sure you selected "Allow" and not "Deny" - easy to do on a D-Link.

Step B: WEP (Wired Equivalent Privacy). This is a simple way of encrypting the packets to prevent snooping. It also has the added benefit of locking out those who don't have the right key. There are two ways to configure this key: Pass phrase and Direct.

Step B1: Pass Phrase Key uses an easily remembered word (phrase) that is then shoved into an algorithm to generate the actual key. This means you punch in something like "penguin" as your phrase (on BOTH the router and card), and it'll generate the actual key of something like "12AB34CD5E". The nice thing is, humans can remember this more easily. The bad thing is, the two (or more) devices have to use the exact same algorithm, or the key will be different.

Step B2: Direct Key is exactly that. You enter the key value into both router and client, no algorithm is used. This has the benefit of not having any incompatibility, but it's harder to memorize (unless you use my guides above). So, just punch in "ABBA15600D" in the key entry, and you're all set.

However, WEP isn't all that great of an encryption protocol...

Step C: WPA (Wireless Protected Access). Much more robust than WEP, but some cards and routers don't support this (check for any firmware updates for your hardware). The setup is pretty much the same as with WEP.

Now, as stated earlier, you have to set this up on BOTH the router and card. It only takes me a few minutes to set up wireless, because I use the following steps:

1) Configure router for OPEN wireless, check access with client. If not connecting, then problem is with router or card.
2) If both are connecting when open, then set router to direct WEP key, add same key to client, and check. If client is not connecting, then either key value is bad/mistyped, or card/OS is flaky dealing with WEP. If this is the case, turn WEP off and go to step 3.
3) Try WPA (if available). Again, if not connecting, then turn it off.
4) If all else fails, then set the router's wireless security MAC filtering to allow the client's MAC. You may want to do this anyway, as extra protection.

Now, I can't hand-hold you through the config, as I use a Linksys router, and I still don't know what card you're using - each one has a different utility to configure the WEP/WPA. In the router's wireless setup, there should be an option as to which WEP key type you want to use. The first option is usually "Pass Phrase/ASCII", with "Manual Entry/HEX" somewhere below that. For the time being, just "Disable" the #%$@& WEP, so we can see if it connects (step 1). Then tell your wlan0 config that you're using an "Open" WAP, and it should then pop up. If not, then there's something else wrong.

Once connected in "Open" mode, THEN you can start playing with WEP again. On the D-Link 514s, you click the Wireless button, Enable WEP, Select 64-bit WEP Encryption, select "HEX" as Key Type, then punch in your ten-digit key into the Key1 box. Save it, exit. Then config your wlan0, and set key to the same as the router. Restart the wlan0, and it should connect.

If not, just keep both in Open mode (WEP disabled), set the router's MAC Filter to allow your card, and call it a day.

banzai "weirdless" kai