News for hackers. Stuff that matters.

A comment on The FBI's internal guide for getting data from AT&T, T-Mobile, Verizon.

Re:The FBI's internal guide for getting data from AT&T, T-Mo... by gzer0 on Monday October 25, 2021 @02:57PM (#28991670)
Sprint cannot currently translate IPV4 addresses (ex. 152.138.17.240) to an actual phone number

Sprint may be able to translate IPV6 addresses (ex. 001:0db8:0000:0042:0000:8a2e:0370:7334) to a phone number.

Interesting, anyone know which aspect of the IPV6 protocol allows for this?

[ Parent | on HN ]
Re:The FBI's internal guide for getting data from AT&T, T-Mo... by bibaheu on Monday October 25, 2021 @03:00PM (#28991718)
Probably IPv4 is on CGNAT and Sprint doesn't keep the logs of the translation. On IPv6 there's no NAT, and there might be a deterministic relationship between subscription and IP
[ Parent | on HN ]
Re:The FBI's internal guide for getting data from AT&T, T-Mo... by glogla on Monday October 25, 2021 @03:03PM (#28991752)
That, or they don't give devices IPv4 addresses at all and run 464XLAT - according to Wikipedia, quite a few telcos do it that way.
[ Parent | on HN ]
Re:The FBI's internal guide for getting data from AT&T, T-Mo... by p1mrx on Monday October 25, 2021 @04:30PM (#28992746)
464XLAT is a form of CGNAT.

The main difference is whether the subscriber side uses an IPv6 or private IPv4 address, but on the internet side they are equivalent.

[ Parent | on HN ]
Re:The FBI's internal guide for getting data from AT&T, T-Mo... by keneda7 on Monday October 25, 2021 @03:28PM (#28992036)
I believe you are correct.

https://news.ycombinator.com/item?id=16440850

[ Parent | on HN ]