Thread: [Ndiswrapper-general] SMC 2802W v2 with Linux 2.6.9
Status: Beta
Brought to you by:
pgiri
From: Sebastian K. <se...@to...> - 2004-10-25 14:31:44
|
Hi! I just got a SMC 2802W v2 WLAN PCI Card which I'm trying to get to work with Linux 2.6.9 and ndiswrapper 0.11 (I also tried the current CVS version). lspci -n lists the card as follows: ,---- | 0000:00:09.0 Class 0280: 1260:3890 (rev 01) `---- I downloaded the current driver from the smc webpage and followed the installation instructions on http://ndiswrapper.sourceforge.net/wiki/index.php/Installation. iwconfig says: ,---- | eth2 NOT READY! ESSID:"WLAN" | Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00 | Tx-Power=31 dBm Sensitivity=0/200 | Retry min limit:0 RTS thr=0 B Fragment thr=0 B | Encryption key:XXXX Security mode:restricted | Link Quality:0 Signal level:0 Noise level:0 | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 | Tx excessive retries:0 Invalid misc:0 Missed beacon:0 `---- What is "NOT READY!" supposed to tell me? And why is the card called eth2 instead of wlan0? When I do an "ifconfig eth2 up" I get the following messages in syslog: ,---- | ndiswrapper version 0.11 loaded (preempt=yes,smp=no) | ndiswrapper: driver 2802w (SMC,04/29/2004, 3.0.11.1) added | eth2: islpci_open() | eth2: resetting device... | eth2: uploading firmware... | prism54: request_firmware() failed for 'isl3890' | eth2: could not upload firmware ('isl3890') `---- Ok, it tries to load some firmware which fails. The installation page didn't mention that I needed a firmware file. Do I? I downloaded the most recent firmware file from prism54.org and copied it to /usr/lib/hotplug/firmware/isl3890. Now I get: ,---- | eth2: islpci_open() | eth2: resetting device... | eth2: uploading firmware... | eth2: firmware uploaded done, now triggering reset... | eth2: device soft reset timed out | eth2: timeout waiting for mgmt response 1000, triggering device | eth2: timeout waiting for mgmt response 845, triggering device | eth2: timeout waiting for mgmt response 552, triggering device | eth2: timeout waiting for mgmt response 333, triggering device | eth2: timeout waiting for mgmt response 139, triggering device | eth2: timeout waiting for mgmt response | eth2: timeout waiting for mgmt response 1000, triggering device | eth2: timeout waiting for mgmt response 759, triggering device | eth2: timeout waiting for mgmt response 477, triggering device | eth2: timeout waiting for mgmt response 283, triggering device | eth2: timeout waiting for mgmt response 92, triggering device | eth2: timeout waiting for mgmt response | eth2: timeout waiting for mgmt response 1000, triggering device | eth2: timeout waiting for mgmt response 589, triggering device | eth2: timeout waiting for mgmt response 170, triggering device | eth2: timeout waiting for mgmt response | eth2: timeout waiting for mgmt response 1000, triggering device | eth2: timeout waiting for mgmt response 784, triggering device | eth2: timeout waiting for mgmt response | eth2: mgmt tx queue is still full | last message repeated 14 times | eth2: mgt_commit has failed. Restart the device `---- I've found out that the firmware is supposed to be contained in the 2902w.sys file that comes with the driver. Is ndiswrapper supposed to recognize that? What am I doing wrong? -- Ciao, Sebastian |
From: <az...@se...> - 2004-10-25 15:44:56
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastian Kaps wrote: | When I do an "ifconfig eth2 up" I get the following messages in syslog: | ,---- | | ndiswrapper version 0.11 loaded (preempt=yes,smp=no) | | ndiswrapper: driver 2802w (SMC,04/29/2004, 3.0.11.1) added | | eth2: islpci_open() | | eth2: resetting device... | | eth2: uploading firmware... | | prism54: request_firmware() failed for 'isl3890' | | eth2: could not upload firmware ('isl3890') | `---- - ------8<----- | I've found out that the firmware is supposed to be contained in the | 2902w.sys file that comes with the driver. Is ndiswrapper supposed to | recognize that? | | What am I doing wrong? You are -NOT- using ndiswrapper. As you can see in the log, it's prism54 that gives that error. Try uninstall all prism54 related drivers, and remodprobe ndiswrapper. That should get you going. - -- ~ .''`. Torbjörn Svensson, azoff (at) se (dot) linux (dot) org ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A DBDB 0CFD ~ `. `' http://azoff.homeip.net | http://azoff.tty0.org ~ `-- http://www.se.linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBfR/neY7jmtvbDP0RAmCHAKC5gsrz/NPLgfG5T1zxgHphfYYt3QCfYo3q N4jvqevkzg34Xg4xnpXyCpk= =rKm8 -----END PGP SIGNATURE----- |
From: Vijay V. <vvi...@ya...> - 2004-10-25 17:26:56
|
1. If you want to use prism54 driver, then you need to get the isl3890 firmware and use it, like in this link http://prism54.org/~mcgrof/firmware/ 2. If you want to use ndiswrapper, just do "rmmod prism54" and then "modprobe ndiswrapper". If you have the firmware installed, the card will come up as wlan0. Vijay --- Torbjörn Svensson <az...@se...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sebastian Kaps wrote: > | When I do an "ifconfig eth2 up" I get the > following messages in syslog: > | ,---- > | | ndiswrapper version 0.11 loaded > (preempt=yes,smp=no) > | | ndiswrapper: driver 2802w (SMC,04/29/2004, > 3.0.11.1) added > | | eth2: islpci_open() > | | eth2: resetting device... > | | eth2: uploading firmware... > | | prism54: request_firmware() failed for 'isl3890' > | | eth2: could not upload firmware ('isl3890') > | `---- > > - ------8<----- > > | I've found out that the firmware is supposed to be > contained in the > | 2902w.sys file that comes with the driver. Is > ndiswrapper supposed to > | recognize that? > | > | What am I doing wrong? > > > You are -NOT- using ndiswrapper. > As you can see in the log, it's prism54 that gives > that error. Try > uninstall all prism54 related drivers, and > remodprobe ndiswrapper. That > should get you going. > > - -- > ~ .''`. Torbjörn Svensson, azoff (at) se (dot) > linux (dot) org > ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A > DBDB 0CFD > ~ `. `' http://azoff.homeip.net | > http://azoff.tty0.org > ~ `-- http://www.se.linux.org > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.6 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - > http://enigmail.mozdev.org > > iD8DBQFBfR/neY7jmtvbDP0RAmCHAKC5gsrz/NPLgfG5T1zxgHphfYYt3QCfYo3q > N4jvqevkzg34Xg4xnpXyCpk= > =rKm8 > -----END PGP SIGNATURE----- > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide > on ITManagersJournal > Use IT products in your business? Tell us what you > think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! > Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Jean-Luc C. (f5ibh) <jea...@wa...> - 2004-10-25 18:14:30
|
Le 25.10.2004 19:26:50, Vijay Venkatraman a =E9crit=A0: >1. If you want to use prism54 driver, then you need to >get the isl3890 firmware and use it, like in this link >http://prism54.org/~mcgrof/firmware/ > >2. If you want to use ndiswrapper, just do "rmmod >prism54" and then "modprobe ndiswrapper". If you have >the firmware installed, the card will come up as >wlan0. > >Vijay Hi, As is card is a "V2" one it is not supported by prism54. So ha has to =20 use ndiswrapper. The best to avoid recompiling a kernel and avoid the prism54 module to =20 be load ed is to blacklist simply editong /etc/hotplug/blacklist Regards Jean-Luc > >--- Torbjrn Svensson <az...@se...> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Sebastian Kaps wrote: >> | When I do an "ifconfig eth2 up" I get the >> following messages in syslog: >> | ,---- >> | | ndiswrapper version 0.11 loaded >> (preempt=3Dyes,smp=3Dno) >> | | ndiswrapper: driver 2802w (SMC,04/29/2004, >> 3.0.11.1) added >> | | eth2: islpci_open() >> | | eth2: resetting device... >> | | eth2: uploading firmware... >> | | prism54: request_firmware() failed for 'isl3890' >> | | eth2: could not upload firmware ('isl3890') >> | `---- >> >> - ------8<----- >> >> | I've found out that the firmware is supposed to be >> contained in the >> | 2902w.sys file that comes with the driver. Is >> ndiswrapper supposed to >> | recognize that? >> | >> | What am I doing wrong? >> >> >> You are -NOT- using ndiswrapper. >> As you can see in the log, it's prism54 that gives >> that error. Try >> uninstall all prism54 related drivers, and >> remodprobe ndiswrapper. That >> should get you going. >> >> - -- >> ~ .''`. Torbjrn Svensson, azoff (at) se (dot) >> linux (dot) org >> ~ : :' : 7EB9 2DC5 61AE DAB5 7099 BAC6 798E E39A >> DBDB 0CFD >> ~ `. `' http://azoff.homeip.net | >> http://azoff.tty0.org >> ~ `-- http://www.se.linux.org >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.2.6 (GNU/Linux) >> Comment: Using GnuPG with Thunderbird - >> http://enigmail.mozdev.org >> >> >iD8DBQFBfR/neY7jmtvbDP0RAmCHAKC5gsrz/NPLgfG5T1zxgHphfYYt3QCfYo3q >> N4jvqevkzg34Xg4xnpXyCpk=3D >> =3DrKm8 >> -----END PGP SIGNATURE----- >> >> >> >------------------------------------------------------- >> This SF.net email is sponsored by: IT Product Guide >> on ITManagersJournal >> Use IT products in your business? Tell us what you >> think of them. Give us >> Your Opinions, Get Free ThinkGeek Gift Certificates! >> Click to find out more >> >http://productguide.itmanagersjournal.com/guidepromo.tmpl >> _______________________________________________ >> Ndiswrapper-general mailing list >> Ndi...@li... >> >https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general >> > > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > > >------------------------------------------------------- >This SF.net email is sponsored by: IT Product Guide on >ITManagersJournal >Use IT products in your business? Tell us what you think of them. Give >us >Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out >more >http://productguide.itmanagersjournal.com/guidepromo.tmpl >_______________________________________________ >Ndiswrapper-general mailing list >Ndi...@li... >https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > > |
From: Sebastian K. <se...@to...> - 2004-10-25 20:32:49
|
Hi! > You are -NOT- using ndiswrapper. > As you can see in the log, it's prism54 that gives that error. Try > uninstall all prism54 related drivers, and remodprobe ndiswrapper. That > should get you going. Ah, thanks for that hint. I thought I was using a kernel compiled without prism but I wasn't. I made sure I'm using the correct kernel version and I've had more success. Now I get an "error -22" and I'm trying to solve this now (I've read the FAQ). -- Ciao, Sebastian |
From: Sebastian K. <se...@to...> - 2004-10-26 06:33:00
|
Hi! I'm now getting these messages when I do 'modprobe ndiswrapper': ,---- | ndiswrapper version 0.11+CVS loaded (preempt=yes,smp=no) | PCI: Enabling device 0000:00:0b.0 (0000 -> 0002) | PCI: Found IRQ 12 for device 0000:00:0b.0 | ndiswrapper: using irq 12 | ndiswrapper (NdisAcquireSpinLock:907): Windows driver trying to use uninitialized lock cbadd774, fixing it. | ndiswrapper (setup_dev:1342): unable to get mac address from driver | ndiswrapper (ndis_init_one_pci:1600): Couldn't setup interface | 2802w: probe of 0000:00:0b.0 failed with error -22 | ndiswrapper: driver 2802w () added `---- The card used IRQ 5 before and shared it with the USB. So I put it into another PCI slot and it now uses IRQ 12 which is not shared: ,---- | # cat /proc/interrupts | CPU0 | 0: 34647789 XT-PIC timer | 2: 0 XT-PIC cascade | 5: 0 XT-PIC uhci_hcd | 8: 225 XT-PIC rtc | 10: 6542 XT-PIC eth0 | 11: 871340 XT-PIC eth1 | 14: 154347 XT-PIC ide0 | NMI: 0 | LOC: 0 | ERR: 0 | MIS: 0 `---- But I keep getting this error. Any ideas? -- Ciao, Sebastian |
From: Jan K. <jan...@we...> - 2004-10-26 06:42:28
Attachments:
smime.p7s
|
Sebastian Kaps wrote: > Hi! > > I'm now getting these messages when I do 'modprobe ndiswrapper': > ,---- > | ndiswrapper version 0.11+CVS loaded (preempt=yes,smp=no) > | PCI: Enabling device 0000:00:0b.0 (0000 -> 0002) > | PCI: Found IRQ 12 for device 0000:00:0b.0 > | ndiswrapper: using irq 12 > | ndiswrapper (NdisAcquireSpinLock:907): Windows driver trying to use uninitialized lock cbadd774, fixing it. > | ndiswrapper (setup_dev:1342): unable to get mac address from driver When did you check out? We fixed a minor bug last night which caused exactly the error line above. If in doubt, please try again with the current version. Jan |
From: Sebastian K. <se...@to...> - 2004-10-26 10:26:40
|
Hi! > When did you check out? Yesterday afternoon (GMT). > We fixed a minor bug last night which caused exactly the error line > above. If in doubt, please try again with the current version. Thanks! It works now: ,---- | ndiswrapper version 0.11+CVS loaded (preempt=yes,smp=no) | PCI: Enabling device 0000:00:0b.0 (0000 -> 0002) | PCI: Found IRQ 12 for device 0000:00:0b.0 | ndiswrapper: using irq 12 | ndiswrapper (NdisAcquireSpinLock:907): Windows driver trying to use uninitialized lock cb057b74, fixing it. | wlan0: ndiswrapper ethernet device 00:04:e2:a5:ad:12 using driver 2802w | wlan0: encryption modes supported: WEP, WPA with TKIP, AES/CCMP | ndiswrapper: driver 2802w () added `---- -- Ciao, Sebastian |
From: Sebastian K. <se...@to...> - 2004-10-26 11:03:38
|
Hi! Ok, now I got the interface up and running but it won't talk to my AP. I can use "iwlist wlan0 scan" to bring up information about my AP, but I can't set the essid, bit rate and the AP's MAC: # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00 Bit Rate=2 Mb/s Tx-Power:32 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:0303-2383-3353-9343-8373-6343-13 Security mode:restricted Power Management:off Link Quality:100 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:3 Invalid misc:156 Missed beacon:0 # iwconfig wlan0 rate 54M # iwconfig wlan0 00:04:0E:1F:23:4C # iwconfig wlan0 essid WLAN # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00 Bit Rate=2 Mb/s Tx-Power:32 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:0303-2383-3353-9343-8373-6343-13 Security mode:restricted Power Management:off Link Quality:100 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:3 Invalid misc:164 Missed beacon:0 :-? -- Ciao, Sebastian |
From: Jean-Luc C. (f5ibh) <jea...@wa...> - 2004-10-26 11:16:59
|
Le 26.10.2004 13:03:31, Sebastian Kaps a =E9crit=A0: >Hi! > >Ok, now I got the interface up and running but it won't talk to my AP. >I can use "iwlist wlan0 scan" to bring up information about my AP, but >I >can't set the essid, bit rate and the AP's MAC: > ># iwconfig wlan0 >wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" > Mode:Managed Frequency:2.437 GHz Access Point: >00:00:00:00:00:00 > Bit Rate=3D2 Mb/s Tx-Power:32 dBm > RTS thr=3D2347 B Fragment thr=3D2346 B > Encryption key:0303-2383-3353-9343-8373-6343-13 Security >mode:restricted > Power Management:off > Link Quality:100 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:3 Invalid misc:156 Missed beacon:0 > ># iwconfig wlan0 rate 54M ># iwconfig wlan0 00:04:0E:1F:23:4C ># iwconfig wlan0 essid WLAN ># iwconfig wlan0 >wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" > Mode:Managed Frequency:2.437 GHz Access Point: which channel is using your access point ? >00:00:00:00:00:00 > Bit Rate=3D2 Mb/s Tx-Power:32 dBm > RTS thr=3D2347 B Fragment thr=3D2346 B > Encryption key:0303-2383-3353-9343-8373-6343-13 Security >mode:restricted > Power Management:off > Link Quality:100 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:3 Invalid misc:164 Missed beacon:0 > >:-? > >-- >Ciao, Sebastian > Jean-Luc |
From: Sebastian K. <se...@to...> - 2004-10-26 11:33:21
|
Hi Jean-Luc! >> # iwconfig wlan0 >> wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" >> Mode:Managed Frequency:2.437 GHz Access Point: > which channel is using your access point ? The AP uses Channel 6. 2.437 should be the correct value and I'm also able to change it with iwconfig. -- Ciao, Sebastian |
From: Jean-Luc C. (f. <jea...@wa...> - 2004-10-26 11:52:59
|
On Tue, Oct 26, 2004 at 01:33:14PM +0200, Sebastian Kaps wrote: hi Sebastien, > Hi Jean-Luc! >=20 > >> # iwconfig wlan0 > >> wlan0 IEEE 802.11g ESSID:off/any Nickname:"server" > >> Mode:Managed Frequency:2.437 GHz Access Point: >=20 > > which channel is using your access point ? >=20 > The AP uses Channel 6. > 2.437 should be the correct value and I'm also able to change it with > iwconfig. yes, should be right, but anyway in my case, the card has found the correct frequency from its own. For your information, here is my /etc/network/interface (mostly from the FAQ) auto wlan0 iface wlan0 inet static address 192.168.1.11 netmask 255.255.255.0 gateway 192.168.1.1 wireless_key BB90340FA82B6FD7D26A1DC735 wireless_essid WANADOO-79EB pre-up if grep -q ndiswrapper /proc/modules; then :; else modprobe ndis= wrapper; fi And here is a result of a iwconfig (I use channel 10): wlan0 IEEE 802.11g ESSID:"WANADOO-79EB" =20 Mode:Managed Frequency:2.457 GHz Access Point: 00:90:4B:84:F7:96 = =20 Bit Rate:24 Mb/s Tx-Power:32 dBm =20 RTS thr:2347 B Fragment thr:2346 B =20 Encryption key:BB90-340F-A82B-6FD7-D26A-1DC7-35 Security mode:restr= icted Power Management:off Link Quality:96/100 Signal level:-67 dBm Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:744 Invalid misc:9123 Missed beacon:0 - Regards Jean-Luc >=20 > --=20 > Ciao, Sebastian |
From: Sebastian K. <se...@to...> - 2004-10-26 13:18:03
|
Hi Jean-Luc! > yes, should be right, but anyway in my case, the card has found the correct > frequency from its own. I'm not sure if I did initially set the channel, so maybe it was auto-detected too. > For your information, here is my /etc/network/interface > (mostly from the FAQ) Thanks. I didn't know about the wireless_<function> options. Anyway, that doesn't change anything. I still can't set the ESSID. Am I correct that I have to set the ESSID to the correct value in order to get it all working? -- Ciao, Sebastian |
From: Adrian Irving-B. <wis...@wi...> - 2004-10-26 13:39:48
|
On Tue, Oct 26, 2004 at 01:03:31PM +0200, Sebastian Kaps wrote: > # iwconfig wlan0 00:04:0E:1F:23:4C What does this do? I can't find this 'no keyword' syntax referenced in the iwconfig manpage, and I don't have hardware to test on. Does it set the AP? |
From: Sebastian K. <se...@to...> - 2004-10-26 13:43:30
|
Hi Adrian! >> # iwconfig wlan0 00:04:0E:1F:23:4C > What does this do? Oh, sorry. This was supposed to mean "iwconfig wlan0 ap ...". -- Ciao, Sebastian |
From: Jean-Luc C. (f5ibh) <jea...@wa...> - 2004-10-26 15:08:08
|
Le 26.10.2004 15:17:56, Sebastian Kaps a =E9crit=A0: >Hi Jean-Luc! > >> yes, should be right, but anyway in my case, the card has found the >correct >> frequency from its own. > >I'm not sure if I did initially set the channel, so maybe it was >auto-detected too. > >> For your information, here is my /etc/network/interface >> (mostly from the FAQ) > >Thanks. I didn't know about the wireless_<function> options. >Anyway, that doesn't change anything. I still can't set the ESSID. >Am I correct that I have to set the ESSID to the correct value in =20 > order >to get it all working? No, if the essid is left blank you can see "any" and it will be set =20 according to the negociation with the access point sen man (7) wireless for the wirelesss functions in /etc/network/=20 interfaces > >-- >Ciao, Sebastian J-L |
From: Sebastian K. <se...@to...> - 2004-10-26 15:44:54
|
Hi Jean-Luc! > No, if the essid is left blank you can see "any" and it will be set > according to the negociation with the access point Ah, I see. So what do I have to do to force the card to negotiate with the access point? I'm new to WLAN, so excuse me if I don't see the obvious. > sen man (7) wireless for the wirelesss functions in /etc/network/ > interfaces Yes, I've already found it. -- Ciao, Sebastian |
From: Jean-Luc C. (f5ibh) <jea...@wa...> - 2004-10-26 17:22:08
|
Le 26.10.2004 17:44:48, Sebastian Kaps a =E9crit=A0: >Hi Jean-Luc! > >> No, if the essid is left blank you can see "any" and it will be set >> according to the negociation with the access point > >Ah, I see. So what do I have to do to force the card to negotiate with >the access point? I'm new to WLAN, so excuse me if I don't see the >obvious. In *my* case, I've to press a button on the access point for it to =20 register a new WiFI device, maybe it is the same in your case? The following command will give you the access points and ad-hoc cells =20 available around: iwlist wlan0 scan > >> sen man (7) wireless for the wirelesss functions in /etc/network/ >> interfaces > >Yes, I've already found it. > >-- >Ciao, Sebastian J-L |
From: Sebastian K. <se...@to...> - 2004-10-26 18:00:14
|
Hi Jean-Luc! > In *my* case, I've to press a button on the access point for it to > register a new WiFI device, maybe it is the same in your case? My AP doesn't have such a button. According to its documentation I don't need to register any WiFi device. I guess this is just needed if there's an authentication mechanism based on a device's MAC address. > The following command will give you the access points and ad-hoc cells > available around: > iwlist wlan0 scan Yes, I know that. I can "see" my access point: ,---- | wlan0 Scan completed : | Cell 01 - Address: 00:04:0E:1F:23:4C | ESSID:"WLAN" | Protocol:IEEE 802.11g | Mode:Managed | Frequency:2.437 GHz (Channel 6) | Quality:0/100 Signal level:-86 dBm Noise level:-256 dBm | Encryption key:on | Bit Rate:1 Mb/s | Bit Rate:2 Mb/s | Bit Rate:5.5 Mb/s | Bit Rate:11 Mb/s | Bit Rate:6 Mb/s | Bit Rate:9 Mb/s | Bit Rate:12 Mb/s | Bit Rate:18 Mb/s | Bit Rate:24 Mb/s | Bit Rate:36 Mb/s | Bit Rate:48 Mb/s | Bit Rate:54 Mb/s | Extra:bcn_int=200 | Extra:atim=2 `---- So what do I have to do now? As far as I understand, I have to set the ESSID on the wlan card to "WLAN" (which does not work) and then it's supposed to work. Or am I wrong? -- Ciao, Sebastian |
From: Jean-Luc C. (f5ibh) <jea...@wa...> - 2004-10-26 18:16:22
|
Le 26.10.2004 20:00:06, Sebastian Kaps a =E9crit=A0: >Hi Jean-Luc! > >> In *my* case, I've to press a button on the access point for it to >> register a new WiFI device, maybe it is the same in your case? > >My AP doesn't have such a button. According to its documentation I >don't >need to register any WiFi device. I guess this is just needed if >there's >an authentication mechanism based on a device's MAC address. > >> The following command will give you the access points and ad-hoc >cells >> available around: >> iwlist wlan0 scan > >Yes, I know that. I can "see" my access point: >,---- >| wlan0 Scan completed : >| Cell 01 - Address: 00:04:0E:1F:23:4C >| ESSID:"WLAN" >| Protocol:IEEE 802.11g >| Mode:Managed >| Frequency:2.437 GHz (Channel 6) >| Quality:0/100 Signal level:-86 dBm Noise >level:-256 dBm >| Encryption key:on >| Bit Rate:1 Mb/s >| Bit Rate:2 Mb/s >| Bit Rate:5.5 Mb/s >| Bit Rate:11 Mb/s >| Bit Rate:6 Mb/s >| Bit Rate:9 Mb/s >| Bit Rate:12 Mb/s >| Bit Rate:18 Mb/s >| Bit Rate:24 Mb/s >| Bit Rate:36 Mb/s >| Bit Rate:48 Mb/s >| Bit Rate:54 Mb/s >| Extra:bcn_int=3D200 >| Extra:atim=3D2 >`---- >So what do I have to do now? >As far as I understand, I have to set the ESSID on the wlan card to >"WLAN" (which does not work) and then it's supposed to work. >Or am I wrong? Yes, it should be 'WLAN' Now, there are 2 things to notice: - he Signal level of -86 dbm is very poor, but maybe this is only a bad =20 sample - the access point is set to "encryption key: on" Are you sure of your key? > >-- >Ciao, Sebastian J-L |
From: Sebastian K. <se...@to...> - 2004-10-26 18:43:21
|
Hi Jean-Luc! I got it! The problem was that the key mode defaults to "restricted" while on my AP it is "open". After changing that, it worked. Finally :-) -- Ciao, Sebastian |