Shibby build, not stable on my RT-N16

Discussion in 'Tomato Firmware' started by Manna420, May 8, 2012.

  1. Manna420

    Manna420 Networkin' Nut Member

    Hi Guys

    I created a thread few days ago where i asked for help updating my RT-N16 with latest build. In the end i was suggested this one: Tomato Firmware 1.28.0000 MIPSR2-092 K26 USB AIO
    I have almost everything running just fine on my network apart from some more important things which i dont have a clue why it is happening. Before flashing this build, i saved the configuration. So after flashing i did perform a restore of configuration and expected it to work exactly as it did before flashing. I started getting problems with some of the devices in network unable to connect to the WIFI. So i figured out little later that it did change the encryption on my WIFI settings from TKIP/AES to only TKIP. After changing it back to original, the devices were able to connect again.

    But now i am experiencing something else which i did not notice right away. My internet is soooo slow. I have a 12Mbit down and 5Mbit up. When testing the internet i just get max 3Mbit down and 5Mbit up. Upload is alright but what has happend to my download? Another thing i noticed is that transfer something on my Network share is sooo slow compare to what it was before flashing. Is there something which needs to be done to correct this? Am i using a bad build or whats happening? Please Help.
  2. lancethepants

    lancethepants Network Guru Member

    Backing up and restoring a configuration is only recommended when using the same exact firmware. When upgrading to a different firmware, you should always clear nvram, and then configure from scratch. Personally, I create a files with all my settings, then run through those manually placing them in the gui. I will grab a couple from an nvram dump, like qos rules, which is very extensive, and set it using "nvram set <nvram variable and value>". I know there are scripts floating around the forum that can help automate this process.
    Your configuration restoration, however, is almost certainly what is messing things up.
  3. Manna420

    Manna420 Networkin' Nut Member

    Thanks for the reply. So now as i have done this mistake, what should i do now? The guy who suggested me this firmware asked me to take a backup of the configuration, but i think he asked me for that incase the new build didnt work, so i had something to fall back on. I thought i was suppose to use this configuration file to just dump it in the new build and go on. To be quite ownest, im not a pro in using the commands, just a newbie, so i would appritiate if someone could tell me what to do. I dont even know how to clear nvram. In the tomato GUI where you upgrade the build, there is an option which we can tick that says the following: After flashing, erase all data in NVRAM memory. Is this what you are poiting towards?
  4. Riddlah

    Riddlah LI Guru Member

    Sorry if I wasn't clear on it earlier.

    First, make note of the configuration you need for when you are reconfiguring from scratch. Since you are already on the firmware, go to Administration --> Configuration. Under 'Restore Default Configuration' choose 'Erase all data in NVRAM (thorough)' and press 'OK'.

    This will reset everything and make sure it is a clean setup. After the router has finished rebooting, set a static ip on your desktop/pc and either connect to the router through wired/wireless. Once that is done, go through the configuration and reconfigure all your settings.
  5. Manna420

    Manna420 Networkin' Nut Member

    Hmmm, oki, ill give it a go, thanks for the reply, ill keep u posted.
  6. Elfew

    Elfew Network Guru Member

    Shibby AIO v92 on my RT16 is pretty stable! I like it!
    66xx66xx66 likes this.
  7. Manna420

    Manna420 Networkin' Nut Member

    Ah so you are running the same, glad to hear others out there have it running perfectly, im gonna perform the steps as suggested by Riddlah and post the update.
  8. Elfew

    Elfew Network Guru Member

    I had before Toastman build, but month ago I switched to Shibby - I have better performance over wifi... and I need BW limiter, which Toastman doesnt support yet
  9. Manna420

    Manna420 Networkin' Nut Member

    Great, thats good. Oki, so i just wanted to tell that i now have performed the steps as suggested, and reconfigured everything manually back to its original configuration. Everything is working just fine so far. Internet speed is as it should, file sharing is working and transfering on my share stuff is as it should., around 7-10 MB/sec. So im realy happy so far. Hope it just continues like that :) Thanks for all the help guys, specially Ridlah.
  10. Manna420

    Manna420 Networkin' Nut Member

    Hi guys. I am experiencing that my download from bittorent is now getting very unstable, getting high speed then dropping down to very low. Is there anything i could do. Thanks. I am still using the same build. Here it is:

    Tomato Firmware 1.28.0000 MIPSR2-092 K26 USB AIO
  11. shibby20

    shibby20 Network Guru Member

  12. Mowax

    Mowax Networkin' Nut Member

    when using torrents though you can never tell, could be people just "jumping ship" from the torrent, could be the fact that your ISP is throttling you? could be a that you have a version that has too many connections (I use Toastman just for the pure fact of when connecting to a torrent then if I stat getting more and more connections, above 2000 I think it is then the router thinks it's under a DDOS attack, or something like that and then shuts off access to the web)

    Any of the above ?

    Go to nvidia's web site and test download the 350 meg driver file, and maybe do some speed tests.

    are you trying to run the torrent hard wired or wireless?


    This is from a post on the board so thanks to the OP (Toastman)


    If your router becomes unstable, perhaps freezing or rebooting, apparently randomly, then it may have been asked to open too many connections, filling the connection tracking table and running the router low on memory. Often this can happen because poorly behaved applications (usually P2P clients) can attempt to open thousands of connections, mostly UDP, in a short space of time, just a few seconds. The router often does not record these "connection storms" in the logs, because it runs out of memory and crashes before it has time to do so.

    Obviously, there is a flaw in the firmware, which most definitely should never allow this situation to happen. Until such time as we can correct this situation, we must resort to some means of damage prevention and control. Setting the timeout value of TCP and especially UDP connections is necessary.

    Setting the number of allowed connections high (say 8192) makes the situation worse. In fact this number is almost never required. Most connections shown in the conntrack page will actually be old connections waiting to be timed out. Leaving the limit low, say 2000 to 3000 connections, gives the router more breathing space to act before it crashes.

    The following settings have been found to help limit the connection storm problem without too many side effects.
  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