Is it possible to use a Raspberry Pi 3B as a tunnel server for ARDEN nodes? If so, which VLAN should it be on and any configuration guidelines would be greatly appreciated.
I'm trying to get past the client limits with the nodes acting as servers.
Perry K4PWO
I'm trying to get past the client limits with the nodes acting as servers.
Perry K4PWO
Are you referring to the limit of 10 clients and 10 servers on the node?
to be clear, you are talking about the 10 client limit on the node. right?
That's a lot of "mesh islands" you are trying to build out.
And yes, we're talking about the 10 client limit on a single node.
As many as are practical without degrading performance. 30-100? (I like to push the limits!)
I figure if we have a powerful enough computer behind it - should be able to handle a big load since that is about all if will be doing. Internet bandwidth won't be an issue as we will have Gigabit + bandwidth available at the server sites.
I would also like to pursue the ability to "choose" priority on MESH nodes of which mode (RF vs Tunnel) is the primary. There will probably be many cases where I would like the RF path to be primary.
Also while I'm at it - can you fix the display of the Tunnel Client fields to display the maximum allowable characters so my screen shots will capture "all" of the node information on the Tunnel Client and Server screens? (I may have mentioned this before in the "bug/wishes" area on the forum.
Thanks,
T.D.
Olsrd is not going to select an RF link over a DTD link. the costs is less in the first place. That said read https://github.com/OLSR/olsrd/blob/master/README-Olsr-Extensions you may be able to tweek the etx algorithms for smart gateway.
2) tunnels also work on TPLink Devices
A reminder tunnels are NOT intended to be high performance links, they are temporary system joiners, low CPU intensive solutions were chosen but in depth profiling hasn't been done because they are not intended to be high performance.
The AREDN project may not formally support non-Ubiquiti nodes, but you can still easily interoperate with them using the Raspberry Pi or any other Linux or Unix-like system. This includes building tunnels, running clients and servers, etc.
The core component of an AREDN (or BBHN) node is olsrd, the Optimized Link State Routing daemon. This is not unique to AREDN or BBHN, and in fact it comes from outside ham radio where it has been used to build ad-hoc WiFi mesh networks in many countries. It has been widely available as open source for years, and it even has its own Wiki: http://www.olsr.org/mediawiki/index.php/Main_Page
Debian-like systems (including Raspbian) provide olsrd as a package, naturally enough named 'olsrd'.
You do have to know what you're doing, as you will have to write your own configuration file that will follow the conventions of the local mesh network and avoid causing it any trouble.
The recent discussions of the release candidate firmware have raised concerns about the base AREDN functionality requiring more memory resources. The development team has politely reminded us that best practices are to offload applications like mesh chat to an external host. Could we revisit the discussion of (officially) offering a tunnel host server external to the mesh radio hardware? As K4PWO and K1KY noted above, this could be hosted on a Raspberry Pi or more robust Linux system, provided a reliable internet connection, and allow mesh devices to tunnel in as clients. There wouldn't be a need to have this host act as a node in the mesh network (show up in the mesh status view), only provide a common point to bring tunnel clients together.
There could be value in supporting hEX PoE or hEX. or hEX-s ? looks to be supported in openwrt?
Looking thru the Git last night, I had thoughts. Thant the OLSRD conf broken up in a few places. Could we branch the project to explore, olsrd v1 vs v2 evaluation?
The https://github.com/urlgrey/hsmm-pi project is still posted!!! The vlan port tagging configuration should work the same in the debian Buster environment. I would suggest you pull the OLSRD conf from the current release. There has been no change in the way OLSRD attaches. With OLSRD v1 attached to the proper vlan interface it should DTD with a Node. There is an olsrd status page too just needs to be turned on.
I dont know how to the Vtun server could transfer over...?
73
https://www.arednmesh.org/content/aredn-official-tunnel-server-testing-a...