4 May 2012 23:01
Re: [PATCH net-next] tcp: be more strict before accepting ECN negociation
Rick Jones <rick.jones2 <at> hp.com>
2012-05-04 21:01:42 GMT
2012-05-04 21:01:42 GMT
>
> 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
RSS Feed