Come faccio a mantenere vivo un tunnel ssh usando launchd?

Question

Come faccio a mantenere vivo un tunnel ssh usando launchd?

#1 da (1 voti)

2

Vorrei mantenere vivo un tunnel ssh. Di seguito è riportato il file plist dell'agente di avvio, ma mantiene il tunnel solo per un giorno o due al massimo. Sto usando OS X 10.10.3.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
        <dict>
                <key>Label</key>
                <string>com.my.ssh_tunnel</string>
                <key>ProgramArguments</key>
                <array>
                        <string>/usr/bin/ssh</string>
                        <string>-R 0.0.0.0:22221:localhost:22</string>
                        <string>-NTC</string>
                        <string>-f</string>
                        <string>-o ExitOnForwardFailure=yes</string>
                        <string>-o ServerAliveInterval=60</string>
                        <string>[email protected]</string>
                </array>
                <key>RunAtLoad</key>
                <true/>
                <key>KeepAlive</key>
                <true/>
        </dict>
</plist>

macos launchd ssh tunnel

posta wkmor1 01.05.2015 - 07:59

fonte

1 risposta

Leggi altre domande sui tag macos launchd ssh tunnel

Il disco di backup "non contiene una partizione di sistema EFI" Come disattivare i download e gli aggiornamenti automatici?

score 1 · Accepted Answer

Penso che sia necessario aggiungere "ServerAliveCountMax". Poiché non lo hai impostato, il valore predefinito è 3. Prova a impostarlo su un valore superiore a 3 e vedere se rivive alcuni dei tuoi problemi. Nel tuo caso si disconnetterebbe se il server non rispondesse per 180 secondi.

Dalla pagina man ssh:

 ServerAliveCountMax:

     Sets the number of server alive messages (see below) which may be
     sent without ssh(1) receiving any messages back from the server.
     If this threshold is reached while server alive messages are
     being sent, ssh will disconnect from the server, terminating the
     session.  It is important to note that the use of server alive
     messages is very different from TCPKeepAlive (below).  The server
     alive messages are sent through the encrypted channel and there‐
     fore will not be spoofable.  The TCP keepalive option enabled by
     TCPKeepAlive is spoofable.  The server alive mechanism is valu‐
     able when the client or server depend on knowing when a connec‐
     tion has become inactive.

     The default value is 3.  If, for example, ServerAliveInterval
     (see below) is set to 15 and ServerAliveCountMax is left at the
     default, if the server becomes unresponsive, ssh will disconnect
     after approximately 45 seconds.  This option applies to protocol
     version 2 only.