On Thu, Jan 03, 2002 at 06:08:26PM +1100, Martijn van Oosterhout wrote:
> On Thu, Jan 03, 2002 at 10:07:21AM +1100, David Gibson wrote:
> > Well, matching frequencies and essids is critical (or should be), but
> > the cards do have a tendency to autoselect frequencies and essid to
> > find other cards. If you explicitly give to cards different essids
> > they should not communicate - that's the whole point of essid. Are
> > you sure they really have a different essid, or has one of them
> > changed essid behind your back? Note that iwconfig will give
> > misleading results for essid (and other things) if the interface is
> > down.
>
> I'm serious. I have set in my pcmcia/wireless.opts (iirc) file I set ESSID
> to "wireless" yet without changing any settings I can see and be seen by
> machines with the ESSID "rainmaker" (a powerbook, win98 laptop and a
> 486

Ok, but do the machines still show different essids after they've
talked?

> linux one). iwconfig shows the essid as "wireless". In fact, the 486 I don't
> think sets it's ESSID at all (can't find a wireless-tools compiled for
> slink).

...and if you're not setting it, it will be "auto" and look for the
essid of other nearby machines.

-- 
David Gibson			| For every complex problem there is a
davidgibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.  -- H.L. Mencken
http://www.ozlabs.org/people/dgibson

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