Joe, Conrad, and I have been bouncing around ideas for quality of service.  There will come a time when served agency traffic is more important or urgent than general ham traffic.  Any QoS functions will need to recognize that and give the agency traffic higher priority through the mesh.

Yes Vegas, wonderful town, never turn on your computer when near the Defcon convention, bad things may happen.

The feature to add a code was added in version 1.1.0, however on tracking down the stability problems of 1.1.x  the Secure module was found to have numerous code problems that increased the level of instability in the release and had to be pulled for further testing. It has been retasked to be dug into in the future.

You can't disable SSID in an AdHoc network as it's needed to know that devices exist and associate (not to mention hidden SSID doesn't really hide anything.

Don't really want to bring up an old thread, but it is the most relevant to my concerns. I have 2-3 nodes up here in the center of town. My neighborhood can only be described as "crackwhore infested". My building has already had trouble with our WLAN because of the neighbors. I secured it with an 8 character WPA2, they cracked it. When I locked down the MAC's, they spoofed it. I increased the password and they haven't come back. My question is, what's to keep them from going after my meshes?

Something as simple as a password for Las Vegas mesh nodes that only the hams know would be great.

Or disabling SSID. the nodes would still be able to connect, but I would be "invisible"

I need to be invisible in this neighborhood.

Once they are configured you must connect using a wire to the node.

The wireless card on the router is used to talk to other mesh nodes, it can not speak to a laptop because the laptop does not know how to speak mesh. 

Plug an Ethernet cable into the wrt54g and into your laptop.  Make sure wifi is off on your laptop.  Then launch http://localnode:8080 

You will see the basic screen again.  From here if you have multiple mesh modes turned on you can then click on "Mesh Status" and see them as well.

the important thing is you MUST be hard wired in with a cable to a node to be able to access it.

Thanks AE5CA for the tunnel info. I now have 14 nodes, 4 or 5 of them being WRT54GS (less than rev 4). I'm pretty much isolated here and would appreciate a heads up when the new version releases...

There is a set of scripts that are currently being beta tested that once installed on a node, will allow Tunnel Clients and Tunnel Servers to be set up from within the setup menu of a mesh node.  Members of the Beta Test/Developer Team have successfully created tunnels connecting New Jersey, Texas and California.  We have found some problems with firewall settings.  Work is under way to make sure we have proper firewall settings before the scripts are released. We are close to having the firewall issues satisfied for the UNBT nodes.

Some work has to be done still for the Linksys WRT54GS version 1 through 3.  The Linksys runs an different style of firewall.  It is looking like we will be able to use the WRT54GS versions 1 through 3 for tunneling and they will be able to connect to the UBNT tunnel nodes.  But some of the applications on Linksys are older versions and we have some compatibility issues we are looking at. The WRT54G, GL, and GS v4 will not have enough memory to run the tunneling application.  The WRT54GS versions 1 through 3 have double the memory of the other Linksys boxes.

I have been using NanoStation Loco M2's for a lot of my testing.  At $50 for the complete package it is a great choice.  It will most likely be less expensive than a 10 year old used WRT54GS v1-3. The NanoStation M2 is my favorite. It costs around $80. Either one is ready to be mounted in an outdoor setting and comes complete with antennas.  I have done 13 mile links with both the NanoStation M2 and M5.

The folks doing the heavy lifting on this effort are volunteers that have real jobs and families.  Understand we are working on it but sometimes real life gets in the way

Clint, AE5CA

Joseph,

I may be missing something or there may be a typo, but if your wifi is turned off and you are not hard wired, how are you connecting your PC to the node??  How were you connected to the Linksys when you uploaded the firmware?  were you connected by ethernet or wifi?  Are you running Windows or MacOS on your PC?

If you are using a Windows PC and are connecting via wifi, try this:

1.  Enable your wifi connection and configure the TCP/IP properties to use DHCP

2.  Disable all of the other connections (ethernet, VPN, etc.) and disconnect the ethernet cable.

3.  Connect your wifi to the SSID "MeshNode"

4.  Before you proceed further, make sure that you have an IP address in the 10.x.x.x range.  Open a command prompt, type ipconfig.  If you don't have an IP address or it is not in the 10.x.x.x range, type ipconfig /renew.  If you still cannot get an IP address, open the connection properties and click on the repair button.

5.  Open a web browser, and enter the following URL "http://localnode:8080"

6.  Click the setup button.  The login name is "root" and the default password is "hsmm"

If you are running MacOS, replace steps 1-4 with this:

1.  Open the System Configuration, click on Network

2.  Disable or unplug any connections other than wifi (i.e., ethernet, VPN, modem)

3.  Connect to the SSID "MeshNode"

4.  Wait until your wifi has an IP address in the 10.x.x.x range.  If you don't have one, click on "Advanced" and make sure the wifi is set to use DHCP, then click the renew button.

There are some dish mounts that are made to accept a NanoStation. So they may not be old cable tv ones. I saw one location claim it added 10db over the radio built in antenna.

probably is doable I would imagine but I don't have enough knowledge on microwave antenna design to calculate the pattern and effect of the shape of the dish and the optimal mounting distance plus the effect the internal patch antenna on a NanoStation would have.

Correct using a BBHN node paired with an M3 in factory install until M3's become supported.

Hello Conrad. I am not following your line of thought. Are you referring to the use of the "factory" Ubiquiti firmware (airmax) or are you referring to using a modified version of BBHN software?

I presume that you are referring to using the 3Ghz equipment as a "backbone" tunnel for say 2 local BBHN meshs.

While it should be doable I do not have any instructions on how you would do it.

Ideally you would want to bring up a new interface (say vlan 9 so it's out and away from anything we actively use or may use in the future) and probably set it up with an IP in the VPN address space and add the required routing and firewall rules and dns rules.

The other alternative would be to modify the dtdlink but then you need to remember you made changes if you replace the device and you won't be able to dtdlink to other devices without modifying them as well.