Hi Conrad,

I have NOT modified any of the code.  The only parameters that I have changed are those vi the WWW interface. 

BTW the number I left on your answering machine, call anytime from 9 am to 9 pm.

THX Conrad

Paul Strauss

WD6EBY

Output of 

 cat /sys/devices/pci0000:00/0000:00:00.0/subsystem_device

On the node please.

Have you modified any files on the node itself ? 

Hello,

I am sitting on the bench with several units talking to each other.  PicoStation2HP, Rocket M2, and a NanoStation loco M2.  Every thing is so close that I would expect and do read 100% under Mesh Status/Current Neighbors/ LQ.  Every thing except the loco unit it reads ~89%.  Don't fully understand.  I signed into the loco unit, under SETUP/BasicInformation/WiFi/active settings list and the the RX and TX antenna pull downs show up as "N Connector" and can not be changed.  I can see that this would hold true if I was working with a UBNT Bullet, but I am not, its a loco.

Yes I did do the proper factory flash with the proper software.  Does any body have any idea what is going on?

Thank you.

Paul Strauss

WD6EBY

There's a huge volume of stuff on Youtube. To wit:

https://www.youtube.com/playlist?list=PLDfWZ-E8CtRj0U61dbkC5fkk64-Iia4QC

It might take a while to get exactly what you need, but there's a lot of educational stuff.

At this time we are only able to generate images for the M series.

We currently are using more resources  (ram and flash) in the ar71xx build than are available on the previous hardware.

In addition OpenWrt has announced the devices with 16mb of ram are prone to overload in 12.09.

 Low resources is already a problem on Linksys builds (not enough flash and ram). The Linksys build already is unable to be brought to the same level Ubiquiti is at, the same issue would exist with pre-m Ubiquiti (less than 32/8)

Hi,

We have access to  Nanostation 2 but BBHN firmware is available only for Ar71xx. I have look on openwrt page :

http://wiki.openwrt.org/toh/start#ubiquiti

http://downloads.openwrt.org/snapshots/trunk/atheros/

and I have see that  UBT on atheros is supported by OpenWRT v8.09.

Is it possible generate BBHN firmware for "atheros" version ?

73 Waldek sp2ong

We only support the M series of Ubiquiti gear.

It needs to be a NanoStation M2 

Thank youthank you for all the information presented on the site because I debuted with Hamnet in the south of France.

I use a nanostation2 with the latest software version Ubiquiti.I can not seem to load the Hsmm by AirOS software file. A message says that the software is invalid.

I tested bbhn-1.1.2 and earlier version. Does anyone have a solution? 

Hello everyone,

Exactly.  I used to use Linux a lot and was always of the opinion that the "man" pages were wonderful if you KNEW how to do something.  If you didn't know, all you could do is hunt for an example from someone who had done it.

So, could someone, PLEASE, put up a few screen shots of the setup pages which are needed to set up services, port redirection, etc. 

Computers (usually) do what they are told to do.  But they are pedantic about the exact syntax of what they are  told.

PLEASE, PLEASE, PLEASE  a few EXAMPLES. 

73, Graham Lees ZL3GSL

I used Filezilla to do link speed testing this past weekend. Just install the app, identifiy a folder to share, then use any other computer from the same lan to test if FTP works. After that, it should be accessible from elsewhere on the mesh, using using only the IP address of the hosting computer.

You are using 5 node or 13 node direct on the hosting node aren't you? If you use NAT, you hide all of the devices on your node's LAN from all other users on the mesh unless you set up port forwarding. It certainly can be done, but so can driving to the store in reverse. One is lots easier than the other.

My Beaglebone Black hosts NTP, Asterisk, chat, a large file collection, get started web pages, and similar. The 5 node direct required no setup at all to see the device by name or IP, and only advertising of the services to let everyone on the same mesh see my devices and services.

Rick, NG5V

The post comes up a number of times about resetting passwords and/or changing the firmeware. Sometimes this is required to make sure the current load is valid, other times to return to factory firmware.

If you click the help link on several of the pages, you will find the answer to many of the frequently asked questions about what things mean and how to make changes such as this. The TFTP method and links to other tools like JTAG are found in the help section.

From any working mesh node, explore the help screens for a wealth of info. This is local to the device so anyone, anywhere can use the info.

Rick, NG5V

I had a friend give me his mesh nodes which are under his callsign and cannot remember the passwords.  I am not familiar with Linux that much, so if the solution requires that... please be patient.  How do I go about a re-flash?  I know the software needs updating, but I need to wipe it clean so I can restart with my callsign.

Thanks

Bill R.

N5VEI

The node's default is to go out a gateway to the specified ntp site. Without a gateway, the nodes don't seem to be able to sync up amongst themselves. I don't want to have to fiddle with every node's ntp config file to have them point to a specific node. That would require a manual setup for every deployment.

Just out of curiosity, could this be spoofed by adding an advertised service or named host with the ntp host named in the config file? ie, add a computer or gps time server to the mesh via a node, and give it a host name equivalent to the one the ntp clients are looking for? If a gateway isn't available, none of the nodes should be able to look at an internet DNS...

Think I just found next weekend's project.

Hmm. Re-read your post and think I missed the point. Sounds like your nodes aren't going out to get time updates, but devices connected to them are successfully updating. I haven't had that issue; every time I connect a node to a mesh with a gateway, the first thing that happens is it updates it's own time. I haven't updated yet, all my nodes are V 1.0. I've been interested in getting NTP working across a mesh without a gateway.

Not sure about your first question, but NAT and DHCP are two different animals. You won't be able to exceed the number of DHCP leases you've set in the config, 1, 5 or 13 regardless of NATting.

That setting is on a per-node basis. I use 13 DIRECT as a default on all my nodes. I use a wifi router connected to one of the node ports, giving me 8 WIFI adresses available for devices. I found out the hard way that leaving it at 5 DIRECT only gives me one assignable address via DHCP. In order to give wifi clients direct access to the mesh, you need to set the wifi router to pass through DHCP requests, so the node manages addressing. This is done automatically if you use a BBHN node in AP mode, or DD-WRT is pretty easy to set up for this type of operation.

Using a connected wifi router with it's own DHCP active, and connecting that to a node, does open up the wifi to use as many addresses as you have enabled in the wifi router. That creates a pretty complicated setup that seriously messes up the whole mesh idea, and usually does require NAT. I tried it, didn't like it, and don't do it anymore. Someone with lots of network savvy would probably say I'm a chicken, but I really like the simplicity and rapid setup of direct mode.

A disadvantage I've found when mixing direct and nat modes is that the name services seem to go a bit wonky. When everyone is in direct mode, it's a simple matter to manipulate the advertised services so that computers and devices can join the mesh and quickly find services by name; 'ftp_server', 'pbx', etc. A node in nat mode seems to have a problem resolving names, making advertised services harder to set up. Might just be my attempts at setup, but that's been my experience. 

Has anyone set up FileZilla (FTP Server and Client) to work with the Ham Mesh net?

If so, could you contact me at "ke6wez@gmail.com".

I have tried, but just haven't been able to get it working over the Ham Mesh Nodes.

Thanks.