Post date: Jul 4, 2011 1:52:33 PM
Q: What are the supported Wifi Cards? How about my old ISA card?
See the [MeshAP/Docs/HardwareCompatibility] page!
(Link to be corrected)
Q: What's the root password?
It varies, from "terra" all the way to terra3 and terra4
On Builds 22, 23, 24 and 25 its 'terra7'
Q: What useful shell commands can I try?
Here's a list of the one's I know
watch -d someshellcommand - allows you to watch (in real-time) most of the commands below, with updates every 2 seconds. Parameters that have changed are highlighted. Example: watch -d reporter
reporter - shows the ethernet & wlan card settings, will also show if you have a gateway connection, clients connected or other mesh nodes in range. Can be prefixed with 'watch ' to get a continuously updating report - see ReporterDetails
ifconfig - shows the interface configuration, the same as the ethernet/wlan section of 'reporter'
iwconfig - shows the wireless interface configuration - many options available - more information at http://leaf.sourceforge.net/devel/jnilo/manpages/iwconfig.html
iwlist - useful stats from wireless interface - more info at: http://leaf.sourceforge.net/devel/jnilo/manpages/iwlist.html
distread - when used before a 'remotemanagement' this cleans up some things - basically returning the Meshbox to default configuration. Careful! It is roughly the same as 'factoryreset'. Any changes (channel, essid, etc...) will be lost.
factoryreset - puts meshbox back to original factory state. Will require you to get a new certificate again from wiana and get the wiana settings again.
remotemanagement - use this to get the Mesh node to connect to Wiana and get the latest settings. The Mesh node should do this automatically every 30mins, but sometimes you just don't want to wait :-)
getandverify - use: 'getandverify tobuild23' etc to download the latest mesh software and patches. 'getandverify test' can be used to check the link to Wiana
checkforupdates - checks at wiana.org for the latest released software version. If you're up- to-date it will report your current version.
cat /proc/aodv/... - in here you can find files with current details of the meshing and aodv operation.
cat /var/state/dhcp/dhcpd.leases (?) - tells you which DHCP leases have been given out to clients and when they expire.
ssh <ipaddress> - us SSH to remote control another machine or node
ping <ipaddress> - check the tcp/ip connection between machines
pingtest - pings all nodes in reporter including over the tunnels
sr <ipaddress> - source route - shows the route taken across the mesh to a node - shows the route there, and the route back (which can be different) - see below for detailed example
shutdown or reboot or poweroff - self explainatory?
cwradius : use to test user authentication from Radius server. Usage: cwradius username password
mii-tool - allows interrogation of status of ethernet module, and allows you to specify settings or to reset the ethernet
leechtest - when this command is issued from your GATEWAY meshbox, you can test the throughput available to your network (pulls a file from a remote site). When issued from a REPEATER node, you can test the throughput available to each box. This command is very useful when diagnosing throughput issues, as it allows you to identify where bottlenecks may be occurring.
sigspy - gives signal strength and noise for wireless connections (client and MeshAP) - see SigSpy
blocknode <ipaddress> - allows you to manually block a link between nodes (useful if you want to prevent a node using a weaker link but with fewer hops. If Unblock retest is enabled, the block will be removed after the specified interval.
unblocknode <ipaddress> - allows you to unblock a blocked node (blocked nodes are shown by doing cat /proc/aodv/blocked)
broadunblock - sends out a broadcast to remove all blocks between nodes. If signal testing is enabled the nodes will re-test the link. If not, you will need to manually reblock links you want to block.
doubleunblock <ipaddress> - will apply an unblocknode at either end of a link.
When you send a ping from a node thought mesh to your gateway and you want see it's track for the node (other world, see the route the nodes goes thought to ping the device in the mesh) then issue a SR command.
Example
A is the Gateway
B and C are the first hope of the gateway
D, E, F and G are the second hopes
If E see B and C then issue the following command:
sr < A ip address of gateway>
i.e. sr xxx.xxx.xxx.xxx <enter>
What it actually does is check to see if the route is the same coming into the mesh node gateway as it coming from the mesh node gateway.
If there is a two different routes then you may have a performance problem.
Q: What software versions can be downloaded with 'getandverify'?
See MeshAPFirmwareVersions for a complete history of the firmware revisions.
You can see if 'getandverify' is 'working' using getandverify test
Q: How do I turn the power off on my MeshBox?
make sure you've 'shutdown' the OS (see above) and HOLD the power button in for 5 seconds or so.
Q: I've changed/added/deleted some users from a realm in Wiana, but the MeshBox doesn't know about it
You should ssh into the meshbox and type 'remotemanagement'
Q: Can I SSH into one Meshbox from another?
Yes, use 'reporter' to find its 1.x.x.x address and just do SSH 1.x.x.x. You can do this again on the next Meshbox to remote control any node on the Mesh.