Would it be possible to "embed" the model type or ID somewhere to be displayed, maybe on the front page under Firmware version or configuration?

It may even snoop out and display the MAC addressess as the original AirOs does

We have an rapidly expanding mesh here in the (west) Toronto area and we have several different types of nodes.

We have started including node types with our call ID such as

VE3CWU-NSM2-01 (Ubiquity NanostationM2 number 1)

VE3CWU-UNLM2-01 (Ubuiquity NanoLocoM2)

VE3CWU-UBM2-01 (Ubiquity Bullet M2)

VE3CWU-LS-01 (Linksys number 1)

VE3CWU-X01 (Xagyl number 1)

Thanks, Bob VE3CWU

ve3cwu at rac.ca

Our mesh now has several Ubiquity NanoStation M2 ( UNSM2) nodes. 

I want to start using the Secondary POE port on some for accessories such as camera etc.

On checking the pins for power I do not detect any power on this connector.

Googling the UBNT website it seems that the "standard AirOS" has an option to "Enable PoE Passthrough" port.  see here

http://community.ubnt.com/t5/Installation-Troubleshooting/How-to-connect-ip-cameras-to-NanoStation-M2/m-p/479065#M49525

Question is, has anyone else been able to enable this PoE Passthrough and us it ? Or is this option not enabled yet in BBHN ?

thanks, Bob VE3CWU

ve3cwu at rac.ca

Seeing an IP address is indicative of your node hearing the remote node, but the remote node not hearing your node well enough.  This makes sense in your scenario, because the NSM2 is considerably higher power and has an 11dB antenna... Approaching 100 times the effective radiated power of the Linksys with stock antennas.  The Ubiquiti also has nearly a 10dB receiver sensitivity advantage.

When using external antennas on Linksys you want to keep the coax as short as possible (1-2' max), avoid as many connectors/adapters as possible, and be sure to shut off the unused antenna port in the config screen.  The Linksys and Ubiquity use different techniques in using the two RF ports.

Adding an ampilfier is probably not a wise approach to solving the problem.  It only tends to trash the band for everyone and, unless you have sophisticated test equipment, will most likely distort the signal making it harder for the remote node to decode.

A clear line of sight is paramount.

Andre, K6AH

Our local MESH is developing based on readings and fixing errors between the chair and the keys.  A wrt54 is working fine at close distances, but is only seeing the WIFI address of our NSM2 at a further distance.  Why would it not continue to see the MESH?  We are trying with various antenna, amps etc, but no change in what it sees at 7+ miless.  The WIFI from the NSM2 LQs at 66-100% on the WRT54

Vance, KC8RGO.

First method worked like a champ...now I'm able to connect to the MESH 

First method worked like a champ...now I'm able to connect to the MESH 

You may want to try reaching out to Bart Kus, AE7SJ.  He is the guy behind hamwan.org and may have the necessary test equipment to look at and verify a modified openwrt build like we are talking about.

Specifically, are there step-by-step instructions for installing IRC on a Ubiquiti NanoStation M2 available on this site?

I would like to clear up some confusion people are having with how HamChat compares to IRC and other similar solutions.

Yes, HamChat is very basic in functionality and, yes, it is very small and compact. However, the main advantage of HamChat and the only reason it was developed is to help communicate on Broadband-Hamnet without any prearrangements.

Imaging, you are mobile and enetered an area where your router connected to some established mesh network. You have no idea what ways of communication to use, what additional software you need to install, etc. However, HamChat running on your router will be visible in the resource link related to your station. And this is a simple http link which can be clicked on in any regular Web browser. As soon as your station is noticed and someone clicks on the link they will be in your small chat room and you could "talk" to each other.

You don't need a special client to work with HamChat, almost any modern browser could be used for this purpose. This means that you can assume that the client software is already installed on every computer connected to the mesh.

73, Nikolai (VE3NKL)

http://www.cnsp-inc.com/

I have a 5.9GHz link to the AMPRnet thru HamWAN, and am using my BBHN mesh to access the internet thru the link. 

However, I am unable to access anything on the AMPR network.  Do I need to put an additional router in between the link and the BBHN gateway node or something?

I have been assigned a small (5 addresses) AMPR subnet.   I have seen where some people have modified the OLSR settings to change from a 10.x to a 44.x network, but I only have 5 addresses, and want to use one, maybe two for the HamWAN/BBHN gateway, and reserve the others for devices in front of the BBHN mesh.

Can I just put routing rules in the BBHN gateway node (the one that's connected to the HamWAN modem)??

The wireless modem that is used for HamWAN is a Mikrotik Metal and has full router functions as far as I can tell.

Thanks!

If you're using MS Explorer, I suspect you would have had the same result if you had closed and reopened the browser.  We see many phantom issues with a root cause of browser caching.

Andre, K6AH

Russ, nice write up, sounds like a fun event.

I've been thinking of setting up winlink for a mesh mail server. Haven't played with it in a while, but I understand the current version no longer requires a connection to the Common Message Servers on the internet to deploy for an event.

Joe AE6XE, from SOARA field day BBHN setup.

I'm sorry about the quick panic.  A reboot of the computer solved the problem.

After doing an upgrade on router 7 I am unable to save a password.  I did a transfer from router 7 to router 16 to make a variable change.  After that router 16 now is without a password nor can I save a password to it.  This also occurred on router 11.  The rest of the routers are ok but I have not transfer from the above three routers to them nor did I use the upgrade software on them.  Is there a bug in the upgrade firmware or what is my problem?  I tried to save the password multiple times on each of the three routers without success.  They all had a password prior to the upgrade on seven and eleven.

AB3BL