There are currently three node types listed on the NodeMap. They are:
- Active - This is the location of a node which wirelessly shares internet access with an area around it. It is currently up and working.
- Inactive - This is the location of a node which used to share out access but is broken for some reason.
- Interested - This is the location of a person who isn't currently running a node but is interested in doing so at some point in the future.
After the last MonthlyMeeting I would like propose two more node types:
- End User - This is the location of a person who has a permenant connection to another node but doesn't currently share out access from their location. This is basically a sub-category of the Interested type but may be useful information from an RF troubleshooting point of view and from a social point of view because an End User probably has more gear and experience then an interested node.
- Repeater - This is the location of a node which doesn't share access but connects two or more nodes together.
The only remaining issues is that currently the map's NodeType selection mechanism is exclusive (you can only belong to one type). So I'd like to do one more reworking and finally propose this:
GatewayNode - This is the location of a node which wirelessly shares out access to the internet and/or the WirelessCloud.
RepeaterNode - This is the location of a node which doesn't share access but connects two or more gateways together.
EndUserNode - This is the location of a person who has a permanent connection to another node but doesn't currently share out access from their location.
InterestedNode - This is the location of a person who isn't currently running a node but is interested in doing so at some point in the future.
Node types 1-3 can have a status of either Working or Broken (less politically correct but I think it's clearer language then Active/Inactive). I'd also like to include one more status type of "Official" or something like that. That means that the node is configured to the to our NodeStandardization spec and that someone has audited it and approved that it's basically all legit.
So can anyone pick holes in this or offer improvements? -- AdamShand
For comparison, Seattlewireless.net has addressing and routing structure types that include Ax, BX, Cx, and Dx Nodes: [http://seattlewireless.net/index.cgi/NodeType Their NodeType page] . --ChadPatteson
Yeah, the Seattle concepts are a little different then what I'm trying to address here. This is basically purely for the mapping application, not from a network architecture point of view. -- AdamShand