[TriLUG] OT: solar wireless mesh router

[Ben Pitzer]

You're serious?  A T1?  Playa, please.  1.5Mbps of shared bandwidth is a
joke.  Even with TWC on a bad day you still get more than that, and you
don't have to worry about the fools in your HOA.  No, this has to be DS3 or
better <http://en.wikipedia.org/wiki/List_of_device_bandwidths> to serve any
more than 4-5 houses.  And then you'd be responsible for collecting money
from everybody, much the same way you did with paying the electric bill,
water, or phone bill back in college.  Remember that?  No thank you.  Oh,
and you'd also be responsible for security, and making sure that
wardrivers<http://en.wikipedia.org/wiki/War_driving>weren't out there
using your wireless to surf kiddie pr0n, and the
neighbors' kids weren't trying to hack Facebook to change some other kid's
profile into a solicitation for gay swingers.

I'm actually trying to put some humor into this, but the bottom line is that
I doubt you'll get the buy-in from your neighbors without a significantly
fat pipe which will probably put the price tag out of reach, and you REALLY
don't want the support and maintenance aggrevation.

Regards,
Ben Pitzer


On 6/12/07, Tim Jowers <timjowers at gmail.com> wrote:
>
> Kevin,
>
>    I'm with you. I have a good rooftop (HOA withstanding) with excellent
> coverage of about 100 homes. I live off of Lake Pine in Kildaire Farm.
> Maybe
> we can find enough people to justify a T1 somewhere and roll this out
> legally. I guess the legal problems are what killed boingo although I
> never
> followed them closely. What prototocol? 802.11n?
>
>   On a Linux-specific note, has anyone setup Linux to share two networks?
> I
> understand Linux supports failover to another network card but what I
> wanted
> was load-balanced packets and for Linux to repond on the incoming network.
> I
> tried this with Apache but could not get it to respond on the network from
> which the packet came. It always responded on one network and - of course-
> this is not what I wanted. More exactly:
>
>        /----NIC1------- <-- please send/recv only on this network ---->
> CPU
>        \----NIC2------- <-- please send/recv only on this network ---->
>
>     I guess we'd setup squid and allow any person who helps pay for the T1
> and equipment to use the network. And encourage others to add their
> POP/router to extend the network.
>
>     I am toying with writing a distributed peer-based webserver module.
> Sorta like bittorrent for the web. I've antipatented this idea on
> shouldexist.org several years back and think it would be a great way to
> ensure Internet control remains with the actual users rather than
> centralized computing which is inherently bad both technically and civilly
> IMO.
>
> Thanks,
> TimJowers
>
>
> On 6/11/07, Kevin Otte <nivex at nivex.net> wrote:
> >
> > http://www.ehomeupgrade.com/entry/3950/meraki_introduces_first
> > Thanks to Dave Pcolar for the link.
> >
> > Perhaps something like this can be a building block in a system that
> > will give TWC, et al, a run for their money.
> >
> > -- Kevin
> > --
> > TriLUG mailing list        :
> http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ  : http://trilug.org/faq/
> > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> >
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>