Administrative Limitations

Security

While Muscadine isn’t strictly a secure computing resource, it lives in an enterprise secure computing environment. As such, precautions have been taken to protect Muscadine as well as the environment

SSH

SSH TCP forwarding has been administratively prohibited for security reasons. DO NOT attempt to circumvent this.

SSH pubkey authenticion has been administratively prohibited. University policy maintains that users must authenticate themselves with 2-factor security upon each login. If you find yourself authenticating more often then you’d like, read the page on Setting up SSH ControlMaster.

Networking

Muscadine does not have direct access to the World wide web. All attempts to access the outside web from muscadine or to access muscadine from the worldwide web will be blocked

Getting Files on Muscadine

Since Muscadine is in a private network, the simplest way to copy a file onto muscadine is to connect to it’s network using the HPC2 VPN and scp files to it.

First, read to “Connecting to the VPN”

Then, run

scp localfile myuser@muscadine-node-1:/path/to/myfile

This should prompt the normal password+duo authentication

HTTP Proxy

In order to facilitate basic functionally of a modern system, an HTTP proxy is afforded to Muscadine users, this allows users to do things such as:

  • git clone

  • curl/wget

  • pip install (in a venv only)

  • apptainer pull