Node Information

From - The Columbus Georgia Wireless Community
Revision as of 12:29, 29 November 2007 by FiveAble (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Getting Onboard

IP Addressing

In the early stage, we're choosing IP ranges ourselves, because we're doing all the nodes. In the future, when people start meshing their own equipment in with ours, we'll have a more organized process for handing out netblocks.

Subnet Allocations

Everything is a 10.x.x.x. I'm alotting a /24 block for each access point.

The core switch is currently on a handing out leases to anybody and everybody. I'm in the process of re-working this scheme to easily alot a /24 for each AP that will be routable end-to-end anywhere else in the cloud. This will be done pretty soon.

More information is available at IP Scheme

Node Map

Please visit our live Hotspot Map!

Map of Uptown Columbus, GA. with Access Points

Node Listing


FIXME - how the network is structured. what subnets are allocated for plain-vanilla nodes, which are administrative, which are reserved for testing, etc. also what routing protocols we intend to use in the future, when the need arises.


An ad-hoc network has been established for the testing of the OLSR routing protocol. To connect, select the SSID of ''. Public internet connectivity will not always available as this is only in testing phase.


For the community network to function as a whole, the individual nodes should follow some basic guidelines. We recommend some hardware and software to start your own node, but it really doesn't matter what you use, as long as you can do the following.

  • End-user Node - provides the access to individuals
    • must speak 802.11b or 802.11g.
    • must adhere to the IP addressing rules.
    • must uplink to the backbone
    • should be open to the public (no WEP or WPA.)
    • should pass traffic without NAT (for full end-user routability)
    • should broadcast a descriptive SSID.
  • Routing Node - moves data from two or more end-user nodes
    • must speak 802.11b (802.11g isn't licensed for outdoors yet)
    • must use directional or sector antennas for efficient use of the spectrum
    • must be compliant with the (FIXME - probably going to be OSPF) routing protocol

Note! The previous guidelines apply to our structure when we get the backbone operational, which isn't quite there yet. Currently our APs are operating in stand-alone mode, and feeding off of cable modems. As soon as the NOC is in place we'll free them from that.

Update! We're actually there now. We're in the process of bringing nodes into the central network.

Existing Access Points

The following access points are available for public access.

Node fcc.cfn

Fountain City Coffee (admin: Kevin Welch) 1007 Broadway Columbus, GA 31901

Node eaterplex.cfn

Casa de Eater (admin: Eater) 1007 Broadway permanently down, but not forgotten

Node cantina.cfn

Cantina (admin: fiveable) Locos Amigos Cantina 1030 Broadway Columbus, GA 31901

Node judybugs.cfn

JubyBug's Books / The LOLpht (admin: fiveable) 1033 Broadway Columbus, GA 31901

Node rideonbikes.cfn

Ride-On Bikes/The Loft (admin: fiveable) 1036 Broadway Columbus, GA 31901

Node scruffys.cfn

Scruffy Murphy's Irish Pub (admin: fiveable) 1037 Broadway Columbus, GA 31901

Node cannon.cfn

No longer part of the CFn network.

The Cannon Brewpub 1041 Broadway Columbus, GA 31901

Node gymnastics_unlimited.cfn

Gymnastics Unlimited (admin: fiveable) 4368 Warm Springs Road, Columbus, GA, 31909

Personal tools