Open Mesh A Technical Breakdown

I’m writing this for everyone that is interested in the more technical part of the open-mesh devices and wants to know the ins and outs.

Open-Mesh is built upon the opensource openwrt platform.
At the moment of writing the latest stable version is the so called “Chaos Calmer” and open-mesh is starting to use that version as well in their latest beta release, version nr 6!

To gain access to your open-mesh device you can simply install putty and SSH to your device.
If you don’t know the ip address, just use any ip scanner such as zenmap/nmap on windows to scan your range or check in the cloudtrax environment in the tab access point.
The username is root, the password can be found through when navigation to configuration/advanced settings.

Now that you’ve entered the system you can validate the version by using
cat /etc/openwrt_release.

Checking the interfaces can be done with
iw list

checking the routing stats can be verified with

the open connections with
netstat -p

the running processes with

to get a list of all installed packages
opkg list-installed | grep more

or to check the repositories where the sources came from
cat /etc/opkg.conf
Editing that file opens a number of possibilities!
if you edit the above file with
vi /etc/opkg.conf

and enter one or more of the following urls:

you can update your cache with
opkg update
to get a full list of the installable tools.

by installing the graphical user interface you get a perfect view on your open-mesh boxes!
cp /www/index.html /www/index.old
rm /www/index.html
opkg install luci
uhttpd -p 81 -h /www
and surf to the ip address of your device on which you were connected through ssl as well.
and see for yourselve what a massive amount of information can be retrieved from here.

By using
tcpdump -i any
you’ll get a full wireshark trace of all your interfaces on the screen.
(opkg install tcpdump)

Installing the dsniff package
opkg install dsniff
allows you to snoop on all the http traffic that is passing by.
urlsnarf -i any

reading the last log entries can be done by the commands :


more info here:

and here for troubleshooting :

full debug output: | more

udshape -l to list all currently connected clients

some more commands:

cat /sys/kernel/debug/ieee80211/phy0/sta_tracking_table

uci show

ls /sys/kernel/debug/ieee80211/phy0/ath9k/

how long is an antenna in use ?
iw dev ap0_3 survey dump | grep -A 4 “in use”