[jira] [Commented] (TS-1075) Port range bottleneck in transparent proxy mode

["B Wyatt (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224821#comment-13224821 ] 

B Wyatt commented on TS-1075:
-----------------------------

I will investigate as this will no doubt bite me as well (it may be biting me already).
                
> Port range bottleneck in transparent proxy mode
> -----------------------------------------------
>
>                 Key: TS-1075
>                 URL: https://issues.apache.org/jira/browse/TS-1075
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.1
>         Environment: Centos 5.6, kernel 2.6.39.2 compiled with TPROXY support
> ATS compiled as: ./configure --enable-tproxy 
>            Reporter: Danny Shporer
>            Assignee: B Wyatt
>             Fix For: 3.1.3
>
>         Attachments: ports.patch
>
>
> The Linux TPROXY stack only takes into account the local addresses when using dynamic bind (bind without specifying a specific port). This limits the port range to only the local range (around 30K by default and can be extended to around 64K) - this together with the TIME-WAIT Linux method of releasing ports causes a bottleneck).
> One symptom of this is that traffic_cop cannot open a connection to the server to monitor it (it gets error 99 - address already in use) and kills it. 
> Another issue is when opening the connection to the server.

--
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