[
https://issues.apache.org/jira/browse/TS-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396092#comment-13396092
]
Alan M. Carroll commented on TS-1303:
-------------------------------------
The config settings in use here are now deprecated and will be probably be
removed for 3.3. HTTP ports are now configured via the
proxy.config.http.server_ports
value. Note the plural!
This single settings configures all ports and their properties. To use it for
this case, you should use
STRING 3128:ipv6:tr-full
The setting can have multiple port specifications, separated by space or comma.
There are additional comments in the default records.config .
This replaces all the various port configuration values in to a single value,
including SSL port configuration. There is no longer the main port and other
ports, and SSL ports, there is only this setting.
I will look a bit but I will probably mark this as "won't fix". I tried to
preserve backwards compatibility but I seem to have missed this case.
> The 3.1.4 ATS build - trafficserver is broken from 3.0.2 and does not listen
> on the IPv6 interface when server_port_attr is set to =6
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TS-1303
> URL: https://issues.apache.org/jira/browse/TS-1303
> Project: Traffic Server
> Issue Type: Bug
> Components: Network
> Affects Versions: 3.1.4
> Environment: IPv6 Redhat 6.1
> Reporter: leo mcalinden
> Labels: ipv6
>
> On ATS 3.1.4 changing server_port_attr to:
> CONFIG proxy.config.http.server_port_attr STRING =6
> ...doesn't bring up an IPv6 socket? We get:
> # netstat -an | grep 3128
> tcp 0 0 0.0.0.0:3128 0.0.0.0:*
> LISTEN
> ...previously on ATS/3.0.2 this was fine:
> # netstat -an | grep 3128
> tcp 0 0 :::3128 :::*
> LISTEN
> This will have a major impact on IPv6 functionality.
> Any ideas what's wrong or how to fix this - or workaround this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
