|
Last change
on this file was 868, checked in by jts21, 10 years ago |
|
Tidy up scripts and add UDPTunnel jar, so tunnelling frameserver shouldn't require any more setup than modifying the config file (see the readme)
|
|
File size:
924 bytes
|
| Line | |
|---|
| 1 | If you're not at the uni and you want to connect to a server running on a uni machine, most likely you'll need to SSH tunnel to access it.
|
|---|
| 2 | This doesn't work for UDP connections (such as FrameShare).
|
|---|
| 3 | You could use netcat (or bash and the virtual files in /dev/tcp and /dev/udp) to pipe data from a UDP to TCP, then back to UDP again on the other end of the SSH tunnel, but I couldn't get that working (and good luck trying to do it on Windows).
|
|---|
| 4 |
|
|---|
| 5 | So, I wrote a little java program to deal with it:
|
|---|
| 6 | https://github.com/jtsymon/UDP-SSH-Tunnel
|
|---|
| 7 |
|
|---|
| 8 | Scripts for Expeditee are in dev/bin/script
|
|---|
| 9 |
|
|---|
| 10 | Edit "Frameshare-SSH-Tunnel-CONFIG.sh" to set the server port, SSH username and host
|
|---|
| 11 | Run "Frameshare-SSH-Tunnel-Client.sh" on the machine that you're running the Expeditee window on
|
|---|
| 12 | Run "Frameshare-SSH-Tunnel-Server.sh" on the machine that the Expeditee frameserver is running on (only needs to be run once and it should support all users)
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
