Size: 2164
Comment:
|
Size: 3030
Comment: added crowbar, fixed hr, respond to caleb, pimp adhoc (-kq)
|
Deletions are marked like this. | Additions are marked like this. |
Line 33: | Line 33: |
This is a good point: specific node information probably belongs in the node pages so that we don't duplicate effort/information. That said, the system probably should be for "auditors" to make sure the node page is accurate, and then log when they last checked on the node with a simple status like: functional, nonfunctional. That information could go on this page, and could be what we use to color the pins on the nodemap (if that every happens). Thoughts? -- CalebPhillips Sure, that sounds reasonable. I'm working on a more coherent system for all of this (see ["Adhocracy"]), but that works fine in the interim. I haven't been logging the last update date because the wiki does that for me, but if you feel that it would be specifically useful I'm not strongly opposed. - KeeganQuinn |
|
Line 36: | Line 40: |
* See NodeCrowBar. | |
Line 39: | Line 44: |
* See NodeSmallWhiteCube. | |
Line 47: | Line 53: |
Original author CalebPhillips Original conception TomHiggins --- |
Original author CalebPhillips [[BR]] Original conception TomHiggins [[BR]] ---- |
Introduction
This page will (hopefully) become a place for people to communicate and post information in an attempt to audit most of the known PersonalTelco nodes. Once before a project with a similar purpose existed, called ["AdoptANode"]. For a list of nodes look to the NodeMap or NetworkAddressAllocations. CategoryNode and the Subversion repository (under http://svn.personaltelco.net/svn/ptp/system/trunk/node) are good places to collect data.
For each node we hope to collect:
- SSID (www.personaltelco.net)
If the ESSID doesn't contain this, it's not really a node, according to the NodeStandards.
Node Name (i.e. SouthParkBlocks, CrowBar) and Number (i.e. 597)
- Not all nodes have numbers.
- Node Address
- [Contact: phone number, email address?]
- Get the name of the person to talk to also.
- It's best to get both a phone number and an email address.
- Some nodes prefer to remain anonymous, and I think it's a good idea to respect that.
- Channel (1-11)
- There are quite a few more channels in 802.11a.
- It might be nice to document whether an AP supports 802.11g or state exactly what types of interface are supported.
- ISP
- Not a very important data point, IMHO.
IP address space (see NetworkAddressAllocations)
- Public IP (Static/DHCP) / Routing Information
- DNS server addresses
- Features/Description of Node Location (i.e. coffee house with good lattes)
- Try and keep these objective...
- Last Audit Date, By Whom?
Progress
I don't want to have duplicate data lying around, and a lot of this information is stuff we've already collected, so I've gone ahead and updated NodeTemplate to make it clear what pieces of information are relevant and updated a couple of node information pages to match that template. - KeeganQuinn
This is a good point: specific node information probably belongs in the node pages so that we don't duplicate effort/information. That said, the system probably should be for "auditors" to make sure the node page is accurate, and then log when they last checked on the node with a simple status like: functional, nonfunctional. That information could go on this page, and could be what we use to color the pins on the nodemap (if that every happens). Thoughts? -- CalebPhillips
Sure, that sounds reasonable. I'm working on a more coherent system for all of this (see ["Adhocracy"]), but that works fine in the interim. I haven't been logging the last update date because the wiki does that for me, but if you feel that it would be specifically useful I'm not strongly opposed. - KeeganQuinn
Data
See NodeCrowBar.
See NodeDittos.
See NodeMississippi.
See NodeRedWing.
See NodeSmallWhiteCube.
See NodeStaccatoGelato.
- See ["NodeTB"].
- See ["NodeTB151"].
Credits
Updated and annotated by KeeganQuinn. BR Original author CalebPhillips BR Original conception TomHiggins BR