[Q] Can't connect to any Google services without first going through T-Mobile

In a browser google resolves to an address in the 208.54.0.0/16 IP address block (example 208.54.38.51). This range is not owned by Google as far I know and actually resolves to tmodns.net, which is owned by T-Mobile.

Looking through Afwall+ firewall logs shows that before connecting to any Google services, for example downloading an app through the play store, the phone connects with an IP in the same 208.54.0.0/16 range. Using IPTABLES to block this range prevents me from being able to do things like access Google in the browser and download apps through the play store.

If I start transparent proxying through Tor I can connect to Google correctly as well as download apps with no problems.

Can anyone confirm that this happens on their T-Mobile phone? Is there anyway I can prevent this without having to go through Tor? Perhaps by using IPTABLES to redirect any connections to the 208.54.0.0/16 block to an IP owned by Google.

I also have my DNS set to use Google's DNS servers so that shouldn't be the issue. It seems like it's happening inside of T-Mobile's internal 10.*.*.* network before the phone connects to the outside Internet.

Show Accepted Answer

Guest Quick Reply (No URL, BBcode or HTML)

Last post by emmitt.schoen
3 hours ago
Last post by garrett.collins
17 minutes ago
Last post by yost.gloria
2 hours ago
Last post by emmanuelle51
43 minutes ago
Last post by monahan.magali
14 minutes ago
Last post by sanford.adriel
23 minutes ago
Last post by raleigh32
1 hour ago