Remote Access

Access to User Account and Files

Users without a reservation can always access their account's home directories, files, and BASH scripts through SSH by connecting to:

ssh USERNAME@gw.cosmos-lab.org

Access to Consoles

The domain consoles can be accessed the same way as the gateway (above), with the following differences:

ssh USERNAME@console.DOMAIN.cosmos-lab.org

• Consoles can ONLY be connected to a current (and approved) reservation.
• In addition to home directories access and computing/running scripts, consoles can run ​OMF commands to control resources within their domain.
• Consoles share a Control Network with resources within their domain.

Access Resources via Console

Resources can only be accessed by running commands from a console or by establishing a connection through the console. For people unfamiliar with ​ProxyJump, the following is recommended:

• SSH into your domain console.
• Use OMF commands to
  • Turn resources on/off
  • Load and save images
  • Run OEDL Scripts with OMF exec
• Open an interactive session wtih SSH from a console to compute resource.
• Use SSH w/ X11 Forwarding to view a graphical window from a resource on your local machine.
  • REMINDER: you can only SSH w/ X11 by adding argument -X or -Y to every SSH command.
• Example:

  ssh -X USERNAME@console.DOMAIN.cosmos-lab.org
  

  ssh -X root@COMPUTE_RESOURCE
  

Access to Resources Directly

This is a convenient only if bridging through the console adds unacceptable overhead or difficulty to your use case. You can only ​ProxyJump if you have a current and approved reservation. Your resource also must be turned on beforehand.

ssh -J USERNAME@console.DOMAIN.cosmos-lab.org root@RESOURCE

• Use additional ​SSH manual/arguments to automate the connection through the console.

Access Tips w/ SSH

The prominent method of connecting to the testbed is via SSH. The SSH protocol is quite powerful, allowing interactive shell sessions, file transfers, port forwarding, and even graphical displays if configured properly with other utilities. Please consult for further help:

• Configuring SSH keys page
• SSH X11 tunneling page.
• SSH tips page.

Using Chrome Remote Desktop

See Chrome Remote Desktop setup page.

Using a VPN

In cases where SSH is insufficient or inconvenient, an IPSEC VPN is available.

See VPN setup page for client set up info.

Common cases include:

• A need to tunnel many, or ephemeral ports.

Site to Site Connection

If you have a need to bridge a remote network with the testbed, this must be arranged with the testbed maintainers manually. This is usually done to provide connectivity between a Vendor's test device and some testbed experiment, or in case of special demo requirements.

See site-to-site for our recommended connection parameters, that will need to be customized per-connection.

Please contact us for more information.