8000 Look into increasing TCP backlock on listening socket · Issue #35 · ciscocsirt/netsarlacc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Look into increasing TCP backlock on listening socket #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bmenrigh opened this issue Jun 13, 2017 · 1 comment
Open

Look into increasing TCP backlock on listening socket #35

bmenrigh opened this issue Jun 13, 2017 · 1 comment

Comments

@bmenrigh
Copy link
Contributor

Go doesn't seem to provide a way to control the TCP backlog setting on a socket but if we create the socket with syscalls we should be able to.

@bmenrigh
Copy link
Contributor Author

From listen man page:

   The  backlog  argument  defines the maximum length to which the queue of pending connections for sockfd may grow.  If a connection request arrives when the queue is full, the client may receive an
   error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds.

   The behavior of the backlog argument on TCP sockets changed with Linux 2.2.  Now it specifies the queue length for completely established sockets waiting to be accepted, instead of the  number  of
   incomplete  connection  requests.   The maximum length of the queue for incomplete sockets can be set using /proc/sys/net/ipv4/tcp_max_syn_backlog.  When syncookies are enabled there is no logical
   maximum length and this setting is ignored.  See tcp(7) for more information.

   If the backlog argument is greater than the value in /proc/sys/net/core/somaxconn, then it is silently truncated to that value; the default value in this file is 128.  In  kernels  before  2.4.25,
   this limit was a hard coded value, SOMAXCONN, with the value 128.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
< 304E !-- -->
Development

No branches or pull requests

1 participant
0