Routing between two BEFVP41

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by clicker666, Jun 26, 2006.

  1. clicker666

    clicker666 LI Guru Member

    I have two BEFVP41 units, connected via a VPN. For some reason they don't seem to discover their own routes.

    I've got unit a, at WAN (example) with a LAN address of, and a subnet of

    I've got unit b, at WAN with a LAN address of, and a subnet of

    On their own, the two units cannot ping their respective LAN sides across the VPN. ie - when connected via VPN cannot ping

    However, when I add route add mask from a machine in the group, I can then ping the router easily, and conversely, if I add route add mask to a machine on the other side, they can ping the router. I tried some static routes in the units, without success.

    I tried Googling up some routing info for these routers, but really couldn't find anything useful. I tried calling Linksys, and after an hour they told me they had no phone people that new anything about routing, and to send an email to support. Still waiting...

    I am sure that *someone* on these boards knows how to add a static route to the units. I find it difficult to believe I would manually have to add routes to every machine in my network since the *router* couldn't do it. :eek:
  2. clicker666

    clicker666 LI Guru Member

    Just to add - from my other thread, I managed to setup SSH Sentinel to connect to the router, and could ping the far end of the tunnel, but no farther. I was only able to hit the far end of the tunnel by entering a manual route.

    I'm sure there's something I'm just missing here, aside from a chromosome. :thumb:
  3. magwai

    magwai Guest

    I had the same problem and I disabled the tunnels and set them up on different tunnels and it started working. I have no idea why but it worked.
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    A screenshot of what you have would help :)
  5. ifican

    ifican Network Guru Member

    From a pure routing standpoint adding the route to the machine should make no difference at all unless the lan ip on the router is not the default gateway for the clients. However if the client you are adding the route to is a dhcp client for the router and its getting an ip (example) of GW then it should not matter, and the route becomes redundant. My guess would be that on the host in question (the one you are adding the route) it has a Default GW of something other then the router.

    Also I have been playing with this very issue myslef with gateway to gateway tunnels, quickvpn works surprising well, but gateway to gateway connects and does not send traffic. I am trying to narrow the playing field to see if its my linksys router or if the symptoms persist with other equipment as well. Hopefully we get this worked out sooner rather then later.
  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