If you are using anything in the 1.1.x release this is likely BBHN->ticket:53 which was fixed in 3.0.0.

i would suggest upgrading to 3.0.0 (for a number of reasons) and give it another shot. 

Of course 3.0.0 is not protocol compatible with 1.1.x so you will need to update all nodes.

So I had great success with my first Ubiquiti Bullet so I decided to buy another.  This one, after flashing with the hamnet firmware and configuring the device I noticed the bottom LED on the signal strength meter is on solid red.  Can anyone tell me what that means?  I can not find anything on Ubiquiti's website.

Thanks!

Matt

W6MCP

Some background information so my answer to your query will make sense:

I purchased a security IP camera. The camera streams the video via RTSP on the default port of 554.

Using a Linksys BBHN node (v2 firmware), I assigned the camera (IPC) one of the addresses from the block of addresses on the LAN.

I put into the Advertised Services:

[IPC]   [RTSP (as the URL)]  [554 (as the port)]

When I saved the configuration, it stated that the configuration was saved, but that there was a problem with the port.

Does that help? Or would you like screen captures? Or do I need to update the node with v3 firmware?

I tried changing the port from 554 to 5540 - both in the camera and in the configuration. I still got the same result.

I have recently upgraded 2 Ubiquity based mesh nodes. I am using a Macintosh running MacOS 10.10.1 (Yosemite). In general the process was well documented. However it would have been helpful to have had more information regarding DNS and default addressing.

I was configuring the nodes from a Mac that was at the same time connected to my home LAN.  In that case, it does not appear the resolution of the BBHN domain names is automatic, as is implied by the Firmware Installation Instructions. This makes sense since the Mac was receiving its network settings from my dhcp server.  I eventually resolved the issue by adding the IP Address of the BBHN node as the first resolver in the DNS on my dhcp server.  A note about DNS settings for cases where the mesh-node is not the sole network connection on the PC would have been helpful.

Then, after doing the upgrade, and without DNS resolution for the internal domains, I was unable to find the nodes on either a direct wired connection or by joining the MeshNode Wi-Fi network. I eventually figured out the node comes up on 192.168.1.1 after being reflashed. A note to that effect would also be helpful for users whose network configurations may stray from the norm.

Other than that, I have been quite happy with bbhn and am no working on applications to layer on top of the network.

What are the parameters you put in for the advertisement and what is the message you receive back?

As an advertised service, the node complains about the configuration after you save it. (And the link is greyed out)  If I go directly to the IP address with my web browser, it works.

Oh gurus of BBHN, what might be the status of supporting this protocol in the Offered Services arena?

I've skimmed through the forum, and see there are ways to recover "bricked" units.

It's not immediately obvious to me whether it should be possible to use the "upgrade" feature to "downgrade" (Now that I've discovered V3 incompatibility with my 7 V1 nodes).

I try it, but all it does is reset my browser connection.

Is this something that should work? If not what is the fastest way to downgrade from V3 to V1?

Joe, AG6QO

BBHN->ticket:72 created for the issue with the firmware list not showing the latest firmware releases to avoid this re-occurring.

RE: AirGrid M2 2G20 0xe212:

reference BBHN->ticket:71

Reported details and details from the board.info do not seem to match, Device is tagged as untested in latest repo commit.

Main concerns are AG2 HP's should be around 28dbm output yet this board.info reports 18,   By firmware looks to be an older device, possibly an AG2 non HP due to no HP in the subtype field (which I didn't even think any non HP were ever produced but appears so)  even than the board.info doesn't appear to match what is known about them by datasheet.

This one will need some actual testing to iron out these questions before being tagged in the gui as supported, around power level and offset but should have better control of the device in an upcoming release.

Thanks Jim, 

Being from the UK , things are a little bit different here. The frequencies 2400MHz - 2483.5MHz are for Wifi equipment designated as 'un-licensed' by ofcom, as long as power is 10mW or 100mW in some cases. In theory we could use it for private networking if TX power was kept below the thresholds. 

I enclosed further info for anyone reading this from the UK below:

The frequencies of the wifi devices (2400MHz-2483.5MHz) appear to be higher than those designated for Amateur Data or High speed data which are 2356MHz - 2360MHz.

http://stakeholders.ofcom.org.uk/binaries/spectrum/spectrum-policy-area/spectrum-management/research-guidelines-tech-info/interface-requirements/uk2005.pdf

The wifi devices seem to fall in the Amateur Satelitte range, however as the band plan is a guide and the established use of these devices is wide spread, we should be able to use them as Amateurs with increased power beyond the un-licensed guys! Also the elevation and short range of the RF spread should pose no problems (please check Exclusions around Bude and Harringate for powers in excess of 100mW)

https://thersgb.org/services/bandplans/#22

Hi All, 

Firstly I am a newbie to the BBHN, I am at the start of my learning curve , so forgive me if I have mentioned something already within the forum. 

Would it not be sensible to have a standard Wifi router coming off the node on a different channel? This way we could have multiple close by pc's connected to the node with standard programs like Skype for example for VOIP (software voice) , File sharing and text chat, conference calls etc?? 

This way standard Wifi comms equipment could be incorporated into the node?

Possible?

Oliver

M0OLI 

There will be a NorCal/SacArea Mesh workshop this coming Saturday to help folks get started in building a mesh net in the Sac Region.

Message me to find out more.

Joe

AG6QO

PS. Thanks to the forum admins for creating this geo section!

TX and ye shall RX ! :-)

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-topiclist/forum-50-sacramentonorcal.html

Enjoy !
Jim
K5KTF