Date: Thu, 14 Jun 2018 16:01:30 +0200 From: Andrea Venturoli <ml@netfence.it> To: freebsd-net@freebsd.org Subject: Re: Proxy a TCP connection Message-ID: <ee09e0ce-d258-4cf6-f519-aa802386ac79@netfence.it> In-Reply-To: <8a9d5799-5451-7f0a-cbd7-64728ab8ae85@netfence.it> References: <2346bc5f-1ca3-3b6a-ac1a-c496e94eb969@netfence.it> <40qGSP6TW1z5BbC@baobab.bilink.it> <8a9d5799-5451-7f0a-cbd7-64728ab8ae85@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ee09e0ce-d258-4cf6-f519-aa802386ac79>