Toastman Firmware - Build Guide

Discussion in 'Tomato Firmware' started by Toastman, Dec 19, 2011.

  1. Toastman

    Toastman Super Moderator Staff Member Member

    What version to use?

    When you get to the download site:

    • First - decide what branch you want. This depends on your router.
    • If it's for the older MIPSR1 routers like WRT54 series, choose "ND"
    • If it's for newer MIPSR2 routers like RT-N16, WNR3500L, Linksys "E" series, then choose "RT"
    • Choose the RT-N branch for some recent MIPSR2 routers (e.g E4200, RT-N10U, RT-N12B1, WNR3500L v2).
    • The E4200 needs the newer "N" wireless driver to get support for the 5GHz radio. You can still use the RT version IF you don't need the 5GHz radio to work. But the other routers mentioned can't use the RT version.
    • This RT-N driver is big, slow, and most have found it buggy. I recommend you don't use it for the E3000, this question is always popping up and we're tired of replying to it.
    Once inside the correct folder, you will have another choice to make:
    • If your needs are simple, and you don't intend to set up a VLAN, then select "STD"
    • If you need the easy setup VLAN GUI, then choose the folder marked "VLAN"
    Now you'll see a list of builds:
    • Mini - no USB, no CIFS, no Zebra
    • MiniIPV6 - no USB, no CIFS, no Zebra + IPv6
    • Std - normal build
    • Ext - normal + Extra utilities + NTFS
    • VPN - normal + Extras + NTFS + VPN
    • VPN-NOCAT - normal + Extras + NTFS + VPN + NOCAT portal
    If your router needs USB support, chose a version with "USB" in the title.
    There are "tailed" versions for specific, named routers that have special needs.
    There's also a "generic" version for other routers which may have 60K nvram.


    K2.4 and K2.6 refer to the version of Linux kernel used for a particular compile. Early routers always used K2.4 (which is smaller/faster/lighter). The newer routers use kernel 2.6 which is necessary to use the latest Broadcom wireless drivers. The IPv6 support is also more complete. While K2.6 builds can be made for, and do work on the earlier routers such as the WRT54 series, they take more memory and are slower in operation. For this reason you will rarely see them. From time to time developers have made such builds available to allow experimentation with IPv6 on those early routers. Mostly, the feedback has been negative. The real answer however is to upgrade to a better router.
    eahm likes this.
  2. smihaila

    smihaila Reformed Router Member

    Hi Toastman,

    You have earned all my respect - your Tomato builds proof to me the most stable ones that I have ever seen.
    Perhaps you could help me with a question that I have:

    The build that I'm using is tomato-Cisco-M10v2-NVRAM32K-1.28.0502.1MIPSR2Toastman-RT-N-Mini
    Unfortunately, there doesn't seem to be any -VPN build flavour for the Cisco Valet M10 v2 router. And I wish to subscribe to a VPN provider which works via OpenVPN. In lack of OpenVPN client support, I would be forced to use L2TP. But I'm not even sure whether the built-in L2TP client is IPSEC compliant (L2TP/IPSEC) or just 'plain/straight L2TP'?

    I understand that the M10 v2's resources are rather limited but I'm willing to make a compromise and not have other features in the firmware (such as traffic graphing etc), just to have OpenVPN support.

    Is there a chance for you to be able to make a 'special' M2 v2 VPN build, please?

    Thanks very much.
  3. JAC70

    JAC70 Addicted to LI Member

    I'd be surprised if there's any room in the M10 V2. I set one up for my FiL, and I can't even enable JFFS, the space is so tight.

    What I'd like to see is a e3000 build with no QoS and CTF and FastNAT enabled. I miss getting my full 150/10 speed. :(
  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