@Smith6612 wrote:Are your RT-AC87R routers connected back to the Quantum Gateway using Ethernetport 1 on the ASUS? That port lives on the Quantenna SoC, not the Broadcom SoC. It looks like the router is updating topology as a part of the Spanning Tree protocol used by all routers, and I suspect the Quantenna SoC could be partially to blame. There have been some bugs with it in the past, and the Quantenna uses RGMII (basically low-profile Gigabit Ethernet) between the Broadcom and itself. Ports 2-4 on the router will go to the Broadcom SoC.
See AlsoVerizon Fios router blinking red: 13 simple ways to fix it!This one quick trick could fix your internet connectionVerizon Fios router blinking red: 13 simple ways to fix it!Can WinXP log onto Verizon DSL at startup? - Verizon DSLAs for the DNS part... why use Verizon's DNS? Go use something more robust like Google DNS or OpenDNS.
When the tech arrives to install 150M Internet, work with them to set up one of your ASUS Routers, or another capable router as primary. If the tech insists getting the Quantum hooked up first, let them do that. Then, once they leave, follow the DSLReports guide on using the Quantum router as a secondary.
https://www.dslreports.com/faq/verizonfios/3.0_Networking
The above applies to the ActionTec router, but the concepts are the same. Your key step here is getting Ethernet from the ONT.
Those notifications were from when the router was in "AP Mode" which means it was connected to the Quantum Gateway on the WAN Port and not any of the LAN Ports. When I switched it to router mode after experiencing so many issues with the Quantum Gateway and just simply DMZ'd the router and created another subnet with routes to and from it was on WAN and LAN Port 2. Those messages were supressed but local DHCP was still raising all sorts of issues similar to the Quantum Gateway.I will explain why in a little bit.
To your question about DNS Servers, both Google DNS and OpenDNS have always responded slower noticably, for as long as I can remember. This actually logically makes sense since the Verizon DNS is "within the network." When people suggest actions like that I will never understand because any DNS server that is "closer" will respond to and query much faster than a DNS outside of one's network. Now there are cases of horrible ISPs with bad DNS servers but anyone knowledgeable in DNS would know this.
Also, to further that, I have ran tests utilizing both "alternative DNS services" and the query times are significantly higher (253ms avg. response vs 43ms avg. response of Verizon's DNS). In fact, the only DNS system faster which is available were NTT from NTT Communications (23ms. avg response) and from one of my own DNS networks (18ms. avg response). Neither of those choices are however fesible to use.
Next, the FiOS Tech has already come and gone. They didn't drill nor did they install ethernet. I am one of the few people within the Verizon FiOS footprint that is capable of sustaining Quantum 150/150 on MoCA 2.0 (more like 200/200). I've been with Verizon for a very long time (11 years) and I know all those ways of getting around from DSLR and have used them before with the old Actiontec's. In case you are wondering why they didn't drill: Verizon caused over $1,000 worth of damage the last time they drilled for FiOS and had to pay for it. It's just not fesible to run Ethernet from the outside and since the where the Fiber lines are run from are literally not that far into my backyard the ONT is on the back right side of the home where copper used to come in (the old telephone box is still there).
Now to why the Quantum Gateway Is Acting Up:After days and days of hopefully getting the log just in time before a Quantum Gateway reboot I did and narrowed it down to one direct cause: the renewal of a 24 hour local DHCP lease to an HP Pavilion H8-1160t's network devices (both WiFi and Ethernet; doesn't matter which one is enabled or which one is disabled) running Windows 10 Pro. Every single time it tries to renew the lease the DHCP server errors, crashes, and the router reboots.I have confirmed this by setting the lease time to the lowest possible and watching to see what happens.
The Fix for the Quantum Gateway:Set a static IP address on the system which is causing the problem. You will need to power off the Quantum Gateway and do this for any incompatible devices!I have an iPad 3 and it would cause the Quantum Gateway to crash too until I set it to Static. Ever since, the Quantum Gateway has been functioning normally though I am getting a replacement.
This is not the first time a Verizon router has been incompatible with devices: A long time ago I had a Westell 327w and a Dell 1150 Wireless Card. Dell replaced the cards over and and over before replacing the computer which "fixed it." Turns out, in 2008 it was disclosed that the Westell 327w was incompatible with that Dell Wireless card. I got around this with a trusty WRT54G that I then used for FiOS until they burned out. WRT54G's are arguably the best routers Linksys ever produced as a sidenote for those of you that don't remember.
Can Verizon Fix This?@DHCP Server is just software. Unless the problem lies with hardware within the Quantum Gateway Verizon could fix this by releasing firmware with a different DHCP Server or an updated DHCP Server. A computer that has a Core i7-2600 is by no means "outdated" when my mid-2010 Macbook Pro can work just fine. My servers and my own server/computer that has a Core i7-3770K @ 5.0GHz and an ASUS PCIe-AC68 WiFi Card as well as Federal Government issued computers, iPhone 6s Plus', and even a Galaxy 6 all work fine (as does an iPad Mini 2).
This is however why some don't experience problems and others do. It's dependant on the hardware you have for your devices.
In the interim, I've been in touch with VZ Tech Support who are shipping a new Quantum Gateway and a Network Extender due to the fact we used to have two Rev. I's that were documented. So I solved my situation and I hope others can use this to help resolve their Quantum Gateway issues!
