Re: Please make sure that you do not run your WLAN in ad hoc mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I honestly think that there is something more than that. I have seen
dozens of instances of "IETF64" as an ad hoc network. (I see 6 sitting here in the plenary.) Unless there is someone with a perverse sense of humor spoofing me, I suspect that people are trying to join to the ietf64 network and getting it wrong, both in captialization, and in
configuration. (Oddly, I have yet to see "ietf64" as an ad hoc network.)

Of course, when the network availability is poor, mis-configuration doesn't stand out like it does
when everyone else in on the network except you.

Regards
Marshall Eubanks

On Nov 10, 2005, at 6:22 PM, Joel Jaeggli wrote:

On Thu, 10 Nov 2005, John Loughney wrote:

Do you have a sense if it is Win 2000 or if it is related to any specific wlan driver software? I'd think a basic list of cards / sw that often misbehave would be a good thing. That way, when we see a few adhoc devices in a meeting, the chairs could more specifically tell people running OS X / card Y to check their devices.
The survey we did is about two years old now, but at the time a  
fair number of the win2k drivers would produce this behavior.  
Basically to much default auto-configuration. having the wireless  
card be mananged by windows (winxp) went a long way towards solving  
this issue for windows machines. It is still possible to hose  
yourself if you try.
It think it would be a fairly serious mistake to add to the  
workload of the working-group chairs by making them  front-line  
tech support for the wireless network. The current exhortation  
towards checking for your laptop being in adhoc mode is well  
meaning, but a lot like throwing salt over the shoulder. If we want  
to characterize certain users or applications as mission critical  
providing additional wired ports in meeting rooms to support them  
seems reasonable. Including large numbers of wired ports seems like  
madness however.
John

--
---------------------------------------------------------------------- ---- Joel Jaeggli Unix Consulting joelja@xxxxxxxxxxxxxxxxxxxx GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]