IP type of service field (RFC1349) (DefaultTOSValue)

[Sharky2006]

The following is my results from the SpeedGuide.net TCP/IP Analyzer:

TCP options string = 020405ac0103030401010402

MTU = 1492

MTU is optimized for PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.

MSS = 1452

MSS is optimized for PPPoE DSL broadband. If not, consider raising your MTU value.

Default TCP Receive Window (RWIN) = 1045440

RWIN Scaling (RFC1323) = 4 bits (scale factor of

Unscaled TCP Receive Window = 65340

RWIN is a multiple of MSS

Other RWIN values that might work well with your current MTU/MSS:

511104 (MSS x 44 * scale factor of

255552 (MSS x 44 * scale factor of 4)

127776 (MSS x 44 * scale factor of 2)

63888 (MSS x 44)

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 41817.6 Kbps (5227.2 KBytes/s) @ 200ms

Your TCP Window limits you to: 16727.04 Kbps (2090.88 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 56 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349) = 01011100 (92)

Precedence (priority) = 010 (immediate)

Delay = 1 (low delay)

Throughput = 1 (high throughput)

Reliability = 1 (high reliability)

Cost = 0 (normal cost)

Check bit = 0 (correct, 8th checking bit must be zero)

DiffServ (RFC 2474) = No valid DiffServ equivalent. See the TCP Optimizer documentation, or RFCs 2474, 2475, 2597, 2598, 2873.

Do I have to change something here...?  No valid DiffServ Equivalent? 

[FallowEarth]

What are your advertised speeds?

[Sharky2006]

Verizon DSL 1.5 and 368 (I think?).

Sorry for late response.  Have a couple of sick children.

[Sharky2006]

Do I have the right TOS value?  Currently at 92. I previously had it at 240 but I read that this was too high..is this true?

[Guest jeffwalker9999]

I had asked this ?? a few weeks ago and vanb

answered with some sites to visit

that answered this question

see this post

http://www.testmy.net/forum/index.php?topic=11410.0

quote from http://www.dslnuts.com/2kxp.shtml

also read this thread http://www.broadbandnuts.com/index.php?PHPSESSID=0129428731711f0c451c6edb09cd5dd2&topic=1878.0

VanBuren

[Sharky2006]

I read all of that and as a matter of fact this is where I read about TOS value and tried the 92 setting.  I still don't know if it is right.  In laments terms (is that spelled right...?) can you explain what this means and where I should be or how I could figure out the right TOS value (sort of like "TOS for Dummies" for me).

I thank you in advance.

[cholla]

I'm not an expert on this  I found this on the web & put it together.I changed mine to 80 it was 92.

The IP Type of Service has the following fields:

  Bits 0-2:  Precedence.

  Bit    3:  0 = Normal Delay,      1 = Low Delay.

  Bits  4:  0 = Normal Throughput, 1 = High Throughput.

  Bits  5:  0 = Normal Relibility, 1 = High Relibility.

  Bit  6-7:  Reserved for Future Use.

Bit #0-2: [128 64 32]     

Bit #3: [16]   

Bit #4: [8]

Bit #5: [4]

Bit #6-7: [Reserved]

Bits 0,1,2 = Priority Control:

 

  111 - Network Control use 128 + 64 + 32 = 224

  110 - Internetwork Control 128 +64 + 0 = 192

  101 - CRITIC/ECP          128 + 0 + 32 = 160

  100 - Flash Override      128 + 0 +  0 = 128 

  011 - Flash                  0 + 64 + 32 = 96

  010 - Immediate              0 + 64 + 0  = 64

  001 - Priority              0 +  0 + 32 = 32

  000 - Routine                0 +  0 +  0=  0

Bit #0-2: [128 64 32]  If I understand this 128 is on for bit 0;64 is on for bit 1,32 is on

for bit 2.

Bit #3: [16] 16= on; 0 = off

Bit #4: [8]  8=on;  0 = off

Bit #5: [4]  4=on;  0 = off

Bit #6-7: [Reserved] Both of these have 0 for value.

From what I read on this You can only have either low delay on or High Throughput on not

both.If you set both I think your OS uses the default.Quote below:

"The TOS value is used to indicate "better".  Only one TOS value or

property can be requested in any one IP datagram.

Generally, protocols which are involved in direct interaction with a

human should select low delay, while data transfers which may involve

large blocks of data are need high throughput.  Finally, high reliability

is most important for datagram-based Internet management functions.

Application protocols not included in these tables should be able to

make appropriate choice of low delay (8 decimal, 1000 binary) or high

throughput (4 decimal, 0100 binary)."

"Reading RCF 1349, it states you have 5 choices in TOS.

            0000    (all normal)                        Use default metric

            1000    (minimize delay)                  Use delay metric

            0100    (maximize throughput)          Use default metric

            0010    (maximize reliability)            Use reliability metric

            0001    (minimize monetary cost)      Use cost metric

            other                                                  Use default metric"

"Anything higher then 010, Immediate, are ment for internal network use. Meaning packets

that are not ment to route to the internet."

So for most I beleive one of these two would be correct:

72 which is Immediate, High Throughput, 010 010 00  That's64forImmediate+8forHighThroughput

80  which is Immediate, Low Delay,  010 100 00