Hi all, hope the BBQ went well, sorry I couldn't come (I was picking up my Brother-In-Law at Logan...sigh, one day I'll get to a meeting). I've got a netgear wifi card that works great in Mandrake Linux, with the exception of wep (I know, it's cracked). In doing some research on the card and the kernel module that loads wvlan_cs, I have found out that this module has been replaced (by and large) by orinoco_cs, which I understand to be more functional (i.e. maybe I can get wep working?). I tried modprobe -r wvlan_cs and modprobe orinoco_cs but it won't bind to my pcmcia card. So I figured, "Well, maybe my card is just one that can't use the newer driver..." WRONG! Just to see what it was like, I download Knoppix, burned it onto a cd, and booted it up. Guess what driver loaded? orinoco_cs!! And it worked well too. Well, since Knoppix is a cd-boot, run in memory distro; I'm not changing to it anytime soon. So I'm going to use this opportunity to learn something new. How can I bind the orinoco driver to my card? Wes -- This message may be digitally signed. For my public key, e-mail me a request.
Hi Wes, I discovered on my laptop that I had to insure that my wireless card was listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE 8.0, I believe the description below is distribution agnostic). Try this as root: # cardctl ident Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with an entry matching the manfid is present. In my case, there was no entry so I added one thus: card "Andy's Linksys Wireless" manfid 0x0274, 0x1613 bind "orinoco_cs" The card string seems to be arbitrary text. The manfid comes from "cardctl ident", and the bind is to a kernel module. I have hotplugging services running, so when I plug in my wireless adapter, it automagically loads the kernel module(s), starts the net, sets up routing, etc. Give it a try and let us know how it goes! Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
Andy, Worked like a charm. There was an entry with my manfid in /etc/pcmcia/config and the bound driver was wvlan_cs; I switched it to orinoco_cs and, taking the cheesy way of rebooting, the network came up with the orinoco driver! Now I need to see if I can get wep working! Thanks, I love learning new tricks. Wes On Thu, 2002-08-22 at 23:20, Andy Stewart wrote:
Hi Wes,
I discovered on my laptop that I had to insure that my wireless card was listed in /etc/pcmcia/config or things didn't work. (Although I use SuSE 8.0, I believe the description below is distribution agnostic).
Try this as root:
# cardctl ident
Note the "manfid" line. Next, check /etc/pcmcia/config and see if a card with an entry matching the manfid is present. In my case, there was no entry so I added one thus:
card "Andy's Linksys Wireless" manfid 0x0274, 0x1613 bind "orinoco_cs"
The card string seems to be arbitrary text. The manfid comes from "cardctl ident", and the bind is to a kernel module. I have hotplugging services running, so when I plug in my wireless adapter, it automagically loads the kernel module(s), starts the net, sets up routing, etc.
Give it a try and let us know how it goes!
Later,
Andy
-- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- This message may be digitally signed. For my public key, e-mail me a request.
Hi Wes, I discovered that I could only get 64 and 128 bit WEP working. Although my hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making it work. I also discovered that typing a pass phrase on a Windows based appliance would yield a different hex string than typing the same pass phrase on Linux. So, what I did was to pick my pass phrase, type it into one machine, and then copy the resulting hex code directly to the other machine ("machine" meaning access point, Linux wireless software, etc). On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm not sure whether that is a SuSE specific file. The syntax of the important line is: WIRELESS_KEY="s:xxxxx" where the "s:" indicates a string (the pass phrase) and the xxxx are the characters. For 64 bit encryption, you need 5 characters, while with 128 bit encryption, you need 13 characters. Have fun! Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
Andy, I just typed the pass-phrase into my router's config utility; since it only does up to 128-bit, I don't have to worry about 256! So I got the key and put that in /etc/network-scripts/eth1-config (after testing it by putting it in iwconfig) and it works. I didn't want to send a plain-text passphrase! But it WORKS! Wes On Fri, 2002-08-23 at 07:58, Andy Stewart wrote:
Hi Wes,
I discovered that I could only get 64 and 128 bit WEP working. Although my hardware allegedly supports up to 256 bit WEP, I was unsuccessful in making it work.
I also discovered that typing a pass phrase on a Windows based appliance would yield a different hex string than typing the same pass phrase on Linux. So, what I did was to pick my pass phrase, type it into one machine, and then copy the resulting hex code directly to the other machine ("machine" meaning access point, Linux wireless software, etc).
On my system, the hex string is coded in /etc/sysconfig/network/wireless. I'm not sure whether that is a SuSE specific file. The syntax of the important line is:
WIRELESS_KEY="s:xxxxx"
where the "s:" indicates a string (the pass phrase) and the xxxx are the characters. For 64 bit encryption, you need 5 characters, while with 128 bit encryption, you need 13 characters.
Have fun!
Andy
-- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- This message may be digitally signed. For my public key, e-mail me a request.
participants (2)
-
Andy Stewart -
Wesley Allen