12-08-2017 10:02 AM - edited 03-08-2019 01:02 PM
I wonder if Cisco exists for small routers or is interested only in the assistance of big ones.
They have in production a router that does not work and it seems that those who bought it are abandoned with an unusable "piece of iron". Which, however, was paid based on the specifics of operation.
Seen from the customer's side, it looks like a scam. Truly incredible.
The flaw is the lack of return from static routes ... it does not seem to me a marginal problem, but a real firmware defect.
And no solution news can be read.
What should I do? Change producer hoping for greater seriousness?
And throw away the RV345P ......
12-09-2017 07:44 AM
You have set a static route on the RV345 to an external network, with the next hop being an IP address on your local LAN. I don't see how this is supposed to work, other than that the Open VPN server has a direct connection to that network.
Draw up the full path from 192.168.12.100 to 192.168.132.100.
The problem for sure is not the RV345 router, as a static route simply forwards all traffic.
12-09-2017 08:12 AM
12-09-2017 08:45 AM
12-09-2017 08:54 AM
Hello,
I think the problem is simply that the RV345 has no support for OpenVPN, it does not have an option to create an OpenVPN client certificate.
The RV325 starting with firmware 1.3.1.10 does have OpenVPN support.
So the problem is not with the static routing. Either way, it doesn't change the fact that if you require OpenVPN support for your new site, the RV345 won't work.
12-09-2017 09:07 AM
12-09-2017 09:21 AM
12-09-2017 10:35 AM
Hello,
you have the latest firmware installed already (1.0.01.17).
Is the hop count/metric the same for the static route on both routers ?
It is of course always a possibility that you have a defective device. Where did you purchase the router ? And do you have a Service Contract ?
12-09-2017 10:59 AM
12-09-2017 11:17 AM - edited 12-09-2017 11:35 AM
The main difference between the RV325 and the RV345 is that the latter has a firewall. Is that disabled on your model ?
Also, resetting the router to factory defaults might be worth a try...
--> To reset the router to factory default settings, press and hold the reset button for 10 seconds
12-09-2017 12:10 PM
12-09-2017 11:34 AM
Hello
@ferdinando.alde wrote:
I wonder if Cisco exists for small routers or is interested only in the assistance of big ones.
They have in production a router that does not work and it seems that those who bought it are abandoned with an unusable "piece of iron". Which, however, was paid based on the specifics of operation.
Seen from the customer's side, it looks like a scam. Truly incredible.
The flaw is the lack of return from static routes ... it does not seem to me a marginal problem, but a real firmware defect.
And no solution news can be read.
What should I do? Change producer hoping for greater seriousness?
And throw away the RV345P ......
What is it your ow happy with? - Can you elaborate?
res
Paul
12-09-2017 11:59 AM - edited 12-09-2017 12:14 PM
Paul,
there is an OpenVPN server connected to one of the switchports on the RV345 with IP address 192.168.12.12. A static route is configured on the RV345 to redirect traffic destined to 192.169.132..0 (which is the remote end of the VPN) to 192.168.12.12. The problem is: a ping to e.g 192.168.132.100 works, but nothing else. Something is blocking the return traffic (SMB on Windows).
The exact same setup works perfectly on an RV325. We have looked at about anything possible, no luck so far...
If a static route is added locally (route add 192.168.132.0 mask 255.255.255.0 192.168.12.12), which means effectively circumventing the static route configured on the RV345, it works fine.
12-09-2017 12:25 PM - edited 12-10-2017 08:30 AM
Hello
So all three devices have interfaces on the same subnet, With the 345 router performing the routing with a static route 192.168.132.100 255.255.255.255 192.168.12.12 ?
192.168.132.100 is a far end vpn destination address originating from 192.168.12.12 ?
To me first instincts suggest the server, you maybe be able to ping ( i am assuming sourced from 192168.12.0 subnet ?) due to the server having dual nics. ----However SMB issues is layer 7 so that isn't routing its application related - what’s mode is the router running as?
res
Paul
12-09-2017 02:08 PM
12-09-2017 02:13 PM - edited 12-10-2017 08:32 AM
Hello
Can you elaborate on how your trying to connect - via what method? Http - htttps - telnet- ssh etc..
Res
Paul
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