[LUGOS] Samba over SSH

Gašper Lakota - Jeriček gasper at bsnet.dhs.org
Fri Jun 6 11:42:47 CEST 2003


Andrej wrote:

>Pozdrav.
>
>Scenarij :
>
>WindowsXP -> gwlinux1 <-> gwlinux2 -> linuxsamba
>
>Z WindowsXP masine bi rad mapiral share (ki je na PCju linuxsamba)
>preko SSH-ja.
>
>Na gwlinux1 sem vzpostavil tunel z ukazom "ssh -2 -q -f -N -g -L
>139:linuxsamba:139 root at gwlinux2". Sedaj pod windowsXP mapiram disk
>"\\gwlinux1\public" in zadeva deluje brez tezav. Ko pa poizkusim enako
>povezavo vzpostaviti cez nekaj casa (cca. 10 min) dobim na gwlinux1
>sporocilo "gwlinux2 has closed connection" - tunel se prekine. Zanima me
>zakaj se to zgodi? Verjetno je nastavljen nekje timeout ali kaj takega...
>
>Hvala za pomoc in lep pozdrav,
>
>	Andrej.
>
>  
>

poglej v man sshd_config, še posebej naslednji dve opciji:
  
  ClientAliveInterval
             Sets a timeout interval in seconds after which if no data has
             been received from the client, sshd will send a message through
             the encrypted channel to request a response from the 
client.  The
             default is 0, indicating that these messages will not be 
sent to
             the client.  This option applies to protocol version 2 only.

     ClientAliveCountMax
             Sets the number of client alive messages (see above) which 
may be
             sent without sshd receiving any messages back from the 
client. If
             this threshold is reached while client alive messages are being
             sent, sshd will disconnect the client, terminating the session.
             It is important to note that the use of client alive 
messages is
             very different from KeepAlive (below). The client alive 
messages
             are sent through the encrypted channel and therefore will 
not be
             spoofable. The TCP keepalive option enabled by KeepAlive is
             spoofable. The client alive mechanism is valuable when the 
client
             or server depend on knowing when a connection has become inac­
             tive.

             The default value is 3. If ClientAliveInterval (above) is 
set to
             15, and ClientAliveCountMax is left at the default, 
unresponsive
             ssh clients will be disconnected after approximately 45 
seconds.


lp,
Gašper





More information about the lugos-list mailing list