First hop out of LTE tracing to Google in Straya? and Strange Cellular Device Nets... a rabbit hole

I was playing around with NET-Toolbox on iOS (literally one of the only ios applications I've ever paid money for, have used, and would still highly recommend ~ non affiliated shilling over).

Shower thoughts: I was curious if my phone's public LTE IP was a local tower IP, and I'm actually NAT'd by their equipment or if my phone is literally getting a public address. Well, if I 'curl icanhazip.com' from my phone, it returns a public ipv4 address, so I sincerely doubt my phone is pulling out of some dhcp pool of public ipv4s. Plus traceroutes out are bouncing around a 10. range, so it looks like I'm hitting some internal equipment before routing out to the rest of the nets...

BUT WAIT, my phone actually says its "LAN" ip is 192.0.0.1 wtf...that's public space

Oh, that's neat... it's not, I've never heard of this "The IP range 192.0.0.0 - 192.0.0.7 is not a public IP block. This block is used for DS-LITE, a technology for sharing an single IPv4 address among multiple broadband customers by combining IP in IP and Network Address Translation. It was assigned by the IETF in the Standards Track document, RFC 6333"

So DS-Lite is doing some weird mutant NAT'ing and what not, I need to go read up on it...

Still, there's that ipv4 public address I'm curling that I now suspect is the DS-Lite gateway or something. I'd expect to hit that gateway on my traceroutes out, but that doesn't appear to happen. I don't know why... but I suspect I might find the answer in that RFC.

This is where the google.com trace comes in, my first hop out of the 10. range hits 72.14.242.140

The Net Toolbox tool is telling me this server is located in Australia, but a couple of geoIP and whois searches tell me it's a google owned address and returns Mountainview, so I don't know if it's just returning their corporate address, and Net-Toolbox is returning correct info, or if NetToolbox is wrong or what. There are 3 more hops after it, and those 3 are returning as US servers.

It's kind if unintuitive for a stateside trace to Google to bounce out to Straya, unless I slam on that tin foil hat and note that the Patriot Act allows for the unsolicited hoovering of any packets leaving US borders.

I figured I'd dump this here and see what yall think, gonna poke at it some more tomorrow.