Date: Wed, 13 Dec 2000 08:43:47 -0000 (GMT) From: Duncan Barclay <dmlb@dmlb.org> To: Greg Lehey <grog@lemis.com> Cc: FreeBSD mobile Mailing List <freebsd-mobile@FreeBSD.org> Subject: Re: ray driver, Pro cards, and Windows Message-ID: <XFMail.001213084347.dmlb@computer.my.domain> In-Reply-To: <20001213122156.C80134@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi On 13-Dec-00 Greg Lehey wrote: > This looks like an area where we should probably encourage cooperation > amongst the BSDs. Thoughts? I agree, especially in the 802.11 additions to the ethernet layer from NetBSD (I think). Duncan > Greg > > ----- Forwarded message from Atsushi Onoe <onoe@sm.sony.co.jp> ----- > >> 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 > --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@dmlb.org | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001213084347.dmlb>