He is right, James. I might add that if you get things working on the command line there is a config file that you can setup the ports you want to connect every time you ssh into a host. That means you don't have to remember a long commplicated command a mile long.
Frederick On Thu, 25 Oct 2012 01:11:19 +0200, Cowboy <[email protected]> wrote: > On Tuesday 23 October 2012 04:10:10 am James Harrison wrote: >> Since most outside broadcasts want talkback functionality anyway, I want >> to implement firewall/NAT tunneling to get around the same problem on >> the transmitter end (because you need an audio link from RX to TX for >> talkback), which essentially involves the transmitter punching a tunnel >> to the receiver that the receiver then passes audio over. > > ssh > Read up on the -L option. ( port redirection ) > You can send most anything via the encrypted channel, both ways, > and need only one open port on one end to initiate the connection. > I use it all the time for other purposes. > > You don't even need a static IP, but you do need a domain name > that can track dynamic DNS in that case. > -- Frederick Henderson Wetzikerstrasse 25 CH-8344 Bäretswil Switzerland +41 32 510 11 63 +41 76 295 26 67 Cell +1 (724) 726-1460 Take the pledge! http://www.emailetiquettepledge.com/take-the-pledge This email sent from Opera's revolutionary e-mail client, http://www.opera.com/mail/ and typed on the Dvorak keyboard. http://dvzine.org Want to learn a new language the way you learned your first? Try LingQ for free! ==> http://www.lingq.com/?referral=frederickjh _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
