User Profile
mrc3
Newbie Caller
Joined 2 years ago
User Widgets
Contribuciones
Re: Is anyone else having problems with a changing IP address?
The binding of IP addresses to Geography is lucky happenstance that is not legislated or mandated. It is generally offered as a third party service by companies such as Maxmind, who make an effort to maintain their mappings for use by other companies. The reason it mostly works, is that companies are allocated IP address ranges and generally those ip address ranges are associated with an internet access point somewhere on the globe. The IP address allocated to your region of Connecticut has been assigned to t-mobile. Perhaps t-mobile moved it from Puerto Rico to Connecticut, or perhaps the geo-location vendor mapped in incorrectly. If it matters to you, contact the webmaster of speedtest and find out who their geolocation provider is. Then contact that vendor to let them know of the incorrect data. Mike28Visto0likes0ComentariosRe: Is anyone else having problems with a changing IP address?
So the device has already NAT'ed my address to map between IPV6 and IPV4 with the first persistent TCP connection that is made. Why does the device need to map a NEW IPV4 address for the next connection that goes out? Just lazy software implementation? Even if they have overallocated their NAT pool, the other members of the TCPtuple (source port primarily) should be able to chosen to make the NAT translation unique for a given destination address and port. Mike17Visto0likes0ComentariosRe: Rapid changes in my Dynamic IP Address
Yep, this is a mess, I do not think it is intentional, rather a misconfiguration of NAT64 device, or faulty firmware for said device that has been rolled out to Minneapolis region first. Again, your IP address is NOT really changing.. However at the NAT device within T-mobiles Minneapolis core, a new source IP address is being utilized for the NAT translation for every new outbound connection. Another possible reason would be that they have deployed a set of NAT64devices behind a load balancer, and your traffic is being "load balanced" to a different NAT64device with each newconnection. In any case, traffic from your real IP address, if it needs to be NAT'ed, but be NAT'ed to the same outbound side source address for every new connection, otherwise it breaks a great many sites on the internet and renders the internet gateway unusable. It is easy to confirm that NAT is taking place, by using your t-mobile phone hotspot, and look at the the IP addresses that have been assigned by DHCP to your phone. (The internet gateway does not appear to let you see this information). Go to any of a number of hosts that display your IP and note that the IP address the site reports, is not the IP address assigned to your phone. Go to a different site that reports your IP address, note that it is different, and also note that your phone's IP address has not changed. Mike24Visto0likes0ComentariosRe: Rapid changes in my Dynamic IP Address
Yep, using a VPN is a workaround for the T-mobile NAT issue (Your IP address is not really changing, just the t-mobile NAT's (network address translation) it differently for every new connection to a different destination IP). if your IP was actually changing, the VPN would be disconnected every time it changed. By using a VPN you are using the VPN providers to be your exit point for all your traffic that goes out to the internet, and they do not have a NAT issue. Mike19Visto0likes0ComentariosRe: Is anyone else having problems with a changing IP address?
t-mobile loves to blame this as normal dynamic IP address assignment which it is NOT. The IP address of traffic leaving your gateway (house) is NOT really changing (well it is changing as often as it normally does with dynamic ip assignment, which is rarely). As evidence, if your gateway IP address changes, every existing connection will be terminated. Downloads, video streams, chat connections, etc. this is not happening. What is happening is that a device within t-mobile is doing NAT (network address translation) and using a different source address for every new connection to a different destination IP address. IT SHOULD NOT BE DOING THIS as it causes problems like this, especially with cloud based servers where the a given DNS host name has multiple IP addresses. The NAT device needs to disregard the destination address in it's NAT lookup for new connection attempts. This is best demonstrated using a phone (which has the same problem on t-mobile as the gateways)…But the phone allows you to see the IP addresses assigned to your device. Using your phones web browser, go to a website which reports your IP address…note that it DOES NOT match your phones IP address. This is because of the translation that is taking place. Note you may have two IP addresses assigned and IPV6 address and an IPV4 address. There is another way of demonstrating this problem using multiple sites that report IP address of your connection, but that is less reliable. This is an internal practice of t-mobile that appears to be related the Minneapolis Geography and breaks internet conventions and assumptions used by many servers. Maybe someday somebody will get high enough up into the t-mobile engineering team to reach somebody who understand the technology and equipment that they use and correct the issue. Mike10Visto1like0Comentarios