I still want to be a Node, but, I have more questions
Following are answers to questions that individuals and businesses asked after they read the PotentialNodeOwner page. Perhaps you will be left with the same question. If your question isn't answered here - ask us!
What does "node" mean? How does a "node" differ from an "access point" or a "wireless router"?
"Node" is just a generic term for one component in a larger network. Access Points and Wireless Routers are network components, and hence, they are nodes on a network. In other words, they are "types" of nodes. For Personal Telco, "Node" has a specific meaning as defined in NodeStandards and NodeTypes.
I must have a DSL Connection? What about going "all wireless"?
If you have LineOfSight to one or more other Personal Telco nodes, it is possible to "piggyback" off of their connection. In this case, you node is what we would call a "Repeater Node" because it extends the signal of another node. This type of setup is more complex than those described in PotentialNodeOwner --- if you are considering this, please let us know so we can help you!
There is a distinction between being on the personal telco network and getting Internet access. Going "all wireless" is a useful and needed project, even if no internet access is involved. What you can provide is local content. You might have a web server or file server of your own that would be made available to others who are on the same wireless network. Its this LocalContent that creates a participatory environment and makes your piece of the network unique and valuable.
What about liability? What if someone uses my node for bad things?
If you are concerned about such things, and many people are, you want a CaptivePortal. There is some information on the PotentialNodeOwner page about ["CaptivePortal"]s [http://wiki.personaltelco.net/index.cgi/PotentialNodeOwner#head-11208b29f070375486dd36cc438bf967b956f727 here].
What about Bottlenecking? How do I make sure people play fair with my internet connection?
This is a very common concern, and a very logical one. If people start using your connection, what's to keep the otaku next door from downloading a continuous stream of anime videos and sucking up all your available bandwidth? Well, I find that while this is a reasonable concern, it is much less common in practice then you would expect. Typically, I recommend that people go ahead with the install without dealing with this, and then, if it gets congested, you can always cross that bridge when it comes. When it does come time to do this, there are a couple of options:
Use Linux
If you have a CaptivePortal box as part of your network, you can use it to do this for you. It requires that the NuCab have an additional network card installed (for a total of three) and for you to put it at the front of your network (directly behind your DSL modem). Then, we can use the power of Linux (and things like WonderShaper) to give your traffic priority over the wireless users'. This works pretty good - the main problem is that it puts a server at the front of your network which may go down, and if we set it up for you, you might not know how to fix it.
Get a Seperate DSL Line
Several of our nodes have a seperate DSL line just for the wireless network. This is certainly not the cheapest route, but it does the trick - your two connections will be completely isolated.