[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IPSec Standard - No Flow Control?

To: "Chinmay Patel" <chinmay.patel@corrent.com>
Subject: Re: IPSec Standard - No Flow Control?
From: Bill Sommerfeld <sommerfeld@East.Sun.COM>
Date: Mon, 23 Jul 2001 16:51:58 -0400
cc: "Michael Thomas" <mat@cisco.com>, Rett_Walters@payless.com, ipsec@lists.tislabs.com
In-reply-to: Your message of "Mon, 23 Jul 2001 13:06:57 PDT." <B376E5AC41E3614794DF7408F0266AA021A5E3@CORMAIL01.corrent.com>
Reply-to: sommerfeld@East.Sun.COM
Sender: owner-ipsec@lists.tislabs.com

The trace does not show a large number of packets "in flight" (only 4
or 5); increasing the anti-replay window is thus unlikely to help.
I'm suspicious that there might also be a bug in the host tcp (perhaps
connected with sending segments smaller than the peer's MSS due to
ipsec overhead); getting a packet trace after decryption or before
encryption which included the tcp sequence numbers would help in
pointing fingers.

					- Bill

References:

RE: IPSec Standard - No Flow Control?

From: "Chinmay Patel" <chinmay.patel@corrent.com>

Prev by Date: Re: IPSec Standard - No Flow Control?
Next by Date: RE: What does SIT_IDENTITY_ONLY mean?
Prev by thread: RE: IPSec Standard - No Flow Control?
Next by thread: Re: IPSec Standard - No Flow Control?
Index(es):
- Main
- Thread