[Lerftest-ctrls] Internet access from jlabl1.jlab.org

Slepicka, Hugo Henrique slepicka at slac.stanford.edu
Thu Oct 18 23:41:06 EDT 2018


Hi Wesley and Sonya,

I just tried from home and rhel6-64.slac.stanford.edu can be reached with no problems from my internet connection in here.
    slepicka at TID-PC94483:~  $ ping rhel6-64.slac.stanford.edu
    PING rhel6-64e.slac.stanford.edu (134.79.120.159): 56 data bytes
    64 bytes from 134.79.120.159: icmp_seq=0 ttl=52 time=17.301 ms
    64 bytes from 134.79.120.159: icmp_seq=1 ttl=52 time=18.111 ms
    64 bytes from 134.79.120.159: icmp_seq=2 ttl=52 time=14.991 ms
    64 bytes from 134.79.120.159: icmp_seq=3 ttl=52 time=14.401 ms
    64 bytes from 134.79.120.159: icmp_seq=4 ttl=52 time=13.660 ms
    ^C
    --- rhel6-64e.slac.stanford.edu ping statistics ---
    5 packets transmitted, 5 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 13.660/15.693/18.111/1.716 ms

Some weird issues are back to the VDI machine... If I try from the VDI machine to ssh as softegr into lclsapp1 I asks me for my password again. That happened in the past but it was fixed.
If I go through a regular SSH connection to hallgw and from there to lclsapp1 as softegr the SSH works... 

Once I am connected to the JLab system (lclsapp1) I can't establish my SSH Tunnel as before:

    [softegr at lclsapp1 slepicka]$ ssh -fNT -v -L 6660:rhel6-64.slac.stanford.edu:22 slepicka at jlab1.jlab.org
    OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug1: Connecting to jlab1.jlab.org [192.70.245.101] port 22.

If I try to ping jlab1.jlab.org it fails.

@Wesley did something change on the JLab network?

Cheers,
Hugo


On 10/18/18, 6:05 PM, "Lerftest-ctrls on behalf of Slepicka, Hugo Henrique" <lerftest-ctrls-bounces at jlab.org on behalf of slepicka at slac.stanford.edu> wrote:

    Hi,
    
    I will take a look at that and get back to you later tonight.
    
    Cheers,
    Hugo
    
    Sent from my iPhone
    
    > On Oct 18, 2018, at 5:52 PM, Wesley Moore <wmoore at jlab.org> wrote:
    > 
    > Looks more like an issue with an ssh tunnel you guys setup.  Does that ring a bell?
    > 
    > Wesley
    > 
    > On 10/18/18, 8:44 PM, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
    > 
    >    Okay, my image was too large and is holding up the submission.
    > 
    >    The test was:
    > 
    >    cd /usr/local/lcls/tools/edm/display/llrf
    >    cvs stat rf_ampset_diag.edl
    > 
    >    But I have to leave work now, so I'll have to come back to this tomorrow. 
    >    Thanks for your help so late!
    > 
    >    Sonya
    > 
    > 
    > 
    > 
    >>    On Thu, 18 Oct 2018, Sonya Hoobler wrote:
    >> 
    >> Yes, I've attached a screenshot of an example command (can't copy/paste).
    >> 
    >> I could use scp as a temporary solution if we can get access between jlabl1 
    >> and rhel6-64.slac.stanford.edu (which we used to have, right? checking my 
    >> memory).
    >> 
    >> Thanks,
    >> Sonya
    >> 
    >> 
    >> 
    >> 
    >> 
    >>> On Fri, 19 Oct 2018, Wesley Moore wrote:
    >>> 
    >>> Can you send me a cvs and git command to try?  I'll see what the network 
    >>> traffic looks like to see if that well highlight the issue.
    >>> 
    >>> Wesley
    >>> 
    >>> On 10/18/18, 8:13 PM, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
    >>> 
    >>>   Hmm, I seem to be able to ping the world (google, FNAL) from my SLAC
    >>>   machine (using rhel6-64c.slac.stanford.edu at the moment) but cannot 
    >>> ping
    >>>   rhel6-64c from jlabl1.
    >>> 
    >>>   Do you have a favorite domain to ping or other test I should run from
    >>>   jlabl1.jlab.org?
    >>> 
    >>>   Thanks,
    >>>      Sonya
    >>> 
    >>> 
    >>>>   On Fri, 19 Oct 2018, Wesley Moore wrote:
    >>>> 
    >>>> It looks to be proxied.  So it should work from the lcls hosts also. 
    >>> I'll have to see it there's something special required for cvs/git, but I 
    >>> know git works through the proxy.  Possible issue on the slac side (maybe 
    >>> not open to the world)?
    >>>> 
    >>>> Wesley
    >>>> 
    >>>> On 10/18/18, 8:01 PM, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
    >>>> 
    >>>>   Hi Wesley,
    >>>> 
    >>>>   If I remember correctly, jlabl1.jlab.org (and friends) should have
    >>>>   internet access, but it does not seem to currently. For example, I 
    >>> am
    >>>>   unable to ping rhel6-64.slac.stanford.edu. (I also suspect this is 
    >>> why
    >>>>   remote cvs/git is not currently working.)
    >>>> 
    >>>>   Should I be using a different server?
    >>>> 
    >>>>   Thanks,
    >>>>      Sonya
    >>>> 
    >>>> 
    >>>> 
    >>>> 
    >>> 
    >> 
    > 
    > 
    > _______________________________________________
    > Mailing List: Lerftest-ctrls at jlab.org
    > https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
    > Wiki: https://wiki.jlab.org/lerf/index.php/Network
    
    _______________________________________________
    Mailing List: Lerftest-ctrls at jlab.org
    https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
    Wiki: https://wiki.jlab.org/lerf/index.php/Network
    




More information about the Lerftest-ctrls mailing list