From owner-freebsd-net@freebsd.org  Thu Jun 14 14:20:59 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B816410086D2
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 14 Jun 2018 14:20:59 +0000 (UTC) (envelope-from ml@netfence.it)
Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it
 [2.44.121.52])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "mailserver.netfence.it",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 26FAE6CAF0
 for <freebsd-net@freebsd.org>; Thu, 14 Jun 2018 14:20:58 +0000 (UTC)
 (envelope-from ml@netfence.it)
Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18])
 (authenticated bits=0)
 by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w5EE1U7o020067
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
 for <freebsd-net@freebsd.org>; Thu, 14 Jun 2018 16:01:37 +0200 (CEST)
 (envelope-from ml@netfence.it)
X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it
 [10.1.2.18] claimed to be alamar.ventu
Subject: Re: Proxy a TCP connection
From: Andrea Venturoli <ml@netfence.it>
To: freebsd-net@freebsd.org
References: <2346bc5f-1ca3-3b6a-ac1a-c496e94eb969@netfence.it>
 <40qGSP6TW1z5BbC@baobab.bilink.it>
 <8a9d5799-5451-7f0a-cbd7-64728ab8ae85@netfence.it>
Message-ID: <ee09e0ce-d258-4cf6-f519-aa802386ac79@netfence.it>
Date: Thu, 14 Jun 2018 16:01:30 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <8a9d5799-5451-7f0a-cbd7-64728ab8ae85@netfence.it>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2018 14:20:59 -0000

On 05/21/18 18:10, Andrea Venturoli wrote:

> Thanks to anyone who answered.
> 
> I'm currently trying net/bounce, as suggested by Eugene.
> If that won't work properly, I'll sure give plugdaemon a shot.

Just an update in case anyone is interested...

Bounce is still dying occasionally; in some way it is better than 
tcpproxy, in that it uses different process, one for each port, so when 
one dies, the other ports will still work (when tcpproxy dies, all port 
redirections stop working).

I still haven't managed to understang why it dies: really no clue is in 
the log...
It's always the same port (same device) and once I had to tcpdrop a 
FIN_WAIT2 connection in order to be able to restart it.

Guess I'll have to get daemontools' svscan out again.

  bye & Thanks
	av.