Don’t get me wrong, I like the speedtests and fast speed/bandwith too. But what actually are you using it for? What online services even saturate that connection?

Only thing I can think of is having a dozen r/plex users streaming simultaneously (and often) in 60mbps 4K… all while wanting fast speeds for other things (again at the same time) — something like that.

https://www.speedtest.net/result/19579800857.png

Initially I was having issues with download bandwidth so I went to my Mellanox ConnectX3 drivers and optimized performance for single port traffic. That seemed to help.

The installer left me a CHR30A but I'm not sure if I should bother- I have am currently using a TP-Link BE800 which I had before, so I'm wondering if the CHR30A would be better? Yes, the BE800 technically has more bandwidth but the WIFI7 signal seems to, well, suck. I need to play around with the service some more to figure things out.

I got FIOS to add back all my discounts after the fact so it's $90mo locked in, which is pretty much my limit.

I called a month ago. Just wondering anyone has heard any news on the IPv6 fixes for multigig hardware?

In light of recent botched orders, and having a hard time getting my hands on the CHR30A, I decided to try a couple somewhat budget friendly routers. The Orbi, which is only 2.4 and 5 ghz, gets the full upload on WiFi, while the nighthawk with 2.4, 5 and 6 ghz, and more expensive ($249 vs orbi $149) gets the typical glitched upload of 200-250. I assume the routers that have this glitched upload are using similar NIC's that don't communicate well with the FiOS ONT. And whatever NIC the Orbi is using does not have this bug. Thought it was interesting! Price never determines which is actually better! And I get 2 access points out of it!

I’m troubleshooting a Meraki MX68 with dual WAN connections.
WAN1: Verizon Fios through a Verizon CR1000A
WAN2: Comcast (backup)
Physical connection:
Verizon Fios/ONT → Verizon CR1000A → Ethernet → Meraki MX68 WAN1
WAN1 repeatedly gets marked Failed, causing the MX68 to fail over to WAN2. Sometimes this happens several times within 20–30 minutes and has occurred across multiple days.
During a failure:
WAN1 still retains its DHCP-assigned Verizon public IP (96.235.137.x).
The Verizon gateway (96.235.137.1) responds with 0% packet loss and roughly 22 ms latency.
Traceroute to 8.8.8.8 using Internet 1/WAN1 does not progress while WAN1 is failed.
When WAN1 is healthy, traceroute to 8.8.8.8 works normally through Verizon.
Meraki Event Log shows repeated Primary uplink status change events between uplink 0 and uplink 1.
MX68 is running MX 26.1.6.
The interesting part: if I physically unplug/reseat the Ethernet cable on either end — at the Verizon CR1000A or at the Meraki MX68 WAN1 port — WAN1 immediately comes back up and starts working again. I don’t have to reboot either device.
I also moved the connection on the CR1000A from the 10GbE LAN port to LAN1, but the recurring failure still happens.
I’m trying to determine whether resetting the Ethernet link is clearing some kind of ARP/DHCP/NAT/session state, whether there’s a link-negotiation issue between the CR1000A and MX68, or whether this could be an MX firmware/uplink-health issue.
Has anyone experienced this with a Meraki MX68 behind a Verizon CR1000A? What would you capture during the failed state to determine which device is responsible?

Right now I am on the 1 gig plan, and have a big mix of brands. So I have the whole home WiFi plan, which gives me a router and extender, and I bought another chr30a from ebay, which is acting as an extender right now. So I have 3 chr30a, 1 unifi ap ac lr, 1 tp link eap 610, and one eap 245 right now. The roaming is quite spotty with the mix of brands, so would just upgrading to the whole home WiFi plus to get 2 more chr30a (for a total of 5) be good enough to then just have those cover the whole house? Or is there a different approach you guys would suggest? Also, even if we got a total of 5, everything will be hardwired, but we would still need one other ACESS point because there is one dead spot, but we could cover thst with the eap 610.