Connecting to the Linux lab machines

For help email: uwbit@uw.edu

Unlike the Windows lab, where the only way to use the machines is to be physically present in the lab, there are a number of ways to use the machines in the Linux lab.

With all of the following methods, your username and password are your UW NetID username and password, the ones you would use when logging in to MyUW.

Please note that you need to use the Husky Onnet VPN service if you are trying to connect to remotely login to a lab machine outside campus (e.g. from your home or work.)

More info: https://itconnect.uw.edu/connect/uw-networks/about-husky-onnet/

Remote lab machine access

From Windows machines

At first, please install Husky Onnet VPN on your machine, and then launch the Huskyonnet VPN to connect to UW network. Once connection to UW network is established, you can download an SSH client program: either PuTTY SSH or MobaXterm is fine.

Remote lab machines:

There are 12 machines available for students and faculty to use: csslab1.uwb.edu all the way to csslab12.uwb.edu. The NFS file space is limited to 2 GB/user.

On the latest Windows 10 with the latest patch, please go to the command line and type ssh yourUWNetID@csslab1.uwb.edu all the way to ssh yourUWNetID@csslab12.uwb.edu.

You can also open your SSH client program and type in the machine information to connect to.

To end ssh connection: Type exit or log out.

Faculty research machines:

There are 4 machines exclusive for faculty to use: csslabr1.uwb.edu all the way to csslabr4.uwb.edu. The NFS file space is limited to 2 GB/user. There is extra space for faculty members: cd /faculty/faculty

Faculty can access these machines as the same as accessing other lab machines.

To end ssh connection: Type exit or log out.

Accessing UDrive data

https://itconnect.uw.edu/wares/online-storage/u-drive-central-file-storage-for-users/

You can use SFTP to access UDrive data. The SFTP client is installed by default on the Windows, Mac and Linux Lab, and provides an FTP-like get/put command interface to transfer files. To make a connection use the following command:

sftp your-uwnetid@sftp.udrive.uw.edu:udrive
You will be prompted for your UWNetID and password. See the SFTP manual page for further instructions (man sftp).

From Mac / Linux machines

At first, please install Husky Onnet VPN on your machine, and then launch the Huskyonnet VPN to connect to UW network. Once connection to UW network is established, you can use the Terminal application on a Mac (found in Applications → Utilities) to get a command line. Most Linux distributions also have a Terminal application. From the command line, you can connect to the Linux lab using the following command:

Remote lab machines:

ssh yourUWnetID@csslab1.uwb.edu all the way to ssh yourUWnetID@csslab12.uwb.edu

Use your own UW NetID, not netid, in that command. That will connect you to one of the machines. If there is a specific machine you want to connect to (if you saved a file in /tmp instead of your home directory, for example), you can do that by specifying that particular machine in the command:

ssh yourUWnetID@csslab4.uwb.edu

That would connect you to machine 4.

To end ssh connection: Type exit or log out.

Faculty research machines:

ssh yourUWnetID@csslabr1.uwb.edu all the way to ssh yourUWnetID@csslabr4.uwb.edu

To end ssh connection: Type exit or log out.

Accessing UDrive data

https://itconnect.uw.edu/wares/online-storage/u-drive-central-file-storage-for-users/

You can use SFTP to access UDrive data. The SFTP client is installed by default on the Windows, Mac and Linux Lab, and provides an FTP-like get/put command interface to transfer files. To make a connection use the following command:

sftp your-uwnetid@sftp.udrive.uw.edu:udrive
You will be prompted for your UWNetID and password. See the SFTP manual page for further instructions (man sftp).

Connection Warnings

The first time you connect to a system using ssh from any given machine, you may encounter a warning such as this:

The authenticity of host 'uw1-320-10.uwb.edu (69.91.198.161)' can't be established.
RSA key fingerprint is 9d:03:dd:3f:19:a0:19:d3:22:6a:33:93:c4:9e:2d:b5.
Are you sure you want to continue connecting (yes/no)? Type in yes

SSH uses public key cryptography to ensure that when you connect to a machine, your session is not hijacked by an attacker. By verifying the fingerprint your ssh client is asking about against a list of known fingerprints, you can know that your connection is going to the machine you think it is. Most people skip this step and just accept any fingerprints their ssh client asks them about.

Graphical ssh clients such as PuTTY may display a dialog about the key fingerprint. Most will ask if you want to save the key for future use. This is generally a good idea, since it means you don't have to see the message every time you connect.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@              WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!                    @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:2mnui10y7jn99/kkkkkkyjfrewwwwwerer.
Please contact your system administrator.
Add correct host key in /users/username/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /users/username/ .ssh/know_hosts:15
ECDSA host key for something@uwb.edu has changed and you have requested strict checking.
Host key verification failed.

From the command line: Type

$ ssh-keygen -R [hostname or IP address]
So you would type in like the following:

$ ssh-keygen -R hostname.uwb.edu

Remote graphical environment

In-person lab machine access

The CSS Linux Lab is located in UW1-320. Access is controlled by a Husky Card reader; if your card doesn't unlock the door, please see: https://www.uwb.edu/safety

Logging In: There are 15 desktop Linux systems in the lab, not counting the podium machine. When you log in to a machine directly by being physically present at the machine, you are said to be “on the console”. If a particular machine is free, you will know by the red login screen asking for a password. If the screen is blank, wiggle the mouse or press a key on the keyboard to disable the screen saver. If someone else is logged into the machine, please don't just sit down and start using it. They should have locked the screen when they got up, but not everyone remembers to do that every time.

Use your UW netID and password here without the domain name FOR example: bobross1 AND NOT bobross1@uw.com

Locking or Logging Out: You can lock the screen by clicking the “System” menu and clicking the lock button. If you are done using the computer, you can logout from this menu as well.

Please do not remove network cables, keyboards, mice, power cables, or any other cables or peripherals from machines in the Linux lab. Do not press the power button or control-alt-delete except as a measure of last resort.

Access NFS file space for in person lab: Please logon to the new remote lab at least once first to set the NFS home space. Once logon using your UWNetid with out the @.

$ YourUWnetID@uw1-320-02p ~]$ To access NFS follow below:
$ ls
$ B 
$ cd B
For NFS file space, it is limited to 2 GB/user

UW U drive UW Uware(software) Husky Onnet VPN WinSCP QSC tutors Matlab

Writing High Quality C++ Code

In order to write high quality C++ code, we need to make use of some existing tools.

Navigation

The best way to find something here is to use the search box in the upper right or the site index link below.

Print/export
Mobile QR Link