Posted: Wed Aug 07, 2019 11:28 Post subject: R6400v2 WAN Provision Issue
About five months ago I purchased a used Netgear R6400v2 off Newegg. Once I flashed DD-WRT; it has since been a daily driver for our network.
There has only been one issue that I have been having, and I am not sure if it is an issue with my configuration or the unit itself.
I have a network policy with no DHCP auto-assign (I must assign devices a static IP manually), mac filtering for WiFi; and no UPnP.
Keep Alive set to reboot at 0400 hours every Wednesday with NTP set to America/Los_Angeles
The issue I am having is that when the Keep Alive reboot initiates weekly, the router will not pickup the WAN IP until the modem itself is rebooted, then the router is suddenly provisioned an IP address.
This would not be a problem if the modem itself had a scheduled reboot function, but alas; it does not.
Modem is a Touchstone TM1602AP2 Telephony Modem. ISP is Charter.
Prior to this, My old WNDR3800 was provisioned a WAN IP just fine, with all the same settings; so I know it is a conflict with the new router.
Posted: Wed Aug 07, 2019 12:51 Post subject: Re: R6400v2 WAN Provision Issue
dbrown1986 wrote:
The issue I am having is that when the Keep Alive reboot initiates weekly, the router will not pickup the WAN IP until the modem itself is rebooted, then the router is suddenly provisioned an IP address.
Have you tried `nvram erase && reboot` from telnet (assuming this is a recent build), and manual setup?
Build is v3.0-r40559 std (08/06/19)
I thought it good practice to schedule a reboot. So I did.
Those tickets do present the same issue that I am having, but are from different users who both have Arris equipment too. Perhaps it's an Arris/Broadcom thing; as the WNDR3800 I had (Atheros chipset) got its WAN IP just fine.
The first ticket mentions he unplugged the WAN cable from the modem and plugged it back in and got a WAN IP that way too, so maybe I will do that from here on out.
What build are you on? Try the latest build, or if you already are, try an older build. 
I saw tickets about this in SVN: