You are here

Tunnel server using a Raspberry Pi 3B?

19 posts / 0 new
Last post
k4pwo
Tunnel server using a Raspberry Pi 3B?
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
K5DLQ
K5DLQ's picture
We don't support the Pi's as
We don't support the Pi's as nodes within the AREDN project.
Are you referring to the limit of 10 clients and 10 servers on the node?

 
k4pwo
Clients... on a server.
Clients... on a server.
K5DLQ
K5DLQ's picture
to be clear, you are talking

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.

k1ky
k1ky's picture
Yes, Tennessee is a BIG Ocean!
We are working on getting the "buzz" going in a big way.  The other reason for this is that we have space in some big data centers and would like to use these as some alternate "backup" paths if and when needed. 
And yes, we're talking about the 10 client limit on a single node.

 
K5DLQ
K5DLQ's picture
Understood.  Thx.  How many
Understood.  Thx.  How many tunnel clients do you need?
k1ky
k1ky's picture
How many?
Darryl,
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.
kj6dzb
kj6dzb's picture
Unless the Rpi bus speed has
Unless the Rpi bus speed has increased (likely NOT) your only going to see 5mbs throu-put. For a single client tunnel. Ive built a a rpi for VPN tunnel client and found it to be a bottle neck. I upgraded the VPN tunnel to a core2 1.8 ghz cpu and a modest RAM and I dont have a bottle neck there any more. Ive mentioned few times now the need to Benchmark the performance of a Ubut Node running tunnel server. Im wainting on my the fiber to be run to my qth, so right now I cant get more than 7mbs up over my comcast so i cant conduct an A sync speed test. I know the RPi is underpowered for tunneling and there has never been a port of the tunnel server/client to any thing other than the Ubnt nodes. The VLAN tagging should port to Debian, the Tunnel server should too and OLSRD will need to be running as well, the routing table may be a problems.    

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. 







 
KG6JEI
1) if your going to profile
1) if your going to profile it should be done over a controlled Lan link into a gigabit switch (rule out the switch being a limiting factor it should be faster then the devices under test)
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.
 
KA9Q
The AREDN project may not

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.

 

KG6JEI
The above suggestions are
While the above suggestions are doable, they come with significant risk of corrupting your entire network.  I highly recommend not doing it.  The San Diego network has narrowly dodged such an event.
 
So follow these suggestions at your own risk and, as noted in another thread, don't be surprised if any non standard node needs to be removed before a support ticket will be accepted by this team.
N4CV
Reconsider Tunnel Host Server?

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.  

K5DLQ
K5DLQ's picture
It does need to be a "node"
It does need to be a "node" because it needs OLSR on it for proper routing.
WU2S
WU2S's picture
"Node"on a Raspberry Pi
If I understood him correctly, in a recent conversation Mark N2MH told me he has OLSR running on a Raspberry Pi. Maybe he can shed some light on this.
kc8ufv
kc8ufv's picture
OLSR can be manually
OLSR can be manually installed on any *nix and be manually configured to be a node. Though, it might not provide the nice web interface we typically think of a node having. This is discouraged on "production" networks, because if certain parameters in the configuration file are slightly misconfigured on one node, it can cause major routing issues in the mesh as a whole, especially in the vicinity of the misconfigured node. The configuration pages of the AREDN firmware act like a shield, making it so that such a problematic misconfiguration can't happen on a node with AREDN firmware (or even the old BBHN firmware, if you're trying to talk to something really old with a compatible firmware)
kc8ufv
kc8ufv's picture
Just because it needs to have
Just because it needs to have OLSR running and be a node doesn't mean it needs to have RF... I like the idea of a version to run on any *nix, possibly with the option to have it NOT have a RF interface, specifically to act as a tunnel server. Could simply have a node only link 1 tunnel, or if the server is local, could be DtD linked in on one interface. It'd even let someone theoretically have a VM running in a datacenter somewhere to connect lots of islands...
 
N3WTT
Could you not run something
Could you not run something such as softether as a VPN (disabling the encryption) on a raspberry pi to link multiple nodes? If not mistaken softether allows for multiple connections for link aggrigation channel bonding for better speed ( 802.3 ad ) or failover/redundancy. This may even be of use for users who do not utilize tunneling if it works with AREDN? Bonding of two 300 mbs between two location could yeild 600 mbs (theoretical) links or more .... Again if this is en possible? Not anywhere near as smart as the devs on this project.
kj6dzb
kj6dzb's picture
there is a point to be made
there is a point to be made on both sides. 

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 





 
K5DLQ
K5DLQ's picture
The public AREDN Tunnel
The public AREDN Tunnel Server is in testing now if interested.
https://www.arednmesh.org/content/aredn-official-tunnel-server-testing-a...
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer