[PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP

2010-12-08 Thread Martin Willi
Add TFC padding to all packets smaller than the boundary configured on the xfrm state. If the boundary is larger than the PMTU, limit padding to the PMTU. Signed-off-by: Martin Willi --- net/ipv4/esp4.c | 32 1 files changed, 24 insertions(+), 8 deletions(-) d

Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP

2010-12-08 Thread Herbert Xu
On Wed, Dec 08, 2010 at 10:20:41AM +0100, Martin Willi wrote: > > > In particular, why would we need a boundary at all? Setting it to > > anything other than the PMTU would seem to defeat the purpose of > > TFC for packets between the boundary and the PMTU. > > I don't agree, this highly depends

Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP

2010-12-08 Thread Martin Willi
> In particular, why would we need a boundary at all? Setting it to > anything other than the PMTU would seem to defeat the purpose of > TFC for packets between the boundary and the PMTU. I don't agree, this highly depends on the traffic on the SA. For a general purpose tunnel with TCP flows, PMT

Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP

2010-12-08 Thread Herbert Xu
On Tue, Dec 07, 2010 at 11:29:03AM +0100, Martin Willi wrote: > Add TFC padding to all packets smaller than the boundary configured > on the xfrm state. If the boundary is larger than the PMTU, limit > padding to the PMTU. Thanks for the update Martin. However, I still think it's more complicated

[PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP

2010-12-07 Thread Martin Willi
Add TFC padding to all packets smaller than the boundary configured on the xfrm state. If the boundary is larger than the PMTU, limit padding to the PMTU. Signed-off-by: Martin Willi --- net/ipv4/esp4.c | 33 + 1 files changed, 25 insertions(+), 8 deletions(-)