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

The RT-N66U Hash-Bang Shell Parameter Bug

Discussion in 'Tomato Firmware' started by Planiwa, Apr 20, 2012.

  1. Planiwa

    Planiwa LI Guru Member

    Here is a minimalist demonstration of the RT-N66U Hash-Bang Shell Parameter Bug:

    Paste this:
    Code:
    cd /tmp;echo -e '#!/bin/sh\necho -n $1' >x;chmod +x x
    for i in N o _ p r o b l e m _ h e r e .; do x $i; done;echo
    
    You should see "No_problem_here.".
    But on the N66U, you might see something else instead.
    You can do this from Tools>System -- no need to ssh or telnet.
     
  2. Planiwa

    Planiwa LI Guru Member

    Can we please confirm which N66U Firmwares have this bug?

    Please do not post redundant information.

    Does the factory firmware for the N66U have a command line interface?

    Does it have the bug?
     
  3. ppsun

    ppsun Networkin' Nut Member

    RT-N66U, h/w ver: B1 and shibby 87V AIO:
    .1.2.ug.ug.ug.6.7.8.ug.
     
  4. RobF

    RobF Serious Server Member

    no bug with Shibby 88V AIO on my RT-N66U
     
  5. Planiwa

    Planiwa LI Guru Member

    @ RobF & @ ppsun, can you please post your BusyBox versions?
     
  6. RobF

    RobF Serious Server Member

    root@router:/bin# busybox
    BusyBox v1.18.5 (2012-03-22 11:53:31 CET) multi-call binary.
    Copyright (C) 1998-2009 Erik Andersen, Rob Landley, Denys Vlasenko
    and others. Licensed under GPLv2.
    See source distribution for full notice.
     
  7. ppsun

    ppsun Networkin' Nut Member

    87V AIO
    BusyBox v1.18.5 (2012-03-12 17:38:28 CET) multi-call binary.

    Still fails when updated to 88V AIO.
     
  8. Planiwa

    Planiwa LI Guru Member

    Which BB version with 88V?

    Also do you use any modifications, such as internal SD card?
     
  9. ppsun

    ppsun Networkin' Nut Member

    88V AIO
    BusyBox v1.18.5 (2012-03-22 11:53:31 CET) multi-call binary.

    No hardware mods. Low CPU usage and plenty of free RAMS, but NVRAM is only 4k to 5k after setup.
     
  10. RobF

    RobF Serious Server Member

    Same version and characteristics here as ppsun.

    Question: Are you using optware?
    I have that installed via a USB stick mounted on /opt.

    Since /opt/lib and /opt/usr/lib appear first in the ld.so.conf file it may be that my version of busybox is linking to a different library than a non-optware router would link to.

    Code:
     root@router:/tmp/etc# cat ld.so.conf
    /opt/lib
    /opt/usr/lib
    /lib
    /usr/lib
    root@router:/tmp/etc#
    
    Without optware loaded you'll link to libs in /lib or /usr/lib but with optware loaded the system will look first in /opt/lib and /opt/usr/lib

    Just a thought but it could explain why two different versions of 88V would behave differently.
     
  11. ppsun

    ppsun Networkin' Nut Member

    Not running optware. Just a 4GB USB thumbdrive as ftp & samba server storage.
    That could be why both 88V are behaving differently.
     
  12. shibby20

    shibby20 Network Guru Member

    i successful upgraded busybox in tomato to latest version 1.20 :) Will test and let you know :)
     
  13. shibby20

    shibby20 Network Guru Member

    i cant test it now on RT-N66U but i did test on Rt-N15u (RT-N branch also). Result:

    BusyBox v1.20.0 (2012-04-26 11:51:25 CEST) multi-call binary.

    0.1.2.3.4.5.6.7.8.9.

    :)
    re-test on RT-N66U when i go back to home.
     
  14. ppsun

    ppsun Networkin' Nut Member

    Shibby,
    Do you need me to test the new version before release?
    My RT-N66U fails the bug test consistently for 87V-AIO and 88V-AIO.
     
  15. shibby20

    shibby20 Network Guru Member

    i will test on my router and will give you new build for testing.
     
  16. Planiwa

    Planiwa LI Guru Member

    I find it very interesting that . . .

    Asus firmware using BusyBox 1.17.4 does not have the bug.
    Tomato firmware using BusyBox 1.18.5 has the bug.
    BusyBox 1.19.0 fixes an unspecified bug with shell scripts without the Hash-Bang first line.
    Tomato Victek firmware, using BusyBox 1.20.4 has the bug.

    Does any non-Tomato non-Asus FW have the bug?

    Cf: http://git.busybox.net/busybox/comm...e&id=aefe1c260ec5aa691e8b6f773c7fa393bfad0f7b
     
  17. shibby20

    shibby20 Network Guru Member

    Planiwa - thx.
     
  18. Planiwa

    Planiwa LI Guru Member

    Another user has now confirmed this bug on his router.

    Some people are unconcerned about this bug, and even recommend this router running Tomato firmware to others.

    Others seem to have implied that they find it hard to imagine that the reports are true, since such a severe bug could not possibly exist.

    Others appear to have implied that they can't imagine what might cause the problem, and therefore are not investigating it.
     
  19. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    What problems has this bug caused (or can cause)? I think maybe that's why some users are unconcerned, ether they haven't found it to be causing problems or don't know what problems it could or has caused.
     
  20. ppsun

    ppsun Networkin' Nut Member

    I suspect that this problem may be a timing issue as I get random results when I perform the test multiple times:
    0.ug.ug.3.ug.5.6.ug.ug.9.
    .ug.ug.ug.ug.ug.6.ug.ug.ug.
    .ug.ug.ug.ug.5.ug.7.ug.ug.
    .ug.2.ug.ug.5.ug.ug.8.ug.

    Can someone modify the test script in post 1? (as I don't how myself)
    Such that it inserts a time delay between characters (say 1 second per character).
    I want to see if the results comes out any better.
    Thanks.
     
  21. Planiwa

    Planiwa LI Guru Member

  22. Planiwa

    Planiwa LI Guru Member

    The purpose of the test script I gave was to confirm that one's router has the problem.
    It should take less than 1 minute. I've simplified it even more:

    Code:
    cd /tmp;echo -e '#!/bin/sh\necho -n $1' >x;chmod +x x
    for i in N o _ p r o b l e m _ h e r e .; do x $i; done;echo
    tail -1 /etc/motd;sh --help 2>&1|sed 1q; egrep 'BCM|MHz' /proc/cpuinfo
     
    
    If enough RT-N66U owners want their Tomato routers to stop being at risk of failing unpredictably, at any time. a first step would seem to be to get the attention of people who are in a position to diagnose and, identify, and fix the cause.

    A high proportion of Tomato RT-N66U owners confirming the bug on their router might help get that attention.

    A whole week ago Shibby said he would do something, but he has not actually confirmed the bug on his router.

    I think it is very important that Tomato RT-N66U owners state unambiguously:

    [ ] My RT-N66U running Tomato-XYZ-build HAS the bug.
    or
    [ ] My RT-N66U running Tomato-XYZ-build DOES NOT have the bug.
     
  23. Planiwa

    Planiwa LI Guru Member

    (Perhaps you might consider reducing the CPU speed of your router?)

    It appears that Tomato firmware fails nondeterministically on most instances of this hardware.
    The same Tomato firmware does not fail on other hardware.
    The same hardware does not fail with other firmware.
     
  24. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    I still don't get how this could make a router "fail". Could you please explain clearly why this is such a problem. What does it cause? And why hasn't it caused problems?
     
  25. Planiwa

    Planiwa LI Guru Member

    Computers take commands. Commands take arguments.
    Commands are like verbs, arguments are like objects.
    Thus, a command line may be of the form: Shoot enemy.

    This bug arbitrarily substitutes some other argument for the specified argument.
    Thus, you issue the command: Shoot enemy.
    and this software corrupts it to: Shoot friend.

    Why has this not yet caused outrageous damage?
    My guess:

    1. Very few people (10?) run Tomato on this router.
    2. Almost all of those very few use it as an appliance, rather than a programmable computer.
    3. Almost none have enough understanding to realize the severity of this bug, let alone diagnose it.

    Thus far, neither in this forum, nor the Tomato USB forum, has there been a single system administrator who owns this device and runs Tomato on it. Not a single one!

    There have been a handful of people who run Tomato on an RT-N66U and have the bug, and may even realize its catastrophic potential, but lack the understanding to diagnose it.

    There are also three or four people who understand the implications of this disastrous bug, but who have no access to such a router.

    And no one has offered access. -- In other words, no one understands the seriousness of this disastrous bug.

    The short answer to the question "what's so bad about this bug?" is, to paraphrase Louis Armstrong, when he was asked "what is rhythm?" -- His answer: "If you have to ask, you won't understand the answer."
    (Actually he said "Lady, if you gotta ask, you ain't got it.")

    My advice to nontechnical people who want this router: Use Asus firmware, not Tomato.
    To self-centred semi-technical people: Use Asus firmware, not Tomato.
    To conscious semi-technical people: install Tomato and give technical experts access to the router so that they can fix it for you.
    To technical experts: Here's a challenge, let's get to work.
     
  26. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    Thank you for the explanation. It helps to understand the situation. Now, from a developers stand point, this is something they do in they're spare time, not a daily job for them. How ever, I think shibby has this device and may be lacking in the time to look at it at the moment. I do know he has made some changes in the BB/ash portion of the git. I have no problem opening access to my router to toastman or shibby to diagnose this problem when time permits.
     
  27. Toastman

    Toastman Super Moderator Staff Member Member

    Planiwa, just uploading a version to 4shared that you guys may find useful to try, not finished yet - but take a look in the readme file.
     
  28. shibby20

    shibby20 Network Guru Member

    @Planiwa - does not help. Problem is only on RT-N66U. The same build flashed to RT-N15u and problem is not exists. I really dont know why :/
     
  29. Planiwa

    Planiwa LI Guru Member

    Toastman -- I see nothing new for the RT-N66U.
    Since you have no access to an RT-N66U router, I cannot imagine how you can even see the problem.

    Shibby -- your signature states that you are a user of an RT-N66U.
    You have never confirmed the existence of the bug on your RT-N66U.
    It takes less than 1 minute to do so. Will you please do it? Thanks.

    It is important that people who are seen as technically competent confirm the existence of the bug.
    Also important is that the severity of this bug be appreciated.

    Without this, there will be a fog of denial, either that the bug is real, or that it is worth paying attention to.

    Everyone --

    The RT-N66U Shell Parameter Bug has only ever been observed on the RT-N66U running Tomato.

    As I wrote yesterday:


    Tomato firmware fails nondeterministically on most all instances of the RT-N66U hardware.
    The same Tomato firmware does not fail on non-RT-N66U hardware.
    The same RT-N66U hardware does not fail with non-Tomato firmware.
     
  30. RobF

    RobF Serious Server Member

    I ran the first test but didn't see the problem but then I saw it once I ran the "N o P r o b l e m" script. The odd thing is that I've not been able to identify any other malfunction in my router. Its seems to be working just fine.
    Forwarded ports are working, logging is working, dyndns is working most importantly NAT is working.
    I have perl via optware installed... perhaps I should do some tests with that.

    I'm running shibby V88 AIO
    Code:
    Tomato v1.28.0000 MIPSR2-088V K26 USB AIO
     
  31. Planiwa

    Planiwa LI Guru Member

    RobF -- Thanks. This report is important since, as far as I know, this means that every Tomato RT-N66U that has been tested does have the bug.
     
  32. RobF

    RobF Serious Server Member

    Ok.. tested with perl... as I expected we have the same type of "scrambled" results.

    I logged in with Putty to my router as root and created a script /tmp/mytest containing the the following perl script.
    Basically, it just prints command line arguments 0, 1 and 2 and exits

    Code:
    #!/usr/bin/perl
    print "$ARGV[0]\n";
    print "$ARGV[1]\n";
    print "$ARGV[2]\n";
    I then invoked it with 3 arguments as such
    Code:
    ./mytest one two three
    Now here is the bizarre part... I would hit the up arrow key and then hit enter to repeatedly execute the script... very different results.

    Code:
    root@router:/tmp# ./mytest one two three
    mytest
    one
    two
    root@router:/tmp# ./mytest one two three
    /mytest
    one
    two
    root@router:/tmp# ./mytest one two three
    /bin/sh
    TERM=xterm
    SSH_TTY=/dev/pts/1
    root@router:/tmp# ./mytest one two three four
    one
    two
    three
    root@router:/tmp# ./mytest one two three four
    /bin/sh
    TERM=xterm
    SSH_TTY=/dev/pts/1
    
    This may not tell us much since the shell is passing the arguments to perl and we already know that the shell has problems.
     
  33. shibby20

    shibby20 Network Guru Member

    i confirm a bug. It`s exists only on RT-N66U. On others routers all works correct. First when i tested i haven`t "ug" problem. Now i have too.

    I tried upgrade busybox to stable 1.19.4 and unstable 1.20 but stiil have this problem. I even tried revert busybox to 1.17.x (this is in asus ofw) but still problem exists. I cant resolve this problem but i`m trying.
     
  34. RobF

    RobF Serious Server Member

    out of curiosity Shibby.. What gcc optimization flags do you use to build... Is that something to consider?
    Just a thought.
     
  35. Jacques

    Jacques Addicted to LI Member

    My test.
    tail -1 /etc/motd;sh --help 2>&1|sed 1q; egrep 'BCM|MHz' /proc/cpuinfo
    cd /tmp;echo -e '#!/bin/sh\necho -n$ $1' >x;chmod +x x
    for i in N o _ p r o b l e m _ h e r e .; do x $i; done;echo

    Tomato v1.28.0498 MIPSR2Toastman-RT-N K26 USB VPN
    BusyBox v1.18.5 (2012-05-04 05:55:54 ICT) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz : 600
    -n$ N
    -n$
    -n$ _
    -n$ p
    -n$
    -n$
    -n$
    -n$ l
    -n$
    -n$
    -n$ _
    -n$
    -n$
    -n$ r
    -n$
    -n$

    when you click on execute each time the result is not the same.
    -n$ N
    -n$ o
    -n$
    -n$
    -n$
    -n$ o
    -n$
    -n$
    -n$ e
    -n$
    -n$ _
    -n$ h
    -n$
    -n$
    -n$ e
    -n$
    execute
    -n$
    -n$ o
    -n$ _
    -n$ p
    -n$ r
    -n$ o
    -n$
    -n$
    -n$ e
    -n$
    -n$ _
    -n$ h
    -n$ e
    -n$
    -n$ e
    -n$ .
     
  36. shibby20

    shibby20 Network Guru Member

    it`s not busybox fault, because when i try to use full bash from optware (#!/opt/bin/bash) i have the same effect.This is failt with CPU BCM4706 support. I`m thying fix it.
     
  37. Planiwa

    Planiwa LI Guru Member

    Shibby -- "This is a fault with CPU BCM4706 support." -- very interesting.


    Jacques -- Your copy-paste is broken (something inserted a '$' after "-n").

    . . .

    FWIW, the following Tomato commands are examples of shell scripts that will fail (intermittently) because of this bug:

    /usr/sbin/cru
    /usr/sbin/gencert
     
  38. Jacques

    Jacques Addicted to LI Member

    Planiwa, everything is ok

    tail -1 /etc/motd;sh --help 2>&1|sed 1q; egrep 'BCM|MHz' /proc/cpuinfo
    cd /tmp;echo -e '#!/bin/sh\necho step by step = $1' >x;chmod +x x
    for i in N o _ p r o b l e m _ h e r e .; do x $i; done;echo

    Tomato v1.28.0498 MIPSR2Toastman-RT-N K26 USB VPN
    BusyBox v1.18.5 (2012-05-04 05:55:54 ICT) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz : 600
    step by step = N
    step by step = o
    step by step = _
    step by step = p
    step by step =
    step by step = o
    step by step = b
    step by step = l
    step by step = e
    step by step = m
    step by step = _
    step by step =
    step by step = e
    step by step = r
    step by step = e
    step by step = .
     
  39. azdps

    azdps LI Guru Member

    using the updated script you posted Planiwa. each time the command is used the result is different.

    Code:
    root@RT-20CF30B74E90:/tmp# cd /tmp;echo -e '#!/bin/sh\necho -n $1' >x;chmod +x x
    root@RT-20CF30B74E90:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
     
    No/x/xr/xbl/xm_/x/xr/x.
     
    root@RT-20CF30B74E90:/tmp# tail -1 /etc/motd;sh --help 2>&1|sed 1q; egrep 'BCM|MHz' /proc/cpuinfo
     
    Tomato v1.28.0498 MIPSR2-Toastman-RT-N K26 USB Std
    BusyBox v1.18.5 (2012-04-23 11:37:03 ICT) multi-call binary.
    system type            : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz                : 600
    
     
  40. shibby20

    shibby20 Network Guru Member

    i fhash ddwrt into rtn66u and

    root@DD-WRT:/tmp# cat /etc/motd
    ==========================================================
    ____ ___ __ ______ _____ ____ _ _
    | _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || |
    || | || ||____\ \ /\ / /| |_) || | \ \ / / __) | || |_
    ||_| ||_||_____\ V V / | _ < | | \ V / / __/|__ _|
    |___/|___/ \_/\_/ |_| \_\|_| \_/ |_____| |_|
    DD-WRT v24-sp2
    http://www.dd-wrt.com
    ==========================================================
    root@DD-WRT:/tmp# egrep 'BCM|MHz' /proc/cpuinfo
    system type : Broadcom BCM5300 chip rev 1
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.
    root@DD-WRT:/tmp# for i in N o _ p r o b l e m _ h e r e .; do ./x $i; done;echo
    No_problem_here.

    i`m still fighting with tomato.
     
  41. Demolishing81

    Demolishing81 Serious Server Member

    Code:
    cd /tmp;echo -e '#!/bin/sh\necho -n $1' >x;chmod +x x
    for i in N o _ p r o b l e m _ h e r e .; do x $i; done;echo
    tail -1 /etc/motd;sh --help 2>&1|sed 1q; egrep 'BCM|MHz' /proc/cpuinfo
    
    Produces:
    Code:
    00oobl_e
    Tomato v1.28.0000 MIPSR2-092 K26 USB Mega-VPN
    BusyBox v1.18.5 (2012-04-13 16:06:33 CEST) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz    : 600
    
     
  42. shibby20

    shibby20 Network Guru Member

    sorry but i failed. I`m not able to find and fix this bug. I made many changes in kernel from asus sources and ddwrt sources but bug is still exists. I tried 2 weeks, every day... When i will have more free time maybe i will return to this case.
     
  43. shibby20

    shibby20 Network Guru Member

    one more: IMO it`s not a problem with shell and CPU support. I tested tomato on Netgear WNDR4500 (same cpu as in RT-N66U) and it works correct:
    IMO it`s a fault memory >128MB. Asus RT-N66U is the one router with memory higher than 128MB. Tomato propably have a problem with that.
     
  44. ppsun

    ppsun Networkin' Nut Member

    Thanks Shibby! As a fellow owner of the RT-N66U and long-time user of tomatousb, I do appreciate all your effort in trying to fix this issue. Though, even with this issue, my RT-N66U seems reasonably stable enough for me to use it day-to-day. I must be not using the functionality that "activates" this bug.

    Is there anything a non-developer user, like myself, can help you in any way?
     
  45. Planiwa

    Planiwa LI Guru Member

  46. shibby20

    shibby20 Network Guru Member

  47. ryzhov_al

    ryzhov_al Networkin' Nut Member

    If so, it's not too hard to check. You may configure (limit!) RAM usage through CFE before linux boot like we did on WL-500gpv1.

    Just refer to BCM Memory Controller guide and set:
    Code:
    $ sdram_config=...
    $ sdram_init=...
    $ nvram commit && reboot
    And you will get 128Mb (or 64Mb) version of RT-N66U^)
     
  48. shibby20

    shibby20 Network Guru Member

    nice. Can anyone check this? i havent RT-N66U at the moment.
     
  49. ArCan

    ArCan Networkin' Nut Member

    I can check it right now.
    But I don't know what I should input instead "..." in
    "$ sdram_config=...
    $ sdram_init=...
    $ nvram commit && reboot"
    (It doesn't matter for me how much memory I will have 64 or 128Mb).

    In my NVRAM dump I can see now:
    "...
    sdram_config=0x0000
    sdram_init=0x0000
    sdram_ncdl=0x00000000
    sdram_refresh=0x0000
    ..."

    Please give me advice what I should write down instead "..." ?
    Thanks.
     
  50. ArCan

    ArCan Networkin' Nut Member

    I run
    "nvram set sdram_init=0x0011
    nvram set sdram_config=0x0062
    nvram commit
    reboot"
    and after reboot I have in NVRAM dump
    "sdram_init=0x0011
    sdram_config=0x0062"
    BUT
    still "Total / Free Memory 250.00 MB / 222.70 MB (89.08%)" on Overveiw page
    and "Memory: 255584k/131068k available (33k kernel code, 6260k reserved, 2701k data, 124k init, 131072k highmem)"
    in log.

    I'm only dump user and may be do something wrong?
     
  51. sumsar

    sumsar Serious Server Member

    What if you set nvram set sdram_init=0x0010 instead of nvram set sdram_init=0x0011?
    I'm waiting for a mega file transfer to finish so I can't test my self right now.

    EDIT: Ah yeah, N66U uses DDR.

    Btw: How did you calc sdram_config=0x0062?

    EDIT 2: I have also messed some with this now. I'm having the same results as ArCan.
    No real change in RAM size whatever the settings.
     
  52. Planiwa

    Planiwa LI Guru Member

    Jean-Yves Avenard writes:

    "I have a fix for the tomato's kernel…
    the issue is in the initialisation of the pages map…
    I'll push the commit shortly.. I want to do a final round of tests first.. it's a rather invasive change.
    It looks like Broadcom/Asus haven't submitted to upstream linux their changes. Because I can't find any references to the paging init they are doing."

    http://tomatousb.org/forum/t-461749/asus-rt-n66u-script-execution-fails-in-about-50-of-all-tries
     
  53. NeutralGold

    NeutralGold Serious Server Member

    Great news. Has anyone else tried using one of the modified builds he placed the fix in? I haven't used any other firmware besides asus's so far because of that "ug" bug. I'll probably try that build Jean-Yves compiled this afternoon. I'll have to read up on the latest firmware flashing issues before I do it. Can't wait to try it..

    I wonder if asus's fix for the nvram is still getting released this month. Hope so! I've got a couple of forums set to alert me on the issue, but not all of them. That problems discussed on a lot of different post so it's hard to keep up with what's going on.

    But I'm more interested in getting tomato going atm..
     
  54. shibby20

    shibby20 Network Guru Member

    i will publish one test build with "ug" fix today

    No_problem_here.
    Tomato v1.28.0000 MIPSR2-094.1 K26 USB AIO
    BusyBox v1.18.5 (2012-06-08 16:24:38 CEST) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz : 600
     
  55. shibby20

    shibby20 Network Guru Member

  56. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    No_problem_here.
    Tomato v1.28.0000 MIPSR2-094.1 K26 USB AIO
    BusyBox v1.18.5 (2012-06-08 16:24:38 CEST) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz : 600

    Altho I am getting a problem running my auto scripts from the SD card now, maybe a timing issue, will post more later
     
  57. quietsy

    quietsy LI Guru Member

    No_problem_here.
    Tomato v1.28.0000 MIPSR2-094.1 K26 USB AIO
    BusyBox v1.18.5 (2012-06-08 16:24:38 CEST) multi-call binary.
    system type : Broadcom BCM5300 chip rev 1 pkg 0
    cpu MHz : 600
    Everything seems to work, don't have an SD card so can't test that.
     
  58. sumsar

    sumsar Serious Server Member

    No_problem_here.

    Tomato v1.28.0000 MIPSR2-094.1 K26 USB AIO

    I run all my scripts from internal sd-card, no problems what so ever.
     
  59. Dark_Shadow

    Dark_Shadow Addicted to LI Member

    Everything is running great here, turns out some things don't like to be run from the root of external storage. So I moved those scripts to /opt/etc/config and changed they're extension properly and every thing runs as it is supposed to and QOS graphs have no problem thus far.

    EDIT: Now to get Asus to fix the nvram problem hehehe
     

Share This Page