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

WRV54G - Disappointing - Not even good as a WAP - Now what?

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by GuyllFyre, May 17, 2005.

  1. GuyllFyre

    GuyllFyre Network Guru Member

    OK, I bought one of these abominations when they were relatively new because I needed a device that would handle router, VPN endpoint, and wireless access point with WPA.

    I spent a couple of weeks trying to get it to connect to my work VPN as an endpoint with a SonicWall SOHO3 and had no luck. Did the usual, reset, flash the firmware, try again...

    I couldn't get it to work, so I turned around, took a spare PC and made a SmoothWall Express 2.0 box and it connects to the VPN solid, simple, and fast. It also provides me with firewall with SPI and IDS.

    While it doesn't handle the wireless, I took basically scraps and free software and made a better product. It never reboots for no reason, it has more than enough throughput for my needs, and it was simple to make.

    This is highly dissapointing since I spent over $140 on this damned WRV54G and it's useless. The wireless doesn't even work properly!

    I've got it set up as a WAP and it randomly reboots for no reason. I went into my home-office this morning and it was making a high-pitch whine and then rebooted.

    So...now what?

    I can't get my money back for it. LinkSys support is useless...

    What WAP should I get to replace the WRV54G?

    I'd use the SmoothWall but it does not yet support wireless network cards.

    It's not like I don't do this for a living. I'm not the smartest guy in the world but I have a lot of experience in setting up basic networks. I've been doing IT work since I was 15 and pulled my first PC apart.

    I didn't think this was going to be this hard but it seems like many people are having similar problems with this unit, so it can't be just me.

    Are all the WRV54G users gathering together and throwing the units through the Cisco Systems front windows?

    Will we ever see some sort of positive results with this unit or should I just give up?

    I have been using LinkSys stuff for years. They used to be pretty consistent at getting an easy to use product out that works. While I didn't always have good luck with the reliability (I had a few failures of thier equipment) I normally could set one up in minutes and have it work.

    The LinkSys BEFSR11 and BEFSR41 were the first two routers that I could always reliably get a VPN tunnel to pass through. I couldn't even get a PASS THROUGH tunnel through the WRV54G.

    I literally spent four hours straight one day trying to get the WRV54G to either allow a tunnel to pass through or have it establish one of it's own.

    I literally spent 15 minutes setting up the SmoothWall and it was working. I had a stable, established, point to point IPSEC VPN tunnel immediately after finishing entering the values in the fileds and clicking "restart."

    Sorry to ramble on so much but I'm so frustrated with this product and I seem to have found people who understand.

    Any ideas?

    Thanks,

    -S
     
  2. Guyfromhe

    Guyfromhe Network Guru Member

    i've been using my WRT54G's for years now as an ap with no trouble though some people are having lots of issues with them randomly restarting... I have 2 v2.0's and I can't reprodouce any problems on them they both run perfectly.
     
  3. DocLarge

    DocLarge Super Moderator Staff Member Member

    Since you were 15, eh? So, how have things changed in the last year or so as a 16 year old?? :) Forgive me, the door was open on that one...

    Here's a link to some infor already posted and it's working in all forums for those who've tried it.

    Upgrade to 2.38 if you have't already done so...

    http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=5173

    Doc
     
  4. GuyllFyre

    GuyllFyre Network Guru Member

    Heh. :)

    Actually, I'm 33 now. Been doing this for a while. This is one of the first pieces of hardware to completely frustrate me.

    I'll check out the updated firmware, thanks!

    -S
     
  5. billpoly

    billpoly Guest

    2.38 firmware

    I've been having a hell of a time getting the WRV54G to work consistently. At home, I set it up as a single device to replace a (failed) SonicWALL SOHO3 acting as DHCP server, firewall, etc. and a Microsoft MN-700 acting as an AP.

    I set up the WRV54G and got it working as both a wireless AP and DHCP, set it up no problem. I then found that it wouldn't route out to my Internet connection. I checked with my ISP to make sure they had my outside interface MAC registered - no problems. No matter what I did it would not route to the Internet. I flashed it to 2.37 - still nada. Then I took the same router - no changes - into my office and it routed perfectly when using an office LAN connection as the "Internet" on the router.

    Frustrated, I flashed the WRV54G to 2.38. Now it is completely dead - the "Internet" status light is orange and it won't route traffic, act as a DHCP server - absolute zero. I flashed the device from a wired connection and the upgrade appeared to go through smoothly.

    I think I'm going to pull an "Office Space" on this thing. It's taken up too much of my life.
     
  6. DocLarge

    DocLarge Super Moderator Staff Member Member

    Cripes,

    what are you guys doing out there?!?!?! :) :)

    I've flashed my WRV54G 5 or 6 times in the last two months testing firmware versions and have "NEVER" bricked it once!!

    Here's a link I just found to "de-brick" your router so you can start again. I'm running 2.38 also (for the third time):

    http://www.dslreports.com/forum/remark,8925312

    If you can get it running and run into the same problem again, try doing both of these two commands from the command prompt (in no particular order):

    1) nbtstat -R (clears remote cache)
    2) ipconfig /flushdns (clears dns tables)

    Obviously, it "was" working when you took it to the office prior your "flashdance" session. The issue just may be how it was negotiating your home connection, hence not getting the same type of response when you put it on line versus at your job.

    Apparently when you connected it to your job network, it was able to interprete the routing tables and received packets more efficiently being your job most likely has a better backbone than your home network, so, again, the router was working.

    See if the above information helps you get back into the game and then see if the info from the link below is of any use to you:

    http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=5173

    Doc
     
  7. GuyllFyre

    GuyllFyre Network Guru Member

    Heh, I've only bricked a router once. Was able to get it back by resetting it and reflashing according to a FAQ. He should be able to get it back.

    I flashed mine and was immediately annoyed by the fact that it reset all my config and doesn't accept the backup I made. I ended up flashing back to 2.37 and restoring the config until I write it all down.

    Really, this router is more hassle than it's worth. I think I'll flash it and sell it or something...probably pick up a WAP.

    What WAP is good?

    Thanks,

    -S
     

Share This Page