From: David Miller <davem@redhat.com>
To: eric.dumazet@gmail.com
Cc: fw@strlen.de, hannes@stressinduktion.org, netdev@vger.kernel.org
Subject: Re: updates to syncookies - timestamps not needed any more (freebsd)
Date: Fri, 12 Jul 2013 16:37:20 -0700 (PDT) [thread overview]
Message-ID: <20130712.163720.1878859530623469256.davem@redhat.com> (raw)
In-Reply-To: <1373639563.10804.10.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 12 Jul 2013 07:32:43 -0700
> Another quick hack would be to allow sack being generated by the client.
>
> If we receive sackOK in SYN, then syncookie SYNACK could contain sackOK,
> if timestamps are not used.
>
> Client would be allowed to use SACK in his ACK. Server would not
> generate SACK, but would process incoming SACK.
>
> Not sure what could break ?
This seems quite clumsy and would result in being able to use SACK only
in one direction.
There has to be a better way.
next prev parent reply other threads:[~2013-07-12 23:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 16:04 updates to syncookies - timestamps not needed any more (freebsd) Hannes Frederic Sowa
2013-07-08 16:39 ` Eric Dumazet
2013-07-08 18:09 ` Hannes Frederic Sowa
2013-07-11 23:57 ` David Miller
2013-07-12 1:41 ` Hannes Frederic Sowa
2013-07-12 2:25 ` Eric Dumazet
2013-07-12 6:59 ` richard -rw- weinberger
2013-07-12 15:22 ` Rick Jones
2013-07-12 16:18 ` Eric Dumazet
2013-07-12 16:33 ` Rick Jones
2013-07-12 17:00 ` Eric Dumazet
2013-07-12 7:24 ` David Miller
2013-07-12 8:41 ` Florian Westphal
2013-07-12 14:04 ` Eric Dumazet
2013-07-12 14:25 ` Florian Westphal
2013-07-12 14:32 ` Eric Dumazet
2013-07-12 23:37 ` David Miller [this message]
2013-07-26 6:45 ` Hannes Frederic Sowa
2013-07-26 12:56 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130712.163720.1878859530623469256.davem@redhat.com \
--to=davem@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).