Tomato: 2 minor observations

Discussion in 'Tomato Firmware' started by jeffjs, Nov 2, 2006.

  1. jeffjs

    jeffjs Network Guru Member

    I know I shouldn't do it, but I've always remotely upgraded the WRT54G v3 in my home from the laptop in my office. However, I have not been able to do a remote upgrade in any version of Tomato. It's gets so far, then just reboots the router.

    It's a pain to visit and see that Tomato has been upgraded, but I can't play with it until I get home from the office.

    Is anyone else seeing this problem?

    Also, another small observation: the bandwidth graph colors aren't saved.

    I know these problems aren't a high priority like IPTables, but keep in mind I'm just a casual user and these two issues are something I've come across during normal use of Tomato.
  2. fareal

    fareal LI Guru Member

    I've noticed the same with remote upgrades and only intermittently with bandwidth graph colors.

    One other thing I'd like is in the QOS Details list of activity, is there a way to organize it by first in - first out or some sort of timestamping, or as a last resort a button to clear it so if at a specific time we're looking for only new activity we can differentiate between the new and old.
  3. RTSAnime

    RTSAnime Network Guru Member

    Well if you know you aren't supposed to be doing it, then why should he allow you to do something that could potentially fry your box?

    Also, on .8 (I have none of the bugs fixed in .9 so no need to upg for me) the graph colors do save.
  4. tievolu

    tievolu Network Guru Member

    To be fair, flashing any firmware via any method could fry your box - the different methods just have different levels of risk attached. Following your logic, one could argue that Jon shouldn't be creating this firmware at all :)

    If someone wants to be able to upgrade via the Internet, I think they should be able to - there's no technological reason why it shouldn't be possible, and it's clearly important to some people (personally I'd never risk it though!).
  5. pharma

    pharma Network Guru Member

    Saving Bandwidth colors works here ... using the latest version. :)
  6. RTSAnime

    RTSAnime Network Guru Member

    Upgrading from the WAN is the most dangerous way to go, as such it should be blocked. WAN is far more likely to have transfer issues than LAN or WLAN
  7. jeffjs

    jeffjs Network Guru Member

    I've never had a problem upgrading from WAN - ever. Now I can't. That's all I was saying. I don't agree that it should be blocked.
  8. tievolu

    tievolu Network Guru Member

    Hmmm. We'll have to agree to disagree on this. I don't think dangerous things should be blocked - I think they should be clearly documented as dangerous (e.g. a quick note on the upgrade page) and people should be allowed to make their own minds up.
  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