Hi all. I had a comp. savvy person flash my extra wireless router (WRT54G v8) with DD-WRT I think so I could use it in other rooms, like a bridge I guess, but I'm basically just using it instead of a wireless adapter. It's been cable connected to my HTPC for a while working great, receiving wirelessly from my main router (Verizon wireless router). Suddenly it won't connect to internet anymore. I also tried it on other pc's in other rooms where I tested it before I hooked up the HTPC and it wont get Internet there anymore either so I know the HTPC is not the problem.
I'm wondering if it could have something to do with changing my Verizon router. Verizon router stopped working a while back, tech suport was no help, so they sent me a new one. The new one was doa (wouldn't even power) and while switching them I found a reset button on the first one which fixed it (so much for tech suport). So I'm still using my original Verizon router now, all pc's work fine, but since then I can't get online with the Linksys. Coincidence?
I build my own pc's but I'm a basic user with limited geek skills so I need help on these things. The lighting on the front doesn't look abnormal, (Lt to Rt) power light on, DMZ light off, WLAN light on, then 4 ethernet and 1 internet lights off except for the one I plug ethernet cable into from the pc. Any Ideas here?

Dani AI

Generated

Brief addendum based on 's followup: a Linksys WRT54G v8 running DD‑WRT commonly “loses Internet” after the main router is changed because one or more bridge/AP settings no longer match the primary router. The checklist and quick recovery steps below target the exact, repeatable things that break in that scenario.

Checklist of the most common causes

  • Wireless mode mismatch: Client, Client Bridge, Repeater Bridge and AP modes behave differently (some modes do not accept wireless clients or only forward wired ports). Verify which mode was used and switch to the one that matches the original setup. (blog.flashrouters.com)
  • SSID/security mismatch: SSID, WPA/WPA2 selection and cipher (AES vs TKIP) must match exactly on both ends; any change will prevent association. (deviwiki.com)
  • IP/DHCP conflicts: the secondary must have a unique LAN IP on the main subnet and the DD‑WRT DHCP server should be disabled when acting as a bridge; identical LAN IPs (both 192.168.1.1, for example) or overlapping DHCP ranges will break connectivity. (howtogeek.com)
  • Access restrictions and radio settings: check MAC filtering on the primary, wireless channel and mode (b/g) compatibility. (deviwiki.com)

Minimal recovery procedure (fast)

  1. Connect a PC to a WRT54G LAN port and log into the DD‑WRT GUI.
  2. Set the WRT LAN IP to an unused address in the main router’s subnet (outside its DHCP range) and disable WRT DHCP if using bridge/repeater modes. (howtogeek.com)
  3. In Wireless settings choose the original mode (Client/Client Bridge or Repeater Bridge), enter the exact SSID and security settings, save and reboot both routers. (blog.flashrouters.com)
  4. If association still fails, try a factory reset and reconfigure; if firmware/build issues are suspected (WRT54G v8 has limited flash and historically needs specific DD‑WRT builds), reflash with a known v8-compatible image and restore settings from scratch. (dotnetworkaholic.com)

These targeted checks—mode, SSID/security, LAN IP/DHCP, and access restrictions—are the usual culprits and explain why the router worked before but stopped after the main router was changed.

Found the answers on another website. My suspisions were correct, somehow the settings got messed up around the same time I worked on my main router and thus my linksys stopped funtioning.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.