<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Chandler, AZ (about 25 min south of Scottsale).... in </title>
<link>http://www.dslreports.com/forum/r20430149</link>
<description></description>
<language>en</language>
<pubDate>Wed, 11 Nov 2009 11:22:36 EDT</pubDate>
<lastBuildDate>Wed, 11 Nov 2009 11:22:36 EDT</lastBuildDate>

<item>
<title>Re: Chandler, AZ (about 25 min south of Scottsale)....</title>
<link>http://www.dslreports.com/forum/remark,20431059</link>
<description><![CDATA[<A HREF="/useremail/u/353464"><b>dagg</b></A> : <div class="bquote"><small>said by  amigo_boy <A HREF="/useremail/u/1236971"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br><div class="bquote"><small>said by  TuPaK <A HREF="/useremail/u/661410"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>  :</small><br><br>was planning on a city-wide WiFi but it didn't go anywhere.<br> </div>I believe that was Kite Networks (owned by Mobile Pro), purchased by Gobility. <br> </div>close, it was NeoReach who was owned by MobilePro that started the tempe/chandler/gilbert network. MobilePro then bought Kite in order to run those wireless operations as Kite was already supporting the old SprintMMDS fixed wireless operations. I dont know what happened with gilbert but i know much of tempe was already built out before kite came into the picture.<br>Gobility came into the picute as a result of the spectacular failure of mesh networks to provide adequate service in both the tempe market and the farmers branch market. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20431059</guid>
<pubDate>Sun, 04 May 2008 17:57:08 EDT</pubDate>
</item>

<item>
<title>Re: Chandler, AZ (about 25 min south of Scottsale)....</title>
<link>http://www.dslreports.com/forum/remark,20430149</link>
<description><![CDATA[<A HREF="/useremail/u/1236971"><b>amigo_boy</b></A> : <div class="bquote"><small>said by  TuPaK <A HREF="/useremail/u/661410"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>was planning on a city-wide WiFi but it didn't go anywhere.<br> </div>I believe that was Kite Networks (owned by Mobile Pro), purchased by Gobility. Kite did Tempe's muni wifi. At about the time Gobility was closing the deal, Kite/Mobile Pro took the network off line. Gobility went ahead with the purchase. But, the last thing I read is that the network is operating in an unsupported state. Customers can still use it if (if an access point is still functioning). Nobody's being billed. If an access point goes down, nobody will fix it.<br><br>I used Kite about 18 months ago. I'm 90 yards from the nearest access point (which was removed three months ago when the city relocated the light pole two feet). I got a good signal using a directional panel antenna pointed out a window. I didn't have line of sight. It worked fine until the wind blew. I think my signal was based upon reflections. When the wind blew, the reflections became unstable due to trees swaying.<br><br>I've read wireless N is supposed to reduce reflection problems. Even capitalize on reflections. I wonder if these muni projects will use N.<br><br>Mark]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20430149</guid>
<pubDate>Sun, 04 May 2008 13:41:30 EDT</pubDate>
</item>

<item>
<title>Chandler, AZ (about 25 min south of Scottsale)....</title>
<link>http://www.dslreports.com/forum/remark,20430037</link>
<description><![CDATA[<A HREF="/useremail/u/661410"><b>TuPaK</b></A> : was planning on a city-wide WiFi but it didn't go anywhere.<br><br>I remember reading it in their local paper a few years back and they were serious about having it ready by late 2007.<br><br>*yawn*]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20430037</guid>
<pubDate>Sun, 04 May 2008 13:05:10 EDT</pubDate>
</item>

</channel>
</rss>
