Showing posts with label WRT54G MESH. Show all posts
Showing posts with label WRT54G MESH. Show all posts

Setting up Asterisk on a Raspberry Pi for use on a Broadband-Hamnet(TM) mesh network

Setting up Asterisk on a Raspberry Pi for use on a Broadband-Hamnet(TM) mesh network


AREDN Project - Amateur Radio Emergency Data Network

AREDN Project - Amateur Radio Emergency Data Network

Mesh technology has been around for ten years or more. Over the past two years a team of developers has advanced the art by porting Broadband‐Hamnet’s extremely popular mesh firmware to the Ubiquiti airMAX line of commercial Wireless ISP routers and expanded its utility across a wide range of microwave bands. This has literally changed the complexion of mesh technology from an experimental, hobby‐oriented, novelty into a viable alternative network suitable for restoring some degree of Inter/intra‐net connectivity “when all else fails.”

In the midst of this work the AREDN Project was kicked off to focus development on taking this technology to the next level in EMCOMM communications.

This paper [2] begins with an introduction to the AREDN Project and mesh networking and concludes with a roadmap for the Project’s future. It dives into implementation techniques and aggressive plans to implement across broad portions of the Southwestern US.

http://hsmm-meshubiquiti.blogspot.com/

AREDN Project

AREDN Project - Amateur Radio Emergency Data Network

BTW: you may want to look at the AREDN group if you plan on doing anything with Ubiquiti gear as that is where all the BBHN developers have move to and are no longer developing the BBHN firmware. Channel -2 support for example is in the latest beta but Linksys gear can't handle it.

Formation
The AREDN Development Team was formed February of 2015 by former members of the BBHNDev team interested in making mesh software work for the needs of Amateur Radio Operators and emergency networks. The AREDN™ work is based on the experiences and skills gained working on the BBHNDev team.

Group Mission
To provide the Amateur Radio Community with a quality solution for supporting the needs of high speed data in the Amateur Radio and Emergency Communications field.

http://www.aredn.org/about-us
http://hsmm-meshubiquiti.blogspot.com/

Broadband Hamnet from HSMM-Mesh node is up and running

Broadband Hamnet from HSMM-Mesh
Now what? - Some ideas on what to do AFTER your node is up and running.
 
[After answering many of the same questions of newbies in email, I put this together to give a few folks an idea of what's in store...]

If you are like me, you found out about this mesh stuff and thought this might be an interesting tool... You saw possibilities. You thought, yeah, this is what TCP/IP packet SHOULD have been!

If you are like me, you hunted down some gear, you figured out which software to download, you leaned how to get inside the box and re-flash the firmware – and voila! You are almost there! You click update and cross your fingers...

MESH how do you deploy and finance in a city?

We have started to create a mesh in our city.  Some significant issues.  The terrain (especially with tall buildings) means we need lots of nodes for infrastructure. I am getting a strong 'have you build it yet' from the local ham population.

How have other areas financed (or convinced the local hams) to be involved (AKA donate kit) ?

Unlike a repeater which only needs 2 or 3 guys to do EVERYTHING, a mesh needs to be a community project.  What if the community is not ready? Do we cancel and use the existing kit for other purposes or keep pushing slowwwwwly forward? Even when we setup the packet nodes & PBBS 25 years ago, it was only a few hams that really got involved.

Any words of wisdom are welcomed.  Even doom and gloom are welcomed. Will the mesh catch on with the general ham population or is this going to be the pet project of a select few?

How many MESH nodes in local network

I am wonder haw many nodes you have in local networks ? and how many hops ?

I am asking about this because we have see that in Mesh network bandwidth changing with follwoing

    1 hop - 50% of the possible bandwidth.
    2 hops - 25% of the possible bandwidth.
    3 hops - <10% of the possible bandwidth.
    4 or more hops - it stabilizes at 7% of the available bandwidth.

How to solve problem bandwidth with many nodes in local network  ?

How to use HotPlug for SES and Reset buttons

How to use HotPlug for SES and Reset buttons
On the WRT54G, GL, and GS models there are both a Reset and a Secure Easy Setup (SES) button. The SES button is behind the Cisco/Linksys logo on the left front panel while the reset button is recessed into the back side between the WAN jack and the nearest antenna. Actually, WRT54G versions 1.0 up to version 2.2 are excluded because they do not have the SES button.
What we're doing is having shell scripts executed whenever a given event occurs, such as pressing the SES or Reset buttons.
To do this we first remove or comment out the following lines from the file "/etc/hotplug2-init.rules":
SUBSYSTEM ~~ button {
 exec kill -USR1 1 ;
}
These lines are not needed and may interfere with our scripts.
Next, create the directory "/etc/hotplug.d/button". This is where our button scripts will go.