On Wed, January 10, 2007 2:24 pm, Carl Lowenstein wrote: > On 1/10/07, Carl Lowenstein <[EMAIL PROTECTED]> wrote: >> >> Are you sure you are using the same WEP code for both ends of the path? >> >> Some brands of equipment will let you use a passphrase to set up >> 128-bit WEP, others require the full frontal hexadecimal code word. >> Some devices will do the translation from passphrase to hex. Some >> won't. Some software requires the hexadecimal password to be preceded >> by 0x when you type it in, some requires some other character, some >> wants none. Its sort of a mess. > > p.s. There is a lot of fine-print reading involved in this. More than > there should be. >
I already have more experience with this than I want. The d-link router requires a leading 0x. The Fedora GUI set-up interface requires it not to be there. Because I have a laptop working with wireless, I have ample opportunity to scope out what works. However, the modules are different. orinoco_pci for the Myth machine that is not accepting WEP, atheros for the laptop. The initialization for the laptop (atheros) has a command: iwpriv ath0 authmode 2 orinoco_pci barfs at this. AFAICT, iwpriv is a generic command for passing custom switches to the wireless modules. It is possible, I think, that there is a secret sauce for introducing the WEP idea to orinoco_pci, but that I don't have it yet. I plan to do some aggressive googling, but if anyone out there knows a way to do this, or an alternative security system (I understand WEP is pretty simplistic, anyway), I'm very open minded. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
