On Wed, Mar 21, 2001 at 09:26:46AM -0500, Douglas S. J. De Couto wrote:
>
> > I'm not sure but that may just be because the scripts are setting the
> > mode before setting the ESSID, so when the card enters ad-hoc mode
> > with no essid the driver complains.
>
> i have definitely found this to be the case with the newest frimware
> and driver; in my adhoc application i use something like;
>
> ``iwconfig wvlan0 essid foobar mode ad-hoc channel 5'' e.g.
>
> but it also works to do them separately, as in
>
> iwconfig wvlan0 essid foobar
> iwconfig wvlan0 mode ad-hoc
>
> it's weird because of course the card already has an ssid from the
> base-stations before switching modes.

I beleive the requirement for an essid in ibss ad-hoc mode is a
firmware bug, fixed in 6.16.

-- 
David Gibson			| Microsoft: Making the easy things hard
davidgibson.dropbear.id.au	| and the hard things buggy

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]