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

slow to connect to wireless network

Discussion in 'Tomato Firmware' started by nxmehta, Apr 21, 2007.

  1. nxmehta

    nxmehta LI Guru Member

    I'm a new user to tomato and am experiencing some issues with wireless connectivity. I tried to search the forum for similar issues but didn't find any.

    I installed tomato v1.06 on a Linksys WRT54GS v1, and when I connect to the wireless network (WPA with TKIP/AES), windows takes a long time to acquire a network address. After a long delay I get "limited or no connectivity", and have to repair the connection. After which I quickly connect and get an IP address. This has been verified with both my laptop and another laptop (both running Windows XP SP2 with Intel PRO Wireless 2200BG adapters). I also installed tomato on another, separate router (Linksys WRT54G v4) and am having the exact same problem with both laptops.

    Is anyone else seeing the same issues? Is there some delay setting or something in the firmware that I should change to resolve this?

    Let me know if there's any other information that I need to provide, and thanks for any help.
     
  2. ntest7

    ntest7 Network Guru Member

  3. shadowmonk

    shadowmonk LI Guru Member

    I've got the same issue, however, my laptop has a broadcom wireless card. I've changed settings to AES only, G only, upped my transmit to 84mw at the router, "installed" some reflectors on the antennas, and followed suggestions in other threads but it still does as nxmehta above describes.

    I've checked for driver updates, played with setting based on the guide here on the forums, and still no dice.

    I moved off of thibor and like this firmware enough that I will still use it even if this is just a weird issue, just would like to know if there is a workaround. My router is a WRT54G v4, same as nxmehta's second attempt.

    Update: I did a clear of the NVRAM and took off static dhcp, it now seems to work fine on the wireless dhcp
     
  4. nxmehta

    nxmehta LI Guru Member

    Upgraded my drivers and am seeing the same behavior. I guess I'll try turning off the static DHCP (although that's the main feature that I need)...
     
  5. shadowmonk

    shadowmonk LI Guru Member

    I kinda liked the static dhcp, mainly because of bittorrent and not trusting upnp. But with upnp working I don't really see a need for static, even thoguh it's nice to know what an ipaddress will be for file transfers w/o needing to look at the router device list.
     
  6. nxmehta

    nxmehta LI Guru Member

    I upgraded my wireless drivers to the newest version, installed tomato 1.07, and disabled static DCHP. I'm still seeing this issue. Does anyone have the same problem?
     
  7. nxmehta

    nxmehta LI Guru Member

    Another followup: here is Tomato's logfile for when I connect:

    Jul 3 09:34:04 Silverlake syslog.info -- MARK --
    Jul 3 09:37:40 Silverlake daemon.info dnsmasq[315]: DHCPDISCOVER(br0) 00:0e:35:17:90:02
    Jul 3 09:37:40 Silverlake daemon.info dnsmasq[315]: DHCPOFFER(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:37:44 Silverlake daemon.info dnsmasq[315]: DHCPDISCOVER(br0) 00:0e:35:17:90:02
    Jul 3 09:37:44 Silverlake daemon.info dnsmasq[315]: DHCPOFFER(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:37:53 Silverlake daemon.info dnsmasq[315]: DHCPDISCOVER(br0) 00:0e:35:17:90:02
    Jul 3 09:37:53 Silverlake daemon.info dnsmasq[315]: DHCPOFFER(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:38:10 Silverlake daemon.info dnsmasq[315]: DHCPDISCOVER(br0) 00:0e:35:17:90:02
    Jul 3 09:38:10 Silverlake daemon.info dnsmasq[315]: DHCPOFFER(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:38:46 Silverlake daemon.info dnsmasq[315]: DHCPDISCOVER(br0) 00:0e:35:17:90:02
    Jul 3 09:38:46 Silverlake daemon.info dnsmasq[315]: DHCPOFFER(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:38:46 Silverlake daemon.info dnsmasq[315]: DHCPREQUEST(br0) 192.168.10.10 00:0e:35:17:90:02
    Jul 3 09:38:46 Silverlake daemon.info dnsmasq[315]: DHCPACK(br0) 192.168.10.10 00:0e:35:17:90:02 mesaana

    Should it take a full minute for my pc to get an address from the DCHP server? Might that be the problem here? Seems like a long time. Maybe there is a way to speed this up?
     

Share This Page