Date: Thu, 14 Jun 2018 09:29:40 -0500 From: Adam <amvandemore@gmail.com> To: Andrea Venturoli <ml@netfence.it> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: Proxy a TCP connection Message-ID: <CA%2BtpaK0RYHwBJcguEuhE_QG1jGj%2B6EC-CBb0XUFG2P9W=Gs5kA@mail.gmail.com> In-Reply-To: <ee09e0ce-d258-4cf6-f519-aa802386ac79@netfence.it> References: <2346bc5f-1ca3-3b6a-ac1a-c496e94eb969@netfence.it> <40qGSP6TW1z5BbC@baobab.bilink.it> <8a9d5799-5451-7f0a-cbd7-64728ab8ae85@netfence.it> <ee09e0ce-d258-4cf6-f519-aa802386ac79@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 14, 2018 at 9:01 AM, Andrea Venturoli <ml@netfence.it> wrote: > 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. > haproxy or nginx can do tcp proxy/lb. I haven't used nginx for that exactly but here's your doc: https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/ -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK0RYHwBJcguEuhE_QG1jGj%2B6EC-CBb0XUFG2P9W=Gs5kA>