Posted: 6/26/2014 4:18:32 PM EDT
|
I apologize in advance. I tried about 4 times to make a video but the only device I had available was my phone, and it refused to work correctly and focus. Maybe if there is enough demand at field day I can get a famous YouTuber to give me a hand.
This is a simple solution to a remote shack. I don't know if it would work with Windows. It will work on Mac and Linux though. Step 1) Have a digital station already setup. Got it? Good. Step 2) Plug that station into a network and make sure you have ssh enabled Step 3) Connect remote laptop to network Step 4) On laptop issue ~$ pax11publish -r ~$ ssh -X user@host Step 5) launch fldigi and flrig Step 6) Enjoy 
And who might my first remote shack digital QSO be with? 
CO4SM IOTA NA-056
Sorry for the cruddy pics but after 4 video attempts I was a little frustrated. |
|
Quoted:
Linux is cool Quoted:
Quoted:
Love that screensaver. Used to run it 10 years ago when I though Linux was cool. Linux is cool Doesn't make me money. Linux is free (mostly). So is my MSDN subscription. I have spent plenty of time writing apps in Java and batch scripts for Linux. I much prefer C#. And please don't tell me I can run Visual Studio efficiently over Linux. |
| On the Windows side same thing except use RDP (fastest), VNC (middle of the road) or something like Teamviewer (slowest) to accomplish the same thing. Or, if you want to run phone, use Remaud. |
|
You might take a look at my post in this thread:
http://www.ar15.com/forums/t_10_22/673898_Operating_a_remote_station_over_the_Internet.html Mod's: maybe there should be a sticky thread for remote op's? This is the third relevant thread in a week. |
|
Quoted:
You might take a look at my post in this thread: http://www.ar15.com/forums/t_10_22/673898_Operating_a_remote_station_over_the_Internet.html Mod's: maybe there should be a sticky thread for remote op's? This is the third relevant thread in a week. Wow I remember that thread but I guess I stopped reading it before your write up. |
|
You can make it even more responsive if you change the SSH Cipher to arcfour128 or arcfour256. It's a more network efficient.
Add something like the following to your ~/.ssh/config (with the correct hostname/ip substituted) Host my.remotemachine.com Ciphers arcfour256, arcfour128 Also, if you use -C in addition to -X when you ssh, then ssh will compress the packet data prior to encrypting and putting it on the wire. This is only good if you're connecting to a machine with enough processor overhead so that the further compression doesn't slow anything down. It's not a good option if you're connection to a pi, for example. |
|
Quoted:
You can make it even more responsive if you change the SSH Cipher to arcfour128 or arcfour256. It's a more network efficient. Add something like the following to your ~/.ssh/config (with the correct hostname/ip substituted) Also, if you use -C in addition to -X when you ssh, then ssh will compress the packet data prior to encrypting and putting it on the wire. This is only good if you're connecting to a machine with enough processor overhead so that the further compression doesn't slow anything down. It's not a good option if you're connection to a pi, for example. Quoted:
You can make it even more responsive if you change the SSH Cipher to arcfour128 or arcfour256. It's a more network efficient. Add something like the following to your ~/.ssh/config (with the correct hostname/ip substituted) Host my.remotemachine.com Ciphers arcfour256, arcfour128 Also, if you use -C in addition to -X when you ssh, then ssh will compress the packet data prior to encrypting and putting it on the wire. This is only good if you're connecting to a machine with enough processor overhead so that the further compression doesn't slow anything down. It's not a good option if you're connection to a pi, for example. I just learned about this not to long ago. I have not tested it yet. |