Delivery-Date: Tue, 08 Jul 2014 00:14:13 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 5CAAD1E0A44
	for <archiver@seul.org>; Tue,  8 Jul 2014 00:14:10 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8C6FF30237;
	Tue,  8 Jul 2014 04:14:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F1D8D2FE4E
 for <tor-talk@lists.torproject.org>; Tue,  8 Jul 2014 04:08:53 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uiuYw7oOoSgd for <tor-talk@lists.torproject.org>;
 Tue,  8 Jul 2014 04:08:53 +0000 (UTC)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com
 [209.85.216.52])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 83BF42FE4A
 for <tor-talk@lists.torproject.org>; Tue,  8 Jul 2014 04:08:53 +0000 (UTC)
Received: by mail-qa0-f52.google.com with SMTP id w8so4248746qac.25
 for <tor-talk@lists.torproject.org>; Mon, 07 Jul 2014 21:08:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=om0e6tHl/9i0nxlH6VBcAWWlyxE0Ql+D+Gis8l0jGXY=;
 b=Tg9r/mT+u6M6COm8C/+lzZWkoa8flmO6qo+TJcpI9qKcSRasj/A6LF9vMMewCP8hJB
 teYU7MGiYbebGDwyRwWyZC/d7CqSjiMrBkr0ud74peUQYg/3FH2k0oyMRbbrSCe/w0q+
 Hj50GTW1zsKNU8NEUl8IfesR+d5hRH3ne6DuecA4xq9rgLbLnaWT8LPmrujm/Wi+BcKB
 AY/wj7EEL6nClDLW/zx8r9j5EE4PNppNz+tA10mhsTM2+vVUqCJnO0SxjfWB6vW+cdhU
 iORe0SUGsGgpsF2ql2FqpM48UXxMDnK/1CsMkk5u/rN7it6y3TKd5Ax2TMLxuIXcOyrU
 ucVg==
X-Gm-Message-State: ALoCoQl1myrtmUYgCTxP1iNxe1c2FaeFXp9AGp1yOizu0b/fzK/Qz1NxYFgsqy6NycgbnoKr4QRZ
MIME-Version: 1.0
X-Received: by 10.140.83.209 with SMTP id j75mr51864788qgd.42.1404792530974;
 Mon, 07 Jul 2014 21:08:50 -0700 (PDT)
Received: by 10.224.129.65 with HTTP; Mon, 7 Jul 2014 21:08:50 -0700 (PDT)
X-Originating-IP: [178.248.30.132]
Date: Tue, 8 Jul 2014 07:08:50 +0300
Message-ID: <CAJ8LpWq5_ga6mDVkKrO-Jr-7K8=oErqqwsRd9+9UumdVE0YKiQ@mail.gmail.com>
From: "Nurmi, Juha" <juha.nurmi@ahmia.fi>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] What is keeping the SSH connection alive?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hi,

I have a Raspberry Pi as wireless router and Tor proxy. Everything from
wlan0 is directed to Tor. When I am taking SSH connection using this
wireless transparent proxy with my laptop the SSH connection is sometimes
left alive forever after the laptop is closed.

How it works:

1) I am taking SSH connection from my laptop to an SSH server.
2) I am walking away from my home with the laptop and the connection to the
wireless network is lost.
3) The SSH connection stays on (from the server point of view) forever.

The wireless router is keeping the SSH connection alive until I reboot it.

I don't understand how this is possible.

In the wireless router I am running the Tor software version 0.2.3.25.
Moreover, there is nothing special in the SSH server.

It seems that the connection stays on until the router is rebooted. I see
the SSH connection coming from some exit node:

[juha@server ~]$ who
juha    pts/1        2014-07-07 13:04 (:pts/2:S.0)
juha    pts/0        2014-07-07 10:43 (h-213.61.149.100.host.de.colt.net)

[juha@server ~]$ sudo netstat -tnpa | grep ESTABLISHED.*sshd
tcp        0      0 XXX.XXX.XXX.XXX:22          213.61.149.100:19120
 ESTABLISHED 8743/sshd

The SSH server has the default settings (keep alive settings are commented
out):

[juha@server ~]$ sudo grep -ni alive /etc/ssh/sshd_config
114:#TCPKeepAlive yes
119:#ClientAliveInterval 0
120:#ClientAliveCountMax 3

So, how does the SSH connection is kept alive forever without the client
side?

Greetings,
Juha
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

