The problem stems (I hope) from people not knowing that they
have their PC in Ad-Hoc mode when they specify that they want
to connect to network "ietf64". So the answer should be that
"ad hoc mode with SSID = ietf<XX>".
However, people wanting to have a private ad hoc network ought
to look at the frequencies being used by local base-stations
so that their signals do not interfere with people using the
"infrastructure" mode.
--
Eric
--> -----Original Message-----
--> From: ietf-bounces(_at_)ietf(_dot_)org
[mailto:ietf-bounces(_at_)ietf(_dot_)org]
--> On Behalf Of Spencer Dawkins
--> Sent: Thursday, November 10, 2005 5:13 PM
--> To: ietf(_at_)ietf(_dot_)org
--> Subject: Re: Please make sure that you do not run your WLAN
--> in ad hoc mode
-->
--> Just to be clear - is the problem "ad hoc mode" or "ad hoc
--> mode with SSID ietf"?
-->
--> The last time we were in Minneapolis, Dean Willis noticed
--> that the wireless projector controls in the conference
--> rooms used 802.11b ad hoc ... in an increasingly IP-deviced
--> world, if the problem is "ad hoc mode", we are going to die
--> at an increasing rate over time.
-->
--> Spencer
-->
-->
--> _______________________________________________
--> Ietf mailing list
--> Ietf(_at_)ietf(_dot_)org
--> https://www1.ietf.org/mailman/listinfo/ietf
-->
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf