From owner-freebsd-mobile Wed Feb 7 14:38:37 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 662C637B6BE for ; Wed, 7 Feb 2001 14:38:20 -0800 (PST) Received: from pir by moek.pir.net with local (Exim) id 14QdEB-0002jM-00 for mobile@freebsd.org; Wed, 07 Feb 2001 17:38:19 -0500 Date: Wed, 7 Feb 2001 17:38:18 -0500 From: Peter Radcliffe To: mobile@freebsd.org Subject: Re: FreeBSD - windows wavelan interop Message-ID: <20010207173818.G12123@pir.net> Reply-To: mobile@freebsd.org Mail-Followup-To: mobile@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from morganw@chemikals.org on Wed, Feb 07, 2001 at 05:33:28PM -0500 X-fish: < Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wesley Morgan probably said: > I just added a pair of wavelan cards to my network and found them quite > easy to use with freebsd out of the box. However, interoperability with > one in windows is nonexistant. the most recent windows drivers use a different ad-hoc mode. Downgrade to the old drivers if you want this to work right now. > No settings seems to allow them to communicate. I have seen several > posts referring to changing the ad-hoc mode to BSS, but this only > seems to disable the cards completely (all led's turn off). BSS mode is for use with a base station, liek an Apple Airport which is what I use. If you don't have a base station it won't work. > And why does the encryption in windows always seem to jump > back to alphanumeric keys even when I am using (and originally input) > hexadecimal keys. because thats the way the windows driver stuff was written. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message