|
|
SSH Tunnel Manager
There is one more step you can take here that's really pretty cool.
First add the -g option to your tunnel, which allows anyone on your local LAN to access the remote computer via yours. Then download Network Beacon and create a new beacon. Enter the name of the remote file server for "Service Name", choose "AppleShare Server (AFP)" from the menu for "Service Type", and the local port number you're using for the tunnel (in your example, 10548) for the "Port number". When you enable the beacon, the remote server shows up all over the local LAN as if it was a local machine (through the magic of Rendezvous/Bonjour/whatever-it's-called-now) and you can just connect to it the normal way. No more entering afp://localhost:10548 in the connection dialog. The only problem is that in my experience, -g doesn't seem to work with the -R option for reverse tunnels. I haven't had to use -R much, but in the few cases I have, I managed to kludge something together using two tunnels. Once you have the reverse tunnel going, you open another one on the local machine along the lines "ssh -gL51548:127.0.0.1:50548 127.0.0.1". Then you use 51548 instead of 50548 for the beacon. Ugly, but it seems to work. If anyone knows a better way, let me know.
SSH Tunnel Manager
The remote sshd must have
in their sshd config to permit off-box connection to a -R tunnel. Since this is a potential security hole, it's generally turned off.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|