From owner-freebsd-mobile Fri Oct 13 10:40:18 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 481BC37B673 for ; Fri, 13 Oct 2000 10:40:13 -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 KAA63533; Fri, 13 Oct 2000 10:35:06 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id KAA98351; Fri, 13 Oct 2000 10:35:04 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200010131735.KAA98351@whistle.com> Subject: Re: interoperability In-Reply-To: <20001013095916.A28198@Odin.AC.HMC.Edu> from Brooks Davis at "Oct 13, 2000 09:59:16 am" To: Brooks Davis Date: Fri, 13 Oct 2000 10:35:04 -0700 (PDT) Cc: Doug Ambrisko , 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 Brooks Davis writes: | On Fri, Oct 13, 2000 at 09:18:06AM -0700, Doug Ambrisko wrote: | > Brooks Davis writes: | > | So far, I haven't been able to get an Aironet card to connect to an | > | access point running with all the security options enabled even with | > | the encryption patches. I'm not convinced that it should work with | > | them since they are missing the ability to set the transmit key which | > | is required for things to work. Without that functionality, they aren't | > | going to work on FreeBSD on a network my company security officer will | > | let me deploy. | > | > Huh? How is the "transmit key" different from the WEP key???? | > ancontrol -i iface [-v 0|1|2|3|4|5|6|7] -k key (set key) | > Note the even number are permanent and the odd are | > temporary. I let you set four keys. The permanent | > key are permanent until you re-write them. | | You can set any of the eight WEP keys, but you must also select the one | you will actually use as the transmit key. See the -T option to | wicontrol. This is something you can do with the windows key manager. 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'll do some more debugging today. I'll try and figure out exactly | which AP options are breaking things. That would be great. I have been playing a little with Windows trying to get it to work with an access point with WEP on and even it isn't working. If you could give me any hints on a working setup then it might be easier getting the FreeBSD part working. Thanks, Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message