RV340 & WISP WAN Connection Problems

[DestinationNetUnreachable]

Hello.

We recently purchased an RV345 to use in our SMB setting.  We have a static IP, gateway, subnet, and DNS1 & DNS2 from our WISP, and the configuration is very simple - something I've setup many, many times in the past.  There is no MAC lock on the connection, as is sometimes the case with ISPs.

I powered up the RV345, logged in, changed the admin password, and set up WAN1 with the settings specified, and was shown in the WAN window that the connection was up on IPV4.  But no internet connectivity.  Could resolve hostnames (yahoo.com) and perform DNS lookups in the router's diagnostics area, but couldn't ping them.  Machines on the network could connect to the internet, for about 30 seconds, after which no connectivity was available.  The WAN status still showed IPV4 as up.

I reset the router and set it up again.  Same thing.  I did this many times, sometimes using DHCP, sometimes the Static IP settings.  Finally I involved the ISP, and had them check things on their end.  They said it looked like it was connected on their end and could see that the router was sending traffic to an IP on AWS - I'm guessing this is a Cisco firmware update check.  But the issue was always the same.  I could ping websites on the router or on a network device for about 20-30 seconds after re-configuring WAN1, but afterwards, nothing.  No internet connectivity, though the router responded to LAN pings.  I tried configuring the connection when connected to WAN2, but same thing. 

Finally, I returned the RV345, thinking it may have been a hardware issue, and got a new RV340.  Brand new - same exact thing.  Nothing else is configured in the router - I'm literally powering it up, configuring WAN1, and then this happens.  I've tried disabling the firewall in the router, but it makes no difference. 

Finally, in order to rule out the possibility that it was anything other than a router issue, I brought in a Ubiquiti EdgeRouter 4 that I have as an on-hand backup router.  Configured it with the same Static IP I had been using, and it worked like a charm instantly.  Later still I grabbed a $50 Belkin Wireless Router we'd been using as a WAP and tried it - same thing, worked perfectly. 

Does anyone have any suggestions I could try to make this work?  The ONLY thing I haven't done is update the firmware.  It shipped with the second-to-latest release.  But, so far, every other router I've tried works perfectly after configuring the static IP.  Only the Cisco RV-series appears to have problems.  I'm replacing a Cisco C881 that we do not own and was only used as we used to be a branch office connected via a tunnel. 

Our ISP is a WISP, or a fixed-based wireless provider.  So we have an antennae and radio outside our facility.  The only non-standard aspect to our install is that there's a POE injector on the WAN cable - the cable that would ordinarily be running from the ISP's modem to our router.  This is because that cable powers the radio equipment on a tower outside our facility.  I've run cable tests on it and they've all passed.  So the CAT5 cable runs from the antennae to the POE injector, which then plugs into our router. I don't believe that these components are causing the issue.

Any help would be greatly appreciated.  Not sure what to try at this point.  I should add that the config on the C881 we're currently running matches the config that I'm using, with respect to the WAN configuration.  They're identical. 

[Ed C]

June 2021 - Just adding to the group that I am having a similar issue!

The setup wizard was able to detect and connect to the WAN but when the setting is saved, I have no access to the internet.

Read the above and tired the various settings and all failed!

Ping to 8.8.8.8 failed

DNS lookup works and was able to resolve bbc.co.uk, yahoo.com etc.

I unchecked Network Service Detection and that did not work either.

tried using various DNS settings - it's no good either!

Look forward to hearing if anyone else has this issue and managed to resolve it!

[Richard Burts]

I am not clear whether this is the same issue or a similar issue. Could you clarify a couple of points:

- if you reconfigure the WAN do you briefly get connectivity to Internet (can ping things) and then lose the ability to ping?

- when it is not working and you attempt ping from the administrator session, troubleshooting page, do you get the error about operation not permitted?

If you unchecked Network Service Detection and it still does not work it sounds like it is not the same issue but a similar one. If name resolution continues to work it suggests that UDP is not impacted. Could you try some other traffic that is UDP, perhaps tftp or some other application to verify that UDP is not impacted. If ping fails it sounds like ICMP is impacted. I wonder about TCP. Could you try something that uses TCP, perhaps HTTP/HTTPS?

I do not know enough about this platform to suggest other settings that you might check. But if it sounds like a software bug it might be a good thing to try a different version of code, depending on the version you are running it might be newer or might be older.

Do you have the ability to open a support case on this?

[donbuckley]

I also have this problem.

This bug persists.

Cisco RV345, Firmware 1.0.03.21, today's date is August 5, 2021

I was initially configuring the router with the WAN2 plugged in. My ISP's upstream gateway was blocking the echo response.
I would watch the Cisco RV345 boot up, a steady ping on 8.8.8.8 would ensue for a few seconds and then be blocked.

the traffic was flowing and then it was shut down.

So at that point I new it was something in the router's config.

At first I think it was a firewall rule blocking ping.

Nope.

The un-pingable gateway problem

'Network Service Setection' is enabled by default on on both WAN1 and WAN2, ***with the 'Detect Destination' as 'Default Gateway' ***

meaning if your ISP's gateway is un-pingable, the router will disable the WAN port.

It will disable the wan port even if the other wan port is offline. In my case only 1 of 2 WANs was plugged in at the time of testing.

When I switched the ISP and plugged my other ISP into WAN2, immediate functionality.

The problem was in part, my ISP not responding to ping, from its own clients. **bleep** move there, ISP.

So even though I had nothing plugged into the WAN1 port, the RV345 disabled the WAN2 which I was plugged into because of no ping response from the upstream gateway.

WAN2 was on DHCP, and got a lease no problem. WAN2 showed as 'Online'

The workaround is to set the detection target to be a ping-able IP address a few hops outside / nearby the ISP provider that the WAN can see. Or just 8.8.8.8.

Then the wan port won't be disabled by the router.

Cisco here is the fix:

1) Put 'Network Status Detection' as an indicator in the web interface on the 'Interface Setting Table', showing the values as read-only, and indicate if there is no echo response from the Detect Destination.

2) Update the manual properly

3) Set the default value for the 'Network Service Detection' to 'disabled', and disable the Multi-wan 'Precedence' fields if the Network Service Detection is not enabled. If that isn't enabled you can't do Multi-Wan anyway.

Cheers

Don

It won't be hard to program a fix for this aside from disabling the external connection detection by default.

[Richard Burts]

Don

Thanks for sharing this with the community. +5 for sharing this insight.