[
https://issues.apache.org/jira/browse/TS-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865609#comment-13865609
]
James Peach commented on TS-2482:
---------------------------------
I expect that then IPv6 support was added, the author did not want to deal with
SOCKS, so they tried to force SOCKS to always use IPv4. Over time, those
assumptions probably changed and now SOCKS gets hit by IPv6 connections.
> Problems with SOCKS
> -------------------
>
> Key: TS-2482
> URL: https://issues.apache.org/jira/browse/TS-2482
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Radim Kolar
>
> There are several problems with using SOCKS. I am interested in case when TF
> is sock client. Client sends HTTP request and TF uses SOCKS server to make
> connection to internet.
> a/ - not documented enough in default configs
> From default configs comments it seems that for running
> TF 4.1.2 as socks client, it is sufficient to add one line to socks.config:
> dest_ip=0.0.0.0-255.255.255.255 parent="10.0.0.7:9050"
> but socks proxy is not used. If i run tcpdump sniffing packets TF never
> tries to connect to that SOCKS.
> From source code -
> https://github.com/apache/trafficserver/blob/master/iocore/net/Socks.cc it
> looks that is needed to set "proxy.config.socks.socks_needed" to activate
> socks support. This should be documented in both sample files: socks.config
> and record.config
> b/
> after enabling socks, i am hit by this assert:
> Assertion failed: (ats_is_ip4(&target_addr)), function init, file Socks.cc,
> line 65.
> i run on dual stack system (ip4,ip6).
> This code is setting default destination for SOCKS request? Can not you use
> just 127.0.0.1 for case if client gets connected over IP6?
> https://github.com/apache/trafficserver/blob/master/iocore/net/Socks.cc#L66
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
