While I do not know if it is related or not, ever since the latest Kong update I have a periodic problem that I'm having difficulty to track down. Every few days when I wake up in the morning I find the Netgear Nighthawk is servicing the LAN just fine but no internet connection. When I scan my LAN I see the DD-WRT router on its' normal IP (2.1) yet it refuses to connect when I try to access via browser, I just get "not available". There is no internet connection, yet I can access any other device (like my RPi3 home controller) on that (192.168.2.xxx) network.
I use DD-WRT with NordVPN to set up a UDP VPN conection. Since one of the things I use my RPi3 for is to monitor my internet connection integrity and speed (my ISP has a habit of lowering the speed from what I'm paying for), I notice in its' log that every night, exactly at midnight, the connection goes down for a few seconds, like an ISP wide reset. Most times the NIghthawk must recover fine but sometimes it gets stuck in this funcky status wheere I cannot access it and it has no internet connection. I have a second wifi router that sets up a normal internet wifi connection (not over VPN) in parallel to the Nighthawk VPN wifi router (some uses require one to not be on a VPN) (my ISP modem is in bridge mode) and it is working and accessing the internet just fine, never seems to be impacted by this "reset", if thats what is causing the problem.
Without the ability to access the Nighthawk by browser, I usually have to do a full HW reset, load the OEM FW, get it up and running as a normal Netgear router, then re-load DD-WRT, then reload the specific VPN config. A major pain in the butt time consumer.
Any suggestions as to what could cause the router to go "blind" to browser access and WAN connectivity like this?