Shell

Beta Test. Please give feedback.

Usage

Simply use SSH to login to this machine:

ssh  user@shell.stud.informatik.uni-goettingen.de

Note that the intially presented banner contains something like

#######  shell.stud.informatik.uni-goettingen.de - login vm: shell5.cip.loc

...telling you the actual local name of the automatically chosen destination machine.

For Windows: use PuTTY (simple) or Cygwin (more complex and powerful) or any other SSH-implementation.

Target audience

These machines are meant to be used by students. But of course they can be used by any staff members! (For first time users: the only requirement is to logon one single time using one of the (physical) pool computers in our building - this will make you a "known user" to our systems.)

Load Balancing

This term is misleading on this specific installation: the default algorithm being used is simply "round-robin" - you'll get connected to the "next" machine one after another. If you landed on an overcrowded system simply disconnect/reconnect to use another machine.

Legacy login.stud

Both login.stud.informatik.uni-goettingen.de and login.informatik.uni-goettingen.de (for staff only) are not affected by this new approach. These "old" machines will continue to work unmodified.

Timeout

• The session Timeout is set to 36 hours -- this is the HAproxy related Timeout regarding the TCP connection
• Kerberos/OpenAFS have separate/shorter timeouts. You need to kinit && aklog when you're approaching timeout

Self defense of the servers

Rate Limiting

Usually we do utilize "fail2ban" to chase brute force attacks by bad guys trying to hack login credentials. For technical reasons this is not possible for this "haproxy" approach. The workaround is:

We do limit the rate of new ssh- (tcp-) connections from any given source IP address to 1 per minute.

When you're going to login via ssh you usually have three tries to enter your password. Technically this is just one single connection! The next three tries come with the next connection, which is only possible after one minute. Trying to to log in too early gives just a generic error message:

~# ssh username@shell.stud.informatik.uni-goettingen.de
ssh_exchange_identification: read: Connection reset by peer

This behavior should be fine for most users where each one has a different IP address than other people.

If you are a group of students behind NAT this could be a problem. We need yet to find out if this might be a problem for students residential establishment in Göttingen.

Additionally...

If you have problems to login take a look at this page. Probably we will limit access by further means soon...

Tips 'n' Tricks

Connect to a specific machine

Circumventing the Round-Robin mechanism is possible: connect to a specific port 42000+n with n={1..6} :-)

For machine number 4:

~$ ssh -p 42004 username@shell.stud.informatik.uni-goettingen.de
#######
#######  shell.stud.informatik.uni-goettingen.de - login vm: shell4.cip.loc

Todo

• Testing! -- current state considered "BETA"
• make Status Information publicly available

See also

• Remote Access
• Long Running Processes

Links

• ...