ndt-users - Re: 5.4.8 may misreport window scaling
Subject: ndt-users list created
List archive
- From: Richard Carlson <>
- To: Peter Van Epp <>,
- Subject: Re: 5.4.8 may misreport window scaling
- Date: Fri, 25 Aug 2006 09:11:37 -0400
Hi Peter;
Us the "More Details" button and let me know what the variables
RcvWinScale
SndWinScale
WinScaleRcvd
WinScaleSent
report?
Rich
At 07:56 PM 8/24/2006, Peter Van Epp wrote:
Lixin is just reinstalling the old version to check but we think
window scaling reporting is broken. Both the server and the client have
window scaling enabled and indeed tcp seems to be negotiating it correctly
but the ndt server reports window scaling off. We ran in to problems trying
to go back to our old version on this machine, but the old version on the
test machine reports (correctly as far as we can see) that window scaling is
on.
---- Data Link Control (DLC) ----
Destination: 0014F6909DA1 [No Vendor Name. - 909DA1] [0014F6909DA1]
Source: 0001F4069842 [No Vendor Name. - 069842] [0001F4069842]
EtherType: 0x8100 (IEEE 802.1Q - Virtual LAN)
---- IEEE 802.1Q - Virtual Bridged Local Area Networks (IEEE 802.1Q) ----
Priority/CFI/VID: 0x020B
: 000. .... .... .... Priority Level: 0
: ...0 .... .... .... Canonical Format
: .... 0010 0000 1011 VLan Identifier: 523
EtherType: 0x0800 (Internet Protocol (IP))
---- Internet Protocol (IP) ----
Version/Header Length: 0x45
: 0100 .... Version 4
: .... 0101 20 bytes - Header Length
Type of Service: 0x00
: 000. .... Routine
: ...0 .... Normal Delay
: .... 0... Normal Throughput
: .... .0.. Normal Reliability
: .... ..0. Normal Monetary Cost
: .... ...0 Not Used
Total Length: 48 bytes
Identification: 0
Flags/Fragment Offset: 0x4000
: 0... .... .... .... Not Used
: .1.. .... .... .... Don't Fragment
: ..0. .... .... .... Last Fragment
: ...0 0000 0000 0000 Fragment Offset: 0 bytes
Time to Live: 62 seconds/hops
Protocol ID: 6 (TCP)
CheckSum: 0x5615 (Correct)
Source Address: 142.58.200.253
Destination Address: 142.58.1.65
: [28 bytes of data]
---- Transmission Control Protocol (TCP) ----
Source Port: 7123
Destination Port: 2822
Sequence Number: 1123305805 (next expected sequence number: 1123305806)
Acknowledgement Number: 2721899098
Header Length: 0x70
: 0111 .... 28 bytes - Header Length
: .... 0000 Not Used
Flags: 0x12
: 00.. .... Not Used
: ..0. .... No URG
: ...1 .... Acknowledgement
: .... 0... No PSH
: .... .0.. No RST
: .... ..1. Synchronize
: .... ...0 No FIN
Window Size: 5840
CheckSum: 0x4ED2 (Correct)
Urgent Pointer: 0
Options Present:
Kind: 2 (Maximum Segment Size)
Length: 4 bytes
Maximum Segment Size: 1460
Kind: 1 (No Operation)
Kind: 3 (Window Scale Factor)
Length: 3 bytes
Shift Count: 8
---- Data/FCS ----
Data/Padding: [0 bytes]
Frame Check Sequence: 0x25867E5F (Correct)
---- Data Link Control (DLC) ----
Destination: 0001F4069842 [No Vendor Name. - 069842] [0001F4069842]
Source: 0014F6909DA1 [No Vendor Name. - 909DA1] [0014F6909DA1]
EtherType: 0x8100 (IEEE 802.1Q - Virtual LAN)
---- IEEE 802.1Q - Virtual Bridged Local Area Networks (IEEE 802.1Q) ----
Priority/CFI/VID: 0x820B
: 100. .... .... .... Priority Level: 4
: ...0 .... .... .... Canonical Format
: .... 0010 0000 1011 VLan Identifier: 523
EtherType: 0x0800 (Internet Protocol (IP))
---- Internet Protocol (IP) ----
Version/Header Length: 0x45
: 0100 .... Version 4
: .... 0101 20 bytes - Header Length
Type of Service: 0x00
: 000. .... Routine
: ...0 .... Normal Delay
: .... 0... Normal Throughput
: .... .0.. Normal Reliability
: .... ..0. Normal Monetary Cost
: .... ...0 Not Used
Total Length: 60 bytes
Identification: 56985
Flags/Fragment Offset: 0x4000
: 0... .... .... .... Not Used
: .1.. .... .... .... Don't Fragment
: ..0. .... .... .... Last Fragment
: ...0 0000 0000 0000 Fragment Offset: 0 bytes
Time to Live: 63 seconds/hops
Protocol ID: 6 (TCP)
CheckSum: 0x766F (Correct)
Source Address: 142.58.1.65
Destination Address: 142.58.200.253
: [40 bytes of data]
---- Transmission Control Protocol (TCP) ----
Source Port: 2822
Destination Port: 7123
Sequence Number: 2721899097 (next expected sequence number: 2721899098)
Acknowledgement Number: 0
Header Length: 0xA0
: 1010 .... 40 bytes - Header Length
: .... 0000 Not Used
Flags: 0x02
: 00.. .... Not Used
: ..0. .... No URG
: ...0 .... No ACK
: .... 0... No PSH
: .... .0.. No RST
: .... ..1. Synchronize
: .... ...0 No FIN
Window Size: 5840
CheckSum: 0x6252 (Correct)
Urgent Pointer: 0
Options Present:
Kind: 2 (Maximum Segment Size)
Length: 4 bytes
Maximum Segment Size: 1460
Kind: 4 (TCP Selective Ack Permitted)
Length: 2 bytes
Kind: 8 (Timestamp)
Length: 10 bytes
Timestamp Value: 15552
Timestamp Echo Reply: 0
Kind: 1 (No Operation)
Kind: 3 (Window Scale Factor)
Length: 3 bytes
Shift Count: 2
---- Data/FCS ----
Data/Padding: [0 bytes]
Frame Check Sequence: 0xEA2AD350 (Correct)
Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada
------------------------------------
Richard A. Carlson e-mail:
Network Engineer phone: (734) 352-7043
Internet2 fax: (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor, MI 48104
- 5.4.8 may misreport window scaling, Peter Van Epp, 08/24/2006
- Re: 5.4.8 may misreport window scaling, Richard Carlson, 08/25/2006
- Re: 5.4.8 may misreport window scaling, Peter Van Epp, 08/25/2006
- Re: 5.4.8 may misreport window scaling, Richard Carlson, 08/28/2006
- Re: 5.4.8 may misreport window scaling, Peter Van Epp, 08/28/2006
- Re: 5.4.8 may misreport window scaling, Richard Carlson, 08/28/2006
- Re: 5.4.8 may misreport window scaling, Peter Van Epp, 08/25/2006
- Re: 5.4.8 may misreport window scaling, Richard Carlson, 08/25/2006
Archive powered by MHonArc 2.6.16.