🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.internet.wireless
Article #375

Re: How many Google wireless access points for San Francisco?

#375
From: Jeff Liebermann
Date: Tue, 25 Oct 2005 16:59
51 lines
3463 bytes
On Tue, 25 Oct 2005 16:25:58 +0000 (UTC), spope33@speedymail.org
(Steve Pope) wrote:

>Jeff Liebermann  <jeffl@comix.santa-cruz.ca.us> wrote:
>
>>Not common?  5.7GHz is where all the wireless backhauls are currently
>>located.
>>  http://www.wbanc.com
>>If SF decided to go with 5.7GHz 802.11a clients, then I'm sure the
>>market would gladly support replaceing everything you own with the
>>latest and greatest.  (Evolution. Upgrade or die).  However,
>>relocating the backhauls to 22Ghz may be a bit of a challenge.
>
>You mean 24 GHz I think.

Y'er correct.  It's 24GHz.  Equipment is available but it's not cheap.
Dragonwave Air Pair 50:
|  http://www.tessco.com/products/displayProductInfo.do?sku=447702&eventPage=1
Only $22,000 each.

>>considering the mesh network rule of thumb of the week of no more than
>>3-4 hops from client to backhaul, and 100 access points per square
>>mile, that means 25-33 backhaul radios or wired connections per square
>>mile.  

>Despite their fumbling, Google definitely has the money to
>deploy that hardware this project requires.  Google's only limit
>is the laws of physics.

I've worked on wasted projects that proposed to solve technical issues
by throwing money at the problem.  I've also learned that if it
doesn't work on paper, it's not going to work in the field.  I find
the Philadelphia system entertaining to follow as technical details
and the entire topology seems to change every month.  I suspect that
the SF network will be much of the same as Google discovers RF
reality.  I'm sure the stockholders will eventually have something to
say when this project starts resembling a financial black hole.

I also find it entertaining to read about how such networks will be
used.  The common description is "untethered access" where users with
PDA's, laptops, and VoIP phones, roam around the city while browsing
the internet.  I learned a few lessons watching Metricom and found
that what most users *REALLY* want is a cheap full time connection in
the home.  My guess(tm) is that the bulk of the use will be from fixed
locations and solely as a cost reduction (or elimination) expedient.

-- 
Jeff Liebermann     jeffl@comix.santa-cruz.ca.us
150 Felker St #D    http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann     AE6KS    831-336-2558
Technical Details
Message-ID: <evnsl1tl9hh8vn6n9foam63fvn4t3tqp03@4ax.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newshub.sdsu.edu!logbridge.uoregon.edu!pln-w!spln!rex!extra.newsguy.com!newsp.newsguy.com!enews1
References: <0sdrl1tcp4bpoi1qonabuuk4bkujoapgpu@4ax.com> <MPG.1dc7aab8eec3a48298a8f8@corp.supernews.com> <a4OdnTAUJ-LBhMPeRVn-qQ@adelphia.com> <p2lsl155nduvnt553t28jdq67m3hhkdpr7@4ax.com> <djlmam$jgi$1@blue.rahul.net>

Show Full Headers
Complete Article Headers
X-Google-Thread: 104fd2,7866016d66b9e3e9
X-Google-Thread: fa874,7866016d66b9e3e9
X-Google-Attributes: gid104fd2,gidfa874,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newshub.sdsu.edu!logbridge.uoregon.edu!pln-w!spln!rex!extra.newsguy.com!newsp.newsguy.com!enews1
From: Jeff Liebermann <jeffl@comix.santa-cruz.ca.us>
Newsgroups: alt.internet.wireless,ba.internet
Subject: Re: How many Google wireless access points for San Francisco?
Date: Tue, 25 Oct 2005 09:59:35 -0700
Organization: http://extra.newsguy.com
Lines: 51
Message-ID: <evnsl1tl9hh8vn6n9foam63fvn4t3tqp03@4ax.com>
References: <0sdrl1tcp4bpoi1qonabuuk4bkujoapgpu@4ax.com> <MPG.1dc7aab8eec3a48298a8f8@corp.supernews.com> <a4OdnTAUJ-LBhMPeRVn-qQ@adelphia.com> <p2lsl155nduvnt553t28jdq67m3hhkdpr7@4ax.com> <djlmam$jgi$1@blue.rahul.net>
NNTP-Posting-Host: p-697.newsdawg.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Newsreader: Forte Agent 3.1/32.783