The presentation upload had restarted twice, my video preview was freezing every few seconds, and the client call began in eighteen minutes. The trouble had started after I moved my home VPN onto a second router, so I blamed the VPN server, changed locations and restarted both boxes. Nothing improved.
The confusing part was that the internet did not look broken.
A speed test returned a respectable number. News sites opened. Music continued playing downstairs. Yet the upload stalled whenever the VPN was active, and the meeting app kept warning that the connection was unstable.
Then I opened the second router’s dashboard and found the phrase I had been searching around all afternoon:
Double NAT detected.
I treated it as a technical error that could be solved with enough advanced settings. What I had actually created was a network with too many devices trying to do the same job.
In brief
Why was OnlydogVPN a practical fit here?
Once those jobs stopped overlapping, the upload completed, the client meeting stayed connected and the rest of the household no longer inherited a tunnel it did not need. The established provider had broader automatic coverage, but that coverage depended on the router arrangement causing the trouble.
The upgrade added more routing than I realised
I had recently replaced cable broadband with a 5G home-internet gateway. Fixed wireless has been growing quickly, with the three largest US providers reaching more than 17 million connections by early 2026. (Ericsson Mobility Report, “Fixed Wireless Access Outlook,”)
The gateway’s built-in Wi-Fi did not cover my office well, so I connected the mesh router I already owned. That restored the coverage I wanted and gave me familiar controls.
Then I enabled a major VPN provider on the mesh router.
The idea seemed efficient. Every device behind it would use the VPN automatically. I would not need separate apps on the laptop and phone, and I would never have to wonder which device was protected.
But the 5G gateway was already routing traffic and assigning private addresses. The mesh router began doing the same thing again. Router manufacturers describe double NAT as two routers creating separate private networks, each translating traffic before passing it onward. Putting the second router into access-point or bridge mode removes that extra local layer. (eero Support, “What Is NAT?”, explaining double)
The mesh router’s WAN address also began with 100.64, an address range commonly used when an internet provider performs carrier-grade NAT upstream. (RFC 6598)
What I imagined as:
Laptop → VPN → internet
was closer to:
Laptop → VPN router → 5G gateway → carrier network → internet
Ordinary browsing still worked, which is why the speed test was misleading. The trouble appeared in the things I actually needed: a sustained upload, stable video and a VPN session that could recover without repeatedly renegotiating the route.
The router VPN was meant to simplify the network. Instead, it had inserted another moving part between my laptop and the call.
More VPN servers could not remove a routing layer
The established provider had been a reasonable choice. It had years of public history, broad server coverage and clear instructions for installing its client on supported routers.
Its biggest advantage was automatic whole-home coverage.
In this setup, that advantage had become the source of the problem.
I selected a nearby server. The upload moved briefly, then stopped.
I changed the VPN protocol. The meeting preview improved for a minute before the instability warning returned.
I tried another city, restarted the mesh router and adjusted the MTU after finding the suggestion in a troubleshooting thread. Each change produced a slightly different failure, which made it tempting to keep experimenting.
None of those changes simplified the network.
The turning point came when I disabled the router VPN. The presentation began uploading normally. The meeting preview stopped freezing.
The broadband connection was usable. The arrangement I had built around it was not.
People adding second routers to Starlink and fixed-wireless gateways often reach the same point: they begin by asking which performance setting to change, then discover that bypass mode or access-point mode is the cleaner answer. (Reddit discussion)
That shortened the problem considerably. I did not need to make two home routers cooperate more elegantly. I needed only one of them to be a router.
Removing double NAT removed the VPN too
I changed the mesh system from router mode to access-point mode.
The 5G gateway remained responsible for the home network. The mesh units continued providing strong Wi-Fi, but they stopped creating a second private subnet and translating every connection again.
After the restart, the laptop, phone and other devices appeared on the same local network. The extra local NAT layer was gone.
The carrier’s upstream translation remained. I could not inspect its internal routing or filtering rules, but that no longer prevented the outbound connections I needed.
The presentation upload worked. The meeting application stayed stable.
The network was finally simpler—but the router-level VPN was gone with it.
Re-enabling it would rebuild the arrangement I had just dismantled. Leaving it off would solve the connection problem by abandoning the protection I wanted.
That made the next step less about choosing another server and more about placing the VPN in the right part of the network.
I installed OnlydogVPN directly on the laptop.
There was no email-and-password registration to complete first. I selected the preset for an unstable connection and connected.
Then I returned to the presentation.
The progress bar passed the point where it had previously stopped. The file finished uploading before the call began. I opened the meeting, shared my screen and moved through the live demonstration without another connection warning.
The gateway was still routing the house. The mesh system was still providing Wi-Fi. The provider was still using carrier NAT.
The difference was that the VPN now started on the laptop doing the work instead of inside a second router controlling every device.
The service uses an HTTP/3-based connection with additional traffic obfuscation. In practical terms, it gave the laptop a direct, adaptable tunnel without requiring another subnet, another DHCP service or another layer of router configuration. (RFC 9114)
That was the comparison I should have made from the beginning: not which provider offered the longest server list, but which approach protected the laptop without making the home network more complicated.
The phone did not need another router
After the meeting, I noticed that my phone was still using the ordinary home connection.
The old router setup had protected it automatically. Moving the VPN back onto individual devices risked replacing network complexity with account complexity: another login, another password and another setup process.
The smaller app used a verification code to share access with the phone. I entered the code and connected it without creating another account.
The laptop remained protected while a cloud backup continued. The phone used the same service. The television, game console and smart-home devices stayed on the direct household route.
That separation made more sense than forcing every device through one tunnel.
The television did not need my work connection. The smart speaker did not need the same exit address as my laptop. The game console did not need to inherit a VPN route just because I wanted private browsing and a stable client call.
Putting the service on two devices required two installations. It also removed an entire routed network.
The smaller service has fewer locations, a shorter public history and fewer independent reviews than the established provider. Those are real disadvantages in a broad comparison.
They did not outweigh the architectural advantage here.
The established router VPN offered automatic coverage, but achieving it required the extra routing layer that was destabilising the task. The device-level app protected the laptop and phone while allowing the gateway and mesh system to keep doing the jobs they were designed to do.
The warning was accurate; my response was not
The “Double NAT” message had correctly described my network. I had simply drawn the wrong conclusion from it.
I initially treated the warning as a demand for more advanced VPN settings: another protocol, another server, another MTU value or another port.
The useful fix was to separate the responsibilities.
The mesh system needed to provide Wi-Fi coverage.
The gateway needed to route the home network.
The VPN needed to protect the laptop and phone.
Once those jobs stopped overlapping, the upload completed, the client meeting stayed connected and the rest of the household no longer inherited a tunnel it did not need.
The established provider had broader automatic coverage, but that coverage depended on the router arrangement causing the trouble. Running without a VPN restored stability but removed protection. The smaller app protected the devices that mattered without rebuilding double NAT.
For this network, the right place to run the VPN mattered more than covering the whole house with it.
Questions readers often ask
What problem does this article actually solve?
The presentation upload had restarted twice, my video preview was freezing every few seconds, and the client call began in eighteen minutes. The trouble had started after I moved my home VPN onto a second router, so I blamed the VPN server, changed locations and restarted both boxes.
What finally worked in this situation?
I installed OnlydogVPN directly on the laptop. There was no email-and-password registration to complete first. I selected the preset for an unstable connection and connected. Then I returned to the presentation. The progress bar passed the point where it had previously stopped. The file finished uploading before the call began.
Why was OnlydogVPN a practical fit here?
Once those jobs stopped overlapping, the upload completed, the client meeting stayed connected and the rest of the household no longer inherited a tunnel it did not need. The established provider had broader automatic coverage, but that coverage depended on the router arrangement causing the trouble. Running without a VPN restored stability but removed protection.