RV34x FW: v1.0.01.18 2018-01-11
WAN static IP: xxx.xxx.xxx.227
gateway IP: xxx.xxx.xxx.225
mask: 255.255.255.248
______________________________
I couldn't believe my eyes!
When I attempted to connect a customer's RV340 to a new fiber ISP using a Static IP assignment (above), the router blocked all Internet traffic in a matter of a few minutes. All Internet connectivity shutdown completely; nothing got through anymore, not IPsec, DNS, HTTP, ICMP - nothing! Rebooting the router reproduced the exact same symptom, initially Internet starts working and then dies. When I restore the old DSL PPPoE connection on either WAN port, Internet traffic resumes but only on that port.
I tried everything I could think of, cloning the old router's MAC, disabling all IPsec and other traffic, etc. All other configuration settings is at default, which ordinarily allows basic router functions out of the box. But no matter what, pings to external sites, whether by IP or resolved DNS, go dead after a few minutes with this particular static WAN setting, during which browser pages freeze up and "no Internet" pops up on every LAN PC. All the while, the RV340 US summary says the WAN is "up".
I could not reproduce this symptom on any other WAN connection I had available, not on PPPoE or DHCP. The router works fine bench-testing with either or both WAN's plugged into another router's LAN, even when making WAN DHCP assignment static. It's only with this particular ISP and static assignment does the RV340 react this way. I don't know if it has something to do with the larger 'xxx.xxx.xxx.248' mask, as I am more used to seeing 'xxx.xxx.xxx.252' masks from other providers. In either case, there is no way to deploy the RV340 with this new provider. Needless to say, my customer is pissed.
After wasting hours on end, I had no choice but to stick back in the old RV042. All of the RV0xx routers run flawlessly and never once let me down. I already regret upgrading to the RV34x. I never expected this of Cisco SMB. Who does? Guess I'm a sucker.
There is next to no diagnostic clues to go on. After all Internet traffic died off, the only indication the RV340 logs is "<error>Webfilter: Error reading from socket: Resource temporarily unavailable". (see sample log attached). Once this entry appears, it logs the typical time-out errors from IPsec and other traffic unable to reach their destination. As you would expect of any dead ISP connection.
Is there some new setting in the RV34x for this type of connection?? I somehow doubt it. Please fix this issue Cisco. I'd like to someday take this router out of mothballs to get my money's worth.
