ndt-dev - [ndt-dev] Issue 61 in ndt: Middlebox test results are interpreted inconsistently
Subject: NDT-DEV email list created
List archive
[ndt-dev] Issue 61 in ndt: Middlebox test results are interpreted inconsistently
Chronological Thread
- From:
- To:
- Subject: [ndt-dev] Issue 61 in ndt: Middlebox test results are interpreted inconsistently
- Date: Mon, 30 Apr 2012 18:02:38 +0000
Status: Accepted
Owner:
Labels: Type-Defect Severity-Medium
New issue 61 by : Middlebox test results are interpreted inconsistently
http://code.google.com/p/ndt/issues/detail?id=61
The NDT client side interprets the middlebox "raw" test results in the order (notice the last two fields)
Server IP; Client IP; CurrentMSS;
WinScaleRecv; WinScaleSent;
But, the server code delivers the middlebox result-items in the order (notice last 2 fields again): Server
address; client address; currentMSS; WinScaleSent;WinScaleRecv;
This has to be made consistent, and documentation changed as necessary. I noticed this in version 3.6.4.
- [ndt-dev] Issue 61 in ndt: Middlebox test results are interpreted inconsistently, ndt, 04/30/2012
Archive powered by MHonArc 2.6.16.