21/09/2024, 10:28 PM
That's a real pity about the speed being throttled in a router, much like it is being treated as the former Vodafone X plan or what Three is performing like this evening here. In this case I will give Sky Mobile a miss as I was considering ordering it to run our VoIP landline over in place of the €20 prepay Vodafone SIM.
The browsing performance difference may be down to the DNS servers being laggy, however, getting 12Mbps consistently with the SIM in the router clearly indicates throttling.
Check if the speed is throttled from a tethered device such as a laptop connected to your phone. If tethering is also throttled to 12Mbps, they are likely checking the TTL value like what Verizon US does, which is where they check if the TTL value is off by 1 due to the additional hop from the router / phone. In this case you can try the following command in a Windows Admin command prompt to change the default TTL to 65 (from 64), so the TTL matches that of data connections from the phone:
netsh interface ipv4 set global defaultcurhoplimit=65
You can undo the change by putting by setting it back to 64, i.e.:
netsh interface ipv4 set global defaultcurhoplimit=64
The browsing performance difference may be down to the DNS servers being laggy, however, getting 12Mbps consistently with the SIM in the router clearly indicates throttling.
Check if the speed is throttled from a tethered device such as a laptop connected to your phone. If tethering is also throttled to 12Mbps, they are likely checking the TTL value like what Verizon US does, which is where they check if the TTL value is off by 1 due to the additional hop from the router / phone. In this case you can try the following command in a Windows Admin command prompt to change the default TTL to 65 (from 64), so the TTL matches that of data connections from the phone:
netsh interface ipv4 set global defaultcurhoplimit=65
You can undo the change by putting by setting it back to 64, i.e.:
netsh interface ipv4 set global defaultcurhoplimit=64