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

BW Limit + Victek 1.2 = Frequent Reboots: What am I doing wrong?

Discussion in 'Tomato Firmware' started by Planiwa, Sep 19, 2013.

  1. Planiwa

    Planiwa LI Guru Member

    Tomato v1.28.9013 MIPSR2-RAF-V1.2 K26 USB VLAN-NGINX-64K -- Asus RT-N66U

    I've been using Victek's 1.2 since it first came out -- erased NVRAM before and after multiple flashings.

    When I use the Bandwidth Limiter the router reboots several times a day.
    When the Bandwidth Limiter is not enabled, the router does not reboot spontaneously.
    Clearly I must be doing something wrong, since no one else has reported this problem.

    Here is what I did:

    *. erase nvram thorough
    *. select upgrade + erase after
    *. upgrade to 1.2

    changed only:

    1. Basic>Network: pppoe
    2. username
    3. password
    4. disable WiFi
    5. Save
    6. Enable bw limiter
    7. 16000 6000
    8. 2-53 1600 16000 600 6000 normal nolimit nolimit
    9. Save


    Apart from the spontaneous reboots, the following may trigger a reboot:

    1. wake from sleep
    2. quit mail
    3. ifconfig down/up

    Other sites, using Shibby FW, typically have uptimes of several months, with many users.
    This site has a single user, with very little traffic.


    I am sure that there is nothing wrong with the firmware
    No one else has reported these reboots.
    Clearly I am doing something wrong.

    Thanks for any help.
     
  2. Victek

    Victek Network Guru Member

    Power Supply ... There are many posts in the forum when people used the previous router PSU due to compatible plug BUT delivering less current (Amperes) provoking the same issue you mention, verify.
     
  3. Planiwa

    Planiwa LI Guru Member

    Did I mention that this problem does not happen if Bandwidth Limiter is not enabled, same router, same power supply.
    FWIW -- Power Supply, with the nice blue light, says 19V, 1.58A.

    Code:
    Sep 19 17:04:38 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:18:31 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:33:03 planiwa.local mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:34:33 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:41:08 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    
     
  4. Victek

    Victek Network Guru Member

    Usually the bandwidth limiter increases router current consumption when the CPU load increases... this was the reason other users discovered for random reboots. Did you added other iptables or rules like access restriction, captive portal, QoS (remember that QoS and BW limiter are not compatible as noticed in the GUI)... or it's a clean install with only BW limiter enabled?. I have BW limiter enabled in my router 24/24 .. no problem.
     
  5. Planiwa

    Planiwa LI Guru Member

    I made no configuration changes except those given above, and listed under "changed only", after flashing.
    I have deliberately left everything possible at default settings.

    Actually right now the 5GHz radio is enabled again, with WPA2 Personal.

    CPU Clock 600 MHz
    CPU Load 1.64%
    CPU Load (1 / 5 / 15 mins) 0.00 / 0.00 / 0.00
     
  6. Planiwa

    Planiwa LI Guru Member

    I plan to go back to 1.1w later tonight or tomorrow . . .

    more reboots:
    Code:
    Sep 19 19:47:08 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:48:44 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:50:16 planiwa.local mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:51:48 planiwa.local mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 19:54:00 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 21:41:14 planiwa.local mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    Sep 19 21:42:44 planiwa mDNSResponder[39]: NAT gateway 192.168.1.1 rebooted
    
     
  7. Planiwa

    Planiwa LI Guru Member

    I forgot something:

    Kingston DataTraveler 2.0
    Partition 'KINGSTON' vfat (7,490.08 MB / 7,489.98 MB free) is mounted on /tmp/mnt/KINGSTON

    I have now removed the USB data thing.

    The LAN has:

    1. MBP, connected via 5GHz,
    2. iPhone, connected via 5GHz.

    Before posting, just for fun, I quit Mail.
    Sure enough, the router rebooted.
     
  8. Planiwa

    Planiwa LI Guru Member

    1.1w -- same problem.

    Perhaps I should go back to Shibby FW, where I never had a random reboot, with uptimes of many months.
    Then if it happens there too, I know my hardware is suddenly bad.

    I *need* BW limiter.
    I *want* NGINX. That's why I spent so many hours struggling with Victek's FW.

    Looks like I may have to give up what I want to get what I need.

    A complete reboot takes less than 1 minute.
    I wonder whether other people are getting random reboots but are not aware of them?

    I get a loud alarm the moment the router becomes unresponsive.
    I wonder what kind of uptimes others have when running BW Limiter?
     
  9. Planiwa

    Planiwa LI Guru Member

    The router has now been running on Shibby AIO 112 for 7 hours. It did no reboot on waking after 5 hours of sleep.
    Victek 1.2 would certainly have rebooted.

    This suggests that whatever made the router reboot with BWL on, running Victek 1.2 is not making it reboot with BWL on, running Shibby.

    But since no one else has reported this problem, the question remains: Since it is apparently not a hardware problem, and since it can't be a software problem, it appears be a user problem: what am I doing wrong?

    Tomato Firmware 1.28.0000 MIPSR2-112 K26 USB AIO-64K

    "Victek/PrinceAMD/Phykris/Shibby" feature:
    - Revised IP/MAC Bandwidth Limiter

    Time Fri, 20 Sep 2013 15:45:46 +0200
    Uptime 0 days, 06:57:35
    CPU Load (1 / 5 / 15 mins) 0.00 / 0.00 / 0.00
    Total / Free Memory 249.73 MB / 238.99 MB (95.70%)
    Total / Free NVRAM 64.00 KB / 37.54 KB (58.65%)
     
  10. Planiwa

    Planiwa LI Guru Member

    There is hope: Victek has discovered a bug and will post a fixed version. So I wait. Then I try it.

    Meanwhile, I just discovered that Victek's BW Limiter doesn't have the "Default" option that Shibby's has.

    In case anyone is interested, here is how I use BW Limiter:

    0. 25/10/300 DSL; 7 or 8 users, perhaps 20 WiFi devices. Some users are short-term, perhaps only a few days.

    1. The old policy was to put all DHCP devices into CRAWL class until they are registered (given a static IP and put into RUN class). Abusers are put into WALK class.

    2. The new policy is to ask users to give their devices proper hostnames. Default (starting) class is RUN. Abusers are placed into WALK. Devices without proper hostnames are subjected to stricter limits.

    The new policy requires no static IPs. It causes no unnecessary hardship for users who stay within the guidelines. It requires less admin work and less network disruption.

    Shibby's BW Limiter, with the Default option, makes this easy to implement.

    I don't know how to do this easily without a Default category, since specifying a range in one rule, and then listing a part of the range in another rule, may or may not be interpreted by Victek's BWL the same ways that I would interpret it.
     
  11. Victek

    Victek Network Guru Member

    I'm not using this workflow, it's why Tomato RAF bandwidth achieves easy 150Mbps with defalut version (more than 200Mbps with Speedtest version) and other Tomato mods can't .... we must be very careful with rules in the kernel..
     
  12. Planiwa

    Planiwa LI Guru Member

    Victek, did you intend to post that in another thread? I can't see how it relates to what I said here.

    But if you could clarify what happens when there are three rules, as follows, in the BWL, that would be much appreciated:

    1. IP Range 80-199 ...... high limits
    2. IP 99 ..... low limits
    3. MAC xyz .... low limits (where this device has an IP address in 80-199)

    Thanks!

    (Looking forward to testing the version with the fixed BWL for RT-N66U.)
     
  13. Victek

    Victek Network Guru Member

    planiwa .. it will provoke a dedicated job for the CPU increasing the sofirq.. I think what you need is a dedicated PC ..
    I'm testing the version by myself before to be sure that it works 100%, I found a very sensible router that crash immediate with BW limiter, also with other tomato mods, the E4200 .. I think that the limited available RAM in this unit (64MB) could be one of the reasons since I can't see anything when it crash... I'm little blind in this issue ..thanks ;)

    Edit: BTW .. did you contributed to Tomato? .. to be honest, I receive a lot of request for added features and ideas (like you now) that cost a lot of money if you want to implement in other units (ask Cisco about...) but after it works people lost the gratitude.. ;), this is the reason why lately I do features that cover my needs only.. ;) .. understood?.. just hobby.
     
    Last edited: Sep 24, 2013
  14. Planiwa

    Planiwa LI Guru Member

    Yesterday's Victek wrote:

    "@Planiwa , since you're one of the 'hard' users for BW Limiter... I review the code again and found some 'holes' in the integration of new models routers 'AC' and 'N', so, I wrote new code trying to workaround 'forward' using 'mangle', would you like to test the build I did few minutes ago? Are you using RT-N66U right? please confirm and I'll indicate the link to download. Thanks"

    Today's Victek seems to have forgotten all about that.

    Are there two Victek's?
     
  15. Victek

    Victek Network Guru Member

  16. Planiwa

    Planiwa LI Guru Member

    The only questions I saw were "would you like to test the build I did few minutes ago? Are you using RT-N66U right?".

    The answer I gave was: "YES!!! Please Victek."

    (Tal vez debería escribir en español?)
     
  17. Victek

    Victek Network Guru Member

    You should read from top to bottom in my last post and see '?' , (a buen entendedor pocas palabras bastan).
     
  18. Planiwa

    Planiwa LI Guru Member

    8 hours and no crash:

    Tomato v1.28.9013 MIPSR2-RAF-V1.2f2 K26 USB
    07:58:48 up 8:06, load average: 0.00, 0.00, 0.00

    new_qoslimit_enable=1
    new_qoslimit_ibw=
    new_qoslimit_obw=
    new_qoslimit_rules=192.168.0.30-40<1000<2000<555<999<2<0<0
    qos_ibw=16000
    qos_obw=6400
    qosl_dlc=500
    qosl_dlr=200
    qosl_enable=1
    qosl_ulc=200
    qosl_ulr=100
     
    Victek likes this.
  19. Victek

    Victek Network Guru Member

    Thanks @Planiwa .. I see then two nvram values not used
    new_qoslimit_ibw=
    new_qoslimit_obw=

    and it's still using old variables.

    qos_ibw=16000
    qos_obw=6400

    Right? did you erased nvram?
    I saw also in /etc/qoslimit values remain after you erased them in the GUI when feature is disabled but wiped in nvram (new_qoslimit_rules=). When it's enabled again the values are deleted/replaced by new ones.. no problem.

    Edit: Hmmmm.. may be I can use /etc/qoslimt instead of nvram space ...
     
    Last edited: Sep 25, 2013
  20. Planiwa

    Planiwa LI Guru Member

    Just did a wake after 5.5 hours -- still no crash.

    @Victek I was wondering about those variables as well, that's why I have their values.
    (Yes, of course I erased nvram before (thorough) and after (as upgrade option)).

    Anything else I should show?

    Right now:

    cat /etc/motd
    uptime

    echo
    nvram show | egrep 'slimit|[io]bw|l_[ud]l[rc]|l_ena'

    echo
    head -99 /etc/qoslimit



    Notes (Click here to show)


    Tomato v1.28.9013 MIPSR2-RAF-V1.2f2 K26 USB
    15:28:14 up 15:35, load average: 0.00, 0.00, 0.00

    new_qoslimit_enable=1
    new_qoslimit_ibw=
    new_qoslimit_obw=
    new_qoslimit_rules=192.168.0.30-40<1000<2000<555<999<2<0<0
    qos_ibw=16000
    qos_obw=6400
    qosl_dlc=500
    qosl_dlr=200
    qosl_enable=1
    qosl_ulc=200
    qosl_ulr=100

    #!/bin/sh
    tc qdisc del dev br0 root 2>/dev/null
    tc qdisc del dev vlan2 root 2>/dev/null

    TCA="tc class add dev br0"
    TFA="tc filter add dev br0"
    TQA="tc qdisc add dev br0"

    SFQ="sfq perturb 10"

    TCAU="tc class add dev vlan2"
    TFAU="tc filter add dev vlan2"
    TQAU="tc qdisc add dev vlan2"

    tc qdisc add dev br0 root handle 1: htb
    tc class add dev br0 parent 1: classid 1:1 htb rate 16000kbit

    tc qdisc add dev vlan2 root handle 2: htb
    tc class add dev vlan2 parent 2: classid 2:1 htb rate 6400kbit

    $TCA parent 1:1 classid 1:100 htb rate 200kbit ceil 500kbit prio 3
    $TQA parent 1:100 handle 100: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 100 fw flowid 1:100

    $TCAU parent 2:1 classid 2:100 htb rate 100kbit ceil 200kbit prio 3
    $TQAU parent 2:100 handle 100: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 100 fw flowid 2:100

    $TCA parent 1:1 classid 1:10 htb rate 1000kbit ceil 2000kbit prio 2
    $TQA parent 1:10 handle 10: $SFQ
    $TFA parent 1:0 prio 2 protocol ip handle 10 fw flowid 1:10

    $TCAU parent 2:1 classid 2:10 htb rate 555kbit ceil 999kbit prio 2
    $TQAU parent 2:10 handle 10: $SFQ
    $TFAU parent 2:0 prio 2 protocol ip handle 10 fw flowid 2:10



    === after disable save enable save ===


    Notes (Click here to show)


    Tomato v1.28.9013 MIPSR2-RAF-V1.2f2 K26 USB
    15:31:58 up 15:39, load average: 0.14, 0.07, 0.02

    new_qoslimit_enable=0
    new_qoslimit_ibw=
    new_qoslimit_obw=
    new_qoslimit_rules=192.168.0.30-40<1000<2000<555<999<2<0<0
    qos_ibw=16000
    qos_obw=6400
    qosl_dlc=500
    qosl_dlr=200
    qosl_enable=1
    qosl_ulc=200
    qosl_ulr=100

    #!/bin/sh
    tc qdisc del dev br0 root 2>/dev/null
    tc qdisc del dev vlan2 root 2>/dev/null

    TCA="tc class add dev br0"
    TFA="tc filter add dev br0"
    TQA="tc qdisc add dev br0"

    SFQ="sfq perturb 10"

    TCAU="tc class add dev vlan2"
    TFAU="tc filter add dev vlan2"
    TQAU="tc qdisc add dev vlan2"

    tc qdisc add dev br0 root handle 1: htb
    tc class add dev br0 parent 1: classid 1:1 htb rate 16000kbit

    tc qdisc add dev vlan2 root handle 2: htb
    tc class add dev vlan2 parent 2: classid 2:1 htb rate 6400kbit

    $TCA parent 1:1 classid 1:100 htb rate 200kbit ceil 500kbit prio 3
    $TQA parent 1:100 handle 100: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 100 fw flowid 1:100

    $TCAU parent 2:1 classid 2:100 htb rate 100kbit ceil 200kbit prio 3
    $TQAU parent 2:100 handle 100: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 100 fw flowid 2:100

    $TCA parent 1:1 classid 1:10 htb rate 1000kbit ceil 2000kbit prio 2
    $TQA parent 1:10 handle 10: $SFQ
    $TFA parent 1:0 prio 2 protocol ip handle 10 fw flowid 1:10

    $TCAU parent 2:1 classid 2:10 htb rate 555kbit ceil 999kbit prio 2
    $TQAU parent 2:10 handle 10: $SFQ
    $TFAU parent 2:0 prio 2 protocol ip handle 10 fw flowid 2:10
     
  21. Victek

    Victek Network Guru Member

    Yes.. I did some changes triying to transfer these nvram values to qoslimit.conf file .. but then I disconnected PSU during 'save values' (worst condition) and the file get corrupted, so .. have to clean these unused values and leave nvram storage. I'll release a new build tomorrow, updating mips32r2 code for arch/kernel and modules, it increases 10KB build size but then we are fully using mips32r2 set of instructions, my hope is that will contribute a better performance. I'm already runnig a test version in E4200 .. the weakest device that manifest any programming mistake ..
     
    Last edited: Sep 25, 2013
  22. Elfew

    Elfew Addicted to LI Member

    Ok, I am waiting ;)
     
  23. Planiwa

    Planiwa LI Guru Member

    It's now been 1d 6h and no crash!
     
  24. Planiwa

    Planiwa LI Guru Member

    Tomato v1.28.9013 MIPSR2-RAF-V1.2g K26 USB
    09:00:27 up 19 min, load average: 0.00, 0.04, 0.01

    new_qoslimit_enable=1
    new_qoslimit_rules=192.168.0.30-40<200<600<100<200<3<50<1
    qos_ibw=24000
    qos_obw=9000
    qosl_dlc=10000
    qosl_dlr=2000
    qosl_enable=1
    qosl_ulc=4000
    qosl_ulr=1000

    #!/bin/sh
    tc qdisc del dev br0 root 2>/dev/null
    tc qdisc del dev vlan2 root 2>/dev/null

    TCA="tc class add dev br0"
    TFA="tc filter add dev br0"
    TQA="tc qdisc add dev br0"

    SFQ="sfq perturb 10"

    TCAU="tc class add dev vlan2"
    TFAU="tc filter add dev vlan2"
    TQAU="tc qdisc add dev vlan2"

    tc qdisc add dev br0 root handle 1: htb
    tc class add dev br0 parent 1: classid 1:1 htb rate 24000kbit

    tc qdisc add dev vlan2 root handle 2: htb
    tc class add dev vlan2 parent 2: classid 2:1 htb rate 9000kbit

    $TCA parent 1:1 classid 1:100 htb rate 2000kbit ceil 10000kbit prio 3
    $TQA parent 1:100 handle 100: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 100 fw flowid 1:100

    $TCAU parent 2:1 classid 2:100 htb rate 1000kbit ceil 4000kbit prio 3
    $TQAU parent 2:100 handle 100: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 100 fw flowid 2:100

    $TCA parent 1:1 classid 1:10 htb rate 200kbit ceil 600kbit prio 3
    $TQA parent 1:10 handle 10: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 10 fw flowid 1:10

    $TCAU parent 2:1 classid 2:10 htb rate 100kbit ceil 200kbit prio 3
    $TQAU parent 2:10 handle 10: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 10 fw flowid 2:10
     
  25. Victek

    Victek Network Guru Member

    Thanks for updating to 1.2g version.;)
     
  26. Elfew

    Elfew Addicted to LI Member

    Thank you Victek - same results, just perfect! Keep good work!
     
  27. Planiwa

    Planiwa LI Guru Member

    Tomato v1.28.9013 MIPSR2-RAF-V1.2h K26 USB
    02:48:11 up 12 min, load average: 0.06, 0.03, 0.00

    new_qoslimit_enable=1
    new_qoslimit_rules=192.168.0.80-89<200<600<100<200<3<50<1
    qos_ibw=2400
    qos_obw=9000
    qosl_dlc=10000
    qosl_dlr=2000
    qosl_enable=1
    qosl_ulc=4000
    qosl_ulr=1000

    #!/bin/sh
    tc qdisc del dev br0 root 2>/dev/null
    tc qdisc del dev vlan2 root 2>/dev/null

    TCA="tc class add dev br0"
    TFA="tc filter add dev br0"
    TQA="tc qdisc add dev br0"

    SFQ="sfq perturb 10"

    TCAU="tc class add dev vlan2"
    TFAU="tc filter add dev vlan2"
    TQAU="tc qdisc add dev vlan2"

    tc qdisc add dev br0 root handle 1: htb
    tc class add dev br0 parent 1: classid 1:1 htb rate 2400kbit

    tc qdisc add dev vlan2 root handle 2: htb
    tc class add dev vlan2 parent 2: classid 2:1 htb rate 9000kbit

    $TCA parent 1:1 classid 1:100 htb rate 2000kbit ceil 10000kbit prio 3
    $TQA parent 1:100 handle 100: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 100 fw flowid 1:100

    $TCAU parent 2:1 classid 2:100 htb rate 1000kbit ceil 4000kbit prio 3
    $TQAU parent 2:100 handle 100: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 100 fw flowid 2:100

    $TCA parent 1:1 classid 1:10 htb rate 200kbit ceil 600kbit prio 3
    $TQA parent 1:10 handle 10: $SFQ
    $TFA parent 1:0 prio 3 protocol ip handle 10 fw flowid 1:10

    $TCAU parent 2:1 classid 2:10 htb rate 100kbit ceil 200kbit prio 3
    $TQAU parent 2:10 handle 10: $SFQ
    $TFAU parent 2:0 prio 3 protocol ip handle 10 fw flowid 2:10
     

Share This Page