Troubleshooting Guide

The visualization tool is the best way to start troubleshooting.

From the viz page you can test the connection between you and the node. You can also test the connectivity along the route to the internet. If the local network has packet loss then the problem is probably with your Wireless Access Point or your LAN rather than with the CUWiN wireless mesh network. If your path to the internet has packet loss then it is time to investigate the viz map for bad links. If you can't access the software at all then either the node is down or you have found a bug in the node code.

If you identify a problem on the mesh as the reason for your network outage, please send the text from the Test Local Network and Test Internet Connectivity links to cu-wireless-support@cuwireless.net along with a description of the problem that you are having.

If your node has been completely knocked offline, you will most likely need to climb up on the roof and check it out. Nodes have been known to fill with water when there is a leak in the top, but no leak in the bottom. Lightning strikes also occur.

What follows is a list of helpful commands that are useful in troubleshooting the network.

df -h: Shows all of the mounted partitions; -h makes numbers easy to read. Use this to show the memory space. If nfs is small, programs will be unable to run.
netstat -rn -f inet: Shows routing tables.
ifconfig -av: All the information about your network interfaces will be displayed in verbose mode.
ping -n google.com: Tests to see if the node can use the network to reach google.com
traceroute -n google.com: Documents the route that a packet to reach google.com