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

Tomato WLAN disconnections with Intel 2200BG [SOLVED]

Discussion in 'Tomato Firmware' started by psychowood, Mar 16, 2007.

  1. psychowood

    psychowood LI Guru Member

    I'm still not sure about the strange behaviour I'm having with my WLAN (continuous disconnections, every now and then, without apparent cause), the only things I can say for sure is that with 1.04 I've ever had this problem neither once single time, that neighbor wireless network, mi hardware, my software, anything has changed. I'm on a Centrino platform (with Intel2200 chipset), and even my Nintendo DS seems to experience problems connecting.
    One thing I've noticed is that when the connection is lost, my GLv1.1 does not appear anymore, for some seconds, in the reachable wireless network list.

    I don't want to blame 1.05 yet, I'm just asking if someone else is having this problem. I'm going to revert back to 1.04 and see if the problem stays.

    Btw, my network works has a simple WEP 128bit encryption and MAC access list.

    Solved with 1.06 and Intel v9.0.0.60 driver


    • Upgraded WRT54GLv1.1 to Tomato 1.06
    • Removed every piece of Intel driver and software I had in my PC
    • Installed original driver version, v9.0.0.60 (hp oem here)
    • Left untouched default settings (trasmit power, etc etc)
    • Set a static IP to the card, avoiding DHCP (this point should not be needed, I did it just because I was passing by ;) )
     
  2. psychowood

    psychowood LI Guru Member

    Update: before reverting, I tried rebooting the router to see if it could somewhat help, but just after the reboot, my PC disconnected 3 times in a row.

    Now I'm 1.04.0944, 20mins of stable connection so far, never disconnected, and my WLAN seems more responsive, too (VNC and SSH to my Linux Box lags lot less).
     
  3. roadkill

    roadkill Super Moderator Staff Member Member

    from what I gather 1.05 won't be here for long it has some issues...
    wait a couple of weeks
     
  4. petepat

    petepat Guest

    Back to 1.04 for me too.
     
  5. johnhau

    johnhau LI Guru Member

    Same problem

    I had the same problem, however it was solved after choosing
    "Erase all data in NVRAM memory(thorough)" from Administration->Configuration menu. Afterwords I changed all settings back again. No disconnections afterwords.
     
  6. digitalgeek

    digitalgeek Network Guru Member

    Curious what you guys are doing... my wan is stable (so it appears) I have never had any problems... upnp dops once in a while on my laptop(not like with Thibor, I don't need to reboot it comes back up on its own)... but everything apears to be working wireless/wds is fine too...

    I would suggest a nvram clear and reconfigure...
     
  7. psychowood

    psychowood LI Guru Member

    @johnhau: I'll try that, but don't understand why it should bother, since I upgraded from 1.04 to 1.05, not from a different firmware. I've sent my nvram show to Jon, probably he'll figure out if there is something wrong in them.

    Up to the firmware upgrade (and after the downgrade :) ) my router has always been perfectly stable, never had a single problem, so I was a bit curious about where the problem could lie in, that's all :)
     
  8. psychowood

    psychowood LI Guru Member

    Lol, I just realized I always said WAN meaning Wireless Network, sorry for the messup ^^
     
  9. lengo lad

    lengo lad LI Guru Member

    There's LAN, WAN, and I think "wireless network" would be WLAN (wireless local area network), right?
     
  10. psychowood

    psychowood LI Guru Member

    WLAN, exactly.
     
  11. digitalgeek

    digitalgeek Network Guru Member

    WAN... LAN... WLAN... all are stable, seems more like a config error... although it used to work? have you tried a clear nvram? restoring from a backup config would solve the problem, cause if there was an error in the config you would just restore the same error.
     
  12. johnhau

    johnhau LI Guru Member

    Btw. I also got the disconnection problems after upgrading from 1.04 to 1.05. The disconnection problems only appeared on one of my three computers. It was a Compac Evo 800c with integrated 802.11b networkcard. Now it is stable again.
     
  13. psychowood

    psychowood LI Guru Member

    Yes, used to, and now is working again with 1.04.

    Not yet, have a rather full config (Qos, Static DHCP, NAT, ... ), don't have the head to redo that manually now :)
    Perhaps later.

    You meant not solve, right?
    Btw I restored the backup config both after upgrading to 1.05 and after downgrading.

    Probably there is an unlucky parameter of 1.04 not liked by the 1.05, since johnhau solved the same problem with a clear nvram.
     
  14. digitalgeek

    digitalgeek Network Guru Member

    I not sure about this because I did a straight upgrade... with any trouble and I have a pretty full config...

    PPPoE, QOS[added medium and high categories], Port Forwading, WDS, WLan Filter, Static DHCP... not something you want to redo manual to often.

    You might want to try upgrade to 1.05 and manual config and see if it solves the problem. (I understand it is a lot of work, but sometimes a clear nvram solves a lot of problems)
     
  15. psychowood

    psychowood LI Guru Member

    That's basically the very same config of mine, except WDS :)

    I know, that's the next planned step, but since now I lack time, I'd stay with 1.04 till my clock stops for a while :wink:
     
  16. Riotblade

    Riotblade Network Guru Member

    Well, I'm on the 1.02 firmware and I constantly receive the exact same problem. I then found out that it was conntrack and my connections somehow reaching 4096(!). After that, all wireless clients would disconnect (wired stay connected), network disappears or won't allow you to connect, and will have to wait about 10 minutes for it to fully stabilize again. I managed to tweak my settings to make it stable. I'm wondering if upgrading might help?
     
  17. der_Kief

    der_Kief Super Moderator Staff Member Member

    Hi,
    if you are on the same problem, upgrading wont help ! So this must be a configuration problem !?

    der_Kief
     
  18. psychowood

    psychowood LI Guru Member

    I checked my connections while it was disconnecting (was the 1st thing that came up in my mind, actually :biggrin: ) but nothing special in there. Your seems more a problem of the wireless adapter driver, imho.
    Have you tried cleaning nvram as someone stated before?
     
  19. priit

    priit LI Guru Member

    Started randomly dropping connection and then disappearing at all since upgrading to 1.05 and now it seems to be doing the same with other firmwares too! I've cleared NVRAM a dozen of times now, but to no avail, it seems...

    I have a WRT54GL v1.1 and using a 2200BG to connect to it.
     
  20. psychowood

    psychowood LI Guru Member

    You are making me fear trying 1.05 again, I think I'll stop on .04 for now. :eyebrow:
    Btw, you did a thorough erase, didn't you?

    Exactly the very same setup of mine. I'm even more thinking of some kind of incompatibility, now.
     
  21. priit

    priit LI Guru Member

    Of course.

    BTW, it's doing the same with my GF's laptop, she has some Broadcom card.
     
  22. psychowood

    psychowood LI Guru Member

    Another perhaps stupid question :) (jut trying to have a base to work on, want to be sure I'm not missing anything): after clearing nvram, you re-setup the router manually and not by restoring a backup, right? Otherwise you'd end up restoring the bug, too ^^
     
  23. pharma

    pharma Network Guru Member

    I don't think it's the router or the firmware. If you do a forum search at Linksysinfo.org you'll see people who have had disconnect issues with the Intel 2200BG regardless of what firmware they use. I remember seeing quite a few in the Wireless Adapter forum awhile ago -- most of those folks were trying to find a good driver upgrade. It might be a good test to try another wireless adapter even if it's older.

    Good luck!

    Pharma
     
  24. psychowood

    psychowood LI Guru Member

    Well, that's inconfutable that the problem lies in the adapter, mostly because it is the only one that is giving problems :biggrin: but it's also true that, at least for me, I have absolutely no problem with 1.04, while 1.05 is unusable, so there is also something (not necessarly broken, just incompatible) in the firmware, too..

    Thanks ^^
     
  25. psychowood

    psychowood LI Guru Member

    Another update: yesterday I updated my 2200BG (bad bad choice.. :frown: ) drivers and started to have disconnection problems even with 1.04 :oops:

    After trying many drivers (reverting to the older one would not help, probably other files were overwritten), now my setup seems stable, so I want to share, just in case someone wants to try..

    • Upgraded WRT54GLv1.1 to Tomato 1.06
    • Removed every piece of Intel driver and software I had in my PC
    • Installed original driver version, v9.0.0.60
    • Left untouched default settings (trasmit power, etc etc)
    • Set a static IP to the card, avoiding DHCP (this point should not be needed, I did it just because I was passing by ;) )

    If someone wants to try the driver, I can upload it somewhere (I'm not sure if can be downloaded from the official Intel page, since is rather old).

    [EDIT]Driver found here, it's a HP oem one, but it should work for others too[/EDIT]
     
  26. fastpakr

    fastpakr Network Guru Member

    Interesting, I went to a remote site last week and installed 1.05 in a wireless ethernet bridge configuration and have had issues with one leg of the link out constantly since Wednesday. If I can flash the firmware to 1.06 remotely, will an NVRAM clear be required? I can certainly update the firmware from here, but if I have to reset it to default settings then it becomes vastly more complicated to do remotely.
     
  27. psychowood

    psychowood LI Guru Member

    I haven't cleared NVRAM :)
    A reboot may be required, tho (more than once if you have jffs: disable jffs -> reboot -> upgrade -> enable jffs -> reboot).
     
  28. fastpakr

    fastpakr Network Guru Member

    I don't mind rebooting, it's just throwing it onto a different subnet that would make things 'interesting'. Thanks for the info!
     
  29. priit

    priit LI Guru Member

    So... what was fixed 1.06 that worked for you guys? As I stated before, a Broadcom card, which was right next to me had the *exact* same problems...
     
  30. psychowood

    psychowood LI Guru Member

    Oh, I didn't notice that broadcom, sorry :frown:
    I thought the the problem was Intel-only.. my fix was using the older driver, nothing more, nothing less.
     
  31. fastpakr

    fastpakr Network Guru Member

    This all has me very curious now, since I'm using Buffalo WHR-HP-G54 equipment for bridging. It may not be a 1.05 related issue, but this was the first time I'd seen symptoms like this in Tomato.
     
  32. pharma

    pharma Network Guru Member

    Did you try updating your drivers? I believe Broadcom updated their drivers recently ... perhaps you should uninstall your wireless drivers, reinstall and keep the default wireless driver settings and see how that goes. :)

    BTW: I have no problems with my Linksys wireless adapter (Broadcom chipset).
     
  33. priit

    priit LI Guru Member

    Trying to upgrade to 1.06 now... let's see how that goes.

    [EDIT]Okay... half an hour and not a single drop. I guess 1.05 was b0rked then.[/EDIT]
     
  34. Damian_S

    Damian_S Networkin' Nut Member

    I had the same problem and I have Intel 5300AGN.

    I noticed under adapter settings that the channel width was set at 20Mhz and the default setting is set at 40Mhz in Tomato.

    I changed the settings in Tomato and now everything seems to be more stable.

    I do not know if that is the fix, but I will keep you posted.
     
  35. Damian_S

    Damian_S Networkin' Nut Member

    Well, I just googled channel width and it seems to be related to speed. Does anyone knows if this has anything to do with the disconnection issues we are having?
     

Share This Page