Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Table of Contents

Objectives

This page explains the remote access to User Equipment (UE) assigned to the OWL RAN. 
The solution bases on remote-desktop functions at jumphost "node4-1" and is inspired by the COSMOS project:

Prerequisites

  • ORBIT account for Sandbox10 (SB10)
  • Google account
  • Browser with Chrome engine

Procedure

Chrome Remote Desktop Setup Page

Chrome Remote Desktop is a [https://en.wikipedia.org/wiki/Chrome_Remote_Desktop Google developed client-server framework] that allows for remote desktop access to (in this case) a [https://en.wikipedia.org/wiki/Headless_computer headless machine]. In order to access a node that has Chrome Remote Desktop server side installed, you need to:

  • Access the [https://remotedesktop.google.com/headless remote access page] on your local Chrome browser and hit the ''Begin'' button
  • Select the '''Next''' button (under the assumption that you already have remote desktop service installed on the target node)
  • Generate authorization token for the node but hitting the ''Authorize'' button
  • Copy the command line with the token to you clipboard by selecting the target OS ''Copy'' button (icon to the right of the command line content pane - use the  Copy button for the Linux platform)

  • Paste that command line in the remote ssh session on the node command line. This needs to be on OWL physical node called "node4-1". 

    ssh <your-orbit-account-user-name>@console.sb10.orbit-lab.org
ssh native@node4-1

    The service will prompt you (twice) for a ''PIN'' number that will be needed in the next step as an additional security feature.

  • Switch to the '''Remote Access''' mode in your local browser
  • If the authorization was successfully applied you should see the node listed under the ''Remote devices'' section
  • Select that node and you should be prompted for the ''PIN'' created in previous step.
  • Once the pin is successfully entered, you should be rewarded with the remote desktop access within your browser


Important note: Chrome Remote Desktop authorization toke can't be saved with the image and will not "survive" reboots i.e. you will have to re-authorize access every time node is booted!


  • No labels