On Tue, Jan 20, 2004 at 02:50:55PM -0800, Jeff Rizzo wrote:
> 
> Thanks for the reply, but a lot of this stuff is not only different
> between netbsd and openbsd, but between older and newer versions of
> netbsd.  :)
> 
> (for example, there's no "ibss-master" option in netbsd)

IBSS "masters" were a figment of somebody's imagination at Lucent
or Intersil. There is no such thing in 802.11.

> > On Tuesday 20 January 2004 03:31 pm, you wrote:
> > > It may be that I'm just blind, so please strike gently with the
> > > clue-by-four:
> > >
> > > I want to get these talking well in adhoc mode (because bridging doesn't
> > > seem to work right with a wi interface in host mode), but I'd also

I don't know host mode. Did you mean hostap mode? Bridging does work
with hostap mode. It cannot work with the other modes.

> > > like to get better control.  ISTR that with 'wiconfig', I could force
> > > an interface to transmit at a particular speed (1,2,5.5,11), but
> > > when I use the 'media' option of ifconfig, it seems to set the
> > > speed, but then ignore it and negotiate down to DS2 anyway.  (yes,
> > > I know that it's probably because of interference.  Can't I force it
> > > anyway?  Just to see how bad it really is?)
> > >
> > > for example, here's the ifconfig output of one side:
> > >
> > > wi0:
> > > flags=8b63<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICA
> > >ST> mtu 1500 nwid BlahBlah
> > >         powersave off
> > >         bssid 02:02:00:a7:0d:23 chan 11
> > >         address: 00:02:6f:03:fd:dc
> > >         media: IEEE802.11 DS11 adhoc (DS2 adhoc)
> > >         status: active
> > >         inet6 fe80::202:6fff:fe03:fddc%wi0 prefixlen 64 scopeid 0x4
> > >
> > > ... but wiconfig shows I still have the TX speed set to '0' (autoselect):

If you enable debugging (ifconfig wi0 debug) then you should see
messages

    wi_write_txrate: tx rate %d -> %d (%d)

where the %d's are filled in to tell which rate the interface is
changing to.

In general, `ifconfig wi0' cannot tell any single sensible media setting
(for example, DS2 adhoc, DS11 adhoc) because there are many stations,
each of which might have adapted to a different rate. This is one of the
reasons that someday I intend to make virtual interfaces (sta0, sta1,
...) for all peers/clients.

> > > Also, how do I control how the IBSS is set up?  For example, I can't seem
> > > to change what channel it uses unless I set *both* sides down, change
> > > the channel on one, then bring it up first.  (this could be a problem when
> > > my only access to the far end is via the interface I just shut down)

I know the problem you are talking about. I think that creating an IBSS
on channel X when there is already an IBSS with the same SSID on channel
Y is something that the Lucent & Prism firmwares do not want for us to do.

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933