Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, 9 September 2018 02:24, Neal Cardwell wrote:
> By default, and essentially always in practice (AFAIK), Linux
> installations enable syncookies. With syncookies, there is essentially
> no limit on the syn queue, o
On Sat, Sep 8, 2018 at 11:23 AM Ttttabcd wrote:
>
> Thank you very much for your previous answer, sorry for the inconvenience.
>
> But now I want to ask you one more question.
>
> The question is why we need two variables to control the syn queue?
>
> The first is the "backlog" parameter of the "l
Thank you very much for your previous answer, sorry for the inconvenience.
But now I want to ask you one more question.
The question is why we need two variables to control the syn queue?
The first is the "backlog" parameter of the "listen" system call that controls
the maximum length limit of
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On 4 September 2018 9:06 PM, Neal Cardwell wrote:
> On Tue, Sep 4, 2018 at 1:48 AM Ttttabcd a...@protonmail.com wrote:
>
> > Hello everyone,recently I am looking at the source code for handling TCP
> > three-way handsha
On Tue, Sep 4, 2018 at 1:48 AM Ttttabcd wrote:
>
> Hello everyone,recently I am looking at the source code for handling TCP
> three-way handshake(Linux Kernel version 4.18.5).
>
> I found some strange places in the source code for handling syn messages.
>
> in the function "tcp_conn_request"
>
>
On 09/03/2018 10:31 PM, Ttttabcd wrote:
> Hello everyone,recently I am looking at the source code for handling TCP
> three-way handshake(Linux Kernel version 4.18.5).
>
> I found some strange places in the source code for handling syn messages.
>
> in the function "tcp_conn_request"
>
> This
Hello everyone,recently I am looking at the source code for handling TCP
three-way handshake(Linux Kernel version 4.18.5).
I found some strange places in the source code for handling syn messages.
in the function "tcp_conn_request"
This code will be executed when we don't enable the syn cookies
