Hey Jim!

Do you have more information on how you integrated the iCruze display to your node?  Namely pinout, etc.

Thanks!!

Channel 1 has been the standards for some time now, it was a common channel used by hams prior to the mesh firmware.

On 802.11g networks in the US you have only 3 channels that don't overlap (1,6,11). Every other channel will cause at least some overlap so 1,6,11 have been common use.

802.11n uses double the "channel" sizes so to stay in the ham band and not overlap with any other channel you really only have channel 1@ 2402-2442 MHz).

This means to have the best chance of talking to another mesh node channel 1 is the sensible default.

Yes there are other devices in this area, but as hams we can run higher gain antennas (higher EIRP) to have an advantage on signals.

I am new user, just loaded firmware onto WRT54G rev. 2 that I purchased used. Seems to work fine, thanks to everyone's hard work to provide this!

Where I live (Albuquerque) the local phone company offers DSL internet, and their wireless access point appears to default to Wifi Channel 1. When I click WiFi scan on my node, I see many signals on Channel 1. Channels 2, 3, and 4 are empty, and 5 and 6 have sometimes one signal each. Is my location unique, or do others see lots of signals on Channel 1?

Jim, AF5FH

Happy to see the forward thinking.

I know this answer doesn't solve the need for performing this 'right now today' but want to give a bit of the road map.

A standardized protocol for device to device linking is currently being looked into, preferably with the intent of allowing it to be "plug the nodes together and be done" (if possible) in order to keep with the simple setup nature.

This was always expected to be an item to need to be addressed with Ubiquiti gear only having 1 physical port and some devices only have 1 antenna port, or no external RF feeds (Bullets or NanoStations for example).

The goal of the initial UBNT release (1.0.1) was to maintain as much the same to being with (as possible) and start adding features as we go down the road.

Some thoughts and configurations have already been bounced around on the subject and are going through various stages of testing an analysis to be sure they are the best way.

I would suggest looking for a much easier method on the Ubiquiti build in the next release, and the linksys build to follow it as well.

Best Regards,
Conrad Lara
KG6JEI

Maybe this will get you pointed in the right direction? http://kb.iu.edu/data/ahrs.html

I see said the blind man.  I'm still not able to get to a shared drive on another confuser so there is some other things that need to be set.  I will keep trying.

Kirk - N6SXR

The UBNT Bullet only has one ethernet port, so (as I understand it), if you wanted two physical networks (LAN / WAN) then you'd need a "managed switch" and assign some VLANS.

If you only want one network (presumably LAN) then I can't think of any reason why an ordinary 10/100 ethernet switch wouldn't work for you. 

I'm curious though, because I see the firmware for Nanostation M2, and it does indeed have two ports.  However the documentation for the HSMM firmware seems to indicate that ALL UBNT devices have only one port.  So I'm wondering, if maybe HSMM won't support the second port, or (insert unknown quantity here).

 

I picked up a WRT54G V3 the other day at a garage sale. When I got it home and fired up it worked just fine but when I tried to access the interface, it would not let me in and it kept saying that the router says "tomato". I did a hard reset and it still said tomato, but it did let me in with the admin access code. Once in I realized that the software in the router was not DD-wrt but rather something called Tomato! I did a search on the Internet and found out what it was and how it worked. I tried a direct conversion from tomato to the first BBHN iteration for MESH. This did not work and, fortunately, did not brick the router. The router just would not accept it and did a reboot back to tomato. After reading some more, I decided to try and bring the firmware back to the original Linksys software. This worked! I went through a complete process and restarted the router and all was fine. I then did the upgrade to the first level of MESH, followed all the steps, including the new password etc. Turned it off and on and it booted up just fine. I then did the final upgrade to BBHN Ver 1. All went well. I now have another MESH router.

I included this in the forum in case anyone comes across a WRT54G router that has Tomato running on it. 

Happy MESHING 

Lance VA3LP