Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.
Cisco RV320 Gateway to Gateway connected but not passing traffic
I have two Cisco RV320 routers located in two different offices. I have successfully configured and have an active tunnel between the two. Office A is 192.168.0.X and office B is 192.168.10.X. The routers are set at x.x.x.254. From office A I can browse to the router at office B using the internal IP's. I cannot ping or contact any other device in office B. other that the router.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
can you post representation of what your VPN is setup?
rv320 location A
peer address rv320 Location B
Local LAN: 192.168.0.0 255.255.255.0
Remote LAN: 192.168.10.0 255.255.255.0
RV320 Location B
Peer Address RV320 Location A
Local Lan: 192.168.10.0 255.255.255.0
remote LAN: 192.168.0.0 255.255.255.0
either or both location have static IPS?
The other possibility is that you have setup a remote VPN versus a site to site or your limiting of the netmask is what caused your situations that the devices can only talk between them and nothing else?
rv320 location A
peer address rv320 Location B
Local LAN: 192.168.0.0 255.255.255.0
Remote LAN: 192.168.10.0 255.255.255.0
RV320 Location B
Peer Address RV320 Location A
Local Lan: 192.168.10.0 255.255.255.0
remote LAN: 192.168.0.0 255.255.255.0
either or both location have static IPS?
The other possibility is that you have setup a remote VPN versus a site to site or your limiting of the netmask is what caused your situations that the devices can only talk between them and nothing else?
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
We're moving from one network to another and have both up and running parallel. Switching devices to the correct Gateway on the other end solved it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
When you ping the remote device it must have a return route to reply. If the RV320's are the default gateway for all devices at both sites that is not a problem, but if not, you need to add static routes to the devices for the remote subnet. Please advise, and if necessary we can explain how to add the static routes.