HELP wanted: wireless broadband tweak

[uncommonjo]

Hello,

Thank god for a site like This. I'm getting only like 270 kbps instead of the advertise 1 Mbps. The MTU and RWIN on tcpanalyser doesn't reflect the new MTU I set through TCPoptimizer.

1. What type of connection do you have? I'm using a 1 Mbps wireless broadband in malaysia as advertised here. Jaring wilress broadband.

. The technology is soma networks.

2. Who is your ISP and what is your advertised speed from them? My ISP is Jaring. And the advertised speed is 1MBps.

3. What are your current settings now? Do a TCP/IP Analyzer Test and copy and paste the results (remember to XXXXX out your IP address) here.

TCP options string = 020405a00103030201010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising your MTU value.
Default TCP Receive Window (RWIN) = 256960
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled TCP Receive Window = 64240

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
506880 (MSS x 44 * scale factor of 8)
253440 (MSS x 44 * scale factor of 4)
126720 (MSS x 44 * scale factor of 2)
63360 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
Your TCP Window limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops

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


4. Please tell us your operating system i.e. 95, 98, 98SE, ME, 2K or XP.
XP

I'm using DI-724p+ as my router. The router connects to the wireless modem through ethernet. My computer's connectd to the router through ethernet. I'm also using windows firewall.

Thank you

[uncommonjo]

statistic result from http://nitro.ucsc.edu/

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 76.95Kb/s
running 10s inbound test (server to client) . . . . . . 36.94kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_08

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 500.74 msec; the Packet size = 1440 Bytes; and
There were 6 packets retransmitted, 9 duplicate acks received, and 4 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 1.8 seconds (15.0%) of the time
This connection is network limited 99.98% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [202.190.133.197] but Client says [192.168.0.128]

[uncommonjo]

more detail result from http://nitro.ucsc.edu/

WEB100 Kernel Variables:
Client: localhost/127.0.0.1

Checking for mismatch on uplink
(speed > 50 [0>50], (xmitspeed < 5) [0.07<5]
(rwintime > .9) [0>.9], (loss < .01) [0.02<.01]
Checking for excessive errors condition
(loss/sec > .15) [0.00>.15], (cwndtime > .6) [0.99>.6],
(loss < .01) [0.02<.01], (MaxSsthresh > 0) [4320>0]
Checking for 10 Mbps link
(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
(xmitspeed < 9.5) [0.07<9.5] (loss < .01) [0.02<.01], (mylink > 0) [3.0>0]
Checking for Wireless link
(sendtime = 0) [2.0E=0], (speed < 5) [0<5]
(Estimate > 50 [0.13>50], (Rwintime > 90) [0>.90]
(RwinTrans/CwndTrans = 1) [0/1=1], (mylink > 0) [3.0>0]
Checking for DSL/Cable Modem link
(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
(SendTime = 0) [2.0E-4=0], (mylink > 0) [3.0>0]
Checking for half-duplex condition
(rwintime > .95) [0>.95], (RwinTrans/sec > 30) [0>30],
(SenderTrans/sec > 30) [0.08>30], OR (mylink <= 10) [3.0<=10]
Checking for congestion
(cwndtime > .02) [0.99>.02], (mismatch = 0) [0=0]
(MaxSsthresh > 0) [4320>0]

estimate = 0.13 based on packet size = 11Kbits, RTT = 500.74msec, and loss = 0.027777778
The theoretical network limit is 0.13 Mbps
The NDT server has a 8192.0 KByte buffer which limits the throughput to 127.81 Mbps
Your PC/Workstation has a 250.0 KByte buffer which limits the throughput to 3.91 Mbps
The network based flow control limits the throughput to 0.13 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'
Server Data reports link is '10 Gig', Server Acks report link is 'T1'

[trogers]

Hi uncommonjo,

Your MTU is set right for DSL XP PPPoE system.

Your speed is slow (esp. to the US) because of the following:

High Latency - 500 ms

High RWIN setting - 256960 and not a multiple of your MSS

These created lots of excessive packet losses.

Your network has high traffic now, only giving you a throughput of 0.13 Mbps. So if your comp is set right, you can only achieve speed of about 100 Kbps. Check network again during low traffic period ( 2-5 am) to see if network control throughput limit goes up to 1.0 Mbps or more to ensure your ISP is not taking you for a ride.

To tweak with TCP Optimizer, use the following:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1500
TTL - 64
TCP Receive Window - 31680
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - uncheck
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 240
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

[uncommonjo]

This is the result after I alter based on your settings via TCPoptimizer.
Strange thing is the MTU and RWin doesn't reflect the setting I changed.


TCP options string = 020405a001010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising your MTU value.

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

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
506880 (MSS x 44 * scale factor of 8)
253440 (MSS x 44 * scale factor of 4)
126720 (MSS x 44 * scale factor of 2)
63360 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 1750 kbps (218.75 KBytes/s) @ 200ms
Your TCP Window limits you to: 700 kbps (87.5 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops

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

[trogers]

Yes, with small RWIN setting, the TCP optimzer sometimes change values from those that we enter.

I am based in Bangkok and my bandwidth is 1024/512 Kbps, quite similar to yours .

Use the TCP Optimzer again and load the following, twice. Reboot after each loading:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU - 1480
TTL - 64
TCP Receive Window - 63360 (for info, this is your MSS 1440 x 44)
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - uncheck
Timestamps - uncheck
Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 5
Host Priority - 6
DNSPriority - 7
NetbtPriority - 8
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 240
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

After doing this, test again with TCP Analyzer and do a speedtest at your ISP's site. This is more accurate than a speedtest to a website in USA due to large latency to reach USA.

[uncommonjo]

hi trogers thanks again!

here's the result. The Rwin still doesn't reflect to the settings in the TCPOptimizers current settings screen.



TCP options string = 020405a001010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising your MTU value.
Default TCP Receive Window (RWIN) = 43750
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 43750

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
506880 (MSS x 44 * scale factor of 8)
253440 (MSS x 44 * scale factor of 4)
126720 (MSS x 44 * scale factor of 2)
63360 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 1750 kbps (218.75 KBytes/s) @ 200ms
Your TCP Window limits you to: 700 kbps (87.5 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops

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

[trogers]

Then I suggest you use the Cablenut Adjuster. You can download for free here:

http://www.cablenut.com

When you have install and run it, it will give you a blank table. Manually enter the values below from top to bottom and left to right order. Save this file with any filename, click the 'Save to registry' button, exit and reboot your comp. Then test again with TCP Analyzer:

63360
63360
1
100
240
640
819200
64000
150400
0
12800
32
4096
1
1
0
63360
8000
32768
5000000
1
1
0
1
2
100
80
1440
1440
30
0
63360
20
10
64
0
6
240

[uncommonjo]

I apply the cablenut settings.
now the rwin does reflect the new settings. Thanks. However my bandwidth is still the same at abotu 290kbps. Is there anymore we can do for my pc. Thanks



TCP options string = 020405a001010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising your MTU value.
Default TCP Receive Window (RWIN) = 63360
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 63360

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

Your TCP Window limits you to: 2534.4 kbps (316.8 KBytes/s) @ 200ms
Your TCP Window limits you to: 1013.76 kbps (126.72 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops

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

[uncommonjo]

oh btw. How's the situation in bangkok? I heard there was a demostration rally. Better be on guard for riots.

[trogers]

Things are calm here. The protest rally was yesterday afternoon till this morning. They have now dispersed.

Check your system for possible elctromagnetic interference affecting your signals:

Router placed next to the modem is one main cause.

Here are interesting links on EMI:

http://www.speedguide.net/read_articles.php?id=1885

http://www.speedguide.net/read_articles.php?id=117

Also, I heard of dimmer switches in the home interfering with wireless signals too.

Another possiblilty is that your network is still busy and so your speed is limited You can test your network's traffic load using this link:

http://nitro.ucsc.edu/

Status is shown in the 2nd last paragraph of "More Details" section of the report - "The network based flow control limits the throughput to ____ Mbps"

[uncommonjo]

thanks will check it out...

[uncommonjo]

I've move my wifi ap/router away from the soma networks wireless modem. It made a huge differences. Thanks!! The tweaks also help alittle I think.

[uncommonjo]

this are the results I get when there's a low peak in my isp's network

TCP options string = 020405a001010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising your MTU value.
Default TCP Receive Window (RWIN) = 63360
RWIN Scaling (RFC1323) = 0 bits
Unscaled TCP Receive Window = 63360

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

Your TCP Window limits you to: 2534.4 kbps (316.8 KBytes/s) @ 200ms
Your TCP Window limits you to: 1013.76 kbps (126.72 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 53 hops

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



******************************************
statistics
**********************
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client to server) . . . . . 272.49Kb/s
running 10s inbound test (server to client) . . . . . . 762.10kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.4.2_08

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 482.98 msec; the Packet size = 1440 Bytes; and
No packet loss was observed.
This connection is receiver limited 73.41% of the time.
Increasing the the client's receive buffer (61.0 KB) will improve performance
This connection is network limited 26.56% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [202.190.133.197] but Client says [192.168.0.128]


***********************************************
more details
*************************************************
WEB100 Kernel Variables:
Client: localhost/127.0.0.1
AckPktsIn: 375
AckPktsOut: 0
BytesRetrans: 0
CongAvoid: 0
CongestionOverCount: 0
CongestionSignals: 0
CountRTT: 373
CurCwnd: 64800
CurMSS: 1440
CurRTO: 1210
CurRwinRcvd: 63360
CurRwinSent: 16304
CurSsthresh: 2147483647
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 1126080
DataPktsIn: 0
DataPktsOut: 782
DupAcksIn: 0
ECNEnabled: 0
FastRetran: 0
MaxCwnd: 64800
MaxMSS: 1440
MaxRTO: 1300
MaxRTT: 770
MaxRwinRcvd: 63360
MaxRwinSent: 16304
MaxSsthresh: 0
MinMSS: 1440
MinRTO: 600
MinRTT: 330
MinRwinRcvd: 63360
MinRwinSent: 16304
NagleEnabled: 1
OtherReductions: 0
PktsIn: 375
PktsOut: 782
PktsRetrans: 0
X_Rcvbuf: 103424
RcvWinScale: 2147483647
SACKEnabled: 3
SACKsRcvd: 0
SendStall: 0
SlowStart: 43
SampleRTT: 730
SmoothedRTT: 680
X_Sndbuf: 103424
SndWinScale: 2147483647
SndLimTimeRwin: 7597766
SndLimTimeCwnd: 2748747
SndLimTimeSender: 2614
SndLimTransRwin: 1
SndLimTransCwnd: 1
SndLimTransSender: 1
SndLimBytesRwin: 947520
SndLimBytesCwnd: 178560
SndLimBytesSender: 0
SubsequentTimeouts: 0
SumRTT: 180150
Timeouts: 0
TimestampsEnabled: 0
WinScaleRcvd: 2147483647
WinScaleSent: 2147483647
DupAcksOut: 0
StartTimeUsec: 197246
Duration: 10352444
c2sData: 2
c2sAck: 2
s2cData: 9
s2cAck: 2
half_duplex: 0
link: 100
congestion: 0
bad_cable: 0
mismatch: 0
spd: 0.00
bw: 22.75
loss: 0.000001000
avgrtt: 482.98
waitsec: 0.00
timesec: 10.00
order: 0.0000
rwintime: 0.7341
sendtime: 0.0003
cwndtime: 0.2656
rwin: 0.4834
swin: 0.7891
cwin: 0.4944
rttsec: 0.482976
Sndbuf: 103424
aspd: 4.22909

Checking for mismatch on uplink
(speed > 50 [0>50], (xmitspeed < 5) [0.27<5]
(rwintime > .9) [0.73>.9], (loss < .01) [1.0E<.01]
Checking for excessive errors condition
(loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.26>.6],
(loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]
Checking for 10 Mbps link
(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
(xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]
Checking for Wireless link
(sendtime = 0) [3.0E=0], (speed < 5) [0<5]
(Estimate > 50 [22.75>50], (Rwintime > 90) [0.73>.90]
(RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]
Checking for DSL/Cable Modem link
(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
(SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
Checking for half-duplex condition
(rwintime > .95) [0.73>.95], (RwinTrans/sec > 30) [0.1>30],
(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
Checking for congestion
(cwndtime > .02) [0.26>.02], (mismatch = 0) [0=0]
(MaxSsthresh > 0) [0>0]

estimate = 22.75 based on packet size = 11Kbits, RTT = 482.98msec, and loss = 1.0E-6
The theoretical network limit is 22.75 Mbps
The NDT server has a 101.0 KByte buffer which limits the throughput to 1.63 Mbps
Your PC/Workstation has a 61.0 KByte buffer which limits the throughput to 1.00 Mbps
The network based flow control limits the throughput to 1.02 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'
Server Data reports link is '10 Gig', Server Acks report link is 'T1'

[lozada1991]

IP Address: 180.194.xxx.xxx (180.194.xxx.xxx)
Client OS: Windows XP
Browser: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7
Please Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405b40402080a416bfd920000000001030307
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) = 5888
RWIN Scaling (RFC1323) = 7 bits (scale factor: 2^7=128)
Unscaled TCP Receive Window = 46

You seem to be using Google Chrome. Note that Chrome can modify the TCP Window for sockets it creates under some OSes, and therefore servers may not get your correct RWIN value. You may want to test with a different browser. FAQ
RWIN seems to be set to a very small number. If you're on a broadband connection, consider using a larger value.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other RWIN values that might work well with your current MTU/MSS:
64240 (up to 2 Mbit lines, depending on latency. MSS * 44)
128480 (1-5 Mbit lines, depending on latency. MSS * 44 * 2)
256960 (2-14 Mbit lines, depending on latency. MSS * 44 * 2^2)
513920 (8-30 Mbit lines, depending on latency. MSS * 44 * 2^3)
1027840 (25-60 Mbit lines depending on latency. MSS * 44 * 2^4)
bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 236 kbps (29 KBytes/s) @ 200ms
Your TCP Window limits you to: 94 kbps (12 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = ON
Time to live left = 46 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)



is this good enough?

[carloelopre]

Then I suggest you use the Cablenut Adjuster. You can download for free here:

http://www.cablenut.com

When you have install and run it, it will give you a blank table. Manually enter the values below from top to bottom and left to right order. Save this file with any filename, click the 'Save to registry' button, exit and reboot your comp. Then test again with TCP Analyzer:

63360
63360
1
100
240
640
819200
64000
150400
0
12800
32
4096
1
1
0
63360
8000
32768
5000000
1
1
0
1
2
100
80
1440
1440
30
0
63360
20
10
64
0
6
240

* i just want to ask something, with windows 7 modification of RWIN is not possible because of auto-tuning right? can i use cablenut to modify RWIN even if im using windows 7 OS? thanks in advanced... *