Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • There is no need to manually specify port number mapping for each ecflow server
  • You can use original host names in the ecFlow servers connection settigs, instead of 'localhost'
  • You are not limited to a single logserver; there is also no need to modify /etc/hosts file.

The SOCKS proxy can tunnel all network traffic from your ecflow_ui to the servers running inside the Centre:

  • ecflow_ui ↔ ECMWF ecFlow servers
  • ecflow_ui ↔ ECMWF ecFlow logservers
  • ecflow_ui ↔ ECMWF DNS serversc

However, to connect with SOCKS proxyHowever, to use Dynamic Port Forwarding, the client application (ecflow_ui) must understand be able to speak SOCKS protocol. Here we We will show how to :

...

enable it in ecflow_ui

...

.

NOTE: if you were using Local Port Forwarding method, you will now need to:

...

Start SOCKS proxy session

The SOCKS proxy will tunnel all network traffic from your ecflow_ui to the servers running inside the Centre:

...

In a terminal, start the proxy session with:

...