| To: | Cacophonix <cacophonix@xxxxxxxxx> |
|---|---|
| Subject: | Re: 2.4.1: TCP assertion failed |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Sun, 18 Feb 2001 12:55:55 -0500 (EST) |
| Cc: | <kuznet@xxxxxxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20010218175128.5008.qmail@web119.yahoomail.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Sun, 18 Feb 2001, Cacophonix wrote: > If possible you may want to test in the presence of asymmetric routing - that > often causes problems with devices like these that rewrite tcp window > advertisements > in the middle of the network - i.e, traffic in the forward direction flows > through > the device, but in the reverse direction does not. Actually, route asymmetry may not be much of a factor here. Most of these devices are at the client's edge as opposed to the server end i.e they protect the client's network portion of the resources. So you will come and go via them. (in any case the above test would be sufficient if done one way). cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.4.1: TCP assertion failed, Cacophonix |
|---|---|
| Next by Date: | Re: 2.4.1: TCP assertion failed, Cacophonix |
| Previous by Thread: | Re: 2.4.1: TCP assertion failed, Cacophonix |
| Next by Thread: | Re: 2.4.1: TCP assertion failed, Cacophonix |
| Indexes: | [Date] [Thread] [Top] [All Lists] |