strano output sul tunneling ssh: output fallito; connessione non riuscita: connessione scaduta;

Uso il ssh user@xx.yy.zz.41 -p 1234 -D 9898comando per il tunneling e ho impostato firefox socks5 ip su 127.0.0.1 e la sua porta su 9898. Funziona correttamente, ma nel terminale ho un errore nell'output:

channel 39: open failed: connect failed: Connection timed out
channel 41: open failed: connect failed: Connection timed out
channel 42: open failed: connect failed: Connection timed out
channel 43: open failed: connect failed: Connection timed out
channel 44: open failed: connect failed: Connection timed out

Si verifica periodicamente. Che cos'è questo? È un problema? Cosa posso fare?

Ho riscontrato problemi simili. Se si esegue il tunneling con Firefox tramite ssh, alcune connessioni http possono semplicemente scadere a causa del carico del server o di una configurazione errata. Quando la connessione esegue effettivamente il timeout, riceverai un messaggio di errore come quello che hai indicato.

Puoi sopprimere questi messaggi con il seguente comando

ssh user@xx.yy.zz.41 -p 1234 -D 9898 -q

Dalla pagina man ssh(1)

 -q      Quiet mode.  Causes most warning and diagnostic messages to be sup-
         pressed.

La soppressione del messaggio impedirà agli avvisi di creare confusione nelle sessioni ssh o schermo.

Impostare il GatewayPortsto yese riprovare.

ssh -o 'GatewayPorts yes' user@xx.yy.zz.41 -p 1234 -D 9898

man ssh_config

 DynamicForward
         Specifies that a TCP port on the local machine be forwarded over the secure channel, and the application protocol
         is then used to determine where to connect to from the remote machine.

         The argument must be [bind_address:]port.  IPv6 addresses can be specified by enclosing addresses in square
         brackets.  By default, the local port is bound in accordance with the GatewayPorts setting.  However, an explicit
         bind_address may be used to bind the connection to a specific address.  The bind_address of “localhost” indicates
         that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should
         be available from all interfaces.

         Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh(1) will act as a SOCKS server.  Multiple for‐
         wardings may be specified, and additional forwardings can be given on the command line.  Only the superuser can
         forward privileged ports.

 GatewayPorts
         Specifies whether remote hosts are allowed to connect to local forwarded ports.  By default, ssh(1) binds local
         port forwardings to the loopback address.  This prevents other remote hosts from connecting to forwarded ports.
         GatewayPorts can be used to specify that ssh should bind local port forwardings to the wildcard address, thus
         allowing remote hosts to connect to forwarded ports.  The argument must be “yes” or “no”.  The default is “no”.