I was wondering if someone would respond that way! ;-) We did this a while ago before corporate Starbucks decided to roll out their "approved" method. I think it was over a year ago that we put it in.
We use the Apple Airport. We didn't use any antennae beyond the antenna inside the Airport. We did this for no fee and actually purchased the Airport ourselves. They were our prototype for the Ashland Unwired Program. See http://www.ashlandunwired.com. The problem is that Starbucks insisted on putting the Airport in the store room, far from the customers and behind literally hundreds of cans, coffee urns, etc. And seriously, there is a noticeable degradation in signal quality when humans are in the way also. I would imagine that this Starbucks will upgrade to the corporate design at some point. I guess it will no longer be free then, either. Sigh. ;-) Priscilla At 01:31 PM 1/4/02, Patrick Ramsey wrote: >really? we did a roll out to starbucks nationwide through mobilestar >using ap340's and some nokia and 2621 routers. We never saw these >issues. Was this a private contract you did with them? And where did you >place the antenneas? > > > >Patrick Ramsey >Sr. Network Engineer >WellStar Health Systems >770.956.6338 > > >>> "Priscilla Oppenheimer" 01/04/02 01:09PM >>> >On a slightly more serious note, I installed 802.11 at our local Starbucks >and the signal quality if pretty bad. We finally realized that it was being >affected by all the jugs of coffee and other liquids and by the "big bags >of mostly water" (humans). (Some StarTrek creature referred to humans that >way.) > >Of more interest, I discovered that it was mostly DHCP that had a problem. >DHCP doesn't seem to be too persistent. Of course, it runs on UDP, so that >makes sense. Starbucks still refuses to move their access point closer to >where customers sit. So I boot my computer while standing near the closet >where I know the access point is, get my DHCP address, and then go sit >down. SMTP and HTTP do fine despite lost packets. They are TCP based and >are much more persistent. They are somewhat slow but at least they work. > >Priscilla > > >At 10:07 PM 1/3/02, Ken Diliberto wrote: > >Priscilla, > > > >Didn't you see where it says you're suppose to eat the chips first and use > >the *empty* can? > > > >I don't think you considered what would happen to the signal when > >moisture/mold/mildew set in. You'd have a soggy pile of "living" stuff, > >which would probably really mess up the signal properties. > > > >Is it normal to think this way??? ;-) > > > >Ken > > > > >>> "Priscilla Oppenheimer" 01/03/02 07:59PM >>> > >I would imagine it has to be the can from the wavy Pringles chips for this > >to work. The vectors representing the magnetic intensity measured in > >amps/meter and the resulting total electric current calculated for a > >specific distance (the closed interval of the integration) can be affected > >by many factors in a real-world environment, including the amount of bits > >left over by the consumer of the chips. Also, Pringles can result in > >problems due to the antenna gain around the consumer's hips especially when > >direct sequenced spread spectrum causes the gain to also affect the middle. > > > >Just kidding! ;-) > > > >Priscilla > > > > > >At 04:43 PM 1/3/02, Jarmoc, Jeff wrote: > > >There's also the good ol' 802.11b pringles can hack. I haven't tried it, > > >and it's obviously not something you'd want to implement in a business > > >environment, but I've thought about playing with it as a home toy. > > > > > >http://verma.sfsu.edu/users/wireless/pringles.php > > > > > >Jeff Jarmoc - CCSA, CCNA, MCSE > > >Network Analyst - Grubb & Ellis > > >[EMAIL PROTECTED] > > > > >[snip] >________________________ > >Priscilla Oppenheimer >http://www.priscilla.com ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=30966&t=30822 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
