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

Booted off network with full signal with WRT54G v6

Discussion in 'Cisco/Linksys Wireless Routers' started by StarFadedBlack, Jul 25, 2006.

  1. StarFadedBlack

    StarFadedBlack LI Guru Member

    I have a WRT54G v6 with DDwrtv23. The router is kicking my computer off the wireless connection and I have no idea why. The signal will be very good but the router I guess denies the request. I will be connected when I manually choose the connection and connect but about 2 minutes later I am booted and no longer connected, yet I can still see the signal in the visable networks and the signal is very good or excellent. :confused: I'm using WPA and filters I have on are:

    Block Anonymous Internet Requests
    Filter Multicast
    Filter IDENT (Port 113)

    Are these filters interfering? My computer is using a Dlink wireless card, just fyi. Thanks for the help!
     
  2. Toxic

    Toxic Administrator Staff Member

  3. Esquire

    Esquire Mesquire Staff Member Member

    Those settings you quoted are part of the router's SPI firewall settings so they don't interfere usually.

    Sounds like an encryption authentication issue.
    Is the adapter driver and wireless client software up to date?
    Is the WPA-PSK type in use compatible with that on the router (i.e., TKIP to TKIP, AES to AES) and entered correctly?
    Have you tried WEP or no wireless security at all and see if you still get the same problem?
     
  4. StarFadedBlack

    StarFadedBlack LI Guru Member

    Hey thanks for all the help. It seems that something was trying to connect to my old network (since i used to own a dlink before it died and I bought the WRT) and when it would do that, it would boot me off the new network so all I had to do was name the new network the exact same as the old one and the problem seemed to go away. I played COD2 off and on for 4 hours and the never lost the connection so I am assuming the problem is fixed. Again, thanks for all the suggestions!
     

Share This Page