MESH CHAT: MESSAGING FOR AREDN MESH NETWORKS
MESH CHAT: MESSAGING FOR AREDN MESH NETWORKS
http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/
Live Map
http://usercontent.aredn.org/K/5/K5DLQ/livemap.html
http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks/
Live Map
http://usercontent.aredn.org/K/5/K5DLQ/livemap.html
Ubiquiti Nanostation m2 repair AREDN Mesh software
Ubiquiti Nanostation m2 repair AREDN Mesh software
The Amateur Radio Emergency Data Network (AREDN)
the AREDN Project released to its team of volunteer testers, a new beta-version of its upcoming release, v3.15.1.0. This is the most significant and important release since this development team introduced support for the Ubiquiti AirMax line of hardware back in 2013.
Here is a list of some of the new features:
Over the air, remote firmware upgrades – this allows node owners to upgrade a node’s firmware release without going out to the site. It accomplishes this by saving the node’s configuration settings and automatically reloading them after the upgrade has taken place.
Support for NanoStation M5 with the new XW boards – many have purchased these devices unaware that Ubiquiti made a hardware change to the product which rendered it unusable with AREDN firmware… up until now.
Support for the Rocket M3, NanoStation M3, and NanoBridge M3 – This is our first release supporting devices in the 3.4 GHz ham band. This band has no commercial allocations in the U.S. and as a result should be ultra-quiet. We are excited about breaking into this band and what it could mean for this technology.
Here is a list of some of the new features:
Over the air, remote firmware upgrades – this allows node owners to upgrade a node’s firmware release without going out to the site. It accomplishes this by saving the node’s configuration settings and automatically reloading them after the upgrade has taken place.
Support for NanoStation M5 with the new XW boards – many have purchased these devices unaware that Ubiquiti made a hardware change to the product which rendered it unusable with AREDN firmware… up until now.
Support for the Rocket M3, NanoStation M3, and NanoBridge M3 – This is our first release supporting devices in the 3.4 GHz ham band. This band has no commercial allocations in the U.S. and as a result should be ultra-quiet. We are excited about breaking into this band and what it could mean for this technology.
Setting up a MESH Node with AREDN Firmware
Setting up a MESH Node with AREDN Firmware
In this episode, I will walk you through the process of setting up a new Ubiquiti Node from scratch, and flashing it with the latest AREDN firmware. Then we will connect it to another node and look at the channel options on the firmware itself.
In this episode, I will walk you through the process of setting up a new Ubiquiti Node from scratch, and flashing it with the latest AREDN firmware. Then we will connect it to another node and look at the channel options on the firmware itself.
Mesh Tunnels Nodes
Mar 31, 2015
For those that are unfamiliar with the relatively new tunnel feature that is supported in versions 3.0.1, 3.0.2 of BBHN, and version 3.1.0 of the AREDN firmware, perhaps this information will be helpful.
The basic idea is to provide an alternate path via the Internet as a substitute for a RF path. Hopefully this will be used as a temporary solution. A basic concept of an independent, free standing mesh network is to provide connectivity when the Internet fails. So why would you want to connect with the Internet in the first place?
One reason is to connect "mesh islands"; two or more established mesh networks that are isolated from each other by a long or difficult RF path. Perhaps this path will be achievable in the future with some intermediate nodes. In the meantime, an Internet tunnel can be used to connect the networks. A mesh network in the far West Valley wanting to connect to an East Valley network would be an example.
The basic idea is to provide an alternate path via the Internet as a substitute for a RF path. Hopefully this will be used as a temporary solution. A basic concept of an independent, free standing mesh network is to provide connectivity when the Internet fails. So why would you want to connect with the Internet in the first place?
One reason is to connect "mesh islands"; two or more established mesh networks that are isolated from each other by a long or difficult RF path. Perhaps this path will be achievable in the future with some intermediate nodes. In the meantime, an Internet tunnel can be used to connect the networks. A mesh network in the far West Valley wanting to connect to an East Valley network would be an example.
Subscribe to:
Posts (Atom)