Rick Dobbs wrote: > You're right and this is fine for home environments.
its actually designed for enterprise environments. > But setting this up in a hotspot environment just isn't feasible. > Better to have different SSID's. See below. > I've handled too many tech support calls in multiple AP environments > with customers who complain about Windows trying to switch off between > AP's. You can't control which driver the customer is using. Not everybody uses Windows Wireless Configuration. (if they did, your problems would be less severe.) > Like you said, the DHCP request doesn't take long because it keeps the > same IP, but there can be an annoyance if you're downloading something > and that stupid bubble keeps popping up. Rick. I was doing hotspots before other people had heard of 802.11 or had cards in their hands. In particular, in airports. I always set the ESSID to a common name when the APs are connected to the same ethernet backend. Thats the way 802.11 was *designed*, after all. Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SOCALWUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SOCALWUG SOCALWUG website: http://www.socalwug.org -~----------~----~----~----~------~----~------~--~---
