This is my busy part of the year, so I have not been able to keep up with this as I would have liked.
But I want to add some information and an update on possible network options to obtain faster backbone speeds.
We have presented the common equipment used in AREDN networks, but one of the issues that comes up is the fact that OLSR the protocol and handles the mesh routing is not so good for backbones and trunks.
The solution to that is the leave the backbone equipment factory and make it part 97 compliant by using callsigns as the SSID of the radio links.
Those radio links can now carry traffic at the factory rate (300mb to over 1gb depending on the equipment) and not be slowed down by OLSR. The key to passing the OLSR between node sites is using something called X-Links.
Originally designed to allow AREDN traffic to flow over public safety and other non-amateur networks, X-Links is now used to link over factory radio equipment. At the end of each path (the path may go through several links) there will be a device capable of handing X-Link traffic, the most common of which is the Mikrotik hAP-ac2 and the hAP -ac3. These devices have the CPU power to handle both regular LAN routing and tunnels and also X-Links and additionally the Supernode function used to link mesh networks but block OLSR.
As we build out the backbones they will be Pt 15 devices converted to Pt 97 by the use of the callsigns, but they will not be running AREDN. The linking of mesh networks which want a homologous OLSR domain, will be met by the X-Links routing traffic through the high speed devices. It is sort of a pipe within a pipe. Non-OLSR traffic can flow through the point links mesh traffic will to be inside the X-Links pipes.
This will allow for much higher speed of network traffic. Cameras, repeaters, VoIP applications can be routed over the high speed part of the link.
As mentioned previously, these devices can also support the supernode function, which can come in handy if an area has strong growth and wants to have a separate but connected mesh. The supernode would be activated at that site and connected to other supernodes, connections to nodes, devices, facilities and services is done as is normal using URL’s and IP addresses, with the advantage that the local mesh only list the local calls on the mesh status page.
So we have the tools and the ability to build out the network and provide mesh connectivity locally but use higher speed linking to give faster response and higher bandwidth requirements.
Over the past several months the code that resides in the local devices has had some major changes.
The user interface or GUI is totally changed. Indeed it shows more and it much more interactive.
You at a single glance can see the status of the node and you can also on that same screen see any services offered on that node site. Something the previous version did not offer.
Under the hood the new UI has actually allowed the code to speed up and it is quite perceivable.
Below is a shot of the node status screen
This is what you are presented with when you connect to a node I am going to break it down into 3 sections.
The left side has a tool bar on the left edge clicking on the AREDN Globe will take you to your home node if you have connected to another node.
The blue circle with a letter “I” in ti will refresh the node screen you are looking at.
Below is a grid clicking on that icon will take you to the mesh status screen.
Below that should be a small cloud but the link to our supernode is down so it is not visible, clicking on it will take you to the supernode server.
The last icon is a folded document clicking on it will take you to the map where your node is mapped to.
In the main screen we have Local Router Device Interface, entering here will allow you to change the node ID. There is a notes area to leave information regarding the node.
Below that is the node time, next is the up time and below that the CPU load data. Followed by Free memory and RAM.
The next entry is the firmware Rev level, it is green so it is running the latest. The next entry shows that there is 1 package running on the node. And the last entry shows the network information, showing both the Mesh and LAN assignments. Last is the map showing the location of the node. The location data maybe entered manually or you can load in a piece of code that allows the node to read the data from a USB GPS radio.
The middle section of the screen shows 3 divisions, The top is internal services, all the available services on this node, those in green are enabled those in read disabled.
Local Services are links to applications, or devices that are connected to this node. In this case a web cam, and iperfSpeed, which is used to test path speeds.
Local Devices in this case the web came is shown here. Some sites will have weather stations, databases, PBX, mail servers, WinLink servers about anything you have on the Internet we can have here.
Local Nodes shows the nodes which are linked directly to this node via wire or Device to Device (DtD)
The last entry is Neighborhood Nodes, nodes which are RF linked to this node will show up there.
This is a capture taken from the node linked to it showing the link from the granary to the South Edmond node stack, note the small “fan” to the right of the word granary, showing it is a RF link.
These entries show the link quality for both the local node “LQ” and neighbor node “NLQ” for the
wired links only other value is “Errors” Notice that the Neighborhood Node since it is an RF connection, sows SNR and N SNR or local SNR and Neighbor SNR. Also shows error rate, speed in mbps and distance.
The green button indicates that, you can return to the old UI by clicking on the button.
Next to it is a button that allows you to log into the node to modify it, also has a reboot and a help screen.
The upper half, Radio and Mesh allow you to modify the usage of the radio (or radios) in the device In this case this device has 2 radios one is setup for Mesh and the other for LAN.
The next entry Mesh shows the number of nodes on the connected Mesh (Oklahoma) and to the right the number of connected devices.
LAN DHCP shows the LAN assignments and DHCP range. Number of reserved leases and active leases. Tags and options allow for more routing options on the local LAN.
Tunnels shows any tunnels connected or not connected, there are two types the older Legacy tunnels and the newer Wireguard, Oklahoma has migrated to all Wireguard. Note this node does not have any tunnels as it is RF connected via DtD connected radios.
Unlike the old UI, this one has a lot more in a single place, you do not need to swim through pages to access common services they are all right there in front of you on the main page.
We will continue on this soon.
There is one last item I would like to mention.
The Oklahoma DMR and Digital Society has setup a gofundme account, the AREDN network is not a single group it is, like all proper networks there for all amateurs to use. We figured that the best way to go about gathering funds was to setup such a fund and promote it. We are looking for groups and individuals who want to make this work, to pitch in and help.
As the network grows, it will cross areas of responsibility of different groups each group can help in some way or another and at the same time gain use of the network by adding the needed equipment or adding to the fund so we can purchase that equipment.
The cost of equipment is not that high most of the radios we use are less than $100 and several under $50.
AREDN brings an element to amateur radio that is attractive to IT folks, something to put their skills into and add to a part of the Amateur Radio Service in a modern way.
The following link will take you to the gofundme site. Every little bit will help.
Also at this time we are actively looking for someone to handle the money and the account. I would rather not be in that position as I am active getting the radios that we use to build out these links.
If any of you would like to help in that sense please contact me at the following email:
kp4djt@gmail.com or KW5CCC at the following email oklahomadmrsociety@gmail.com
https://www.gofundme.com/f/help-ok-dmr-build-a-reliable-data-network
We want to extend the network to cover all of Edmond, and press on north to link Guthrie.
We also have a Telegram group where we discuss mostly things digital and some All* (digital backend) be most happy to have folks join up there to and get into the discussion. Here is the link to the Telegram OK DMR and Digital group: https://t.me/OK_DMR_digital
Chuck, KP4DJT
