Cli

CLI Testing Instructions

What you will need:

* Two picostations
* The image with the CLI (It requires special build instructions right now, so please ask me for a copy)


Now let's test!

Flash both nodes with the CLI image

Router 1:
Set up the first node using the regular graphical Set Up Wizard, as you normally would, using the following values:

Node Name:
DrBunsenHoneydew

Mesh SSID:
MuppetMesh

Channel:
11

Mesh Encryption:
MuppetMesh

Access Point SSID:
DrBunsenHoneydew

Access Point Encryption:
MuppetAP


Router 2:

Follow these instructions:

Flash Router

Switch to DHCP

... to get a lease (ip address) from the node once it boots up

On command line

Determine your node's IP address

~ ifconfig

Copy the IP address used by the eth0 interface and change the last octet to .1

~ telnet 10.48.162.1 

Run the setup wizard:

~ setupwizard

Use the following values for the second node. We will be trying bad values to make sure that it refuses bad inputs.

New password:
muppetshow

Set Hostname?
First Try:
Meep

Second Try:
y

Host Name:

First Try:
%!^@!^

Second Try:
Beaker

Mesh SSID:

First Try:
(Nothing. Just hit enter)

Second Try:
MuppetMesh

Channel:

First Try:
9001

Second Try:
11

Mesh Encryption:
y

First Try:
Meep

Second Try:
MuppetMesh


Set up an access point?
y

Access Point SSID:
Beaker

Access Point Encryption:
BeakerAP


Keep this configuration?
n  (sorry, but we have to go through it again)

Hostname:
NoBeaker

Mesh SSID:
NoMuppetMesh

Channel:
5

Mesh Encryption:
NoMuppetMesh

Access Point SSID:
NoBeaker

Access Point Encryption:
NoBeakerAP

Keep this configuration?
y


Your node will now restart networking and should after a minute or so begin broadcasting an access point.

Connect to the "NoBeaker" access point, then go back to the command line:

~ ssh root@thisnode 

OR

~ ssh root@[IP address we used to telnet in]

Once you're reconnected, rerun the set up wizard:

~ setupwizard

Set new configuration?
y

Run back through the set up wizard with the following configuration:

Node Name:
Beaker

Mesh SSID:
MuppetMesh

Channel:
11

Mesh Encryption:
MuppetMesh

Access Point SSID:
Beaker

Access Point Encryption:
MuppetAP


Your node will now restart networking and should after a minute or so begin broadcasting an access point. But NOW we should be able to mesh with Dr.BunsenHoneydew

Connect to the "Beaker" access point, then go back to the command line:

~ ssh root@thisnode 

OR

~ ssh root@[IP address we used to telnet in]

Once you're logged in, type:

~ route

You should see in the table a route to DrBunsenHoneydew



<!---
@huboard:{"order":37.0,"custom_state":"blocked"}
-->

@gradyoti is this file supposed to be here? Looks like it might be an artifact.