Hi, Alec, Willy Sorry to ask a not so related question here, I have a Linux gateway to redirect user's TCP traffic by using iptables like `iptables -t nat -A PREROUTING -p tcp dst -j REDIRECT --to-ports 1000`, port 1000 is redsocks transparent tcp-to-socks proxy, since we have Alec's patch here, I wonder if that easy to modify the patch to meet my weird requirement like: ``` listen tcps bind: 1000 transparent server x.x.x.x:2000 ssl ``` x.x.x.x:2000 is a remote socks server with ssl wrap. I want user TCP traffic from port 1000 to redirect to remote socks server. I'm not so familiar in haproxy core architecture, can you guys point me which part in the source should I look at?
Thanks! On Mon, Jun 3, 2019 at 5:45 PM Alec Liu <alec....@gmail.com> wrote: > > Hi Willy, > > Totally understand. > Thank you for the kindness! > > Regards, > Alexander Liu > > On Mon, Jun 3, 2019 at 5:39 PM Willy Tarreau <w...@1wt.eu> wrote: > > > > On Mon, Jun 03, 2019 at 04:50:57PM +0800, Alec Liu wrote: > > > Hi Willy, > > > > > > Good to know it was fixed. > > > I will try to do some more testing as well. > > > > OK. > > > > > btw: do you mind if I am trying to have the SOCKS4 support backported > > > to 1.9 and 1.8? > > > > We normally don't backport new features into stable versions, as > > experience told us that while tempting, over the long term it causes > > quite some issues. It may exceptionally happen very early after a > > release because something doesn't work as expected or is incomplete, > > but we've long past this stage for both 1.8 and 1.9. However if you > > are willing to keep your own patch and apply it to your local tree, > > and just need some help to review it, I can help here. But I'd still > > recommend you to migrate to 2.0 ASAP, this will be less trouble for > > you than to maintain your patch set. > > > > Cheers, > > Willy >
