Subject: Re: Persistent WEP keys
To: None <email@example.com>
From: Atsushi Onoe <firstname.lastname@example.org>
Date: 03/12/2001 07:56:45
> -current machine, I get these errors from the driver:
> an0: RID 0xff68 access failed
> an0: RID 0xff50 access failed
> an0: RID 0xff50 record length mismatch -- expected 138, got 8192
> an0: RID 0xff50 record length mismatch -- expected 138, got 255
> an0: RID 0xff68 record length mismatch -- expected 432, got 8192
> on a regular basis. They might be caused (this is just an uninformed
> guess) by the card trying the bogus temporary key now and then and
Sorry, this is a known bug for current driver. These RIDs are for
status and statistics, which sometimes time-out because of busy
firmware in transmitting and/or receieving. Since it is not fatal,
we can ignore these errors (0xff50 and 0xff68).
> > How about this?
> > ifconfig <if> nwkey <key> # enable WEP with temporary key <key>
> > ifconfig <if> nwkey persist # enable WEP with persistent key
> > ifconfig <if> -nwkey # disable WEP (also delete temp key)
> > Programming persistent key can be a different interface (anconfig).
> I wouldn't like that. I really like these things part of ifconfig and
> believe that's where they belong in a way. Maybe we should just use a
> different parameter for persistent and temporary keys, i.e. like
> ifconfig <if> nwkey <key> # enable WEP with temporary key <key>
> ifconfig <if> -nwkey # disable WEP (also delete temp key, but not persisten one if any)
> ifconfig <if> nwkey persist [key] # enable WEP with persistent key, with optional argument for setting it
It is ambiguous for the special key, such as 'media'.
ifconfig <if> nwkey persist[:<key>]
Note that current <key> definition is <string>, <hexstring>, or
Hmm.. it is already too complex..
I'd like to keep ifconfig as simple as possible, and move any other
complicated or driver/card dependent things to other config commands...