Using v23, AIM keeps disconnecting?

Discussion in 'DD-WRT Firmware' started by lore, Dec 27, 2005.

  1. lore

    lore Network Guru Member

    I've been having problems with AIM these last few weeks on all of my WRT54g routers running v23 betas, and now the final release. I have hardware revisions 2.0, a 3.1, and 4.0. The 2.0 is running on a DSL line and the 3.1/4.0 are running on a fiber connection. The DSL line is PPPoE, and the fiber line has 1 static IP dedicated to the 4.0 router.

    AIM times out and dies all the time now without warning. The only way I know that it's died is 1) I can't IM anyone, or 2) it shows the reconnect dialog, which immediately lets it reconnect. I've seen this happen on both my laptop and my desktop, and I can't figure out what the cause is. I've turned QoS on and off to no avail.

    Has anyone else experienced this?
  2. _splat_

    _splat_ Network Guru Member

    how did you set the Timeout setting for tcp connections in the router setup ? If the timeout is set too low the router will interrupt the connetion if nothing was transfered.
    i dont use AIM, but i set my tcp timeout to 600sec aud udp to 8 sec and have no problems.

    maybe AIM has a "keep connection alive" setting ?
  3. lore

    lore Network Guru Member

    I was just thinking about those settings... I have it set to 4096/90/90 but I just changed it to 180/180. I originally set it to 90/90 because P2P programs were causing the router to freeze up.

    I'll keep an eye out on those settings... good suggestion.
  4. lore

    lore Network Guru Member

    Hm, I set the settings for 4096/600/180 and it didn't seem to make a difference. I'm still getting random disconnects here and there. Anyone else have a suggestion?
  5. gotamd

    gotamd Network Guru Member

    I too am noticing these random disconnects...not just in AIM, but also in IRC. It's very annoying. I forget what I have my timeout settings at, but I did lower them. I'll try raising them since I don't do (much) P2P.
  6. flexy

    flexy Network Guru Member

    might help. Read my post.

    I discover there is a "bug" or what you want to call it... the

    echo 172800 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established

    is very important since otherwise every default connection will timeout TOO SOON. (especially ftp, irc etc.)

    The default value is set to something like 1800 or 3600 which means that after 1800 secs every established TCP connection gets CLOSED. I mentioned that a few times already with no real response to this. The above line sets the tcp ESTABLISHED timeout to two days. (Default for other firmware/routers is 5 days btw.)

    Its NOT a solution to put this to "1800", doesnt make sense at all.
  7. crawdaddy

    crawdaddy Network Guru Member

    I am having the same problem, except that I'm running the stock firmware. I have DSL running through PPoE on a v3 router.
  8. pball3485

    pball3485 Network Guru Member

    Set your MTU manually.

    Cable: 1500
    DSL : 1492
  9. lore

    lore Network Guru Member

    How does this affect people who want to use P2P software? Is this a different setting than setting the TCP timeout settings that we can access via the GUI?
  10. Nimdae

    Nimdae Network Guru Member

    I noticed this problem myself and actually asked others if they were having problems with AIM, unknowingly that this is a problem with my router. This firmware has other problems so I think I'll be dropping it for now.
  11. gotamd

    gotamd Network Guru Member

    I fixed the problem by upping the TCP and UDP Timeout (via the GUI) to 300. That cleared both the IRC and AIM issues right up. I just had them set too low.
  12. phinn

    phinn Network Guru Member

    I too have this problem with IRC / AIM / WoW disconnects. This is the first time I tried a 3rd party firmware too.

    I am now using HyperWRT + tofu12 and its rock solid and everything runs good.

    I love the DD-WRT v23 interface and would like to try it again if this bug gets fixed.

    Also I have some wierd problems with static DHCP and I'm not even sure how to describe it but it locks up sometimes and if I reboot my machine it won't get an IP address.

    I'd love for this stuff to be resolved but I'll stick with Tofu until then
  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