Another problem with WRV54g

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by EyeWallInc, May 5, 2006.

  1. EyeWallInc

    EyeWallInc Network Guru Member

    I just set up a WRV54g for a client who is using a DSL connection, first I set up my laptop to the DSL modem and got to the internet fine, but then when I changed the netopia (ISP provided modem/router) to "bridging mode and added the Linksys I can't get out. I can get to the Linksys from a LAN port so everything is okay there, on the status screen I see the WAN IP address, default gateway and ISP's DNS servers, so that seems okay. However, I cannot ping from the client station to the net, not able browse or resolve DNS (I actually had to manually configure the DNS as for some reason it wasn't being passed to the client from the WRV54g). I tried to ping the listed DNS servers and the default gateway from the WRV54g and get nothing. It is connected and the ISP sees me authenticated and connected. Any ideas?

    I have tired, for grims, to change from gateway to router on the Linksys but it won't let me. Not sure if that's even allowable in this PPPOE config or not.

  2. EyeWallInc

    EyeWallInc Network Guru Member

    Ahhh ooops. The WRV54g is running v2.36, Linksys has 2.37 available.
  3. DocLarge

    DocLarge Super Moderator Staff Member Member

    Make sure your xDSL connection to the internet is either ethernet (PPPOE) and "not" PPPoA. The WRV is ethernet technology and not ATM technology. So, when you bridge your modem, you're basically telling the router to translate the connection, so if you're on PPPOE, the wrv can do that, but not PPPoA...

  4. EyeWallInc

    EyeWallInc Network Guru Member

    thanks for the reply, it is PPPOE. Next question, can I elminate the Netopia and connect the DSL line into the WRV54g or does it need a DSL modem in front of it?

  5. DocLarge

    DocLarge Super Moderator Staff Member Member

    You need a modem of some sort because the WRV54G is strictly a "router" only device.

    The last official firmware release (2.37) is broken. Your IPSEC VPN server will not synchronize the "authentication" algorithm in phase I or II with this firmware. It's best to use Beta Firmware 2.37.13 or 2.39.

    Dumb question: you do have the bridged modem connected to the WRV via the WRV's WAN port, I assume? If so, that "should" do it, provided the WRV is able to authenticate the packet information.

    If you can't get this to work, my next suggestion would be finding a "modem only" device as opposed of this modem/router combo gear that's showing up all over the place.

    Where are you located?

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice