Sean Posted October 24, 2019 CID Report Share Posted October 24, 2019 Over the past few years, the Irish Three mobile network has prioritised certain types of traffic on its network. This includes the likes of Google services (e.g. YouTube), CloudFlare, some Microsoft services and certain hosts. In the past, this included traffic over certain port #s such as port 8080 that Ookla's Speedtest traffic runs over. This also made it possible to exploit the traffic prioritisaton by making a VPN connection over port 8080, however, they (and Vodafone Ireland) stopped traffic shaping by port # shortly after I posted about it. With Cloudflare recently launching a privacy App 184.108.40.206 for Android, it made me wonder if I could exploit Cloudflare's traffic prioritisation with its WARP+ service. I purchased the Unlimited subscription to try, but quickly ran into a problem. While the service worked over Wi-Fi, I could not browse the web over Three's mobile data and Apps had no connectivity. After doing some diagnostics, I found that WARP+'s DNS queries were not getting through, but TCP connectivity was working. This is surprising giving than the 220.127.116.11 App is supposed to securely encrypt DNS queries back to Cloudflare. Since connectivity by IP address was working, this gave me an idea - Enable DNS over HTTPS on Firefox for Android: Enter the address: about:config Change network.trr.bootstrapAddress to 18.104.22.168 Change network.trr.mode to 3 This gave me Internet connectivity in the Firefox App until I disconnected WARP+. I had to change network.trr.mode to 2 for Firefox to work once I disconnected WARP+. While the other Apps still had no connectivity with WARP+ enabled, I was mainly interested in running speed tests. In Ballybofey with a good 4G+ signal on Three, I ran TestMy on every server with a linear 50MB block size with WARP+ disconnected. I then enabled WARP+ and reran the tests. Here are the download speeds in Mbps: While Cloudflare's 22.214.171.124 made a substantial difference, I believe this is mainly down to Three's traffic shaping of Cloudflare traffic. It's interesting to see that even Sydney at the opposite side of the globe to me got nearly a 10x speed boost. The Los Angeles TestMy server appears to be on a server that Three prioritises as repeat tests consistently deliver around 70Mbps when even Ookla's speed test with local servers couldn't achieve anything higher than the 30s. From testing Three's masts in different areas, it appears that most (if not all) Three's 3G masts and certain 4G masts are not affected by traffic shaping. For example, in Donegal town I get much better speed with a direct connection than over 126.96.36.199 WARP+. London,GB - Direct connection vs 188.8.131.52 WARP+: Frankfurt, DE - Direct connection vs 184.108.40.206 WARP+: Sydney, AU - Direct connection vs 220.127.116.11 WARP+: I didn't have enough time to test all the servers, but it's clear that WARP+ was actually slowing down my connection in this location. Based on the London speed test, it's quite possible Three don't apply traffic shaping to masts fed directly into the fibre network. Whenever Cloudflare releases this service for the desktop, I will carry out some testing over a tethered / Hotspot connection as Android bypasses any VPN connection when tethering is enabled. Jardee and CA3LE 2 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.