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

Aim frequently disconnects. WRT54G v2.2 w/ thor14

Discussion in 'HyperWRT Firmware' started by zachariah, Mar 12, 2006.

  1. zachariah

    zachariah Network Guru Member

    Ever since I upgraded to the firmware in my signature, aim disconnects very frequently. This gets annoying for obvious reasons. Can someone with adequate knowledge assist me with settings to fix this little annoyance?
     
  2. Acid-drop

    Acid-drop Network Guru Member

    I have the same problem with thibor 14.
    (it's not only aim or msn, everything disconnect every 5-10 min)

    Since I'm back with tofu 13c, there is no problem anymore.

    The config staid the same.
    I have WRT54G v2
     
  3. Toxic

    Toxic Administrator Staff Member

    a quote from http://www.thibor.co.uk/#upgrade

    Before proceeding, please verify that your router is a Linksys WRT54GS v1, v2, v3, v4 (not v5), or a WRT54GL. This is not for the WRT54G, WRT54GX, etc.

    as it says... it doesn't support YOUR version of router.
     
  4. Acid-drop

    Acid-drop Network Guru Member

    That's clear.
    If i wanna get upgrade, i must go for thibor.
    I'd rather have an upgrade of tofu, but he decided to stop.
     
  5. zachariah

    zachariah Network Guru Member

    toxic: thanks for pointing that out, I've seen it before, but there has been many other people who has sucessfully uprgaded to thibor14 with my router and claimed it worked well.

    acid-drop: so are you still using thibor14 and figured out a remedy for those disconnections? or did you revert back to tofu13c? to do this you simply upgrade firmware to 13c from thibor14 right? I've heard so many scary stories of a router bricking. -.-
     
  6. Acid-drop

    Acid-drop Network Guru Member

    I had to go back to tofu 13c
    I simply did a firmware upgrade from thibor 14

    the config always staid the same
     
  7. zachariah

    zachariah Network Guru Member

    acid: ok wish me luck, I'm going to downgrade to tofu13c and hope nothing bad happens. I really wished there was settings to fix the disconnections instead of downgrading with the risk of bricking the router. I'm inexperienced with reviving dead things :eek:. I like how the internet connection doesn't freeze up for everyone else on the network when someone torrents for a while, it's just now, things randomly disc :(.
     
  8. Acid-drop

    Acid-drop Network Guru Member

    I'm a bit supprised that we are the only 2 people who have problems.

    It's the worse situation for thibor, he'll not be able to find the problem easily.
     
  9. zachariah

    zachariah Network Guru Member

  10. Thibor

    Thibor Super Moderator Staff Member Member

    you're quite correct. as i don't have the problem and/or be able to reproduce it, i can't fix it. on the other hand, since you are "G" owners and i have already stated that i won't support it, as i don't have G routers, only GS's; i won't be investigating it. try dropping back to tofu13c and see if it helps with your problems
     
  11. Thibor

    Thibor Super Moderator Staff Member Member

    also, there is also the consideration that you did not erase your nvrams after flashing. this is the cause of many odd and unreproducable issues. if you are changing from one fw type to another, ie sveasoft to hyperwrt, or dd-wrt to hyperwrt, or even tofu to thibor, you should always erase the nvram and restore the firmware defaults afterwards.
     
  12. Acid-drop

    Acid-drop Network Guru Member

    dropping back to tofu13c definitely helps :)
    but i'm sad i'll not be able to get new improvements in the future.

    Since there are more owner of the G than of the GS, I also guess i'm not the only one sad here ;)

    We'll see in the future what tofu decide, and if it's possible to make a firmware that officialy support both routeur.
     
  13. zachariah

    zachariah Network Guru Member

    i dropped back to tofu13c, I still get those frequent aim disconnections, and potentially other programs too if I would use them.
     
  14. ofbarea

    ofbarea Network Guru Member

    Did you erased the NVRAM?
     
  15. zachariah

    zachariah Network Guru Member

    Yes I did, I never missed that step.

    edit: once in a while, I would get stability, but never a day goes by without the router disconnecting at 11pm sharp.
     
  16. LAGMonkey

    LAGMonkey Network Guru Member

    Very strange, ive got a Gv 2.2 running Thibor 14 and so far ive had no problems with it.
    I think that the router status page dosent realy work but it dosent bother me as i still get the speed im looking for.
    Load on the router is low and the L7 QoS on P2P applications does its job.

    My startup script is as follows if it helps,
    echo 2048 > /proc/sys/net/ipv4/ip_conntrack_max
    echo 2048 > /proc/sys/net/ipv4/tcp_max_orphans
    echo 512 > /proc/sys/kernel/threads-max
    echo 4096 > /proc/sys/fs/file-max
    echo 0 > /proc/sys/net/ipv4/tcp_orphan_retries
    echo 1 > /proc/sys/net/ipv4/tcp_abort_on_overflow
    echo "60 180" > /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
    echo "300 600 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts
    echo "50 500 0 0 200 1000 60 20 0" > /proc/sys/vm/bdflush
    echo "0 0" > /proc/sys/vm/pagetable_cache

    EDIT:: Router uptime has been over 6 days and ive got 8 clients hammering the router at certain points every day.
     
  17. zachariah

    zachariah Network Guru Member

    I appreciate your response, but I do not understand any line of code presented. Can you explain what each one does, variables involved, and how you came about figuring out the best number for each variable. Thanks in advance.
     
  18. LAGMonkey

    LAGMonkey Network Guru Member

    The Code presented above is put into the Startup script (edit startup in the administration tap.)

    To be fair, for P2P problems all you realy need to put into is...

    echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
    echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses

    as most of the stuff i have in my startup scrip is actually unneccisary (ive been playing about with the router)
    The explaination is simple with these two settings as they are ether running (echo 1 ) or no (echo 0 ).

    Another thing is that you might want to increase the "estrablished state timeout" (again located in the management tab on the router) but i dont have a problem with a setting of 600.

    Im still trying to find the best settings for my own router (ive recently had to change to WPA2 as the WPA was dropping my wireless clients) but i hope that these help.
     
  19. kiskakas

    kiskakas Network Guru Member

    zachariah,acid-drop,

    do you use azereus? because my friend's WRT54G with thibor14 do the same problem, but he found, that it's a simple azereus attack,from the internet. He changed azereus's port and turn of upnp on wrt, and no disconnects.. :thumbup:
     
  20. Acid-drop

    Acid-drop Network Guru Member

    very good question

    my bro might have runned azureus during the time i was testing thibor14. It is not impossible.
    that's with a standard port redirect, no upnp here.

    But next to that, i also have all pnp features activated.

    If there is a bug somewhere, it can be it.
     
  21. AnimeLover1985

    AnimeLover1985 Network Guru Member

    MTU: needs to be at 1400 for AIM to work correctly. When you use the hardware settings it is set to 1500... I hope this will help you with AIM being disconnected alot...
     
  22. zachariah

    zachariah Network Guru Member

    I don't think I feel confident enough that these changes will help the stability of my WRT54G v2.2 router to go back to thor14. I still appreciate all the responses I've recieved regarding this matter. I will look back to this thread as a reference in case I do. Thanks all, especially LAGmonkey.
     
  23. ontguy

    ontguy Network Guru Member

    hi,

    I just thought I would add this; that I have countered the same connection drops after doing the upgrade and went back to tofu13c.

    I have a WRT54G v4
     
  24. zachariah

    zachariah Network Guru Member

    Cheers to Thor15

    Edit: "Connection Uptime : 3 days, 05:36:05"

    I'm proud to say that Firmware Version: v4.71.1, Hyperwrt 2.1b1 + Thibor15 has remedied my disconnection problems in addition to providing all of those useful features. Thanks Thibor, keep up the good work :).
     

Share This Page