https://bugzilla.novell.com/show_bug.cgi?id=249709#c22 Joachim Gleissner <jg@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #22 from Joachim Gleissner <jg@novell.com> 2007-06-22 08:45:09 MST --- A value of 164 is invalid and won't work, or course. If YaST wrote it into that variable, it's a bug. But I don't see this on my system, I just configured an Orinoco pc-card on my Alpha4 system with a hashed 128 bit key, and the ifcfg-file looks fine. Are you using a hex, hashed, or ASCII key? The issue with the WEP key length is indeed confusing. The possible lengths of the WEP keys are 40 or 104 bit. WEP uses a 24 bit initialisation vector, if you add that, you get 64 or 128 bit, although the key itself is actually shorter. In marketing speech it's always 64 resp. 128 bit (of course), hence YaST uses these values. ifup supports both values in the ifcfg files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.