Verizon Home Internet Router noet sending DHCP client release to the WAN port of my TP-Link ER605
update.
TP-Link tech support is awesome.
They verified that the issue is with the Verizon device is indeed not sending a update to the TP-Link router when the Verizon IP number changes.
so now I need to somehow get Verizon to update their firmware... not putting much hope on that :-(
meanwhile I'll get the Verizon out of IP Passthrough mode and do a double nat with the ER605.
========= original post ==========
I just got a Verizon LTE Home Internet router ASK-NCQ1338FA (firmware 222656), which I configured as "IP passthrough", i.e. acting as a dumb modem not a router so I can connect it to my existing TP-Link ER605
The Verizon ASK AF is plugged into the WAN/LAN1 port (configured as dynamic IP) of the ER605
everything seems to be working fine, the router is acquiring the IP number (and DNS servers) from the Verizon router/modem.
and everything else works as advertised: the load balancing, online detection and failover (when I pull the plug on the primary WAN, it failover to the secondary Verizon within 30-40 seconds), NO-IP dynamic DNS gets updated for both WAN ports, etc.
so far so good...
until...
the Verizon router gets a new IP assigned by Verizon (which seems to happen every few days)
the ER605 System Status and the Network WAN sections still shows the previous IP number, and the connection status say "link up"
but obviously the link is useless as there is no longer a router at the previous IP number.
the ER605 "online detection" reports that it is "offline" (because it cannot route via the previous IP of the Verizon router).
oh, also the NO-IP dynamic DNS still has the previous number reported to it, which means that I cannot access my network from the outside.
the only way I found to restore connectivity is to go into the ER605 and manually disconnect and then reconnect the WAN/LAN1 connection
and only then does the ER605 acquires the new IP from the Verizon router...
not good at all :-(
I am taking advantage of the fact that NO-IP does not get updated, and set up freshwork's free freshping monitor on the WAN/LAN1 dynamic DNS domain name, which sends me an email whenever Verizon (or the primary ISP) is "offline"
so whenever I start getting these down alert notification email messages from freshping, I have to log into the ER605 and disconnect/connect the WAN/LAN1 so that the ER605 reacquires the new IP number from the Verizon router/mode.
any idea what I might be doing wrong here?
is this a bug in the ER605?
or a bug in the Verizon router/modem?
on a previous issue, Verizon would NOT provide support because of the "IP Passthrough" configuration. they have no clue what it is...