From owner-freebsd-mobile Fri Oct 20 11:21:36 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from cisco.com (flipper.cisco.com [171.69.25.141]) by hub.freebsd.org (Postfix) with ESMTP id B78F737B479 for ; Fri, 20 Oct 2000 11:21:34 -0700 (PDT) Received: from kitab.cisco.com (kitab.cisco.com [171.69.187.233]) by cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id LAA22123; Fri, 20 Oct 2000 11:20:20 -0700 (PDT) Received: (from raj@localhost) by kitab.cisco.com (8.11.0/8.9.2) id e9KIKDE04245; Fri, 20 Oct 2000 11:20:13 -0700 (PDT) (envelope-from raj) From: Richard Johnson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 20 Oct 2000 11:20:12 -0700 (PDT) To: Doug Ambrisko Cc: Brooks Davis , Bob Ney , freebsd-mobile@FreeBSD.ORG Subject: Re: interoperability In-Reply-To: <200010131735.KAA98351@whistle.com> References: <20001013095916.A28198@Odin.AC.HMC.Edu> <200010131735.KAA98351@whistle.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14832.35868.965247.753978@kitab.cisco.com> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Ambrisko writes: > Missed that. Last time I looked at wicontrol it didn't deal with > multiple keys. I think I figured out what that means in term of programming > the card. There is a note in the manual says "The address {1,0,0,0,0,0} > is used to denote the default key". I currently write that whenever > a key is stored. This would imply that you could switch the default > key by changing the key in a slot. It's a kludge for now but it might > be something to experiment with. I wonder how I update this bit of the > key entry without clobbering the key. Maybe I can write a short record > that only has that info. > > Maybe the guy that works at Cisco and has access to the engineers can > answer this. I'm trying to get an answer from our engineers on this issue. In the meantime, I'm constantly getting "an0: device timeout". It works perfectly for a number of hours and then suddenly stops and gets the "device timeout" message. Then, after a while of pinging the local gateway with over 2-3 seconds(!) RTT, it suddenly settles back down and works fine for a while. Anyone else seeing this? /raj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message