[
https://issues.apache.org/jira/browse/TS-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715243#comment-13715243
]
Alan M. Carroll commented on TS-2055:
-------------------------------------
The root problem here isn't obvious. ATS is operating in transparent mode with
use_client_source_port. A connection from client A:P arrives at TS. TS then
tries to create a second connection, originating on the TS box, with a source
of A:P. However, this seems to fail if P is the same port as any INADDRY_ANY
bound listening socket even though A is a foreign address. If the listen socket
is bound to a specific address, this does not happen. Currently the auto_conf
port for ATS is always bound to INADDR_ANY and so will always interfere causing
dropped connections. I think it reasonable to implement both of these solutions.
In the first case, if autoconf.localport_only is set, then only connections
from the localhost are permitted. In this case binding to INADDR_LOOPBACK is
the correct thing to do (as is the case with the "backdoor" port, default 8084).
In the second case, it's frequently useful to be able to force specific
addresses for ATS originated services.
> make port 8083 interface configurable - for src port TP purposes
> -----------------------------------------------------------------
>
> Key: TS-2055
> URL: https://issues.apache.org/jira/browse/TS-2055
> Project: Traffic Server
> Issue Type: Improvement
> Components: Management
> Reporter: Aidan McGurn
>
> the mgmt port 8083 is currently wildcard (INADDR_ANY) with no means to change
> this. We have changed this for now to be INADDR_LOOPBACK and as directed by
> Alan are opening a TS Jira to get this a configurable item (or at least one
> of these options he mentioned):
> (1) set this to LOOPBACK if autoconf.localport_only is set or
> (2) add a configuration value to explicit set the binding IP address.
> The driver for this is we require a src port TP system. Testing shows that
> this is one of the ports causing a 502 bind issue (on the OS backend
> connection) as its already in use. Binding to explicit interface should solve
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
