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

Routing issue with RV082

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by TheEricHarris, Apr 10, 2008.

  1. TheEricHarris

    TheEricHarris Addicted to LI Member

    Hi all,

    I'm really frustrated with this, so hopefully someone with a clear head can help me figure this out.

    My network:

    [ISP Router]------[Linksys VPN-Public IP/192.168.157.214]---------[Layer 3 switch with static routes for 3 VLANs (192.168.157.0/24, 172.30.10.0/24, 172.30.20.0/24)]

    I have a seperate firewall (with different public IP) where all inbound/outbound Internet traffic for my LAN users goes through.

    VPN clients can connect to the RV082 remotely. They can ping the device (192.168.157.214) but CANNOT ping anything else on my LAN.

    I have setup Working Mode as "Router" and put static routes in (192.168.157.0/24-192.168.157.254, 172.30.20.0/24-172.30.30.1, etc.).

    I can get to the 192.168.157.214 (the RV082) from each of my VLANs on the inside with no issues. When I try to ping anything from the RV082, it fails. So devices on my LAN can get to it, but the RV082 can't get back. It's like it doesn't know to contact 192.168.157.254 for it's gateway.

    Please help
     
  2. TheEricHarris

    TheEricHarris Addicted to LI Member

    UPDATE


    I fixed the static routing (in Router mode). From the Diagnostic menu on the RV082, I can ping any device on my internal network and the Internet.

    But when a remote client (Windows XP using the Linksys QuickVPN client) connects, he can only ping the RV082's IP (192.168.157.214). He can't ping anything else.

    Any ideas? I'm so frustrated with this.

    I also don't understand how the RV082 gives out IP addresses to VPN clients. I don't see anything like a Gateway/DNS from my internal network. How is this supposed to work? When I used other VPN solutions, like Cisco, the client obtains all the IP info from a DHCP server. I have a Windows 2003 DHCP server for my LAN. Maybe this part of my issue?
     

Share This Page