Version 17 (modified by 5 years ago) ( diff ) | ,
---|
Site Navigation
Remote Access
To User account and Files
Users with an account can always access their Home Directories, and files, and run basic scripts, by connecting to ssh YOUR_USERNAME@gw.cosmos-lab.org
Detailed Instructions are at Connecting to a Console
To Consoles
The consoles can be connected to the same way as above, with the following differences:
- Consoles can be connected to only during a Getting Started.
- Consoles can run OMF commands to control Resources within their Domain
- Consoles share a Control network with Resources within their Domain
To Resources via console
- Resources can be interacted with by running commands from a Console.
- For example:
- Using OMF commands to
- Turn resources on/off
- Load and save images
- Run OEDL Scripts with OMF exec
- Use SSH from a console to open an interactive session with a compute resource.
- Use SSH with X11 Forwarding to view a graphical window from a resource on your local machine
To Resources directly
This is an advanced topic. In the event that bridging through a console adds unacceptable overhead too your use case, the following options are available:
- Use SSH ProxyJump and similar commands to automate the connection though the console
- Use the VPN to route arbitrary network traffic from the Control Network to or from your local machine.
Using SSH
The most common method of connecting to the testbed is via SSH. The SSH protocol is quite powerful, and allows interactive shell sessions, file transfer, port forwarding, and even graphical display if configured properly with other utilities.
Configuring SSH Keys
See User Guide/Remote Access/SSH
SSH tunneling and X11
See User Guide/Remote Access/Ssh Tunnel
Common SSH Tips and FAQ
See User Guide/Remote Access/Ssh Tips
Using a VPN
In cases where SSH is insufficient or inconvenient, an IPSEC VPN is available.
See User Guide/Remote Access/VPN 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 something special for a Demo.
See User Guide/Remote Access/VPNpersist for our recommended connection parameters, but they will need to be customized per-connection.
Please contact us for more information.