eclipse-sailing-analytics/sailing-analytics
1
0
Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-09-19 04:05:36 +00:00
Code Activity

Clarify GatewayPorts workings

Browse Source
This commit is contained in:
Thomas Stokes
2024-03-22 14:24:24 +00:00
parent 1c945d8bb5
commit 22acff3719
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
wiki/info/landscape/paris2024/olympic-setup.md
+2 -1
View File
@@ -213,7 +213,8 @@ ClientAliveCountMax 3
GatewayPorts yes
```
The ``GatewayPorts`` directive is required in order to get port forwards (including reverse port forwards) accept the "*" as bind address to bind to 0.0.0.0 instead of 127.0.0.1.
The ``GatewayPorts`` directive is required in order to get port forwards (including reverse port forwards) accept the "*" as bind address to bind to 0.0.0.0 instead of 127.0.0.1. Without it a tunnel would only allow localhost connections to the forwarded ports. So for example from one of the P1s, autossh -R portOnRemote:address:portLocally ec2-user@paris-ssh.sapsailing.com, would only allow connections from the ec2-user@paris-ssh.sapsailing.com instance to the port. By adding "yes", any host can access this port and be connected on to the portLocally.
ExitOnForwardFailure will force ssh to exit if one of the port forwards fails. ConnectTimeout manages the time in seconds until an initial connection fails. AliveInterval (client and server) manages the time in seconds after ssh/sshd are sending client and server alive probes. CountMax is the number of retries for those probes.