We've had some pretty bad routers in the past: the old Verizon DSL Westell 327w's that were replaced every other week, the Actiontec Gen II. Rev. D. BHR, the Netgear R7000 Nighthawks which burned out in less than four months, and now the FiOS Quantum Gateway which replaced an Actiontec Gen III. Rev. I BHR that couldn't maintain a WAN connection.
Of course, that issue pales in comparrison to the fact that the FiOS Quantum Gateway can't seem to maintain a WAN or LAN connection. Even though we have a tech coming Monday for the 150M/150M upgrade, I doubt it's going to make much of a difference since clearly there is a problem with the Quantum Gateway itself.
We have had the router since Monday and in that time it has literally reset itself each and every single day. Right now, the Quantum Gateway reports an uptime of just slightly over 6 hours and 30 minutes yet it's been powered on since Monday. This of course is a frequent reoccruance; powered on since Monday but it can't seem to stay active throughout one entire day.
To further that, the FiOS Quantum Gateway seems to be having repeated errors with its DNS Server, providing errors <error137>, <error139>, <error153>, and <error155> in the log enough time that it is usually all the logging reports yet the only DNS changes made was to elect Verizon's non-hijacking DNS servers (for those of you who have been with Verizon for a long time wil know that those are the ones that end in '.14' while the DNS hijacking ones are '.12' and if you're new; congratsulations - you learned something today and welcome to Verizon). Of course, it's clearly not the DNS servers themselves because on of the first things we tried was switching it back to letting it acquire them automatically. Same results.
It is also clear that these issues are now affecting the entire network as ASUS RT-AC87R's which act as AC Access Points (i.e. they still rely on the Verizon router to get DNS) are constantly reporting the following:
Mar 11 18:58:14 kernel: br0: port 1(vlan1) received tcn bpdu Mar 11 18:58:14 kernel: br0: topology change detected, propagating Mar 11 18:58:35 kernel: br0: port 1(vlan1) received tcn bpdu Mar 11 18:58:35 kernel: br0: topology change detected, propagating Mar 11 19:00:35 disk_monitor: Got SIGALRM... Mar 11 23:00:35 disk_monitor: Got SIGALRM...
At intervals concurrent with the FiOS Quantum Gateway presenting errors. However, since that's apparently not enough for this **bleep** of a gateway (I can't believe people paid or rent these devices!): WAN and LAN drop off whether you are connected to directly to the Gateway, on MoCA LAN, or via an Access Point so the only single common denominator is the FiOS Quantum Gateway.
The absolute best parts: there's no apparent way to bypass the Quantum Gateway and let an ASUS router control the DNS and QoS is locked out of the Quantum Gateways leaving the STBs which were in Queue 5 on the Rev. I (an acceptable queue) maxed out at Queue 7 (the highest) which should be reserved for devices that need that queue such as transmissions from the Access Points.
So while I have a tech dispatch on Monday to wire everything up for Quanntum 150M/150M who isn't hopefully incompetent (yes, I have encountered tech visits where the tech was so incompetent that they said my Actiontec router wasn't a Verizon router because the SSID was not default even though it had the Verizon branding and when he wouldn't listen I kicked him out of the house and called his manager and Verizon Executive Relations).
Is there anyway to bypass the Quantum Gateway. I tried a DMZ method I saw posted here whereby two subnets are created and a route is added to route the Quantum Gateway traffic to the router of your choice but it always errors out at setting up a Static NAT and the Quantum Gateway won't even accept the route to the appropriate subnet.
I have a laundry list of complaints for that tech on Monday whose here to install the 150/150 internet but honestly I will cancel Verizon if I can't get a working internet after it's been three weeks! There ETF fee is less than my bill from Verizon Wireless so it's not really a big deal to throw away Verizon's rather lackluster FiOS service which is what it's been for a month. This after eleven (11) years of being a Verizon customer.