For that matter, you could run your vpn server on your cloud machine, and run both xlxd and ambed on a local machine. Either way, the lowest overhead protocol (by a wide margin) for the VPN would be W

#thumbdv

This can certainly be done. The program is called ambed. It is part of the xlxd repository, but it can be built and installed completely separately from xlxd. Good instructions are found in the README

#thumbdv

That should work out fine. I just mentioned the Pi's because there is are quite few different guides online directing the use of a Pi. I run two: one is on a circa 2012 Dell Optiplex connected to Veri

#thumbdv

The absolute quickest and easiest way to get a a transcoding XLX reflector up an running is the N7TAE's new-xlx: https://github.com/n7tae/new-xlxd If your goal is to use YSF and DMR, then you need no

#thumbdv

You would only need 52 chips if you anticipated all 26 modules being used simultaneously. That would likely never happen. Three is four pairs is typically quite sufficient. If you only want to transco

I have used two thunbvs in my the ambed server for xlxd for about six months now. Everything has worked wonderfully. I rebooted the system running everything this morning, I when I went to start the a

#thumbdv