TCP/Ip Analyzer **Post Results Here***

irishpal25

http://www.speedguide.net/analyzer.php TCP/IP Analyzer

post results here.

here is mine

TCP properties for IP = 84.203.8.52 ()
Browser/OS = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Notes: Read the Analyzer FAQ if the above is not your IP address.
TCP options string = 0204058401010402
MTU = 1452
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput. If you are using a router, it could be limiting your MTU regardless of Registry settings.
MSS = 1412
MSS is not optimized for broadband. Consider increasing your MTU value.
Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535

Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
519616 (MSS x 46 * scale factor of 8)
259808 (MSS x 46 * scale factor of 4)
129904 (MSS x 46 * scale factor of 2)
64952 (MSS x 46)
bandwidth * delay product (Note this is not a speed test):

Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 121 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)



26929229 connections tested since 03.10.2001.
Analyzer version: 1.07 - last updated 12.12.2005.

UberNewb

Here's mine for NTL Lucan:

TCP options string = 020405b401010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.
Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535

Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
 64240 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 117 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

irishpal25

noted. lol

Sponge Bob

do not feck with the MTU value ( especially if you don't know what it is) without checking with your BB provider , it could make things way worse.

JNive

and actually, due to PPPoE overhead, MTU for DSL is generally 1496 , unless otherwise directed ( cable is 1500 , but PPPoE is 1496 )

Tazzle

use PPPoA then

Sponge Bob

cant use PPPoA , only BT BB (their LLU exchanges) are PPPoA , all eircom Bitstream ...including resold variants ...are PPoE

dingding

Here is mine - Eircom BB

SpeedGuide.net TCP/IP Analyzer


TCP properties for IP = 86.42.3.126 ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 1.1.4322)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 0204058001010402
MTU = 1448
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput. If you are using a router, it could be limiting your MTU regardless of Registry settings.
MSS = 1408
MSS is not optimized for broadband. Consider increasing your MTU value.

Default TCP Receive Window (RWIN) = 16896
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 16896

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
518144 (MSS x 46 * scale factor of 8)
259072 (MSS x 46 * scale factor of 4)
129536 (MSS x 46 * scale factor of 2)
64768 (MSS x 46)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 675.84 kbps (84.48 KBytes/s) @ 200ms
Your TCP Window limits you to: 270.336 kbps (33.792 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = OFF
Time to live left = 122 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

Steffano2002

Here are my results but what is the point of knowing this?

wrote:

TCP properties for IP = 87.192.***.*** ()
Browser/OS = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Notes: Read the Analyzer FAQ if the above is not your IP address.
TCP options string = 0204058c0103030201010402
MTU = 1460
MTU is not fully optimized for broadband. Consider increasing your MTU to 1500 for better throughput. If you are using a router, it could be limiting your MTU regardless of Registry settings.
MSS = 1420
Maximum useful data in each packet = 1420, which equals MSS.
Default TCP Receive Window (RWIN) = 261280
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 65320

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
522560 (MSS x 46 * scale factor of 8)
130640 (MSS x 46 * scale factor of 2)
65320 (MSS x 46)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 10451.2 kbps (1306.4 KBytes/s) @ 200ms
Your TCP Window limits you to: 4180.48 kbps (522.56 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 116 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

Ardent

Steffano2002 wrote:

Here are my results but what is the point of knowing this?

That's what I want to know.

TempestSabre

Me three. What problems should we be looking for?

Sponge Bob

MTU Discovery (RFC1191) = ON (good)

MTU Discovery (RFC1191) = OFF (bad)

if on then its sorted automatically .

TempestSabre

Sponge Bob wrote:

MTU Discovery (RFC1191) = ON (good)

MTU Discovery (RFC1191) = OFF (bad)

if on then its sorted automatically .

What different does that make?

Sponge Bob

read up on fragmentation and mtu values

TempestSabre

Sponge Bob wrote:

read up on fragmentation and mtu values

RTFM

http://alive.znep.com/~marcs/mtu/

andrew163

JNive wrote:

and actually, due to PPPoE overhead, MTU for DSL is generally 1496 , unless otherwise directed ( cable is 1500 , but PPPoE is 1496 )

1492 isn't it?


(sorry...know it's only 4 of a difference....just...people screwing with this setting can really screw stuff up...)

wanwarlock

SpeedGuide.net TCP/IP Analyzer


TCP properties for IP = 84.***.**.*** ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405ac0103030301010402
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) = 522720
RWIN Scaling (RFC1323) = 3 bits (scale factor of 6)
Unscaled TCP Receive Window = 65340

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
511104 (MSS x 44 * scale factor of 8)
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: 20908.8 kbps (2613.6 KBytes/s) @ 200ms
Your TCP Window limits you to: 8363.52 kbps (1045.44 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 57 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

i'm on smart telecom. what's the fuss all about??? how do we decipher these results?

Tazzle

Sponge Bob wrote:

cant use PPPoA , only BT BB (their LLU exchanges) are PPPoA , all eircom Bitstream ...including resold variants ...are PPPoE

*buzz* wrong. Try PPPoA with VC multiplexing

Sponge Bob

is there a difference between radsl and ipstream products ?

http://www.jeacle.ie/pub/articles/adsl/

"The i-stream service uses a very common ADSL network configuration of PPPoE over RFC1483 bridged ethernet on ATM PVC 8/35."

kekegsm

Hi,

Anybody had a problem before, that after TCP Optimiser everything work (skype, bittorrent, etc), only the browsers not? (IE, Firefox, Mozilla, etc...)

watty

As Sponge Bob says unless you are a qualified Network Engineer, don't mess with this stuff.

PPoE is 1492 (usually). Operators (not on Bitstream) can do all kinds of wierd stuff, for reasons you can't see. Don't change ANYTHING ANYWHERE unless the ISP tells you.

Marlow

JNive wrote:

and actually, due to PPPoE overhead, MTU for DSL is generally 1496 , unless otherwise directed ( cable is 1500 , but PPPoE is 1496 )

Wireless is usually 1500, unless the provider is backhauling over something else than fiber.

/Martin

Battery Rover

Using BBnet wireless 2mb/2mb here in the sticks of County Limerick

What do these results mean?

TCP options string = 020405b401010402
 
MTU = 1500
MTU is fully optimized for broadband.
 
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.
 
Default TCP Receive Window (RWIN) = 17520 
RWIN Scaling (RFC1323) = 0 bits 
Unscaled TCP Receive Window = 17520 

RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS: 
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
 64240 (MSS x 44)
 
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 701 kbps (88 KBytes/s) @ 200ms
Your TCP Window limits you to: 280 kbps (35 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
 
MTU Discovery (RFC1191) = ON
 
Time to live left = 109 hops
TTL value is ok.
 
Timestamps (RFC1323) = OFF 
Selective Acknowledgements (RFC2018) = ON
 
IP type of service field (RFC1349) = 00000000 (0)
 

lucernarian

That TCP/IP receive window is quite small. That would limit your download speeds from the US, I'd expect.

@Marlow: I'm on Digiweb FWA and it uses PPPoE. My MTU is at 1492. And given by the location of the mast, it's definetely not using DSL for backhaul. Too far from the nearest exchange. And digiweb have a lot of customers, so I wouldn't say that 1492 is the exception either.

Redisle

TCP options string = 020405b40103030201010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.
Default TCP Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 64240

RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4) <-- current value
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 10278 kbps (1285 KBytes/s) @ 200ms
Your TCP Window limits you to: 4111 kbps (514 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 47 hops
TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

What use is this information to anyone??

subway

« SpeedGuide.net TCP Analyzer Results »
Tested on: 04.11.2007 07:37
IP address: 87.198.xx.xx

TCP options string: 020405b40103030001010402
MSS: 1460
MTU: 1500
TCP Window: 64240 (multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 64240
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 2570kbps (321KBytes/s)
BDP limit (500ms): 1028kbps (128KBytes/s)
MTU Discovery: ON
TTL: 113
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)


whats the point?

watty

To_be_confirmed wrote:

That TCP/IP receive window is quite small. That would limit your download speeds from the US, I'd expect.

@Marlow: I'm on Digiweb FWA and it uses PPPoE. My MTU is at 1492. And given by the location of the mast, it's definetely not using DSL for backhaul. Too far from the nearest exchange. And digiweb have a lot of customers, so I wouldn't say that 1492 is the exception either.

A lot of Digiweb backhaul is fibre. Some is their own fixed high capacity microwave links.

Yook

TCP properties for IP = 213.168.xx.xx
Browser/OS = Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20060601 Firefox/2.0.0.3 (Ubuntu-edgy)

TCP options string = 020405b40402080a0005d9420000000001030302
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1448, which is less than MSS because of Timestamps, or other TCP/IP options used.

Default TCP Receive Window (RWIN) = 5840
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 1460

RWIN seems to be set to a very small number. If you're on a broadband connection, consider using a larger value.
RWIN is a multiple of MSS
Other RWIN values that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 234 kbps (29 KBytes/s) @ 200ms
Your TCP Window limits you to: 93 kbps (12 KBytes/s) @ 500ms

Consider increasing your RWIN value to optimize TCP/IP for broadband.

MTU Discovery (RFC1191) = ON
Time to live left = 52 hops
TTL value is ok.
Timestamps (RFC1323) = ON

Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.

Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 00000000 (0)

Marlow

To_be_confirmed wrote:

@Marlow: I'm on Digiweb FWA and it uses PPPoE. My MTU is at 1492. And given by the location of the mast, it's definetely not using DSL for backhaul. Too far from the nearest exchange. And digiweb have a lot of customers, so I wouldn't say that 1492 is the exception either.

Anyone with more than 50-60 users should not be on DSL whatsoever, as the DSLAMs often are designed as cheap as possible and can't handle the tcp flow.

The MTU of 1492 can also be down to the type of equipment or the way Digiweb has set their network up. Anyhow, the MTU should not be tampered with by the enduser.

/Martin