Re: [Madwifi-users] Problems associating with AP
Status: Beta
Brought to you by:
otaku
From: Markus D. <da...@gm...> - 2003-08-21 16:16:55
|
Hi Silas, I am using 128Bit encryption and my AP is set to "Shared secret" encryption. I am so far only using Key nr. 1. With my old card and the prism driver it all worked with this configuration: #=======WEP=========================================== # [Dis/En]able WEP. Settings only matter if PrivacyInvoked is true lnxreq_hostWEPEncrypt=true # true|false lnxreq_hostWEPDecrypt=true # true|false dot11PrivacyInvoked=true # true|false dot11WEPDefaultKeyID=0 # 0|1|2|3 dot11ExcludeUnencrypted=true # true|false, in AP this means WEP is required. PRIV_GENERATOR=/sbin/nwepgen # nwepgen, Neesus compatible PRIV_KEY128=true # keylength to generate PRIV_GENSTR="xxxxxxxxxxxx" <-- real string goes here of course AuthType="sharedkey" # opensystem | sharedkey (requires WEP) ---- Of course I now this configuration cannot be used with the Atheros drivers. I am using the ASCII WEP string with my old card, but I used as well the Hex representation already with my XP drivers, so I know that the hex codes I enter for the key are OK. (They are identical to what I've set on the AP) For setting the WEP keys with the Atheros driver I do the following: iwconfig ath0 mode managed iwconfig ath0 essid "ASGARD" iwconfig ath0 mode managed iwconfig ath0 rate auto iwconfig ath0 channel 11 iwconfig ath0 key xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx [1] <-- "xxxx" is identical to what is set in the AP iwconfig ath0 key [1] restricted iwconfig ath0 key on But this does not seem to have any effect, as the resulting "iwonfig ath0" shows no key. I repeat the procedure a couple of times until I get: littleigloo:~ # iwconfig ath0 ath0 IEEE 802.11-DS ESSID:"ASGARD" Mode:Managed Frequency:2.462GHz Access Point: 00:80:C8:12:4C:E0 Bit Rate:1Mb/s Tx-Power:off Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Encryption mode:open Power Management:off Link Quality:0/92 Signal level:24/154 Noise level:0/154 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 When I now try to send something on the network (e.g. get DHCP address or ping) I get "authentication failure (reason 13)". in /var/log/messages littleigloo:~ # iwlist ath0 encryption ath0 2 key sizes : 40, 104bits 4 keys available : [1]: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx (104 bits) [2]: off [3]: off SIOCGIWENCODE: Invalid argument Current Transmit Key: [1] Encryption mode:open littleigloo:~ # iwlist ath0 scanning ath0 Scan completed : Cell 01 - Address: 00:80:C8:12:4C:E0 Mode:Master Encryption key:****-****-**** Quality:0/92 Signal level:35/154 Noise level:0/154 Mode:Master ESSID:"ASGARD" Frequency:2.462GHz Bit Rate:1Mb/s Bit Rate:2Mb/s Bit Rate:5Mb/s Bit Rate:6Mb/s Bit Rate:11Mb/s Bit Rate:12Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Hope this makes sense to you! Markus ========================================================================== silas bennett wrote: > Hi Markus, > > What strength of WEP are you using? 64, 128, ect. and how are you > setting the keys. Are you entering the madwifi keys in hex? If not you > should be. WEP works fine for me, you are assosiating, you are > recieving a DHCP IP address, so you are able to send and recieve > traffic, all this means that you are doing something wrong with the > WEP encryption. Please send all information relevent to your > configuration. i.e. contents of /etc/network/interfaces, output of > iwconfig ath0 and output of iwlist ath0 scan. > > I bet you it is something silly and simple that you are overlooking. ;0) > > Cheers, > Silas > > =0) > > > ----Original Message Follows---- > From: Markus Dauberschmidt <da...@gm...> > Reply-To: Markus Dauberschmidt <da...@gm...> > To: mad...@li... > Subject: Re: [Madwifi-users] Problems associating with AP > Date: Tue, 19 Aug 2003 23:23:37 +0200 > > Hello *, > > I managed to connect now when WEP is disabled and so far everthing > seems to work fine. > It still does not work when I enable WEP on the access point. > ("authentication failure (reason 13)"). > I double checked the WEP keys and also tried to set all 3 keys (I > cannot set 4, see mail below "SIOCGIWENCODE: Invalid argument ") > > What's wrong? Is it a driver issue? > I already tried the CVS version as of 19th August. > > Markus > > ------ > > > Markus Dauberschmidt wrote: > >> Hello, >> >> I am having problems getting my DLink DWL-G650 to work with the madwifi >> drivers. >> Compile went fine, but I can't seem to associate with my AP (DLink >> DI-624) >> What am I doing wrong? I am not very familiar with iwconfig & Co. >> Sorry for the lengthy mail, but I try to provide as much information as >> possible. >> >> /var/log/messages after card insert: >> >> Aug 19 20:21:53 littleigloo kernel: cs: cb_alloc(bus 6): vendor 0x168c, >> device 0x0013 >> Aug 19 20:21:53 littleigloo kernel: PCI: Enabling device 06:00.0 (0000 >> -> 0002) >> Aug 19 20:21:53 littleigloo cardmgr[930]: socket 1: CardBus hotplug >> device >> Aug 19 20:21:54 littleigloo kernel: ath_hal: 0.9.5.3 BETA (Sam Leffler >> <sa...@er...>) >> Aug 19 20:21:54 littleigloo kernel: wlan: 0.7.1.1 BETA (Sam Leffler >> <sa...@er...>) >> Aug 19 20:21:54 littleigloo kernel: ath_pci: 0.8.3.2 BETA (Sam Leffler >> <sam@errn >> o.com>) >> Aug 19 20:21:54 littleigloo kernel: ath_pci: cache line size not set; >> forcing 8 >> Aug 19 20:21:54 littleigloo kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps >> 11Mbps >> Aug 19 20:21:54 littleigloo kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps >> 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36M >> bps 48Mbp >> s 54Mbps >> Aug 19 20:21:54 littleigloo kernel: ath0: 802.11 address: >> 00:80:c8:13:b0:d1 >> Aug 19 20:21:54 littleigloo kernel: ath0: Atheros 5212: mem=0x11000000, >> irq=10 >> Aug 19 20:21:54 littleigloo insmod: Using >> /lib/modules/2.4.20-4GB/net/ath_hal.o >> Aug 19 20:21:54 littleigloo insmod: Symbol version prefix '' >> Aug 19 20:21:54 littleigloo insmod: Warning: loading >> /lib/modules/2.4.20-4GB/net/ath_hal.o will taint the kernel: no >> n-GPL lic >> ense - Proprietary >> Aug 19 20:21:54 littleigloo insmod: See >> http://www.tux.org/lkml/#export-tainted for information about tainted >> modu >> les >> Aug 19 20:21:54 littleigloo insmod: Module ath_hal loaded, with warnings >> Aug 19 20:21:54 littleigloo insmod: Using >> /lib/modules/2.4.20-4GB/net/wlan.o >> Aug 19 20:21:54 littleigloo insmod: Module wlan loaded, with warnings >> Aug 19 20:21:54 littleigloo insmod: Using >> /lib/modules/2.4.20-4GB/net/ath_pci.o >> Aug 19 20:21:54 littleigloo insmod: Module ath_pci loaded, with warnings >> Aug 19 20:21:55 littleigloo /etc/hotplug/pci.agent[1722]: writing >> pcmcia-1 to /var/run/hotplug/net >> Aug 19 20:21:55 littleigloo /etc/hotplug/net.agent[1761]: Using HW >> description ath-pcmcia-1 >> Aug 19 20:21:56 littleigloo ifup: No configuration found for >> ath-pcmcia-1 ath0 >> >> littleigloo:~ # cardctl ident >> Socket 0: >> no product info available >> Socket 1: >> product info: "Atheros Communications, Inc.", "AR5001-0000-0000", >> "Wireless LAN Reference Card", "00" >> manfid: 0x0271, 0x0012 >> function: 6 (network) >> littleigloo:~ # >> >> I set up the card with the following commands: >> >> iwconfig ath0 mode managed >> iwconfig ath0 essid "ASGARD" >> iwconfig ath0 mode managed >> iwconfig ath0 rate auto >> iwconfig ath0 channel 11 >> iwconfig ath0 key xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx [1] >> iwconfig ath0 key [1] restricted >> iwconfig ath0 key on >> >> After issuing an "ifconfig ath0 up" I get the following (before ESSID is >> always "") >> >> littleigloo:~ # iwconfig ath0 >> ath0 IEEE 802.11-DS ESSID:"ASGARD" >> Mode:Managed Frequency:2.462GHz Access Point: >> 00:80:C8:12:4C:E0 >> Bit Rate=1Mb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:off >> Power Management:off >> Link Quality:0/92 Signal level:36/154 Noise level:0/154 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> "iwconfig ath0 key xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx restricted" I >> finally can set the key: >> (as you can see from above no key is set although I set it using the >> commands above!) >> >> littleigloo:~ # iwconfig ath0 >> ath0 IEEE 802.11-DS ESSID:"ASGARD" >> Mode:Managed Frequency:2.437GHz Access Point: >> FF:FF:FF:FF:FF:FF >> Bit Rate:1Mb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Encryption >> mode:open >> Power Management:off >> Link Quality:0/92 Signal level:28/154 Noise level:0/154 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> (As you can see the AP MAC ist now FF:FF:FF:FF:FF:FF) >> After some retries it gets to: >> >> littleigloo:~ # iwconfig ath0 >> ath0 IEEE 802.11-DS ESSID:"ASGARD" >> Mode:Managed Frequency:2.462GHz Access Point: >> 00:80:C8:12:4C:E0 >> Bit Rate:1Mb/s Tx-Power:off Sensitivity=0/3 >> Retry:off RTS thr:off Fragment thr:off >> Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Encryption >> mode:open >> Power Management:off >> Link Quality:0/92 Signal level:24/154 Noise level:0/154 >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 >> >> So everything looks ok but /var/log/messages keeps on giving me: >> Aug 19 20:25:32 littleigloo kernel: ath0: authentication failed (reason >> 13) for 00:80:c8:12:4c:e0 >> >> I've read that DHCP does not yet work (is this still true?), so I tried >> to set an IP with "ipconfig" >> by hand but I still get the authentication failures! >> >> littleigloo:~ # iwlist ath0 encryption >> ath0 2 key sizes : 40, 104bits >> 4 keys available : >> [1]: xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx (104 bits) >> [2]: off >> [3]: off >> SIOCGIWENCODE: Invalid argument >> Current Transmit Key: [1] >> Encryption mode:open >> >> What does "Encryption mode:open" mean? Is it not enabled? >> >> littleigloo:~ # ifconfig ath0 >> ath0 Link encap:Ethernet HWaddr 00:80:C8:13:B0:D1 >> inet6 addr: fe80::280:c8ff:fe13:b0d1/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:445 errors:26 dropped:0 overruns:0 frame:7 >> TX packets:1509 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:199 >> RX bytes:32274 (31.5 Kb) TX bytes:62420 (60.9 Kb) >> Interrupt:10 Memory:d1050000-d1060000 >> >> littleigloo:~ # iwlist ath0 scanning >> ath0 Scan completed : >> Cell 01 - Address: 00:80:C8:12:4C:E0 >> Mode:Master >> Encryption key:****-****-**** >> Quality:0/92 Signal level:35/154 Noise level:0/154 >> Mode:Master >> ESSID:"ASGARD" >> Frequency:2.462GHz >> Bit Rate:1Mb/s >> Bit Rate:2Mb/s >> Bit Rate:5Mb/s >> Bit Rate:6Mb/s >> Bit Rate:11Mb/s >> Bit Rate:12Mb/s >> Bit Rate:24Mb/s >> Bit Rate:36Mb/s >> >> So I am associated, am I not??? >> >> What am I doing wrong? I am not very familiar with iwconfig. Do I have >> to do anything else? >> I tried to have WEP disabled, but it didn't work either... >> The LEDs on the card are blinking alternate but not in sync. >> >> I used a Prism based card before. Everthing was perfect using the >> following config: >> >> #=======USER MIB SETTINGS============================= >> # You can add the assignments for various MIB items >> # of your choosing to this variable, separated by >> # whitespace. The wlan-ng script will then set each one. >> # Just uncomment the variable and set the assignments >> # the way you want them. >> >> #USER_MIBS="p2CnfRoamingMode=1 p2CnfShortPreamble=mixed" >> >> #=======WEP=========================================== >> # [Dis/En]able WEP. Settings only matter if PrivacyInvoked is true >> lnxreq_hostWEPEncrypt=true # true|false >> lnxreq_hostWEPDecrypt=true # true|false >> dot11PrivacyInvoked=true # true|false >> dot11WEPDefaultKeyID=0 # 0|1|2|3 >> dot11ExcludeUnencrypted=true # true|false, in AP this means WEP is >> required. >> >> # If PRIV_GENSTR is not empty, use PRIV_GENTSTR to generate >> # keys (just a convenience) >> PRIV_GENERATOR=/sbin/nwepgen # nwepgen, Neesus compatible >> PRIV_KEY128=true # keylength to generate >> PRIV_GENSTR="xxxxxxxxxxxx" >> >> # or set them explicitly. Set genstr or keys, not both. >> dot11WEPDefaultKey0= # format: xx:xx:xx:xx:xx or >> dot11WEPDefaultKey1= # >> xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx >> dot11WEPDefaultKey2= # e.g. 01:20:03:40:05 or >> dot11WEPDefaultKey3= # >> 01:02:03:04:05:06:07:08:09:0a:0b:0c:0d >> #=======SELECT STATION MODE=================== >> IS_ADHOC=n # y|n, y - adhoc, n - infrastructure >> >> #======= INFRASTRUCTURE STATION =================== >> # What kind of authentication? >> AuthType="sharedkey" # opensystem | sharedkey (requires WEP) >> >> #======= ADHOC STATION ============================ >> BCNINT=100 # Beacon interval (in Kus) >> CHANNEL=11 # DS channel for BSS (1-14, depends >> # on regulatory domain) >> BASICRATES="2 4" # Rates for mgmt&ctl frames (in 500Kb/s) >> OPRATES="2 4 11 22" # Supported rates in BSS (in 500Kb/s) >> >> Is it identically to what I've set via iwconfigf for the DLink? >> >> Markus >> >> >> >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by Dice.com. >> Did you know that Dice has over 25,000 tech jobs available today? From >> careers in IT to Engineering to Tech Sales, Dice has tech jobs from the >> best hiring companies. http://www.dice.com/index.epl?rel_code=104 >> _______________________________________________ >> Madwifi-users mailing list >> Mad...@li... >> https://lists.sourceforge.net/lists/listinfo/madwifi-users >> > > > > > ------------------------------------------------------- > This SF.net email is sponsored by Dice.com. > Did you know that Dice has over 25,000 tech jobs available today? From > careers in IT to Engineering to Tech Sales, Dice has tech jobs from the > best hiring companies. http://www.dice.com/index.epl?rel_code=104 > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > > _________________________________________________________________ > <b>Get MSN 8</b> and help protect your children with advanced parental > controls. http://join.msn.com/?page=features/parental > > > > ------------------------------------------------------- > This SF.net email is sponsored by Dice.com. > Did you know that Dice has over 25,000 tech jobs available today? From > careers in IT to Engineering to Tech Sales, Dice has tech jobs from the > best hiring companies. http://www.dice.com/index.epl?rel_code=104 > _______________________________________________ > Madwifi-users mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-users > |