Thread: [Ndiswrapper-general] When does a (windows-)driver work with my card?
Status: Beta
Brought to you by:
pgiri
From: George P. <gp...@gm...> - 2004-08-16 21:06:23
|
How do I know if a Windriver (bcmwl5.inf and bcmwl5.sys Files) works with my hardware? I use a WLAN-Card from LinkSys (WMP54G) with a Windows DELL-Driver from NDISwrapper-supproted-chipset-page. The WMP54 has one LED which is getting darker when I load the module (modprobe ndiswrapper) I can start a wlan0 device by using 'ifconfig wlan0 up' or 'ifup wlan0' Via iwconfig I can change several parameters of this device. Some others aren't changeable. For example I'd like to chian my card to my AP so I tried: 'iwconfig wlan0 mode managed' 'iwconfig wlan0 ap <MAC-AdressOFmyAP>' But this does not change the preset 'FF:FF:FF:FF:FF:FF'. I would't care but the bad thing is this device does not get any IP-adress from my access-point which is a LinkSys WRT54G. If I sign a IP-Adress by hand 'ifconfig wlan0 192.168.1.110' I can't ping my AP 'ping 192.168.1.1' -> 100% packet loss. Do I have a communication problem between my AP and my WLAN-Card or doesn't work the choosen driver? ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE -- NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler! GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl |
From: Geoff M. <gmi...@ac...> - 2004-08-16 21:18:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think "Managed" has to be capitalized as such when setting the mode. Also, I think you should try to set the access point with: iwconfig wlan0 essid SSID instead of with the MAC address of the AP. Where SSID is the SSID of your AP. --Geoff Mishkin <gmi...@bu...> On Monday 16 August 2004 05:04 pm, George Peters wrote: > How do I know if a Windriver (bcmwl5.inf and bcmwl5.sys Files) works with > my hardware? > > > I use a WLAN-Card from LinkSys (WMP54G) with a Windows DELL-Driver from > NDISwrapper-supproted-chipset-page. > The WMP54 has one LED which is getting darker when I load the module > (modprobe ndiswrapper) > > I can start a wlan0 device by using 'ifconfig wlan0 up' or 'ifup wlan0' > > Via iwconfig I can change several parameters of this device. > Some others aren't changeable. > For example I'd like to chian my card to my AP so I tried: > 'iwconfig wlan0 mode managed' > 'iwconfig wlan0 ap <MAC-AdressOFmyAP>' > But this does not change the preset 'FF:FF:FF:FF:FF:FF'. > > I would't care but the bad thing is this device does not get any IP-adress > from my access-point which is a LinkSys WRT54G. > If I sign a IP-Adress by hand 'ifconfig wlan0 192.168.1.110' I can't ping > my AP 'ping 192.168.1.1' -> 100% packet loss. > > Do I have a communication problem between my AP and my WLAN-Card or doesn't > work the choosen driver? > > > ---- > Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBISPOpH0X57UnVFoRAsoyAJ9ck8Bv5m19xIgc0/DPFckitjVT0gCeKn5N 0jdgmE12F6jskLgzWuwM4wI= =/ow0 -----END PGP SIGNATURE----- |
From: Geoff M. <gmi...@ac...> - 2004-08-16 22:55:46
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been setting the ESSID of my AP with the essid option to iwconfig the= =20 whole time I've been using ndiswrapper. In fact, it's Ad-Hoc mode that=20 doesn't work for me. I don't know what else to say about that except that= =20 I've never used the ap option and it's always worked. I have an IPW2200 in= =20 case that makes any difference. --Geoff Mishkin <gmi...@bu...> On Monday 16 August 2004 06:02 pm, you wrote: > > I think "Managed" has to be capitalized as such when setting the mode. > > Also, I think you should try to set the access point with: > > > > iwconfig wlan0 essid SSID > > > > instead of with the MAC address of the AP. Where SSID is the SSID of > > your AP. > > > > --Geoff Mishkin <gmi...@bu...> > > > > Ndiswrapper-general mailing list > > Ndi...@li... > > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > > Hi Geoff, > you're right the output of 'iwconfig' is 'Managed' and 'Ad-Hoc' but as far > as I know it makes no difference for the parameter if you specify them > capitalized or not. (It does not solve my problem so far :-( > > To set a SSID by 'iwconfig wlan0 essid SSID' is only possible in 'Ad-Hoc' > mode. As fasr as I know my APs are managed on default. I can't chanege it > cause the configuration menues of my AP does not show any options for thi= s. > > George (gpts at gmx.de) > > ---- > Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-= DE =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBITlGpH0X57UnVFoRAkMMAJ0eoPXDrCSBJryX+5Q3pHdSySbU7gCghKTS uU6wi/dsZc7e0NsbbKbG9us=3D =3DPsJr =2D----END PGP SIGNATURE----- |
From: George P. <gp...@gm...> - 2004-08-17 10:23:16
|
Geoff Mishkin wrote: > > I've been setting the ESSID of my AP with the essid option to iwconfig the > whole time I've been using ndiswrapper. In fact, it's Ad-Hoc mode that > doesn't work for me. I don't know what else to say about that except that > I've never used the ap option and it's always worked. I have an IPW2200 > in > case that makes any difference. > > --Geoff Mishkin <gmi...@bu...> Does this mean if I can't set the ESSID ant any time my driver does not work 100% ? George (gpts at gmx.de) ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE -- NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler! GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl |
From: George P. <gp...@gm...> - 2004-08-17 07:45:13
|
> I think "Managed" has to be capitalized as such when setting the mode. > Also, I think you should try to set the access point with: > > iwconfig wlan0 essid SSID > > instead of with the MAC address of the AP. Where SSID is the SSID of your > AP. > > --Geoff Mishkin <gmi...@bu...> > > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > Hi Geoff, you're right the output of 'iwconfig' is 'Managed' and 'Ad-Hoc' but as far as I know it makes no difference for the parameter if you specify them capitalized or not. (It does not solve my problem so far :-( (I followed the output of 'iwconfig --help') To set a SSID by 'iwconfig wlan0 essid SSID' is only possible in 'Ad-Hoc' mode. As fasr as I know my APs are managed on default. I can't chanege it cause the configuration menues of my AP does not show any options for this. George (gpts at gmx.de) ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE -- NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler! GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl -- NEU: WLAN-Router für 0,- EUR* - auch für DSL-Wechsler! GMX DSL = supergünstig & kabellos http://www.gmx.net/de/go/dsl |
From: Chris E. <ch...@ch...> - 2004-08-17 23:02:48
Attachments:
signature.asc
|
George Peters wrote: > To set a SSID by 'iwconfig wlan0 essid SSID' is only possible in 'Ad-Hoc' > mode. As fasr as I know my APs are managed on default. I can't chanege it > cause the configuration menues of my AP does not show any options for this. Huh? I use the following to connect to my AP: iwconfig wlan0 essid chrisenet mode managed key <WEP> Chris E. |
From: Gregor P. <gp...@gm...> - 2004-08-18 09:42:12
|
Chris E. schrieb: > George Peters wrote: > >> To set a SSID by 'iwconfig wlan0 essid SSID' is only possible in 'Ad-Hoc' >> mode. As fasr as I know my APs are managed on default. I can't chanege it >> cause the configuration menues of my AP does not show any options for >> this. > > > Huh? I use the following to connect to my AP: > > iwconfig wlan0 essid chrisenet mode managed key <WEP> > > Chris E. According to the FAQ http://ndiswrapper.sourceforge.net/faq.html (see `I can´t set ESSID!` at the nerly end of the list ) the ESSID isn`t shown in the output of iwconfig until a connection to the accesspoint is established. It makes no difference if I configure my WLAN-card step by step iwconfig wlan0 essid WiFi iwconfig wlan0 mode managed iwconfig wlan0 key 0123456789 open iwconfig wlan0 commit or the way you did with one command like iwconfig wlan0 essid WiFi mode managed key 0123456789 open commit (SSID and WEP-Key on the access point are the same as above) The result is the same no connection to my access point :-( George (gpts at gmx.de) ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE |
From: Laurens V. H. <lau...@ea...> - 2004-08-17 23:02:33
|
> Via iwconfig I can change several parameters of this device. > Some others aren't changeable. > For example I'd like to chian my card to my AP so I tried: > 'iwconfig wlan0 mode managed' > 'iwconfig wlan0 ap <MAC-AdressOFmyAP>' > But this does not change the preset 'FF:FF:FF:FF:FF:FF'. You can't change the AP MAC address in managed mode -- not even with my=20 prism54. You need to set the ESSID, keep scanning. Don't bother to set the= =20 channel in managed mode either. Keep toying with that until you figure out what works for you, it "works" w= hen=20 it has locked on/found your AP MAC address. > I would't care but the bad thing is this device does not get any IP-adress > from my access-point which is a LinkSys WRT54G. > If I sign a IP-Adress by hand 'ifconfig wlan0 192.168.1.110' I can't ping > my AP 'ping 192.168.1.1' -> 100% packet loss. Never set your own IP when the DHCP server should have given it to you. It= =20 means there's something else wrong. |
From: Gregor P. <gp...@gm...> - 2004-08-18 09:57:07
|
Laurens Van Houtven schrieb: >>Via iwconfig I can change several parameters of this device. >>Some others aren't changeable. >>For example I'd like to chian my card to my AP so I tried: >> 'iwconfig wlan0 mode managed' >> 'iwconfig wlan0 ap <MAC-AdressOFmyAP>' >>But this does not change the preset 'FF:FF:FF:FF:FF:FF'. > > > You can't change the AP MAC address in managed mode -- not even with my > prism54. You need to set the ESSID, keep scanning. Don't bother to set the > channel in managed mode either. > Keep toying with that until you figure out what works for you, it "works" when > it has locked on/found your AP MAC address. How to scan? The command `iwlist wlan0 scan` returns `wlan0 No scan results` as loang as I am in managed mode. If I change mode to `Ad-Hoc` (I am not shure in which mode my acess point is on default) `iwlist wlan0 scan` returns: wlan0 Scan complete : Cell 01 - Adress: 5A:22:31:59:32:9D ESSID: "WiFi" Protocol: IEEE 802.11b Mode: Ad-Hoc Frequency:2.462GHz (channel 11) Quality:0 Signal level:0 Noise level:0 Encryption key:on Bit Rate:1Mbit/s Bit Rate:2Mbit/s Bit Rate:5.5Mbit/s Bit Rate:11Mbit/s The funny thing is the WMP54G WLAN-card is a 802.11g device (which is also reported by iwconfig wlan0) and The Cell 01 - Adress is no MAC-Adress (which is OK I think) George ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE |
From: Gregor P. <gp...@gm...> - 2004-08-18 10:04:20
|
Laurens Van Houtven schrieb: >>I would't care but the bad thing is this device does not get any IP-adress >>from my access-point which is a LinkSys WRT54G. >>If I sign a IP-Adress by hand 'ifconfig wlan0 192.168.1.110' I can't ping >>my AP 'ping 192.168.1.1' -> 100% packet loss. > > > Never set your own IP when the DHCP server should have given it to you. It > means there's something else wrong. Yeah, but what? I think the main problem is that I can`t get a connection to my access point which is also the DCHP-server. Each time I do a `dhclient wlan0` the value `TX bytes` in the ooutput of `iFconfig wlan0` increases while `RX bytes` are zero all the time. That means for me my WMP54G-card is keeps on sending but gets no answer from my access point. Thst's is why I think the driver I use is OK but some configuration data isn`t set properly yet. George (gpts AT gmx DOT de) ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE |
From: Gregor P. <gp...@gm...> - 2004-08-18 12:37:36
|
Ooops! Can someone tell me why my postings become a new topic each time? George (gpts AT gmx DOT de) ---- Debian 2.4.24 *** WLAN-PCI: LinkSys WMP54G-DE *** AP: LinkSys WRT54G-DE |