I would like to start making some tunnels on Long Island. Hopefully this will help encourage more nodes as we can populate the mesh status window so we see other nodes. Plus we can begin developing services on the mesh while we wait for RF links to be established.

You can contact me here or via my website http://kc2zqo.com/contact

Another option would be via FB https://www.facebook.com/groups/LIMeshNetwork/

Re Encryption:

This is actually still an issue that needs to be looked at, vtund either needs to be ran without encryption OR be configured/bound to only be able to connect over the WAN port.  At the moment everything I heard has it unbound and not caring so it's possible it may choose to go over the mesh.  Needs to be looked into deeper to be sure that can not happen.

We have a facebook group for Long island meshers all are welcome

LI Mesh Network https://www.facebook.com/groups/LIMeshNetwork/

yes, i understand. this is just one step in my testing. Next, is to get a remote (across the internet/beyond my home router) client to connect. I would not expect to run in this (m2 to wrt) architecture in a normal situation. ;-) D.

Also, the Bullet M2 is the client, so no tunneling "into" the M2.  The server is on the 54GS.

Ok. it appears to be working in this very limited configuration. I am connecting my UBNT M2 via my WRT54GS (which is also running the vtund server). Everything connects properly. The Bullet M2 does have internet access too.

See http://wiki.openwrt.org/toh/linksys/wrt54g. The numbering of the ports vary by model. 

The GS has different numbering. 

So, to make sure I understand completely...

my current WRT54GS v2 has the following in the /etc/vlan file..

config switch eth0
option vlan0    "1 2 3 4 5*"
option vlan1    "0 5"

----------

You suggest that I change to:

config switch eth0
option vlan0    "1 2 3 4 5*"
option vlan1    "0 5"
option vlan2    "0t 1t"

--------

Then, I can plug the UBNT M2 into the LAN port 1 (next to the WAN port 0).

This way, LAN port 1 is tagged and will bridge to the WAN port.

do I have that correct?

It is possible to use a WRT54 to be you switch.  The principle is kind of their in the instructions to activate dtd-linking on the WRT's at http://ubnt.hsmm-mesh.org/products/BBHN/wiki/HowTo/Enable%20DTDLINK%20on%20Linksys?version=1

Basically if you edit the /etc/vlan.conf file to add one of the Lan Ports to Vlan 1 you can use a WRT as the smart switch. 

option vlan1 “3t 4 5t”

Will provide internet to a ubnt node plugged the lan port next to the wan port.

You would probable want to DTD link the two nodes as well with a:
option vlan2 "3t 5t"

Clint, AE5CA

We do not utilize the LED's during normal operation for signal strength indication we currently normally use them for status information to provide easy user feedback as to the node operational status.

Top solid green (Link4) generally mean the node has finished starting, flashing is early in the boot process has begun but not yet successfully finished.

Red (Link1) means we have a connection established with a neighbor (nodes should begin showing up in the status list)

Remaining 2 are reserved for future use.

Just one further question, am I right in assuming that the LED signal strength indication is not fully functional. In my local mesh the first LED is glowing red and the last one (green) is illuminated.

In the sense that this is a linux computer and we can program it do to anything, yes.

You might trial-n-error attempt to swap around the physical interfaces (eth0, eth0.1) assigned to the logical interfaces (LAN, WAN) in /etc/config/network UCI config file (risk is you revert to tftp to reload an image).

I believe this will break the setup gui code (don't do a 'save' in setup). You may wish to allow 2222, 8080, and 1978 ports open from WAN to access the node. Conrad may know if other hardcoded physical interface dependencies of what might break. The firewall zones and olsrd are based on the logical interface definitions (WAN, LAN, etc.), so 'should' still work.

config interface lan

    option ifname "eth0" <- change to "eth0.1"

config interface wan

    option ifname "eth0.1" <- change to "eth0"

~$65 for a GS105E is a known path from A to B...

Downloaded Linksys 54g3g beta 3.0 trx file and it is working a treat!, can see all my 2 Linksys and M2 modems in my local mesh node!

Thanks Conrad..