Test connection to Cluster - LCAS/Cluster_wiki GitHub Wiki

Some people (mainly those with a student account) complain a timeout error when trying to connect to the cluster. In order to do so, try to ping first

ping 10.5.39.159 or ping lch01

you can also check if in your route there is a 10.5.39.x address doing ip route show | grep 10.5.39.

If you don't get meaningful result, the solution is to manually add an entry to your route by

sudo ip route add 10.5.39.159 dev tun0

where tun0 represents the device associated with the VPN connection. After doing so, you should be able to ping and connect to the cluster.

IMPORTANT: the previous command should be inserted at every system login. So it would make sense to create a service starting at boot (if you want).

To find the device associated with the VPN, run either ip addr or ifconfig, and look for the entry showing a "POINTTOPOINT" network, with the IP you're given upon connecting to the VPN.

When connecting to the VPN (note the IP given at the end is the one seen in the output of ifconfig):

Connected to 194.80.55.3:443
SSL negotiation with remote.lincoln.ac.uk
Connected to HTTPS on remote.lincoln.ac.uk
Got CONNECT response: HTTP/1.1 200 OK
CSTP connected. DPD 30, Keepalive 20
Set up DTLS failed; using SSL instead
Connected as 10.2.19.25, using SSL

ifconfig (trimmed):

tun0: flags=4305  mtu 1287
        inet 10.2.19.25  netmask 255.255.255.255  destination 10.2.19.25
        inet6 fe80::6a48:4bee:8f37:7223  prefixlen 64  scopeid 0x20
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 22291  bytes 2946066 (2.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 26593  bytes 1862390 (1.8 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

In this example, the device is tun0.

⚠️ **GitHub.com Fallback** ⚠️