Skip to content
Snippets Groups Projects
vnc.md 9.21 KiB
Newer Older
  • Learn to ignore specific revisions
  • Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    # VNC
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    **Virtual Network Computing** (**VNC**) is a graphical [desktop sharing][a] system that uses the [Remote Frame Buffer protocol (RFB)][b] to remotely control another [computer][c]). It transmits the [keyboard][d] and [mouse][e] events from one computer to another, relaying the graphical [screen][f] updates back in the other direction, over a [network][g].
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Vnc-based connections are usually faster (require less network bandwidth) than [X11][1] applications forwarded directly through SSH.
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    The recommended clients are [TightVNC][h] or [TigerVNC][i] (free, open source, available for almost any platform).
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    In this chapter, we show how to create an underlying SSH tunnel from your client machine to one of our login nodes. Then, how to start your own VNC server on our login node and finally how to connect to your VNC server via the encrypted SSH tunnel.
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## Create VNC Password
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    !!! note
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        Local VNC password should be set before the first login. Use a strong password.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [username@login2 ~]$ vncpasswd
    Password:
    Verify:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    ## Start VNC Server
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    !!! note
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        To access VNC, a local VNC Server must be started first and a tunnel using SSH port forwarding must be established.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    [See below][2] for the details on SSH tunnels.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Start by **choosing your display number**.
    To choose a free one, you should check currently occupied display numbers - list them using the command:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    [username@login2 ~]$ ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    username :79
    username :60
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    .....
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    As you can see above, displays ":79" and ":60" are already occupied.
    
    Generally, you can choose display number freely *except these occupied numbers*.
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Also remember that display number should be lower or equal 99.
    Based on this, **we have chosen the display number 61** for us, as seen in the examples below.
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        Your situation may be different so the choice of your number may differ, as well. **Choose and use your own display number accordingly!**
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Start your VNC server on the chosen display number (61):
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [username@login2 ~]$ vncserver :61 -geometry 1600x900 -depth 16
    
    New 'login2:1 (username)' desktop is login2:1
    
    Starting applications specified in /home/username/.vnc/xstartup
    Log file is /home/username/.vnc/login2:1.log
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Check whether the VNC server is running on the chosen display number (61):
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [username@login2 .vnc]$ vncserver -list
    
    TigerVNC server sessions:
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    X DISPLAY #     PROCESS ID
    :61              18437
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Another way to check it:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    [username@login2 .vnc]$  ps aux | grep Xvnc | sed -rn 's/(\s) .*Xvnc (\:[0-9]+) .*/\1 \2/p'
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    username :61
    username :102
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    !!! note
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        The VNC server runs on port 59xx, where xx is the display number. To get your port number, simply add 5900 + display number, in our example 5900 + 61 = 5961. Another example for display number 102 is calculation of TCP port 5900 + 102 = 6002, but note that TCP ports above 6000 are often used by X11. **Calculate your own port number and use it instead of 5961 from examples below**.
    
    David Hrbáč's avatar
    David Hrbáč committed
    To access the VNC server you have to create a tunnel between the login node using TCP port 5961 and your machine using a free TCP port (for simplicity the very same) in next step. See examples for [Linux/Mac OS][2] and [Windows][3].
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    !!! note
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        The tunnel must point to the same login node where you launched the VNC server, e.g. login2. If you use just cluster-name.it4i.cz, the tunnel might point to a different node due to DNS round robin.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## Linux/Mac OS Example of Creating a Tunnel
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    At your machine, create the tunnel:
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    David Hrbáč's avatar
    David Hrbáč committed
    local $  ssh -TN -f username@login2.cluster-name.it4i.cz -L 5961:localhost:5961
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Issue the following command to check the tunnel is established (note the PID 2022 in the last column, it is required for closing the tunnel):
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    local $ netstat -natp | grep 5961
    (Not all processes could be identified, non-owned process info
    
    David Hrbáč's avatar
    David Hrbáč committed
     will not be shown, you would have to be root to see it all.)
    tcp        0      0 127.0.0.1:5961          0.0.0.0:*               LISTEN      2022/ssh
    tcp6       0      0 ::1:5961                :::*                    LISTEN      2022/ssh
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    Or on Mac OS use this command:
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    local-mac $ lsof -n -i4TCP:5961 | grep LISTEN
    ssh 75890 sta545 7u IPv4 0xfb062b5c15a56a3b 0t0 TCP 127.0.0.1:5961 (LISTEN)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    Connect with the VNC client:
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    local $ vncviewer 127.0.0.1:5961
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    In this example, we connect to VNC server on port 5961, via the SSH tunnel. The connection is encrypted and secured. The VNC server listening on port 5961 provides screen of 1600x900 pixels.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    You have to close the SSH tunnel which is still running in the background after you finish the work. Use the following command (PID 2022 in this case, see the netstat command above):
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    kill 2022
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    !!! note
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        You can watch the instruction video on how to make a VNC connection between a local Ubuntu desktop and the IT4I Salomon cluster [here][k].
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## Windows Example of Creating a Tunnel
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Start the VNC server using the vncserver command described above.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Search for the localhost and port number (in this case 127.0.0.1:5961):
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [username@login2 .vnc]$ netstat -tanp | grep Xvnc
    (Not all processes could be identified, non-owned process info
    
    David Hrbáč's avatar
    David Hrbáč committed
     will not be shown, you would have to be root to see it all.)
    tcp        0      0 127.0.0.1:5961              0.0.0.0:*                   LISTEN      24031/Xvnc
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    ### PuTTY
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    On the PuTTY Configuration screen, go to Connection->SSH->Tunnels to set up the tunnel.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    Fill the Source port and Destination fields. **Do not forget to click the Add button**.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/putty-tunnel.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    ### WSL (Bash on Windows)
    
    Pavel Jirásek's avatar
    h3  
    Pavel Jirásek committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    [Windows Subsystem for Linux][j] is another way to run Linux software in a Windows environment.
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    
    At your machine, create the tunnel:
    
    ```console
    local $ ssh username@login2.cluster-name.it4i.cz -L 5961:localhost:5961
    ```
    
    
    Pavel Jirásek's avatar
    h3  
    Pavel Jirásek committed
    ## Example of Starting VNC Client
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Run the VNC client of your choice, select the VNC server 127.0.0.1, port 5961 and connect using the VNC password.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    h3  
    Pavel Jirásek committed
    ### TigerVNC Viewer
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/vncviewer.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    In this example, we connect to the VNC server on port 5961, via the SSH tunnel, using the TigerVNC viewer. The connection is encrypted and secured. The VNC server listening on port 5961 provides a screen of 1600x900 pixels.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    h3  
    Pavel Jirásek committed
    ### TightVNC Viewer
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Use your VNC password to log using the TightVNC Viewer and start a Gnome Session on the login node.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/TightVNC_login.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## Gnome Session
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    After the successful login, you should see the following screen:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/gnome_screen.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    ### Disable Your Gnome Session Screensaver
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Open the Screensaver preferences dialog:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/gdmscreensaver.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    Uncheck both options below the slider:
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/gdmdisablescreensaver.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Pavel Jirásek's avatar
    Pavel Jirásek committed
    ### Kill Screensaver if Locked Screen
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    If the screen gets locked, you have to kill the screensaver. Do not forget to disable the screensaver then.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [username@login2 .vnc]$ ps aux | grep screen
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    username     1503 0.0 0.0 103244   892 pts/4    S+   14:37   0:00 grep screen
    username     24316 0.0 0.0 270564 3528 ?        Ss   14:12   0:00 gnome-screensaver
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    [username@login2 .vnc]$ kill 24316
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## Kill Vncserver After Finished Work
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    You should kill your VNC server using the command:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    David Hrbáč's avatar
    David Hrbáč committed
    [username@login2 .vnc]$  vncserver  -kill :61
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    Killing Xvnc process ID 7074
    Xvnc process ID 7074 already killed
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    or:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    David Hrbáč's avatar
    David Hrbáč committed
    [username@login2 .vnc]$  pkill vnc
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
        Also, do not forget to terminate the SSH tunnel, if it was used. For details, see the end of [this section][2].
    
    David Hrbáč's avatar
    David Hrbáč committed
    ## GUI Applications on Compute Nodes Over VNC
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    The very same methods as described above may be used to run the GUI applications on compute nodes. However, for maximum performance, follow these steps:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Open a Terminal (Applications -> System Tools -> Terminal). Run all the following commands in the terminal.
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/gnome-terminal.png)
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    Allow incoming X11 graphics from the compute nodes at the login node:
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    $ xhost +
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    David Hrbáč's avatar
    David Hrbáč committed
    Get an interactive session on a compute node (for more detailed info [look here][4]). Use the **-v DISPLAY** option to propagate the DISPLAY on the compute node. In this example, we want a complete node (16 cores in this example) from the production queue:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    $ qsub -I -v DISPLAY=$(uname -n):$(echo $DISPLAY | cut -d ':' -f 2) -A PROJECT_ID -q qprod -l select=1:ncpus=16
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    Test that the DISPLAY redirection into your VNC session works, by running an X11 application (e.g. XTerm) on the assigned compute node:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```console
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    $ xterm
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ```
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Jan Siwiec's avatar
    Jan Siwiec committed
    The example described above:
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    ![](../../../img/gnome-compute-nodes-over-vnc.png)
    
    David Hrbáč's avatar
    David Hrbáč committed
    
    [a]: http://en.wikipedia.org/wiki/Desktop_sharing
    [b]: http://en.wikipedia.org/wiki/RFB_protocol
    [c]: http://en.wikipedia.org/wiki/Computer
    [d]: http://en.wikipedia.org/wiki/Computer_keyboard
    [e]: http://en.wikipedia.org/wiki/Computer_mouse
    [f]: http://en.wikipedia.org/wiki/Computer_screen
    [g]: http://en.wikipedia.org/wiki/Computer_network
    [h]: http://www.tightvnc.com
    [i]: http://sourceforge.net/apps/mediawiki/tigervnc/index.php?title=Main_Page
    [j]: http://docs.microsoft.com/en-us/windows/wsl
    
    [k]: https://www.youtube.com/watch?v=b9Ez9UN2uL0
    
    David Hrbáč's avatar
    David Hrbáč committed
    
    [1]: x-window-system.md
    [2]: #linuxmac-os-example-of-creating-a-tunnel
    [3]: #windows-example-of-creating-a-tunnel
    
    Lukáš Krupčík's avatar
    Lukáš Krupčík committed
    [4]: ../../job-submission-and-execution.md