Verizon 5G Home Internet - Router model ASK-NCQ1338FA - Pass-through connection not working
Verizon 5G Home Internet - Router model ASK-NCQ1338FA - Pass-through connection not working
Verizon router link: https://www.verizon.com/support/verizon-...ncq1338fa/
Device version: OPNsense 23.1.7_3-amd64
Recent experience: Used Verizon 5G Home Internet for four months without major problems. Initially, setting the WAN port in OPNSense to MTU 1428 caused minor issues, but once resolved, everything functioned perfectly. Two weeks ago, I encountered slow or incomplete loading of sites such as Verizon, LinkedIn, and certain Microsoft pages. After troubleshooting and restarting both devices, I attempted various MTU configurations, but the problem persisted. Upgrading to the latest OPNSense version didn’t resolve it either. Eventually, I performed a factory reset on the router and reconfigured passthrough via RouterIP settings, adjusting network options in OPNSense. Despite changing settings and rebooting multiple times, connectivity issues remained. After another factory reset, I set up a static DHCP for the WAN interface on OPNSense within the Verizon web interface, placing the IP in DMZ mode. I reset all interfaces to defaults to avoid forced MTU settings. Testing confirmed everything worked smoothly. However, I now experience double NAT, which is acceptable since it’s my secondary connection. Pings are slightly delayed due to an additional hop, but most users won’t notice. I suspect Verizon may have altered their passthrough functionality—previously the router light changed from white to green, suggesting recent updates. This update might explain the current behavior. I hope this guide assists others facing similar challenges, and I recommend enabling DMZ if passthrough isn’t working for you.
We encountered a user on Verizon 5G Home Internet with GlobalProtect. Their VPN connections were extremely slow, while regular home devices showed speeds between 40 and over 200 Mbps. The AT&T hotspot worked well, but the Verizon internet suffered due to GlobalProtect interference. The solution involved adjusting the MTU settings on both the router and Windows machine to 1360. This required using the command prompt with "netsh interface ipv4 show interfaces" to verify current values and then testing with "ping www.google.com -f -l <MTU>" until fragmentation stopped being reported. The final MTU was successfully set to 1360.