Open john-d13 opened 5 years ago
No. That's inefficient and is not a common requirement.
john-d13 notifications@github.com 于 2019年5月23日周四 05:29写道:
Is it possible to have redsocks2 forward incoming UDP traffic to a destination Proxy over connect type "http-connect" via redudp module or any other method for that matter.
Seems I can only set type="socks5" or "shadowsocks". When setting http-connect it generates a parsing error.
redsocks2: file parsing error at line 109: section->onexit failed
Thanks for your assistance.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/semigodking/redsocks/issues/119?email_source=notifications&email_token=AAP2XD3WDF6D3SIGPQIG4ZDPWW3LDA5CNFSM4HOYELTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVKBO2Q, or mute the thread https://github.com/notifications/unsubscribe-auth/AAP2XD4OFMHVU4G53QCNKZ3PWW3LDANCNFSM4HOYELTA .
I was under the impression the "redudp" attribute implied to route UDP traffic through redsocks to a destination proxy server. I guess its only used to define a fixed destination DNS server for DNS over TCP.
My use case is; Route all incoming VPN TCP traffic on tun0 interface to redsocks chain via IPTABLES. I want to mitigate leaks or redirect BitTorrent traffic into the redsocks chain but that would imply a UDP rule set.
As you want to forward UDP packets, you need proxy protocol that supports forwarding UDP packets. Obviously, HTTP-Connect does not.
Is it possible to have redsocks2 forward incoming UDP traffic to a destination Proxy over connect type "http-connect" via redudp module or any other method for that matter.
Seems I can only set type="socks5" or "shadowsocks". When setting http-connect it generates a parsing error.
redsocks2: file parsing error at line 109: section->onexit failed
Thanks for your assistance.