[Q] Ip address switches between tmobil and DoD

Search This thread

startswithp

New member
Apr 3, 2012
4
0
houston
So no to long ago I decided I would check the my phone's ip address and came across some questionable stuff. Here's my question:

1) How is it that my phone's ip address can change from being registered to tmobil on a 100.x.x.x address to sporadically being registered on DoD 30.x.x.x address?

2) How can it still happen even after I installed android firewall?

Conditions are always the same. I don't download any shady anything's. I pay for my rhapsody account and that's as far as my file sharing goes. I never have my WiFi enabled.

Any ideas or let me know what info you'd need to better access the situation. Thanks.
 

Attachments

  • tmp_IMG_20140503_214153-2006523151.jpg
    tmp_IMG_20140503_214153-2006523151.jpg
    126.8 KB · Views: 102
  • tmp_IMG_20140503_2143081992091443.jpg
    tmp_IMG_20140503_2143081992091443.jpg
    128.9 KB · Views: 99

krelvinaz

Senior Member
Feb 20, 2008
2,729
649
Mesa AZ
Without knowing what the allocated ip address really was, there it's really no way of knowing who the current owner of the block is, many blocks are relocated and may no longer be with who they used to be with, especially ipv4 blocks.

Not sure what android firewall would have to due with what the remote ip you are being allocated to with your dhcp network connection.

You should have no real control over what your network connection is given when you connect, other than possible controlling ipv6 vs ipv4.
 
Last edited:

startswithp

New member
Apr 3, 2012
4
0
houston
Without knowing what the allocated ip address really was, there it's really no way of knowing who the current owner of the block is, many blocks are relocated and may no longer be with who they used to be with, especially ipv4 blocks.

Not sure what android firewall would have to due with what the remote ip you are being allocated to with your dhcp network connection.

You should have no real control over what your network connection is given when you connect, other than possible controlling ipv6 vs ipv4.

So does this help? the firewall lets me know that even though I have set it up to refuse the block of addresses in which in resides, they're still connection to my phone.

Not sure I'm understanding you anyway. You telling me they temporarily relocate my up because they re no longer with.... yet after a few minutes , sometimes hours, I'm right back to the same ip?
 

Attachments

  • tmp_Screenshot_2014-05-03-23-33-24-2006523151.jpg
    tmp_Screenshot_2014-05-03-23-33-24-2006523151.jpg
    151.5 KB · Views: 96
Last edited:

chipworkz

Senior Member
Dec 28, 2011
1,749
3,034
What he was saying I believe is that the IPv4 allocations have been changing do to the available IP address blocks running thin. Companies were encouraged to give up IP blocks that they weren't actually using. In simple terms, a company might have originally owned a block of 100,000 IPs but never actually used more than 50,000. So they gave back a block of 50,000 so another company(s) could use them instead.
 

Eric214

Senior Member
Oct 24, 2012
1,650
551
Philly
I don't believe the IP address' are static on a carrier. I'm not sure but each time you connect to the carrier network (no signal or airplane mode) you could be giving a fresh IP address. Also that is certainly the case if you are on a WiFi network. Unless you phone was set up as a static connection, you would likely receive a new lease on an IP address.
 

krelvinaz

Senior Member
Feb 20, 2008
2,729
649
Mesa AZ

Exactly. Internal allocate IP's are normally Natt'd and not actuall the IP you show up on the Internet as.

When you connect to your provider for Network (not using WiFi), the provider (most likely T-Mobile) will allocate an IP to you via DHCP. That IP is what your phone uses to talk to the provider. It most likely is NOT what you look like when you hit the Internet though, that will most likely be a different IP because TMobile is most likely not providing you with an Internet routable IP.

So, right now, I turned off WiFi and I got the IP 100.143.28.84. When my phone touches the Internet though, it shows up as 206.29.182.169.

So at that point in time, my phone is using 100.143.28.84 to get to T-Mobile's network and the Internet sees my phone as 206.29.182.169. the outside IP is in TMobiles published block. And why the internal IP is also, it really doesn't matter what it is because that is not what your phone looks like when it gets to the Internet.

It is possible in your area there are different networks available internally that are given to you when you connect depending on where you physically are and what towers you are closest to. At some times you get the 100.x network and you might even get the same IP as before because of a lease of that IP to your device, but then you move to a slightly different area which is handing out 30.x addresses. All perfectly normal. and the internal IP's really don't matter much.

You can use a search of Whats My IP to see what the Internet thinks your IP is when you get there.

With some providers (Verizon for example) if you are using ipv6, you will always get a non-routable IP, meaning that if you figure out your Internet IP, an outside connection may not get back to you unless your device initiated the connection, but if you use ipv4, they gave you a temp IP that would end up with a routable IP back. You could then use that to connect to your phone using something like VNC or other service. Now days, that is much more likely not the case unless you are paying for that special IP service. I don't know if Tmobile offers that type of service, but Verizon did at least a year or two ago.

In anycase, you firewall shouldn't matter unless you don't want to access your providers network.

4usu2uvu.jpg


7e6utapu.jpg
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2

    Exactly. Internal allocate IP's are normally Natt'd and not actuall the IP you show up on the Internet as.

    When you connect to your provider for Network (not using WiFi), the provider (most likely T-Mobile) will allocate an IP to you via DHCP. That IP is what your phone uses to talk to the provider. It most likely is NOT what you look like when you hit the Internet though, that will most likely be a different IP because TMobile is most likely not providing you with an Internet routable IP.

    So, right now, I turned off WiFi and I got the IP 100.143.28.84. When my phone touches the Internet though, it shows up as 206.29.182.169.

    So at that point in time, my phone is using 100.143.28.84 to get to T-Mobile's network and the Internet sees my phone as 206.29.182.169. the outside IP is in TMobiles published block. And why the internal IP is also, it really doesn't matter what it is because that is not what your phone looks like when it gets to the Internet.

    It is possible in your area there are different networks available internally that are given to you when you connect depending on where you physically are and what towers you are closest to. At some times you get the 100.x network and you might even get the same IP as before because of a lease of that IP to your device, but then you move to a slightly different area which is handing out 30.x addresses. All perfectly normal. and the internal IP's really don't matter much.

    You can use a search of Whats My IP to see what the Internet thinks your IP is when you get there.

    With some providers (Verizon for example) if you are using ipv6, you will always get a non-routable IP, meaning that if you figure out your Internet IP, an outside connection may not get back to you unless your device initiated the connection, but if you use ipv4, they gave you a temp IP that would end up with a routable IP back. You could then use that to connect to your phone using something like VNC or other service. Now days, that is much more likely not the case unless you are paying for that special IP service. I don't know if Tmobile offers that type of service, but Verizon did at least a year or two ago.

    In anycase, you firewall shouldn't matter unless you don't want to access your providers network.

    4usu2uvu.jpg


    7e6utapu.jpg
    1
    Found this which sounds similar to what you are seeing.

    https://blog.wireshark.org/2010/04/t-mobile-clever-or-insane/