People interested in HSMM / BBHN in the KC area should visit:

http://km3sh.com/

https://plus.google.com/communities/116631856653961827186

https://groups.google.com/forum/#!forum/kc-hsmm-working-group

While digging around on Ebay I ran across these.  Linksys PaP2T-NA   The device is a 2 port SIP VOIP Phone Adapter  VOIP Gateway  Claims to let you run an analog phone and a Fax machine on 1 Box.   It looks like something similar to the Gulfstream device.   They are running around $40.00  Would this run like the gulfstream and just need to be plugged in at each station that need phone access or would a server needed to also  be added to the mesh.   Having a backup phone and fax would be nice at a Hospital or EOC.

Already answered by:

The same way you would stream any audio over the Internet. Take a look on setting up a shoutcast streaming radio server and set it up to use the microphone as its input. Instructions on how to do this can be found online. I had this working on both a Linux and a Windows 98 (Yes...W98 in 2013) computer just over a year ago.

Wondering if you folks had any ideas on how best to stream audio of a repeater or a scanner over the Mesh?

This is the closest geographical forum I could find to our area. If I posted in a wrong place, oops.

This is a copy of a post I did on another reflector concerning San Diego area and its combined Ubiquiti Private LAN and BBHN Mesh linking. Nothing unique I imagine, just information to show its utility and efforts being done on cross border communications.

HDRENS= High Data Rate Emergency Network System, 501 (c) contact w3nrg for info.

CREBC = The Baja California Radio Club  contact me

When mentioning the HDRENS/CREBC lan this is a part 97 style system wide area for emcomm.It is private and controlled by Coronado radio club members in the US and our club here is Baja.

See QST April 2014 80-81

The mesh installations are new and being evaluated for their emcomm application and futuring "tunneling" via our lan as a backbone.

------------------------------------------------------------------------------------------------------------------------------

Two years ago it was on hsmm-mesh.org. The site has changed to broadband-hamnet.org. Same link, different domain works.

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-2-hardware/topic-180-wrt54gtm.html

Thanks, That version seemed to clear up the problems, I'll do more testing to verify everything is working correctly.

Andrew

If you are just testing try the 3.0.0 beta it likely has the fix you need in it.

I have just created my first two nodes.

The node on the WRT54GL v. 1.1 works without issue.

My WRT54Gv2 will assign an IP address of 169.254.127.137 with a mask of 255.255.0.0 or similar.

about 5-8 minutes later it will assign a 10.x ip address and my other node will see it.

This node never picks up my granstream adapters or assigns them an IP address but they work perfectly on the other node.  No static IP is assigned on any adapter or node.

This node also will not recognize my computer and assign it an IP unless it is plugged in before booting up the router.

Any suggestions on how to get it to behave like the other node, recognize the granstream adapter and recognize the computer if I plug it in after bootup?

I am just getting into Mesh, any help is appreciated.

Andrew

AK4FA

1) Edit in /etc/config/network (find lan config section to change netmask accordingly).

2) Edit in /etc/config/olsrd (find "config Hna4" section to propagate subnet to other nodes.)

3) Edit in /etc/config/dhcp (to increase the number of IP addresses that can be allocated.)

then reboot.

THIS IS A quick-n-dirty HACK and from memory. You will have to redo these edits if you ever go into "setup" and "save"--will get overwritten. The proper solution is to edit the perl code behind the setup web page and template files in /etc/config.mesh. This might be relatively easy to do, I've just avoided diving in there to date :) .

I've been through this process and sorry to say, someone will need to find more time to document how to do this setup--not everything is captured in the repo. I have attempted to do this by developing a script that will setup a full development environment that compiles everything--to save a lot of time figuring it out on your own. Please separately send me email at ae6xe@cox.net if anyone is interested in this script.

HOWEVER, you still need to familiarize yourself with openwrt.org and buildroot.org site and their framework to have a clue what to do with this environment (not to mention familiarity with doing embedded development, linux, etc.). This is a solo effort pre-requisite over a long period of time you must have incurred or plan to incur. Otherwise, plan on beating your head against a wall in frustration :) .

BBHN firmware is ~95% built on top of openwrt.org, olsrd.org, and buildroot.org . The only actual source code being compiled to create our firmware is some parts of olsrd to fix bugs that olsrd.org has not incorporated yet. But this ~5% is significant--don't think this is minimized--it is the smarts of how to configure a node for our specialized setup. bbhn custom stuff is in perl for the mesh status, setup pages, etc.(the gui) and the linux custom config files.

I applaud the guys with the initial vision to use these building blocks to create bbhn.

Joe AE6XE

Given your tree and hill situation have you considered 900 MHz?

The 3.0.0 Beta will load on Ubiquiti NanoStation LocoM900 and NanoBridge M9.  These devices are in the early phases of testing and are definitely not fully supported at this time.  A warning banner will come up on the web interface indicating that they are not fully supported.

Version 3.0.0 added a feature to set a 5 MHz, 10Mhz or 20MHz channel width to the setup screen.  Since the entire 900 ham band is only 25 MHz, I recommend using a 5 MHz channel width.  The 900 Mhz channels should be in the channel pull down.

The 3.0.0 Beta is on the BBHN website under downloads, Linksys or Ubiquiti, experimental downloads.  For the NSL M900 or the NBM9 use the Bullet Factory .bin file the same as you would for a NanoStaton Loco M2.

A few more people trying out the 900 MHz gear could really help in getting it fully supported.

You can connect a M9 or a M5 to a M2 by using device –to-device linking.  Basically just connect the Lan Ports together or you can use a switch that supports VLANS to also add a WAN port and additional Lan ports to the UBNT nodes. This way M2, M5 and M9 devices can all exist on the same mesh.

I have M2, M5 and M9 devices on my network running 3.0.0 today and they are working well.

Clint, AE5CA