[[Include(WikiToC)]]
== 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: \\
{{{#!div style="font-size: 100%"
  {{{#!shell
  ssh USERNAME@gw.cosmos-lab.org
  }}}
}}}
=== Access to Consoles
The [wiki:UserGuide/RemoteAccess/Console domain consoles] can be accessed the same way as the gateway (above), with the following differences:
{{{#!div style="font-size: 100%"
  {{{#!shell
  ssh USERNAME@console.DOMAIN.cosmos-lab.org
  }}}
}}}
* Consoles can '''ONLY''' be connected to a current (and approved) [wiki:GettingStarted#MakeaReservation reservation].
* In addition to home directories access and computing/running scripts, consoles can run [http://omf.orbit-lab.org OMF] commands to [wiki:Resources control resources] within their [wiki:Architecture/Domains domain].
* Consoles share a [wiki:Architecture/Network#ControlPlane Control Network] with [wiki:Resources resources] within their [wiki:Architecture/Domains 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 [https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump ProxyJump], the following is recommended:
* SSH into your domain console.
* Use [wiki:UserGuide/OmfQuickStart 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:
{{{#!div style="font-size: 100%"
  {{{#!shell
  ssh -X USERNAME@console.DOMAIN.cosmos-lab.org
  }}}
}}}
{{{#!div style="font-size: 100%"
  {{{#!shell
  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 [https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump ProxyJump] if you have a current and approved reservation. Your resource also must be turned on beforehand.

{{{#!div style="font-size: 100%"
  {{{#!shell
  ssh -J USERNAME@console.DOMAIN.cosmos-lab.org root@RESOURCE
  }}}
}}}

* Use additional [https://man7.org/linux/man-pages/man1/ssh.1.html 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:
* [wiki:UserGuide/RemoteAccess/SSH#ConfiguringSSHKeys Configuring SSH keys page]
* [wiki:UserGuide/RemoteAccess/SshTunnel#SshTunnel SSH X11 tunneling page].
* [wiki:UserGuide/RemoteAccess/SshTips#tips SSH tips page].

=== Access via Third Party Software

* Chrome Remote Desktop setup [wiki:UserGuide/RemoteAccess/ChromeRemoteDesktop page].
* [wiki:./TigerVNCServer&Client TigerVNCServer&Client]


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

* [wiki:UserGuide/RemoteAccess/VPN#setup VPN setup page] for client set up info.

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

* For our recommends parameters, see [wiki:UserGuide/RemoteAccess/VPNpersist#sitetosite site-to-site] that will need to be customized per-connection.
* Please [https://winlab.rutgers.edu/contact/ contact us] for more information.