1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tomato .08 is now out

Discussion in 'Tomato Firmware' started by Mercjoe, Oct 29, 2006.

  1. Mercjoe

    Mercjoe Network Guru Member

    Just found this on the homepage:

    http://www.polarcloud.com/tomato

    0.08 Changelog
    Fixed not working on a v1.x. Thanks to William Myers for providing a guinea pig router. :)
    Fixed L7 inbound may not work correctly. It's also now enabled by default.
    Fixed Advanced/CTNF not counting UDP correctly.
    Fixed UPnP Delete All not working.
    Fixed incorrect SSL cert expire time.
    L7 patterns updated to 2006-10-18.
    You can now match the amount of data transferred to WAN. Note: There is a format change here to accommodate the new field. Please go to QOS:Classification, and hit the Save button to make sure the nvram value is converted.
    Switched to a simpler, more logical way of processing QOS rules. There's probably not that much negative to this, but if you do want to switch back to the old method, disable "Strict Ordering" in QOS: Settings. See the readme also.
    "root" is now also accepted as username for the UI.
    Some minor enhancements to the bandwidth and QOS chart.
    Other minor changes.
    With the v1 problem finally fixed, and the number of bugs being found slowing down, I'm thinking of wrapping this up soon and release a 1.00. So if anyone has any remaining bugs/annoyances they'd like to report, or if I missed something that was previously reported, let me know.


    There you go. Let the downloading begin
     
  2. der_Kief

    der_Kief Super Moderator Staff Member Member

    Hi @ All,

    i flashed it some minutes ago, configured it and everything is working like it should. No problems so far. Here are some screenshots of the "new" things i found so far.

    1)
    [​IMG]
    From the changelog:
    Fixed L7 inbound may not work correctly. It's also now enabled by default.

    2)
    [​IMG]
    From the readme:
    Precedence: The rules are checked in the same order as they appear in the GUI, from top to bottom. The first rule that matches sets the class. If you disable "strict ordering", rules with IPP2P, L7 and KB matches are grouped in one set and are checked first, the rest in another.

    3)
    [​IMG]
    From the readme:
    KB transferred match: (1) This is the to-WAN data transferred in kilobytes. Consider the amount an approximate value since it doesn't take into account protocol overhead. (2) Entering an upper limit of 1GB (1,048,576KB) or more is considered unlimited and will match anything above 1GB. (3) IPP2P may not work properly with this since IPP2P doesn't keep track of its state.

    I don't really understand whats the use of this "KB transferred" is ?

    der_Kief
     
  3. damko

    damko Network Guru Member

    It also has a timeline added in Bandwith/Current.

    It's GREAT firmware!!!
     
  4. myersw

    myersw Network Guru Member

    Just flashed a WRT54GL v1.1 about a hour ago. Looks good so far. Like the nice touches that have been added, like a time for the bandwidth graph.
    Just keeps getting better and better. And now the owners of v1's can now enjoy this fine firmware.
    Great work Jon.
     
  5. der_Kief

    der_Kief Super Moderator Staff Member Member

    Cannot see something new to the bandwidth monitor. What do you mean with timeline ?

    I totally agree. THX to Jon


    der_Kief
     
  6. turbo53

    turbo53 Network Guru Member

    Go to the "Bandwidth --> Current" page. As you move the mouse cursor horizontally and vertically across the page, you will see the time/date as well as the speed represented by your current mouse position in the upper or lower right hand corner.
     
  7. myersw

    myersw Network Guru Member

    What was up with WRT54G v1

    Here basicly is what Jon found to be the issue with the WRT54G v1.x routers when loading Tomato. As was suspected it was a issue with the hardware architecture of the v1's.

    Clip from email from Jon:
    It turned out to be a bad combo of the v1 not having a serial console and Tomato's early use of the nvram. It was basically trying to close the console's handle that doesn't exist so it ends up closing the nvram handle instead.
     
  8. digitalgeek

    digitalgeek Network Guru Member

    Looks good, like the time in bandwidth...

    several times internet connection drops and connect on demand does not reconnect it? I have switch to keep alive, I have avoided it as with Thibor it didn't work very well.
     
  9. der_Kief

    der_Kief Super Moderator Staff Member Member

    BTW Here's the readme :)

    -----------------------------------------------

    WARNING

    This firmware is experimental. Use at your own risk.

    READ BEFORE UPGRADING

    * The GUI relies heavily on JavaScript to generate the content and XMLHTTP (AJAX) to update it. Be careful if you need to use this from an older/minimal browser since it was not designed to downgrade gracefully. This has been tested only on Firefox v1+, Opera v9 and IE v6+.
    * Bandwidth and QOS status displays require a browser with SVG support. This feature has only been tested under Firefox v1.5+, Opera v9 and IE v6+ with Adobe's SVG plugin.
    * Web UI username is "admin" or "root" (username is now required), ssh and telnet username is always "root", and the default password is "admin".
    * By default the SES button is programmed to start a password-less telnet deamon at port 233 if held for 20+ seconds. If you run into a problem of not being able to login, you can use this to view or reset the password (nvram key is http_passwd).
    * If you need to use TFTP to upgrade the firmware, use the bootloader method (192.168.1.1 during bootup). Linksys' password protected TFTP upgrade will not work with Tomato.
    * G\code.bin is for WRT54G v1-4 and WRT54GL v1. GS\code.bin is for WRT54GS v1-3. GSv4\code.bin is for WRT54GS v4. If you're just upgrading an existing Tomato firmware from the GUI, any of these will work on all routers.

    Known Problems & Quirks

    * There is no help file.
    * In some cases, you may need to reboot the router manually before the changes go into effect. If the changes involve switching wireless settings, you may need to reboot both ends.
    * Not all wireless modes / security combinations work.
    * CIFS VFS timesout a lot. (or it might the server kicking the client off...)
    * If you get a blank page or a "connection reset" error message while submitting, close then re-open the browser.

    QOS / Access Restrictions Notes

    * All QOS classification and access restriction checking are performed while packets are traveling out to the Internet. The source is always from your computer and destination is always towards the Internet.
    * Some L7/IPP2P patterns may depend on which direction the data is going. An HTTP request from a browser, for example, is different from an HTTP response from a server. The patterns are not clear which is which, unfortunately.
    * Custom L7 patterns can be stored in /etc/l7-extra/ (you need to create the directory). It's up to you to actually populate it before the firewall starts. This can be tricky if you're using external storage, so consider just using JFFS2 or even simple "echo" statements in the startup script. To learn more about L7 patterns, go to l7-filter.sf.net.
    * When changing QOS settings, the firmware will try to flush existing classifications for 30 seconds to make sure the new rules are used. Note that this doesn't work very well on connections that are idle. When in doubt, close and re-open whatever application you're using to make sure they're are classified using the new rules.
    * Although there is an option to limit the download speed, it's not really recommended in most cases since what the router is really doing is dropping packets, which means they may need to be re-sent again over a slow Internet link.
    * KB transferred match: (1) This is the to-WAN data transferred in kilobytes. Consider the amount an approximate value since it doesn't take into account protocol overhead. (2) Entering an upper limit of 1GB (1,048,576KB) or more is considered unlimited and will match anything above 1GB. (3) IPP2P may not work properly with this since IPP2P doesn't keep track of its state.
    * Sticky rules: IPP2P/L7 are sticky in that once they match, no other rules are processed. IP/MAC/port-only matches can also be sticky if there are no IPP2P/L7/KB match above them. When coupled with a KB transferred match with an upper limit, they are not considered sticky. What this all means is you should watch out for rules like the following: "#1: L7 ABC & 1024KB+, #2: L7 ABC", the #1 rule may not match at all since #2 will lock-on if it sees L7 ABC within 0-1024KB. To get around this particular case: "#1: L7 ABC & 0-1024KB, #2: L7 ABC & 1024KB+."
    * Precedence: The rules are checked in the same order as they appear in the GUI, from top to bottom. The first rule that matches sets the class. If you disable "strict ordering", rules with IPP2P, L7 and KB matches are grouped in one set and are checked first, the rest in another.
    * If you're concerned about performance: IPP2P and especially L7 are slower than simple IP, MAC or port matches.

    Miscellaneous Notes

    * Some NVRAM settings may not be compatible with other firmwares. A config reset is recommended after flashing to or from this firmware.
    * You can enter a custom DDNS URL like the following: http://www.mycustomdns.com/update.cgi?username=scooby&password=spooky&ip=@IP. The "@IP" keyword is automatically replaced with the current IP address. Check with your DDNS provider for the exact format to use.
    * The Busybox crond included in Tomato is a little different from the Vixie crond found in HyperWRT, DD-WRT, etc. To make it easier and safer to schedule a job, use the helper script called "cru" instead of manually changing the config file.
    * Want to try changing things without permanently writing them to nvram? Go to Admin: Miscellaneous and enable "avoid performing an nvram commit." When you're done playing around, reboot to discard the changes, or use the "nvram commit" button to save the changes.
    * If you're saving the bandwidth history, don't forget to backup the data to another location!


    -----------------------------------------------
    der_Kief
     
  10. Reiper

    Reiper LI Guru Member

    I found two small issues and have already e-mailed Jon...

    1) When using the Ping Tool the Min time is not correct; and
    2) All 12pm times so up as 00, i.e. 12:20pm shows up as 00:20pm on the bandwidth graph.

    No big deal with these, only cosmetic! Overall the firmware is great and rock solid!
     
  11. bytes2000

    bytes2000 Network Guru Member

    Thanks for this great firmware!
     
  12. gmoncada

    gmoncada LI Guru Member

    Great Firmware... i flashed it some minutes ago too and really good... stable and the graphics.... beautiful
     
  13. wycf

    wycf Network Guru Member

    Upgraded to 0.08. All the setting in 0.07 was kept and it works just great!
    :)
     
  14. fareal

    fareal LI Guru Member

    Is that what everyone does? Just overwrite existing tomato version? I thought I read somewhere that it was recommended to Restore to Defaults and erase NVRAM, apply the update, and again Restore to Defaults and erase NVRAM, and then rekey all your settings?
     
  15. turbo53

    turbo53 Network Guru Member

    The process you describe is the recommended procedure when you switch from one type of firmware to another. For example, you should do that if you are switching from DD-WRT to Tomato. But when upgrading from one version of the same firmware to another, it is usually not needed unless the author specifically says so.
     
  16. fareal

    fareal LI Guru Member

    ah ok, thanks.
     
  17. rcordorica

    rcordorica Network Guru Member

    thank you for the firmware. v0.7 was up up for 9 days here, that is until I upgraded to v0.8 :D

    one question, what is the added latency of L7 vs IPP2P vs simple port prioritization? Any quantitative differences?

    Although I don't place heavy loads on the router, I am still interested in the best latency possible for my wireless devices when connecting to the internet with QOS enabled. The Bittorrent IPP2P really seems to work great here, but I'm still interested in what is the most "stable" and low latency solution for prioritization of services.
     
  18. dtswk

    dtswk Network Guru Member

    My understanding is that layer 7 is significantly heavier than simple IP or MAC based QoS. Can't really back that up with any solid facts.

    Be interesting to hear what other people say.

    Matt
     
  19. bokh

    bokh Network Guru Member

    And another sticky that prevents people from seeing that Tomato Version 0.09.0852 has been released.

    Sigh...
     

Share This Page