From owner-freebsd-mobile Fri Oct 20 12:36:52 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id CA55537B4C5 for ; Fri, 20 Oct 2000 12:36:50 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA77176; Fri, 20 Oct 2000 12:33:25 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id MAA11148; Fri, 20 Oct 2000 12:33:14 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010201933.MAA11148@whistle.com> Subject: Re: interoperability In-Reply-To: <14832.35868.965247.753978@kitab.cisco.com> from Richard Johnson at "Oct 20, 2000 11:20:12 am" To: Richard Johnson Date: Fri, 20 Oct 2000 12:33:14 -0700 (PDT) Cc: Doug Ambrisko , Brooks Davis , Bob Ney , freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard Johnson writes: | 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. Thanks, that would be great. | 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? I recall reports from someone that has seen it a fair amount on a PCI verison. I haven't seen it happen or really heard about it on PCMCIA and that's all I have. We also have a bunch of people using the PCMCIA driver at work. I may try to look at that some more. I use it for hours at a time without that issue. Maybe it's time to look at the driver with more detail. I've found a bunch of bugs in and fixed the ones I've stumbled across. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message