Victek vs. Teddybear

Discussion in 'Tomato Firmware' started by Murtins, Sep 20, 2010.

  1. Murtins

    Murtins Networkin' Nut Member

    Could anyone tell me what the actual differences are between the 2 when used for the WRT54GL ?

    I have had Victek's 1.25ND for sometime and I also TB 1.28 no usb and both were quite similar in speed and stability.

    Which one of the 2 do you guys prefer and why?
  2. fubdap

    fubdap LI Guru Member

    Check out the middle of the page of this link:

    I believe the third one on the list is the same as TB. This does not exactly answer your question, but it gives you an idea.

  3. teddy_bear

    teddy_bear Network Guru Member

    As far as I can tell (and Vic will correct me if I'm missing anything) the last Victek's builds are based on my Tomato USB mod, so they include every change and addition (and sometimes removal - like in case of ftpget - :biggrin:) of corresponding Tomato USB edition (including newer kernels, wifi drivers etc), plus Victek's RAF features outlined on his web site, and a few cosmetic additions by Toastman (i.e. QoS classes labels).

    I believe the list of RAF features on the Vic's site is [almost] complete, and should give you a clear picture of all differences/additions compare to vanilla Tomato and Tomato USB. If the list is missing anything - Vic, please update it when you get a chance, I'd like to know too ;)...
  4. mstombs

    mstombs Network Guru Member

    I suspect this is now wrong

    2.55 as per Tomato 1.28 more likely!
  5. Murtins

    Murtins Networkin' Nut Member

    One thing I noticed after I upgraded to Victek's 1.28ND 2.4 was that the QoS was totally different then in the previous version and it slowed my connection down.

    I switched back to teddybear's 1.28 no usb and all went back to normal.

    I presume that I probably needed to customize the QoS settings in victek 1.28 to my specific needs but the default QoS settings in teddy's version work just perfectly.
  6. Kiwi8

    Kiwi8 LI Guru Member

    I have not loaded Teddybear's version yet, but can u make a screenshot of his default QOS settings so that we can look at it?
  7. Murtins

    Murtins Networkin' Nut Member

    2 screenshots are attached.

    I'm quite sure it is the same as previous versions of both TB and Victek.

    Attached Files:

  8. Kiwi8

    Kiwi8 LI Guru Member

    Not these. I wish to see the ones on the second page, namely the QOS rules page. :redface:
  9. Murtins

    Murtins Networkin' Nut Member

    Oh sorry... here is the other one

    Attached Files:

  10. Toastman

    Toastman Super Moderator Staff Member Member

    The default QOS rules are not quite the same as previously. Teddy Bear's default rules have been slightly altered, to allow anything not covered by individual rules (which includes P2P) to "fall through" into the default class. This method allows P2P to be properly classified, and has been the generally accepted way to handle P2P for several years now. The original rules tried to classify P2P with an actual port rule covering 1025-65535, which as we all know, doesn't actually work - and was the cause of many people's QOS not working as well as it could have. That rule has been deleted.

    This very simple QOS is sufficient for many people's needs, but everyone's needs are different.

    Victek's build presently seems to be using default class labels and QOS rules from my builds. This rather large set of rules was formulated over the years for large buildings with a hundred or more "anonymous" users. It should be used as an example of what can be done to try to make sure that everyone's needs are met and that no one user can screw it up for everyone else. These rules will slow your system down, inevitably, because a compromise has to be set between speed and bandwidth availability. You have a very big advantage - you KNOW what your PC's run, and so many of these rules will not be necessary. Examine them, see what they do, then modify, disable or delete any rules that you don't need. Everyone's needs are different, and there is no set of rules and speed limits that will be optimum for everybody. You have to learn how to use them and change them to suit your needs.

    Names of the classes were designed to make it easier to see what is going on. The order seems acceptable for most people. The other advantage is, that it clearly spells out that there are 10 classes in Tomato, not just the first 5. Using all 10 can make it much easier to see what is happening in your system using the pie charts.
  11. Murtins

    Murtins Networkin' Nut Member

    Thanks for the explanation. It makes it all clear now. Perhaps I will give it a shot and play around with the QoS settings to see if I can customized it exactly for my needs.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice