[Lerftest-ctrls] ssh tunnelling back to SLAC

[Pascual, Patrick James]

I got the following to work from lclsapp1:

ssh -fNT -L <local_port>:rhel6-64.slac.stanford.edu:22 <CUE_username>@jlabl1.jlab.org

where <local_port> is not an in-use or privileged port (e.g., NOT 22).

The above command says, "Establish an SSH tunnel in the background such that all connections to localhost:<local_port> are forwarded to rhel6-64.slac.stanford.edu:22 through jlabl1.jlab.org".

Then you can do:

git clone ssh://<SLAC_username>@localhost:<local_port>/path/to/git/repo

This can be further streamlined by editing your .ssh/config file and adding the appropriate Host/Port directives.

Patrick J. Pascual
Controls Software/Systems Engineer, EED
Bldg 034, Rm 208A
2575 Sand Hill Rd., MS50
Menlo Park, CA 94025
(650) 926-3539

________________________________________
From: Lerftest-ctrls <lerftest-ctrls-bounces at jlab.org> on behalf of Wesley Moore <wmoore at jlab.org>
Sent: Monday, April 30, 2018 9:59:28 AM
To: lerftest-ctrls at jlab.org
Subject: [Lerftest-ctrls] ssh tunnelling back to SLAC

Specifically asked by Bruce and Patrick:

The JLAB equivalent of public linux hosts (like rhel6-64.slac.stanford.edu) are:

RHEL6:
  jlabl1 - jlabl4

RHEL7:
  jlabl5

Using cue username/password, you should be able to tunnel from lcls* back out through one of those.  I don't have an example, so please reply with one if it works for you.

Wesley
_______________________________________________
Lerftest-ctrls mailing list
Lerftest-ctrls at jlab.org
https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls