From owner-freebsd-mobile Tue Dec 12 17:52:13 2000 From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 12 17:52:10 2000 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 8C4A437B400 for ; Tue, 12 Dec 2000 17:52:08 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 20A586AB6B; Wed, 13 Dec 2000 12:21:57 +1030 (CST) Date: Wed, 13 Dec 2000 12:21:57 +1030 From: Greg Lehey To: FreeBSD mobile Mailing List Subject: Re: ray driver, Pro cards, and Windows Message-ID: <20001213122156.C80134@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This looks like an area where we should probably encourage cooperation amongst the BSDs. Thoughts? Greg ----- Forwarded message from Atsushi Onoe ----- > Delivered-To: grog@lemis.com > Date: Tue, 12 Dec 2000 16:35:05 -0800 (PST) > To: thorpej@zembu.com > Cc: gillham@vaultron.com, current-users@netbsd.org > X-Mailer: Cue version 0.6 (001128-1119/onoe) > Precedence: list > Delivered-To: current-users@netbsd.org > >> We should move all of this stuff into ifconfig(8) -- having wiconfig(8), >> especially with its really ugly command "syntax", is not the best way >> to go. Most of this applies to all 802.11 devices. > > I fully agree. > > The problems are 1) what is the common and minimum required option, and > 2) how to specify it. > > There are some operation mode: > > mode what must be specified > -------------------------------------------- > infrastructure ESSID (may be null) > adhoc ESSID (may be null) > adhoc IBSS creator ESSID and channel (beacon period?) > old wavelan adhoc channel > > And there are combination of these mode, e.g. try infrastructure first, > then try adhoc and finally create IBSS by myself. The problem here is > that we cannot control these behavior but just we can select predefined > behavior by firmware. > > Lucent > infrastructure > infrastructure or IBSS, then create IBSS > old wavelan adhoc > > PRISM-II with Lucent like firmware > infrastructure > old wavelan adhoc > (I don't know IBSS is supported or not) > > PRISM-II with Aironet > infrastructure > IBSS, then create IBSS after specified timeout > > PRISM-I > (any mode can be implemented by the driver) > > Ray > infrastructure > IBSS > > My straightforward proposal to specify the mode via ifconfig is: > > media mediaopt > ----------------------------------------------------------- > auto try infrastructure or IBSS, > then create IBSS only if ESSID is specified. > auto infrastructure infrastructure > auto adhoc try IBSS then create IBSS only if ... > auto adhoc,flag0 old wavelan adhoc > DS11,DS5,DS2,DS1 same combination as above > > To specify IBSS create channel, new option for ifconfig might be: > > ibsschan chan > > Ugh. The number of options for ifconfig is increasing ... > Any other idea? > > Atsushi ----- End forwarded message ----- -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message