08-13-2019 01:36 PM - edited 08-13-2019 01:46 PM
Hey all.
As the title suggests, we've got a Cisco RV325 at one of our locations. Unfortunately, this location has terrible, terrible internet service (a peculiar problem given its seemingly urban and market-ideal location). As such, we have two internet connections coming into the facility, so that we can pipe our general internet and phone usage over one of them... and pipe our camera feeds over the other. If we try to use a single connection, phone calls get very choppy and difficult to understand, and internet slows to a crawl.
We'd like to force our NVR to do all of it's communicating (inbound and outbound) over one of the WANs, and everything else to go through the other. How do we do this?
Solved! Go to Solution.
08-15-2019 12:35 AM
Hi,
You can configure Protocol Binding in RV325 Router to route the NVR traffic via specific WAN interface. And for the remaining specific traffic you can route via the other WAN interface. Please check the page 53 of the admin guide regarding the Protocol Binding configuration…
Also you may refer the Manage Protocol Binding section on the below mentioned link…
Note: Please choose the service, source IP & destination IP carefully as per your needs.
08-15-2019 12:35 AM
Hi,
You can configure Protocol Binding in RV325 Router to route the NVR traffic via specific WAN interface. And for the remaining specific traffic you can route via the other WAN interface. Please check the page 53 of the admin guide regarding the Protocol Binding configuration…
Also you may refer the Manage Protocol Binding section on the below mentioned link…
Note: Please choose the service, source IP & destination IP carefully as per your needs.
09-06-2019 12:26 PM - edited 09-06-2019 12:27 PM
So, update!
Turns out Sujoy's advice up there totally works, you can force a certain IP to stick with a certain WAN interface if you choose - but this was utterly disastrous for our needs. Turns out the RV325 also does a pretty good job of blending bandwidth from two WANs, and so instead of using the Protocol Binding feature at all, we ended up using the Bandwidth Management feature - I gave my end user absolutely dedicated bandwidth on his desk phone (per the VoIP provider's recommendations), and gave him some bandwidth on his office PC and... basically the rest the router gets to decide.
It works perfectly now! Sometimes you just gotta look at things from a different perspective. :)
Thanks for the help anyways, Sujoy! I went ahead and marked your comment as the solution since... it is the correct solution for the question asked - it just wasn't ultimately the solution for our problem. Hopefully your answer, as well as my follow up, will help any wandering users in need of help.
09-09-2019 07:08 AM
Hi,
Thank you for your reply. Good to know that the mentioned issue has has been resolved.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide