GL.iNet X2000 Using Hotspot Data Instead of Mobile Data After Switching to Warp (Verizon)

Routers
1

Hi everyone,

I’ve been using a GL.iNet X2000 router with US Mobile, and I’m running into an issue after switching networks.

Previously, I was on US Mobile Dark Star (AT&T), and everything worked fine — all usage was counted as regular mobile data.

Recently, I switched to Warp (Verizon), and now all my data usage is being counted as hotspot/tethering data instead of mobile data.

Here’s my setup:

  • Device: GL.iNet X2000

  • Carrier: US Mobile (Warp – Verizon)

  • IMEI spoofed to a Samsung S21

  • TTL / HL set to 65

  • ipv4 only

With the same configuration, it worked perfectly on AT&T, but on Verizon it seems like tethering is being detected.

Questions:

  • Is Verizon (Warp) more strict about detecting tethering compared to AT&T?

  • Are there additional settings (TTL, HL, etc.) that need to be adjusted for Verizon?

  • Has anyone successfully avoided hotspot detection on Warp with this router?

Any advice or shared experiences would be appreciated.

Thanks in advance!

2

Hi

Some carriers may deploy and enforce DPI for detection, so there may be no easy way to bypass these restrictions.

4

I think Will is correct in that Verizon is using some sort of DPI to detect tethering. Back when I was using Verizon’s Visible service I had to combine a VPN with the TTL mod to bypass the tethering throttle. I also use US Mobile but with a X3000. I am currently using Dark Star and as the OP experienced, it is not registering hotspot data even without the VPN. I don’t have any plans to switch over to Warp in the near future but when I do I’ll report back with my findings.