[MLB-WIRELESS] meraki-flash package

[Dan Flett]

I've packaged up the Expect script I wrote with the necessary apps and an 
installer:

http://danversj.bravehost.com/meraki-flash-v1.0.zip (9.5 MB)

Just run install-apps.bat to install everything, and meraki-flash.bat to 
send your firmware files to the Meraki.  All other instructions are in 
Readme.txt

Also...

Here's how to get the Meraki's radio to operate in simultaneous 
adhoc/ap/client mode

The trick is to specify adhoc mode first, then an ap, then aps or client 
interfaces.  Note that you need "wlanmode sta nosbeacon" to get client mode 
to work if you already have AP or Adhoc interfaces configured.

Here's an example:
root at OpenWrt:/# iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

wifi0     no wireless extensions.

root at OpenWrt:/# wlanconfig ath create wlandev wifi0 wlanmode adhoc
ath0
root at OpenWrt:/# wlanconfig ath create wlandev wifi0 wlanmode ap
ath1
root at OpenWrt:/# wlanconfig ath create wlandev wifi0 wlanmode ap
ath2
root at OpenWrt:/# wlanconfig ath create wlandev wifi0 wlanmode sta
wlanconfig: ioctl: Input/output error
root at OpenWrt:/# wlanconfig ath create wlandev wifi0 wlanmode sta nosbeacon
ath3
root at OpenWrt:/# iwconfig
eth0      no wireless extensions.

lo        no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11b  ESSID:""  Nickname:""
          Mode:Ad-Hoc  Channel:0  Cell: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath1      IEEE 802.11b  ESSID:""  Nickname:""
          Mode:Master  Channel:0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath2      IEEE 802.11b  ESSID:""  Nickname:""
          Mode:Master  Channel:0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:0 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

ath3      IEEE 802.11b  ESSID:""  Nickname:""
          Mode:Managed  Channel:0  Access Point: Not-Associated
          Bit Rate:1 Mb/s   Tx-Power:0 dBm   Sensitivity=0/3
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root at OpenWrt:/#

The athX devices can then be separately configured using iwconfig.  Don't 
forget to do a "ifconfig athX up" to bring the interface up with the new 
config.  Of course, all athX devices must be on the same channel.

A usage for the above config could be:
ath0 (adhoc)  - mesh interface to connect to other mesh nodes
ath1 (ap)     - General Public Access to the public network - routed or 
bridged to the 10.x.x.x network
ath2 (ap)     - private hidden and/or encrypted AP - bridged to the LAN 
interface - to give the node owner wireless access to their own private LAN
ath3 (client) - to connect to someone else's internet connection ;) - it 
would have to be on the same channel as the other athX devices though.