Re: [PATCH net-next 2/2] tcp: allow to turn tcp timestamp randomization off

2016-11-29 Thread Florian Westphal
Eric Dumazet wrote: > On Tue, 2016-11-29 at 16:45 +0100, Florian Westphal wrote: > > Eric says: "By looking at tcpdump, and TS val of xmit packets of multiple > > flows, we can deduct the relative qdisc delays (think of fq pacing). > > This should work even if we have one flow per remote peer." >

Re: [PATCH net-next 2/2] tcp: allow to turn tcp timestamp randomization off

2016-11-29 Thread Eric Dumazet
On Tue, 2016-11-29 at 16:45 +0100, Florian Westphal wrote: > Eric says: "By looking at tcpdump, and TS val of xmit packets of multiple > flows, we can deduct the relative qdisc delays (think of fq pacing). > This should work even if we have one flow per remote peer." > > Having random per flow (or

[PATCH net-next 2/2] tcp: allow to turn tcp timestamp randomization off

2016-11-29 Thread Florian Westphal
Eric says: "By looking at tcpdump, and TS val of xmit packets of multiple flows, we can deduct the relative qdisc delays (think of fq pacing). This should work even if we have one flow per remote peer." Having random per flow (or host) offsets doesn't allow that anymore so add a way to turn this o