Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How much software and/or networking knowledge do you have?
If it were me, I would make RPi 2 the "server" and RPi 1 the "client" (since RPi 2 is remote). I'd write a little C program to open up a TCP/IP port on RPi 2, listen for commands, and take the appropriate actions with the relays. I'd write another little C program to connect to said port from RPi 1 and issue commands based on the switches. They would be able to freely communicate with each other using whatever handshaking or command structure you want over the TCP/IP socket.
Since RPi 2 will be remote, you can use one of the RPis to autonomously open an SSH tunnel to the other one to allow the TCP/IP connection through an encrypted and protected SSH tunnel. Unless you can give a static public IP to one of the RPis, you'll likely still need to set up port forwarding in the router on one of the ends, and possibly set up a Dyn DNS domain so you don't have to worry about DHCP updates from the ISP.
As for the audio, I don't know the details of these sound cards, but I'm sure there'd be a way to get them to pass data to each other through either the same or a separate TCP/IP socket or SSH tunnel as above.
Last edited by suicidaleggroll; 01-31-2017 at 06:45 PM.
There is lots of software and ways to do it. About the only thing specific I have seen for the pi is echolink but it should be possible. Is this for hf or vhf/uhf? Does the radio have a remote control port?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.