DD-WRT will let you go up to 251mw on the 54GL. At least it will let you set that as the power output in the control panel.

I also need ubiquiti help, 

I've got a UBNT v3.1 bullet together with a cisco 7940 and a pi running asterisks connected with a switch;   trying to connect across the mesh to another bullet/cisco 7940.  As far as I can figure, I've followed the videos exactly,  The mesh is up, the pi is running asterisks, Freepbx shows that its running (except for the phones).  I've set up the config files and phones per the video and the phones seem to be talking/downloading something, but all I ever get, on either phone, is: " phones unprovisioned ".

There is the question of the time base, as the pi thinks its in the 1900's.  Even with bad time, i figured that at least the phones would pick up the configuration.

Are there any cisco firmware concerns? 

Also, I'm wondering if the switch is the right way to combine the pi, phone and UBNT (bullet has only one port).  The bullet seems to be doing the dhcp ok. Maybe disable the dhcp on the bullet and put another router in the middle?

Any thoughts would be greatly appreciated.

19-dBm (79.2-mW) is the specified maximum output power for all three models. There are some hacks for bumping up the power on some models and, if you go to far, will shorten the life of your gear and, in all probability, will distort the signal transmitted. -Rusty-

Hello all,

As the title states, is the BBHN firmware open source?

Thanks!

KK4TGV

Are these numbers for the 54G, 54GS, or 54GL?

Hi all... new to the mesh but have been experimenting with it and have successfully loaded RasPBX on a RaspberryPi and successfully connected it and configured it into the mesh.  I am running two Linksys SPA941 IP phones as well as the 3CX softphone on two laptops connected to the mesh as well for a total of 4 extensions (100,101,102,103).  My problem is that my calls keep disconnecting at precisly 7 seconds.  When first setting it up I connected without disconnecting any calls.  Not sure what I have done or might have changed to have this start happening.  I'm thinking I have something wrong with port forwarding but don't remember what I did initially.  Any suggestions?  Thanks......Phil, KA1PXZ

<BEWARE!  Informational overload arriving>

Yes, if a file is in the pulldown list for "Firmware Download" the system will deal with it appropriately.
Dealing with the differences lies in handling not just the file extensions used (e.g. .tgz vs .trx) but the files having the correct format and contents.

If you try to create and upload your own patch file -- YOU ARE ON YOUR OWN!!   Seriously!

Patch files were used prior to v1.0.0 and were intended to update files the firmware when the amount of changes were small.  They were not intended to take your firmware between major versions (v1 to v3).   The patches (at this time) are not cumulative in that they are intended to be applied between sub-subversions.  A SINGLE patch file will take your firmware from, let's say, v3.1.0 to v3.1.1, but not from v3.1.0 to v3.1.5.  Patching from v3.1.0 to v.3.1.2 will NEED two files and they will NEED to be applied in ORDER.   Given this, the core team is considering renaming patch files to indicate the FROM and TO version numbers as "patch-v3.1.0.tgz" is rather ambiguous.

Hope this helps

        -Rusty-

People in the past have been able to navigate to the administration page and apply it via the firmware update section.  As a side/personal note (respectively), upgrade patches have been previously used (prior to v1.0.0) and I am glad to see them back! :)

An upgrade patch has been posted in the Downloads section for both WRT and UBNT. Great idea.

There is a tar file but no instructions. How is this patch to be applied? Do you move the archive over using an scp session, then ssh into the router, untar the files and over-write existing files in the respective directories? Or is there an easier way with a script perhaps?

Thanks.

Dave, K7DMK

Well said, K3TEG.

Very curious as to antenna selection, as well. Seems to be quite a few differing opinions online as to "best" hardware for directional (yagi or dish) and omni (vertical). Looking to potentially play RF put up some nodes around town.

Dave,

What antenna did you go with for the Bullet?

Looking at AirGrid M to establish a link to K2ALB-CENTRAL, but I think terrain/trees might be an issue from my QTH.

I suppose I could always point the AirGrid in that direction and hope that someone sets up a node somewhere in betweeen... :)

73

Mike

For anyone trying to crack the code to port forwarding across multiple nodes, following is what worked for me in creating the ability to forward from a mesh gateway, across multiple nodes to the node hosting my Echo/IRLP node.

#Node Port Monitor

iptables -A input_wan -p tcp --dport 8088 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 8088 -j DNAT --to 10.7.55.202:8088

iptables -A forwarding_wan -p tcp --dport 8088 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 8088 --to-source 10.212.63.152

#Echo Ports

iptables -A input_wan -p tcp --dport 5198 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 5198 -j DNAT --to 10.7.55.202:5198

iptables -A forwarding_wan -p tcp --dport 5198 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 5198 --to-source 10.212.63.152

iptables -A input_wan -p tcp --dport 5199 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 5199 -j DNAT --to 10.7.55.202:5199

iptables -A forwarding_wan -p tcp --dport 5199 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 5199 --to-source 10.212.63.152

iptables -A input_wan -p tcp --dport 5200 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 5200 -j DNAT --to 10.7.55.202:5200

iptables -A forwarding_wan -p tcp --dport 5200 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 5200 --to-source 10.212.63.152

#IRLP Control

iptables -A input_wan -p tcp --dport 15425 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 15425 -j DNAT --to 10.7.55.202:15425

iptables -A forwarding_wan -p tc --dport 15425 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 15425 --to-source 10.212.63.152

iptables -A input_wan -p tcp --dport 15426 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 15426 -j DNAT --to 10.7.55.202:15426

iptables -A forwarding_wan -p tcp --dport 15426 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 15426 --to-source 10.212.63.152

iptables -A input_wan -p tcp --dport 15427 -j ACCEPT

iptables -t nat -A prerouting_wan -p tcp --dport 15427 -j DNAT --to 10.7.55.202:15427

iptables -A forwarding_wan -p tcp --dport 15427 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p tcp -d 10.7.55.202 -j SNAT -dport 15427 --to-source 10.212.63.152

#IRLP Traffic

iptables -A input_wan -p udp --dport 2074 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2074 -j DNAT --to 10.7.55.202:2074

iptables -A forwarding_wan -p udp --dport 2074 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2074 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2075 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2075 -j DNAT --to 10.7.55.202:2075

iptables -A forwarding_wan -p udp --dport 2075 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2075 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2076 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2076 -j DNAT --to 10.7.55.202:2076

iptables -A forwarding_wan -p udp --dport 2076 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2076 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2077 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2077 -j DNAT --to 10.7.55.202:2077

iptables -A forwarding_wan -p udp --dport 2077 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2077 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2078 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2078 -j DNAT --to 10.7.55.202:2078

iptables -A forwarding_wan -p udp --dport 2078 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2078 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2079 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2079 -j DNAT --to 10.7.55.202:2079

iptables -A forwarding_wan -p udp --dport 2079 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2079 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2080 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2080 -j DNAT --to 10.7.55.202:2080

iptables -A forwarding_wan -p udp --dport 2080 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2080 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2081 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2081 -j DNAT --to 10.7.55.202:2081

iptables -A forwarding_wan -p udp --dport 2081 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2081 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2082 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2082 -j DNAT --to 10.7.55.202:2082

iptables -A forwarding_wan -p udp --dport 2082 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2082 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2083 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2083 -j DNAT --to 10.7.55.202:2083

iptables -A forwarding_wan -p udp --dport 2083 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2083 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2084 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2084 -j DNAT --to 10.7.55.202:2084

iptables -A forwarding_wan -p udp --dport 2084 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2084 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2085 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2085 -j DNAT --to 10.7.55.202:2085

iptables -A forwarding_wan -p udp --dport 2085 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2085 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2086 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2086 -j DNAT --to 10.7.55.202:2086

iptables -A forwarding_wan -p udp --dport 2086 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2086 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2087 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2087 -j DNAT --to 10.7.55.202:2087

iptables -A forwarding_wan -p udp --dport 2087 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2087 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2088 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2088 -j DNAT --to 10.7.55.202:2088

iptables -A forwarding_wan -p udp --dport 2088 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2088 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2089 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2089 -j DNAT --to 10.7.55.202:2089

iptables -A forwarding_wan -p udp --dport 2089 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2089 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2090 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2090 -j DNAT --to 10.7.55.202:2090

iptables -A forwarding_wan -p udp --dport 2090 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2090 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2091 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2091 -j DNAT --to 10.7.55.202:2091

iptables -A forwarding_wan -p udp --dport 2091 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2091 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2092 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2092 -j DNAT --to 10.7.55.202:2092

iptables -A forwarding_wan -p udp --dport 2092 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2092 --to-source 10.212.63.152

iptables -A input_wan -p udp --dport 2093 -j ACCEPT

iptables -t nat -A prerouting_wan -p udp --dport 2093 -j DNAT --to 10.7.55.202:2093

iptables -A forwarding_wan -p udp --dport 2093 -d 10.7.55.202 -j ACCEPT

iptables -t nat -A postrouting_wan -p udp -d 10.7.55.202 -j SNAT -dport 2093 --to-source 10.212.63.152

#EchoIRLP ╨ Kkasin 03-15-15

@K4PWO – I hear where you are coming from... I have some of the same concerns as well...

However, I temper my views with the knowledge that this is a 100% VOLUNTEER effort, it's not a JOB that pays them an honest wage... If it were, we would all probably expect more out of the dedicated people who had a bright idea and brought it forth for us to all marvel at and use...

Having been involved in hardware and software development professionally, it can turn into a game of “whack-a-mole” quite easily. What these guys have done is outstanding. But it is STILL in its infancy!

ALL of us are still in the experimentation stages... Everybody... It aint bullet proof yet!

I understand your frustration... I am there right along with you... But over time, things will settle down and hopefully end up where we all want to be – but it will take time...

Please don't think of this like a commercial product we all paid $199.95 for and expect everything to work the first time we plug it in. The reality is - we are taking toys (like Linksys routers) and forcing them to do things they were never really engineered to do in the first place.

I have done a lot of testing. I have a lot invested. I am one of those idiots who took their idea and slammed it against the wall to see where it would break... I see chinks in the armor and I have seen it crash and burn. I have also seen it give me web cams from the other side of the planet and work beyond my meager expectations!

But my point is, running a website, developing software, trying to support it and putting it out there for all of us to use is like juggling kittens and chainsaws – I don't expect the support of a commercial product with a corporate entity behind it... And neither should you... respectfully... :)

In another 5 years – this could be one heck of an awesome tool all of us could use. Hopefully, things will end up where we all need it to be – a reliable scalable system that allows hams to communicate in ways we never thought possible a few years ago...

I have high hopes, but I am not going to expect VOLUNTEERS to give us all something for free and expect it to be polished like a commercial product...

Bill - N5MBM

Well, to be honest...  Not that many people have jumped off the deep end and tried to tunnel in many parts of the planet either...  I am almost maxed out on the number of people I am tunneled to on one of my routers.  This is new ground for ALL of us!

A little tinkering goes a long way...

Bill - N5MBM