Results 1 to 13 of 13

Thread: EvilAjax = l33t

  1. #1

    EvilAjax = l33t

    I think you're cool dude. You always help out peeps on this messageboard (including myself), and you even took the time to wish BigAmp a happy birthday :P.. I just wanted to say thanks for contributing your time. I know some of you others contribute just as much time, but Ajax ownz your bonez more.

    Anyways, D: I got a question for you... what would you recommend for this setup (as far as connection tweaking goes):

    Asus A7V133 Mobo
    Maxtor UDMA-33 (yuck, i know) 13GB hd (transfer rate is 3.4MB/s uncached, 320MB/s cached)
    384MB PC-133 SDRAM
    Athlon (axia) 1ghz @ 1.3ghz (runs at around 47 C.. heh.. hot mamma)
    RealTek 8139 Nic
    SB Live! Value (i dont know if that has anything to do with it)
    Voodoo 3 (or this either)
    Running windows2000 w/all the updates including SP2
    DSL Speed: 8Mbps/1Mbps; Sprint ION.

    I currently have the speedcorp.net patch installed with a receive window of 373760. I dont think Im juicing my line for what its worth though. Before, with my AMD K6-2 450 i would get 6.8Mb/s ratings from my sprint ion speed test site, now i get like 6.3Mb/s.. I'm stumped. Thanks in advance anyways

    Thanks Again,
    -Derek

  2. #2

    oh yah..

    here are my tcp analyzer results:

    TCP options string = 020405b4010303030101080a000000000000000001010402

    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 Receive Window (RWIN) = 373760
    RWIN Scaling (RFC1323) = 3 bits
    Unscaled Receive Window = 46720
    RWIN is 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:
    Your RcvWindow limits you to: 14950.4 kbps (1868.8 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 5980.16 kbps (747.52 KBytes/s) @ 500ms

    MTU Discovery (RFC1191) = ON

    Time to live left = 18 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

  3. #3
    n00b pWn3r! EvilAjax's Avatar
    Join Date
    Mar 2001
    Location
    New York City, USA
    Posts
    6,991
    Hey thanks man, I try

    Ok, first click the CableNut Adjuster link in my sig and download the newest version, 4.02. Reboot after installing it. Next, double click the shortcut it places on your desktop, then go through ccs/cable/then double click cable_fast_2k. Reboot and retest. If you're going slower and/or you don't notice a difference in speed then try these RWINs. 64240, 227760, 256960, 265720, 280320, 303680, 321200, 327040, 385440, 420480, 467200, 449680, 531440, 560460, 607360, and the big ol' 654080.
    I know those are alot of RWINs, heh.. but test them all out and see which works best for you. Test your speed everytime. Not only speed tests from websites, but also by downloading files.

    For faster webpages, set MaxConnectionsPerServer and MaxConnectionsPer1_0Server both to 500. If this causes you to slow down then simply set them back to what they were. By the way, when changing the RWINs just change the RWINs, leave the other settings the ccs file puts in. Just make sure Tcp1323Opts is set to 1. And when setting an RWIN, put them in these three places, DefaultReceiveWindow, TcpWindowSize, and GlobalMaxTcpWindowSize. They must all have the same number. Let me know how your tests go. Good luck!

    Thanks again for the compliments. I really appreciate it.
    <sarcastic>um... yeah</sarcastic>

    Wanna get pwned?

    Quote Originally Posted by raromoney View Post
    Thanks EvilAjax!
    Yup, I'm baaaackkk!

    EvilAjax unbanned, reinforces stereotypes with gunplay braggadocio...

  4. #4
    Regular Member BigAmp's Avatar
    Join Date
    Jun 2001
    Location
    London
    Posts
    468
    hey EvilAjax I've been seeing you and Lobo talking about theTcpWindowSize, and GlobalMaxTcpWindowSize values. I cant find them where are they in regedit, or is that like a Win2K, cablenut thing
    TweakXP.com RASPPPoE TCP/IP Analyzer TCP Optimizer RWIN Calculator
    Centrino 1.50 GHz | 768 MB RAM | XP Pro.

  5. #5
    n00b pWn3r! EvilAjax's Avatar
    Join Date
    Mar 2001
    Location
    New York City, USA
    Posts
    6,991
    I don't know where they are in the registry... but the adjuster automatically puts it in. You do have the adjuster, right?
    <sarcastic>um... yeah</sarcastic>

    Wanna get pwned?

    Quote Originally Posted by raromoney View Post
    Thanks EvilAjax!
    Yup, I'm baaaackkk!

    EvilAjax unbanned, reinforces stereotypes with gunplay braggadocio...

  6. #6
    Regular Member BigAmp's Avatar
    Join Date
    Jun 2001
    Location
    London
    Posts
    468
    no I just like gong in with regedit. so I know what I'm looking at, besides with my sympatico software the MTU value was set in a other place so the cablenut software would have done nothing for me.
    TweakXP.com RASPPPoE TCP/IP Analyzer TCP Optimizer RWIN Calculator
    Centrino 1.50 GHz | 768 MB RAM | XP Pro.

  7. #7
    New Member
    Join Date
    May 2001
    Location
    scotland
    Posts
    14

    tcp window size

    i have followed various suggestions from this dg before and always find the advice very helpful.
    one problem i have found is that you say to change the window size in three settings.
    my version of cablenut adjuster only allows me to change it in two that you mention.
    there is no setting shown for TCP window size, only for default receive window and global maxtcpwindow size.
    is there something i am missing. thanks

  8. #8
    ehh.. i clicked on the 2k ccs file, and it had different values:

    DefaultRcvWindow was 16384
    GlobalMaxTcpWindowSize was empty
    TcpWindowSize was 128480

    what do i do here?

    Alot of the other boxes are empty too.. and the maxconnetionsperserver vars were like 8 and 16.. weird

    -Derek

  9. #9
    n00b pWn3r! EvilAjax's Avatar
    Join Date
    Mar 2001
    Location
    New York City, USA
    Posts
    6,991
    Just reboot and do what I said above. Leave everything else at default.
    <sarcastic>um... yeah</sarcastic>

    Wanna get pwned?

    Quote Originally Posted by raromoney View Post
    Thanks EvilAjax!
    Yup, I'm baaaackkk!

    EvilAjax unbanned, reinforces stereotypes with gunplay braggadocio...

  10. #10

    Re: tcp window size

    Originally posted by nigel docherty
    i have followed various suggestions from this dg before and always find the advice very helpful.
    one problem i have found is that you say to change the window size in three settings.
    my version of cablenut adjuster only allows me to change it in two that you mention.
    there is no setting shown for TCP window size, only for default receive window and global maxtcpwindow size.
    is there something i am missing. thanks
    Hi Nigel! First off, what version of the Cablenut adjuster do you have? You should be using the new 4.02 version found on their site. If that is the case, then you don't see that 3rd value because it's for Win2K. If you are on Win2K then you may have setup the program to use one of the Win9x or ME configurations. When you first started the program after installation, it comes up with a screen verifying your OS. It should pick the OS you are using by default but you may have accidentally checked something else. In any case, it sounds like you are running either Win98SE or WinME. If that is true, all you really need to do is load the appropriate CCS file for your OS and the type of service you have...if you are on a fast connection, capable of over 4000Kbps, then you want the fastWin9x CCS file. If your service is lower than 4000Kbps, then you want the normalWin9x file. It's that easy. As far as RWIN's are concerned, try using the default values as provided in the CCS file...make no changes! Try for a few days. If you want to "experiment" then try multiples of 64240. the default fast9x file is 128480. So the next logical step up is 256960. That 64240 with a scale factor of 4. The next big step up is 513920. That's 64240 with a scale factor of 8. 8 times 64240 = 513920. simple stuff ehh!

    the only place you need to put that RWIN value is in the default rcv window. Do not put anything in the global max setting...leave it blank.

    As far as everything else, you'll be best served by leaving things as they are, but if you want to experiment, just remember to backup your registry. The cablenut program automates it for you so there is no excuse not to do it. You can even save your settings as your own custom settings file! that way you can tweak to your hearts content and always go back to you best configuration.

    the RWIN issue is based on a few factors, you really need to have at least 128MB ram and a good CPU...preferably over 500mhz but it's not the end of the world if you don't.

    Hope this helps and plz post your analyzer results so we can see if you are setup correctly.

    ...formerly the omnipotent UOD

  11. #11
    Elite Member Lobo's Avatar
    Join Date
    Nov 2000
    Location
    Panama City, FL and a FAN of Dale Earnhardt Jr. Bud Chevy & NASCAR , and the Atlanta Braves
    Posts
    17,662
    BigAmp, On main page this site , on left under W2k tweaks it states:
    TCPWindowSize

    The value of TCP Window in the Windows 2000 Registry is DWORD, representing number of bytes, with range from 0 to 2^30. The recommended values (in red) optimize TCP for any high speed Internet connection and work best in most cases, however if you'd like to use a custom value follow these guidelines:

    For best results, the TCPWindow should be a multiple of MSS (Maximum Segment Size). MSS is generally MTU - 40, where MTU (Maximum Transmission Unit) is the largest packet size that can be transmitted. MTU is usually 1500 (1492 for PPPoE connections). To determine the MTU value of your ISP, check out the Advanced Registry Editing section of our site.

    There are three places in the Windows 2000 Registry where you can add the TCP Window parameter.

    HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
    GlobalMaxTcpWindowSize="256960" (DWORD, number of bytes) Valid range is from MSS to 2^30. Add the value as a decimal.
    Note: For best results RWIN has to be a multiple of MSS lower than 65535 times a scale factor that's a power of 2, i.e. 44 x 1460 = 64240 x 2^2 = 256960. If you choose to use a RWIN lower than 65535, you can simply make it multiple of MSS and turn scaling off (Tcp1323Opts=0)

  12. #12
    it werks pretty good now.. 825KB/s.. meh. I shouldn't be too greedy . Thats what i was getting before, but i would lose packets sometimes. Thanks for the help mang

    -Derek

  13. #13
    n00b pWn3r! EvilAjax's Avatar
    Join Date
    Mar 2001
    Location
    New York City, USA
    Posts
    6,991
    Originally posted by Opticflare
    it werks pretty good now.. 825KB/s.. meh. I shouldn't be too greedy . Thats what i was getting before, but i would lose packets sometimes. Thanks for the help mang

    -Derek
    Great. Glad that we could help.
    <sarcastic>um... yeah</sarcastic>

    Wanna get pwned?

    Quote Originally Posted by raromoney View Post
    Thanks EvilAjax!
    Yup, I'm baaaackkk!

    EvilAjax unbanned, reinforces stereotypes with gunplay braggadocio...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •