From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Perry Lorier" <perryl@google.com>,
"Matt Mathis" <mattmathis@google.com>,
"Yuchung Cheng" <ycheng@google.com>,
"Neal Cardwell" <ncardwell@google.com>,
"Tom Herbert" <therbert@google.com>,
"Wilmer van der Gaast" <wilmer@google.com>,
"Dave Täht" <dave.taht@bufferbloat.net>,
"Ankur Jain" <jankur@google.com>
Subject: Re: [PATCH net-next] tcp: be more strict before accepting ECN negociation
Date: Fri, 04 May 2012 14:01:42 -0700 [thread overview]
Message-ID: <4FA443B6.9010106@hp.com> (raw)
In-Reply-To: <1336164546.3752.460.camel@edumazet-glaptop>
>
> Interesting indeed ;)
>
> Did you check if it was spoofed ?
>
> (did the 3WHS really completed)
Well, the tcpdump command was still:
tcpdump -i eth0 -vvv '(tcp[tcpflags]& tcp-syn != 0)&& (ip[1] != 0x0)'
I didn't see any SYN|ACKs go out, but netperf.org would have had to set
ECT for me to see a SYN|ACK going out. FWIW, this is on a 2.6.31-15
(Ubuntu) kernel with net.ipv4.tcp_ecn = 2 and I don't think the SYNs
themselves were negotiating ECN:
13:26:16.866007 IP (tos 0x3,CE, ttl 41, id 28850, offset 0, flags [DF],
proto TCP (6), length 64)
somesystemin.de.55363 > www.netperf.org.www: Flags [S], cksum
0x4cfc (correct), seq 304457158, win 65535, options [mss 1460,nop,wscale
rick
next prev parent reply other threads:[~2012-05-04 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 15:14 [PATCH net-next] tcp: be more strict before accepting ECN negociation Eric Dumazet
2012-05-04 15:54 ` Neal Cardwell
2012-05-04 16:06 ` David Miller
2012-05-04 18:09 ` Rick Jones
2012-05-04 18:23 ` Eric Dumazet
2012-05-04 18:48 ` Rick Jones
2012-05-04 19:05 ` Eric Dumazet
2012-05-04 20:20 ` Rick Jones
2012-05-04 20:36 ` Rick Jones
2012-05-04 20:49 ` Eric Dumazet
2012-05-04 21:01 ` Rick Jones [this message]
2012-05-04 21:14 ` 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=4FA443B6.9010106@hp.com \
--to=rick.jones2@hp.com \
--cc=dave.taht@bufferbloat.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jankur@google.com \
--cc=mattmathis@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=perryl@google.com \
--cc=therbert@google.com \
--cc=wilmer@google.com \
--cc=ycheng@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.