filer:remote
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
filer:remote [2007/08/02 12:32] – cangiani | filer:remote [2023/10/09 14:28] (current) – admin | ||
---|---|---|---|
Line 6: | Line 6: | ||
The firewall **does not allow to connect to a protected internal server or workstation**. Nevertheless, | The firewall **does not allow to connect to a protected internal server or workstation**. Nevertheless, | ||
\\ | \\ | ||
- | Once the tunnel si estabilished, | + | Once the tunnel si estabilished, |
\\ | \\ | ||
\\ | \\ | ||
- | ===== Tunneling | + | ===== Digging the tunnel |
- | The tunnel can be created using the [[wp> | + | The tunnel can be created using the [[wp> |
\\ | \\ | ||
Some of our services are restricted also to machines that are not within our subnet so, for example, you will not be able to mount your home directory via NFS even if you're using the EPFL VPN client. | Some of our services are restricted also to machines that are not within our subnet so, for example, you will not be able to mount your home directory via NFS even if you're using the EPFL VPN client. | ||
- | |||
- | \\ | ||
\\ | \\ | ||
===== SSH tunnel through our Access Servers ===== | ===== SSH tunnel through our Access Servers ===== | ||
- | We have few servers that can be reaced from outside the firewall. They can be used as gateways to the internal EPFL network by anyone having a valid account on our cluster. | + | We have few servers that can be reaced from outside the firewall |
Every lab has a Access Server that should be used preferably: | Every lab has a Access Server that should be used preferably: | ||
Line 26: | Line 24: | ||
| lthi | lth.epfl.ch | | | lthi | lth.epfl.ch | | ||
| lthc | lth.epfl.ch | | | lthc | lth.epfl.ch | | ||
- | | lcm | lth.epfl.ch | | + | | linx | lth.epfl.ch | |
- | | licos | licos.epfl.ch | | + | | smils | lth.epfl.ch | |
- | | algo | clusteralgo.epfl.ch | | + | |
- | | arni | clusteralgo.epfl.ch or licos.epfl.ch | | + | |
- | \\ | + | |
\\ | \\ | ||
+ | To connect via ssh to a specific (protected) machine, you need first to connect to the access server, and then from this to your actual destination. | ||
+ | |||
+ | Ssh can also be used to create secure tunnels for all other protocols, see [[ssh-remote: | ||
==== Ssh client ==== | ==== Ssh client ==== | ||
Line 39: | Line 37: | ||
The connection made by ssh protocol are encrypted, so nobody can sniff what you are doing. **No clear-text connections (telnet)** is accepted by our machines. | The connection made by ssh protocol are encrypted, so nobody can sniff what you are doing. **No clear-text connections (telnet)** is accepted by our machines. | ||
\\ | \\ | ||
- | At **[[ssh-remote: | + | At **[[ssh-remote: |
- | + | ||
- | ===== Dig a tunnel ===== | + | |
- | Because of the firewalls the servers of EPFL network aren't directly accessible from Internet, but using the ssh protocol you can create one or more tunnel so you can connect directly from your local computer to all our server here in Lausanne. Just connect to the Access Server activating the tunnel option and you can login on the others servers of the network. look [[ssh-remote: | + |
filer/remote.1186050761.txt.gz · Last modified: 2007/08/02 12:32 by cangiani