|
← Revision 5 as of 2002-03-02 16:52:12
Size: 4871
Comment:
|
← Revision 6 as of 2002-03-02 16:55:47 →
Size: 3302
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 33: | Line 33: |
| '''What are the minimums for calling your system a Public Access Point?''' | '''What are the minimums for calling your system a PublicAccessPoint?''' |
| Line 35: | Line 35: |
|
At the last MonthlyMeeting, a discussion took place on the definition of a node. Post-meeting, AdamShand posted a synopsis to the MailingList, which is quoted below: "A Node: * has an 802.11b access point * has a standard ESSID (see below) * broadcasts their ESSID * has a DHCP server * has an internet connection (may be via a connection to another node) * should run a captive/active portal (ie. NoCatAuth) * provides open access to the internet (no WEP, no overly restrictive firewall etc) We briefly touched on the ESSID standardization issue which has gone around the list a few times. We need to make a decision on what the standard we want to adopt is, I think it should be something recognizable as a URL so that people can put it into a browser and find out what it's all about. The options as I see it are: 1. www.personaltelco.net * pro: facilitates roaming * pro: is simple * con: causes problems with dense node population 2. www.personaltelco.net/node111 * pro: doesn't assume that discrete nodes have a common backbone * pro: allows node specific information in the ESSID * con: breaks layer 2 roaming unless ESSID set to "Any" (which can cause problems if there are other non-personaltelco nodes around) 3. use 1 for nodes which are part of the "wireless cloud" and 2 for nodes which are logically discrete from the rest of the network * pro: solves all the problems! * con: is more complicated * con: what happens as networks merge (eg. there's a NE "wireless could" and a SE "wireless cloud" that don't meet) See NodeStandardization to provide further input on this topic." |
Please see PublicAccessPoint or NodeStandardization for more information! |
AccessPointSig is RossOlson and JerrittCollord and Phil.
What is an Access Point?
An AccessPoint is a wireless Internet access service that serves a contiguous physical area from a single 802.11b wireless transceiver. Common hardware that provides this service includes any number of dedicated or multifunctional machines.
Like...?
A dedicated AccessPoint is traditionally just an Ethernet bridge-- that's actually in the IEEE spec. So the Apple Airport base station falls into this.
Linksys makes a product that is essentially their normal broadband router (not wireless) but with wireless ap functionality too-- this could be accomplished by bridging the wireless segment to the NAT'd wired segment, or having both interfaces be NAT'd. (Please edit if you know how it works.)
Can I build one?
Roll-your-own wireless access points are typically mulitfunctional and can take on many forms. See the LinuxAccessPoint page. Having cacheing proxies, enterprise authentication (e.g. NoCatAuth), etc. etc. is possible.
Traditionally there has been operation only in ad hoc mode but there are ways to get true Master/Infrastructure functionality out of a plain old card, depending on what hardware it is.
One involves semi-contraband firmware for the Prism II chipset. The other involves an expanded (though not yet complete) driver that uses a Host AP mode where software on the PC takes over some of the functionalities. This may actually be preferrable as more control may potentially be had at the MAC layer... this could be a more efficient way to manage QOS. (Please edit if anybody knows more.)
What is a Public Access Point?
A Public Access Point is a wireless internet service area that is available for public use, whether through membership in a co-op or through a standard public access login that is publicly available. Or, of course, if there is no login or control whatsoever.
What Hardware is used for constructing and operating an Access Point? What Software is used for an Access Point?
What are the minimums for calling your system a PublicAccessPoint?
Please see PublicAccessPoint or NodeStandardization for more information!
How do you keep your own network secure?
A feature with rolling-our-own e.g. LinuxAccessPoints is that the wireless network can be configured to be directly NAT'd out into the cloud, not just bridged to the wired network. Indeed if one is bridging, subnetting is probably a good idea. At any rate, run appropriate firewalling code on the gateway and/or anything you can see with the wireless clients. Maybe have MAC-addy-specific rules in your firewall so, say *I* can hit my Samba share for my MP3 stash but joe off the street can't (until he jacks my MAC addy).
How do you keep your publicly accessible network connection from becoming a liability because of people doing bad things through your network?
This is an issue of reverse IDS or ExtrusionDetection.
How do you present a 'Welcome' message?
This is an issue of the ActivePortal.