<aside> 💡 Remote Development during Work-From-Home duration This page was initially prepared for the junior research students joining our squad at the very beginning stage - as I was repeatedly asked about questions like "my teamviewer gets slow/suspended lately, what should I do" 😂., especially during the COVID-19 lockdown & WFH period. I then decided to document it out and keep it updated from time to time → hope it helps for CS research students (whose lab machine is Linux-based and not being easily accessible for any reasons...) to ease their stress in dealing with the Teamviewer's annoying delay 🙃 Contributor(s): Chaoyi @ USYD (Pls send me a email if you're interested in improving this tip-page with me)

</aside>

GUI-based remote controls

File Sharing

SSH-based remote controls

Cisco (VPN connection for Mac & Windows)

  1. Download page: https://www.cisco.com/c/en/us/support/security/anyconnect-secure-mobility-client-v4-x/model.html
  2. Find your uni-vpn-domain. (e.g., vpn.sydney.edu.au + login w/ unikey)

SSH - we are more like a CS student now

.................................................. probably still the most naive ones 🙃 .....

  1. Run code in remote terminal (without Teamviewer and other GUI-based ones)

  2. Requires VPN connection.

  3. Setup on remote workstation:

    sudo apt-get install openssh-server
    dpkg -l | grep ssh
    sudo service ssh start 
    #sudo service ssh stop 
    
    #sudo vim /etc/ssh/sshd_config
    #sudo service ssh restart 
    ifconfig
    
  4. launch a SSH-Terminal on local machine (with VPN enabled at first)

    ssh -p PORT_NUMBER ADMIN_NAME@IP_NUMBER
    

TMUX (a magic terminal window that never get killed)

....................... your remote training progress would never be killed due to any poor connection ....................... (maybe try think of another excuse to your mentor when things not running well 🙃

  1. Let your SSH-Terminal never get killed by accidents (due to poor network connection, entering sleeping mode, or etc) - (w/o Teamviewer)