|
← Revision 1 as of 2002-03-02 16:49:18 →
Size: 1823
Comment:
|
Size: 1963
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| I originally posted this to AccessPointSig, but I'm reproducing it here because there's no simple, default WikiWord about a PTP node. | I originally posted this to AccessPointSig, but I'm putting it here because there's no simple, default WikiWord about a PTP node. |
| Line 19: | Line 19: |
|
* pro: facilitates roaming * pro: is simple * con: causes problems with dense node population |
* pro: facilitates roaming * pro: is simple * con: causes problems with dense node population |
| Line 24: | Line 24: |
|
* 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) |
* 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) |
| Line 29: | Line 29: |
|
* 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) |
* 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) |
| Line 33: | Line 33: |
| See NodeStandardization to provide further input on this topic." | See NodeStandards to provide further input on this topic." |
| Line 38: | Line 38: |
| [CategoryUnknown] |
[CategoryDocumentation] HyipInvestment EgoldEcurrency GetRich MakeMoney MlmAndDownlines ForexTrading WorkFromHome HomeBusiness OnlineInvesting SafeInvestment |
I originally posted this to AccessPointSig, but I'm putting it here because there's no simple, default WikiWord about a PTP node.
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 NodeStandards to provide further input on this topic."
[CategoryDocumentation] HyipInvestment EgoldEcurrency GetRich MakeMoney MlmAndDownlines ForexTrading WorkFromHome HomeBusiness OnlineInvesting SafeInvestment