Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Wep
keys are crackable... you could possibly do what hotels do and require people to
pay for connections by routing all unauthenticated connections to the "login or
sign up" SSL website. And you could probably devise some sort of safe
IPSEC/VPN to open internet connection client to allow a customer to connect all
around the city and not be too hassled.
I
don't think it'd be feasible to use wep keys at all in this situation. To
make this work, you need to have *any* user working in seconds, without
involving waitresses at restaurants and the like. The only good way I've
seen this done was through an http redirection system, so that no matter what
page they come up to, unless they've got a recognised
account/connection/mac/pppoe, they come up to a connection page, or a page that
tells them who to call to sign up.
After
you've got a usable (to lamens) signup system and the initial investment out of
the way, you find an ISP to provide you a certain Quality Of Service account for
bandwidth. Frame relay connections are good ideas for this scenario,
because you can spike somewhat without requiring purchase of a larger
pipe. I'm not a big fan of FR, but it seems the economical choice
here.
Then
you can ensure that a certain amount of bandwidth is available, and
increase/decrease its size based on the number of accounts you
have.
*THEN*, you get to find a way to deal with abusers and
hackers.
This
will be the largest overhead, next to the bandwidth. If you use some sort
of pppoe or ipsec tunnel and appropriate termination hardware, I think you could
actually cap or smartly limit abusers. (people using too much
bandwidth).
Sounds
mostly feasible in the long run, but choosing the appropriate connection class
will be the fun part.
I'd
suggest that an 11k$ initial investment wouldn't be enough to procure the proper
routing hardware to do this on a large scale, but would probably be enough to
fullfill all requirements for downtown columbia.
Lastly, you'd need a lot of access to a lot of building
roofs that people typically don't get access to, but if you can put a few
antennas on top of Tiger Hotel, let me know. I'll *help*.
:D
n8
I personally think that a very low cost subscription to the wifi network by
the city would be best... so say if a downtown restaurant wants to offer wifi,
it will have to buy a regularly updated wep key every month from the
city. The same would be done to whoever wants in on the thing... the
city would basically become it's own isp, but could charge less than the
commercial isps (so maybe that's a bad idea due to monopoly)... or maybe a tax
of some sort?
- Jeff Thomann -
They always say that time changes things, but you
actually have to change them yourself.
-Andy
Warhol
>From: "jeff thomann"
>Reply-To: EMAIL:PROTECTED
>To: EMAIL:PROTECTED
>Subject: RE: [MLUG - DISCUSSION] wireless downtown Columbia
>Date: Tue, 11 Feb 2003 15:31:01 -0600
>MIME-Version: 1.0
>X-Originating-IP: [161.130.115.254]
>Received: from mc6-f10.law1.hotmail.com ([65.54.252.146]) by
mc6-s7.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 11 Feb
2003 13:31:34 -0800
>Received: from mlug.missouri.edu ([128.206.61.230]) by
mc6-f10.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 11 Feb
2003 13:31:33 -0800
>Received: from mlug.missouri.edu (EMAIL:PROTECTED [127.0.0.1])by
mlug.missouri.edu (8.12.3/8.12.3/Debian -4) with ESMTP id
h1BLV8Fm013401(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168
verify=FAIL);Tue, 11 Feb 2003 15:31:09 -0600
>Received: from localhost (EMAIL:PROTECTED)by mlug.missouri.edu
(8.12.3/8.12.3/Debian -4) with SMTP id h1BLV843013399;Tue, 11 Feb 2003
15:31:08 -0600
>Received: by mlug.missouri.edu (bulk_mailer v1.12); Tue, 11 Feb
2003 15:31:08 -0600
>Received: from mlug.missouri.edu (EMAIL:PROTECTED
[127.0.0.1])by mlug.missouri.edu (8.12.3/8.12.3/Debian -4) with ESMTP id
h1BLV8Fm013394(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168
verify=FAIL)for ; Tue, 11 Feb 2003 15:31:08
-0600
>Received: (from EMAIL:PROTECTED)by mlug.missouri.edu
(8.12.3/8.12.3/Debian -4) id h1BLV8VI013392for discussion-list; Tue, 11 Feb
2003 15:31:08 -0600
>Received: from hotmail.com (f109.law10.hotmail.com
[64.4.15.109])by mlug.missouri.edu (8.12.3/8.12.3/Debian -4) with ESMTP id
h1BLV7Fl013379for ; Tue, 11 Feb 2003 15:31:07
-0600
>Received: from mail pickup service by hotmail.com with
Microsoft SMTPSVC; Tue, 11 Feb 2003 13:31:01 -0800
>Received: from 161.130.115.254 by lw10fd.law10.hotmail.msn.com
with HTTP;Tue, 11 Feb 2003 21:31:01 GMT
>X-Message-Info: dHZMQeBBv44lPE7o4B5bAg==
>X-Authentication-Warning: mlug.missouri.edu: mail owned process
doing -bs
>X-Authentication-Warning: mlug.missouri.edu: majordom set
sender to EMAIL:PROTECTED using -f
>Message-ID:
>X-OriginalArrivalTime: 11 Feb 2003 21:31:01.0936 (UTC)
FILETIME=[E0046B00:01C2D214]
>Sender: EMAIL:PROTECTED
>Precedence: bulk
>Return-Path: EMAIL:PROTECTED
>
Add photos to your messages with MSN
8. Get 2 months FREE*.
Home | FAQ | Server | Presentations | Mailing Lists/Archives | Member Tools | Links | Sponsors | Contact