Rick Dobbs wrote: > Okay, I'm just relating my experience. I've found it to be a certain > way and it's different than what your'e stating. > > Is this where I'm supposed to join in on the pissing contest and fire > off my accolades as to my wireless accomplishments and how long I've > been doing it? I'm not sure what the point of that was otherwise.
You claimed that running the same ESSID on the APs in one "hot spot" "isn't feasible". I countered, and anticipated any argument that I hadn't any "real world" experience. > > I don't think that thinking that anying in wireless, especially > 802.11x, is an absolute is a very good idea, the amount of variables > involved is astronomical. Yes, that may be "how it's designed" but my > car is designed to drive on highways, but I can also drive it in to a > lake, which, interestingly enough, a few people would prefer I do. Hopefully you're there to pull your boat out (or put it in). Otherwise, I can't imagine why you do so. Your car was designed to perform adequately in a number of driving situations, including those you probably don't often deal with, such as temp extremes that normally aren't experienced in southern California. (Thus the automotive proving grounds in Winsor Canada and Phoenix.) Some of the better-quality APs (and "Wi-Fi switches") can offer nearly transparent roaming, even with WPA enabled. > > --Rick > > On 3/2/06, *Richard* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > That makes sense, setting the ESSID to a common name... RF-wise a > field strength study would show placement based on common point > low signal... I am going to fiddle with that here at home - might > add a third to see what that will do, too. > > (Chewing on it...) > Richard > > On 3/2/06, *Jim Thompson* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > 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 > > > > -- > "Being a bit scattered tends to be a trait of highly imaginative > people." > The more you rattle the marbles around in your brain, the more > creative new connections you make, as it were > – connections that might be lost on those focusing intently on > just the red ones. > - Ed Vogel, University of Oregon, Department of Neuroscience > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
