Changes between Version 16 and Version 17 of User Guide/Remote Access


Ignore:
Timestamp:
May 19, 2020, 9:41:26 PM (5 years ago)
Author:
msherman
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • User Guide/Remote Access

    v16 v17  
    13131. Consoles share a [wiki:Architecture/Network#ControlPlane Control] network with [wiki:Resources] within their [wiki:Architecture/Domains Domain]
    1414
    15 === To Resources
     15=== To Resources via console
    1616
    1717* Resources can be interacted with by running commands from a Console.
    … …  
    2424* Use SSH with X11 Forwarding to view a graphical window from a resource on your local machine
    2525
    26 === Direct Access to Resources
     26=== To Resources directly
    2727This is an advanced topic. In the event that bridging through a console adds unacceptable overhead too your use case, the following options are available:
    2828
    … …  
    3030* Use the [wiki:UserGuide/RemoteAccess/VPN VPN] to route arbitrary network traffic from the [wiki:Architecture/Network#ControlPlane Control Network] to or from your local machine.
    3131
    32 === SSH
     32=== Using SSH
    3333The 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.
    3434
    … …  
    4242See [wiki:UserGuide/RemoteAccess/SshTips#tips]
    4343
    44 === VPN
     44=== Using a VPN
    4545In cases where SSH is insufficient or inconvenient, an IPSEC VPN is available.
    4646
    … …  
    5050* A need to tunnel many, or ephemeral ports.
    5151
    52 
    5352=== Site to Site Connection
    5453If 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.