03-11-2016 07:01 PM
Network service detection keeps showing that WAN1 is down every so often and it is not. I was running 4.2.2.08 and upgraded to the latest 4.2.3.7 and it still has the same issue. It is disconnecting our voip phones and other other connected software outside of our network. Has anyone else heard of an issues like this?
03-16-2016 02:09 PM
Anybody?
03-16-2016 11:56 PM
Hi Bob Boklewski,
What is the status of wan1 connectivity from your isp to your router.Did you check your ISP connectivity.
Thanks,
kafi
03-17-2016 06:29 AM
This is a remote office having the issues, I am now pinging the gateway the router is connected to in order to see any drops before our router. I am doing this from my main office. On the remote office router that has the issues, I did have NSD set to 4 for retry count and 5 for retry timeout. These settings were below the defaults, which I think caused an issue so I put them back to 5 and 5, which are the defaults. It seemed to behave better after making the change and ran with no NSD errors for a few days or so. However, I saw a WAN[1] down again yesterday. I was using 8.8.8.8 to ping and changed it to opendns servers. I did this because I know I had issues in a different location using 4.2.2.2, which was unreliable. So instead of using google dns servers to ping I am going to see how opendns servers work. When I did have retries set to 4 and 5 for retry timeouts, I would have around 4-5 disconnections a day. Still hard to believe 8.8.8.8 would be down for 25 seconds though, but again, 4.2.2.2 became unreliable for NSD on another device so who knows.
03-22-2016 01:35 PM
Pinging opendns servers didn't fix the issue. Does anybody else have failover working correctly on this device?
Mar 21 14:09:01 2016 | System Log | NSD FAIL WAN[1] |
Mar 21 14:09:02 2016 | System Log | WAN connection is down |
Mar 21 14:09:07 2016 | System Log | WAN connection is up : 184.74.247.103/255.255.255.240 gw 152.74.243.97 on eth2 |
Mar 21 14:09:12 2016 | System Log | WAN connection is down |
Mar 21 17:11:24 2016 | System Log | NSD FAIL WAN[1] |
Mar 21 17:11:26 2016 | System Log | WAN connection is down |
Mar 21 17:11:30 2016 | System Log | WAN connection is up : 184.74.247.103/255.255.255.240 gw 152.74.243.97 on eth2 |
Mar 21 17:11:37 2016 | System Log | WAN connection is down |
Mar 22 08:56:31 2016 | System Log | NSD FAIL WAN[1] |
Mar 22 08:56:32 2016 | System Log | WAN connection is down |
Mar 22 08:56:37 2016 | System Log | WAN connection is up : 184.74.247.103/255.255.255.240 gw 152.74.243.97 on eth2 |
Mar 22 08:56:44 2016 | System Log | WAN connection is down |
Mar 22 08:57:36 2016 | System Log | NSD FAIL WAN[1] |
Mar 22 08:57:37 2016 | System Log | WAN connection is down |
Mar 22 08:57:42 2016 | System Log | WAN connection is up : 184.74.247.103/255.255.255.240 gw 152.74.243.97 on eth2 |
Mar 22 08:57:49 2016 | System Log | WAN connection is down |
Mar 22 08:58:41 2016 | System Log | NSD FAIL WAN[1] |
Mar 22 08:58:42 2016 | System Log | WAN connection is down |
Mar 22 08:58:47 2016 | System Log | WAN connection is up : 184.74.247.103/255.255.255.240 gw 152.74.243.97 on eth2 |
Mar 22 08:58:55 2016 | System Log | WAN connection is down |
03-08-2018 06:02 AM
I'm seeing similar faulty behavior on my rv340 and have not yet found a solution.
For now the only viable solution for me seems to be to disable NSD altogether. However, the rv340 docs are unclear on what happens failover-wise and recovery-wise when NSD is disabled.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: