Mobile hotspot IP Address
up vote
0
down vote
favorite
Let's say I am in Oregon and I have a mobile hotspot with a Maine phone number. When I connect to that hotspot on my laptop, would my public IP show from a range in Oregon or Maine? Are there any circumstances, other than using a proxy, under which I would show an IP from a region besides the one I'm in?
The carrier is T-Mobile.
ip hotspot mobile-broadband
add a comment |
up vote
0
down vote
favorite
Let's say I am in Oregon and I have a mobile hotspot with a Maine phone number. When I connect to that hotspot on my laptop, would my public IP show from a range in Oregon or Maine? Are there any circumstances, other than using a proxy, under which I would show an IP from a region besides the one I'm in?
The carrier is T-Mobile.
ip hotspot mobile-broadband
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Let's say I am in Oregon and I have a mobile hotspot with a Maine phone number. When I connect to that hotspot on my laptop, would my public IP show from a range in Oregon or Maine? Are there any circumstances, other than using a proxy, under which I would show an IP from a region besides the one I'm in?
The carrier is T-Mobile.
ip hotspot mobile-broadband
Let's say I am in Oregon and I have a mobile hotspot with a Maine phone number. When I connect to that hotspot on my laptop, would my public IP show from a range in Oregon or Maine? Are there any circumstances, other than using a proxy, under which I would show an IP from a region besides the one I'm in?
The carrier is T-Mobile.
ip hotspot mobile-broadband
ip hotspot mobile-broadband
asked May 25 '16 at 17:36
lyonsinbeta
10112
10112
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05
add a comment |
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05
add a comment |
3 Answers
3
active
oldest
votes
up vote
0
down vote
I'm not either in Oregon or Maine, but from my experience with networking - there is no bigger ISP which would have one big IP address pool for whole US.
Usually IP pools are dedicated per area, and size of area is up to ISP. ISP could set IP pool for users from some region depending on their usernames (it's technically possible), but I never heard for such case.
Having that in mind, if you are not OK with IP you get, you can use either proxy or VPN, whatever and whichever suits you better. If you set VPN on your device, then all network apps will see your VPN IP address, if you use proxy - only apps you set to use proxy will have proxy IP address.
So if you need to "cover all your tracks", VPN is better, as no app you are using will have "wrong" IP address.
Edit: Geolocation by IP address using IPv4 MAY be wildly inaccurate.
Two simple examples:
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country.
If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away. :)
ISP have IP pool DB which is shared by several regions, which are wide apart. In such (rare, but possible) setup only part of IP addresses would be geolocated right, and other would/could have city/state or even continent wrongly attributed. I do not know of such setups for different continents :), but I have found that IP geolocation could easily miss city for 200 or 300 miles. Of course, that depends on your ISP, I speak only from my experience.
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
add a comment |
up vote
0
down vote
It is up to the provider to give you an ip address. It is very likely that if you frequently connect to your ISP's network, they will give you the same IP address as long as you are connected to their network.
Usually when you go out of the range of your own provider, you are connected to another provider's network who's relaying the traffic back to your provider. At least that's what happens in europe. I'm not from the US, so I'm not entirely sure if the provider has network access points throughout the entire region, or that they have to resort into allowing you access through a third-party.
If you go through a third-party, the networkname would reflect that by a change, and obviously you will get a new ip address. If the networkname stays the same, it is possible your ip address also remains the same, but it can change too.
That said, The IP Address protocols do not have a feature called geo location. This means that there is no way to trace your geo location based on your IP Address. So in order to compensate, many websites track your ip address and request your geo location through other means such as the geo information your phone uses. Wifi also has geo location features, and a router is capable of determining its geo location too.
Once a website tracks your ipaddress and is able to also get the geo location information (some websites will trigger: this website wants to know your geo location. Allow?) it can then store this into its database and share it with other web services to build a large database where other websites can query your geo location based on ip address. Because ip addresses change, it is very likely that in the past, someone with your ip address allowed access and shared its geo location to that website.
The database reflects that geo location to the current ip address even though it is false. Whether that geo location is close by or far away does not matter.
It does however state that its unknown what the geo location will match when you query the ipaddress.
I hope you understand where I'm coming from.
add a comment |
up vote
-1
down vote
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country. If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I'm not either in Oregon or Maine, but from my experience with networking - there is no bigger ISP which would have one big IP address pool for whole US.
Usually IP pools are dedicated per area, and size of area is up to ISP. ISP could set IP pool for users from some region depending on their usernames (it's technically possible), but I never heard for such case.
Having that in mind, if you are not OK with IP you get, you can use either proxy or VPN, whatever and whichever suits you better. If you set VPN on your device, then all network apps will see your VPN IP address, if you use proxy - only apps you set to use proxy will have proxy IP address.
So if you need to "cover all your tracks", VPN is better, as no app you are using will have "wrong" IP address.
Edit: Geolocation by IP address using IPv4 MAY be wildly inaccurate.
Two simple examples:
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country.
If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away. :)
ISP have IP pool DB which is shared by several regions, which are wide apart. In such (rare, but possible) setup only part of IP addresses would be geolocated right, and other would/could have city/state or even continent wrongly attributed. I do not know of such setups for different continents :), but I have found that IP geolocation could easily miss city for 200 or 300 miles. Of course, that depends on your ISP, I speak only from my experience.
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
add a comment |
up vote
0
down vote
I'm not either in Oregon or Maine, but from my experience with networking - there is no bigger ISP which would have one big IP address pool for whole US.
Usually IP pools are dedicated per area, and size of area is up to ISP. ISP could set IP pool for users from some region depending on their usernames (it's technically possible), but I never heard for such case.
Having that in mind, if you are not OK with IP you get, you can use either proxy or VPN, whatever and whichever suits you better. If you set VPN on your device, then all network apps will see your VPN IP address, if you use proxy - only apps you set to use proxy will have proxy IP address.
So if you need to "cover all your tracks", VPN is better, as no app you are using will have "wrong" IP address.
Edit: Geolocation by IP address using IPv4 MAY be wildly inaccurate.
Two simple examples:
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country.
If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away. :)
ISP have IP pool DB which is shared by several regions, which are wide apart. In such (rare, but possible) setup only part of IP addresses would be geolocated right, and other would/could have city/state or even continent wrongly attributed. I do not know of such setups for different continents :), but I have found that IP geolocation could easily miss city for 200 or 300 miles. Of course, that depends on your ISP, I speak only from my experience.
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
add a comment |
up vote
0
down vote
up vote
0
down vote
I'm not either in Oregon or Maine, but from my experience with networking - there is no bigger ISP which would have one big IP address pool for whole US.
Usually IP pools are dedicated per area, and size of area is up to ISP. ISP could set IP pool for users from some region depending on their usernames (it's technically possible), but I never heard for such case.
Having that in mind, if you are not OK with IP you get, you can use either proxy or VPN, whatever and whichever suits you better. If you set VPN on your device, then all network apps will see your VPN IP address, if you use proxy - only apps you set to use proxy will have proxy IP address.
So if you need to "cover all your tracks", VPN is better, as no app you are using will have "wrong" IP address.
Edit: Geolocation by IP address using IPv4 MAY be wildly inaccurate.
Two simple examples:
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country.
If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away. :)
ISP have IP pool DB which is shared by several regions, which are wide apart. In such (rare, but possible) setup only part of IP addresses would be geolocated right, and other would/could have city/state or even continent wrongly attributed. I do not know of such setups for different continents :), but I have found that IP geolocation could easily miss city for 200 or 300 miles. Of course, that depends on your ISP, I speak only from my experience.
I'm not either in Oregon or Maine, but from my experience with networking - there is no bigger ISP which would have one big IP address pool for whole US.
Usually IP pools are dedicated per area, and size of area is up to ISP. ISP could set IP pool for users from some region depending on their usernames (it's technically possible), but I never heard for such case.
Having that in mind, if you are not OK with IP you get, you can use either proxy or VPN, whatever and whichever suits you better. If you set VPN on your device, then all network apps will see your VPN IP address, if you use proxy - only apps you set to use proxy will have proxy IP address.
So if you need to "cover all your tracks", VPN is better, as no app you are using will have "wrong" IP address.
Edit: Geolocation by IP address using IPv4 MAY be wildly inaccurate.
Two simple examples:
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country.
If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away. :)
ISP have IP pool DB which is shared by several regions, which are wide apart. In such (rare, but possible) setup only part of IP addresses would be geolocated right, and other would/could have city/state or even continent wrongly attributed. I do not know of such setups for different continents :), but I have found that IP geolocation could easily miss city for 200 or 300 miles. Of course, that depends on your ISP, I speak only from my experience.
edited Jun 2 '16 at 16:17
answered May 25 '16 at 18:39
stemd
34614
34614
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
add a comment |
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
I didn't consider my question in the light you seem to be answering it in until you answered, so thanks for that. :-) This isn't about covering my tracks or being choosy about my IP, I'm just curious about how mobile IPs are assigned and if it would ever be wildly inaccurate about my location. I'm not in Oregon or Maine either, I just picked them because they're far apart.
– lyonsinbeta
May 26 '16 at 3:02
add a comment |
up vote
0
down vote
It is up to the provider to give you an ip address. It is very likely that if you frequently connect to your ISP's network, they will give you the same IP address as long as you are connected to their network.
Usually when you go out of the range of your own provider, you are connected to another provider's network who's relaying the traffic back to your provider. At least that's what happens in europe. I'm not from the US, so I'm not entirely sure if the provider has network access points throughout the entire region, or that they have to resort into allowing you access through a third-party.
If you go through a third-party, the networkname would reflect that by a change, and obviously you will get a new ip address. If the networkname stays the same, it is possible your ip address also remains the same, but it can change too.
That said, The IP Address protocols do not have a feature called geo location. This means that there is no way to trace your geo location based on your IP Address. So in order to compensate, many websites track your ip address and request your geo location through other means such as the geo information your phone uses. Wifi also has geo location features, and a router is capable of determining its geo location too.
Once a website tracks your ipaddress and is able to also get the geo location information (some websites will trigger: this website wants to know your geo location. Allow?) it can then store this into its database and share it with other web services to build a large database where other websites can query your geo location based on ip address. Because ip addresses change, it is very likely that in the past, someone with your ip address allowed access and shared its geo location to that website.
The database reflects that geo location to the current ip address even though it is false. Whether that geo location is close by or far away does not matter.
It does however state that its unknown what the geo location will match when you query the ipaddress.
I hope you understand where I'm coming from.
add a comment |
up vote
0
down vote
It is up to the provider to give you an ip address. It is very likely that if you frequently connect to your ISP's network, they will give you the same IP address as long as you are connected to their network.
Usually when you go out of the range of your own provider, you are connected to another provider's network who's relaying the traffic back to your provider. At least that's what happens in europe. I'm not from the US, so I'm not entirely sure if the provider has network access points throughout the entire region, or that they have to resort into allowing you access through a third-party.
If you go through a third-party, the networkname would reflect that by a change, and obviously you will get a new ip address. If the networkname stays the same, it is possible your ip address also remains the same, but it can change too.
That said, The IP Address protocols do not have a feature called geo location. This means that there is no way to trace your geo location based on your IP Address. So in order to compensate, many websites track your ip address and request your geo location through other means such as the geo information your phone uses. Wifi also has geo location features, and a router is capable of determining its geo location too.
Once a website tracks your ipaddress and is able to also get the geo location information (some websites will trigger: this website wants to know your geo location. Allow?) it can then store this into its database and share it with other web services to build a large database where other websites can query your geo location based on ip address. Because ip addresses change, it is very likely that in the past, someone with your ip address allowed access and shared its geo location to that website.
The database reflects that geo location to the current ip address even though it is false. Whether that geo location is close by or far away does not matter.
It does however state that its unknown what the geo location will match when you query the ipaddress.
I hope you understand where I'm coming from.
add a comment |
up vote
0
down vote
up vote
0
down vote
It is up to the provider to give you an ip address. It is very likely that if you frequently connect to your ISP's network, they will give you the same IP address as long as you are connected to their network.
Usually when you go out of the range of your own provider, you are connected to another provider's network who's relaying the traffic back to your provider. At least that's what happens in europe. I'm not from the US, so I'm not entirely sure if the provider has network access points throughout the entire region, or that they have to resort into allowing you access through a third-party.
If you go through a third-party, the networkname would reflect that by a change, and obviously you will get a new ip address. If the networkname stays the same, it is possible your ip address also remains the same, but it can change too.
That said, The IP Address protocols do not have a feature called geo location. This means that there is no way to trace your geo location based on your IP Address. So in order to compensate, many websites track your ip address and request your geo location through other means such as the geo information your phone uses. Wifi also has geo location features, and a router is capable of determining its geo location too.
Once a website tracks your ipaddress and is able to also get the geo location information (some websites will trigger: this website wants to know your geo location. Allow?) it can then store this into its database and share it with other web services to build a large database where other websites can query your geo location based on ip address. Because ip addresses change, it is very likely that in the past, someone with your ip address allowed access and shared its geo location to that website.
The database reflects that geo location to the current ip address even though it is false. Whether that geo location is close by or far away does not matter.
It does however state that its unknown what the geo location will match when you query the ipaddress.
I hope you understand where I'm coming from.
It is up to the provider to give you an ip address. It is very likely that if you frequently connect to your ISP's network, they will give you the same IP address as long as you are connected to their network.
Usually when you go out of the range of your own provider, you are connected to another provider's network who's relaying the traffic back to your provider. At least that's what happens in europe. I'm not from the US, so I'm not entirely sure if the provider has network access points throughout the entire region, or that they have to resort into allowing you access through a third-party.
If you go through a third-party, the networkname would reflect that by a change, and obviously you will get a new ip address. If the networkname stays the same, it is possible your ip address also remains the same, but it can change too.
That said, The IP Address protocols do not have a feature called geo location. This means that there is no way to trace your geo location based on your IP Address. So in order to compensate, many websites track your ip address and request your geo location through other means such as the geo information your phone uses. Wifi also has geo location features, and a router is capable of determining its geo location too.
Once a website tracks your ipaddress and is able to also get the geo location information (some websites will trigger: this website wants to know your geo location. Allow?) it can then store this into its database and share it with other web services to build a large database where other websites can query your geo location based on ip address. Because ip addresses change, it is very likely that in the past, someone with your ip address allowed access and shared its geo location to that website.
The database reflects that geo location to the current ip address even though it is false. Whether that geo location is close by or far away does not matter.
It does however state that its unknown what the geo location will match when you query the ipaddress.
I hope you understand where I'm coming from.
answered Aug 8 '17 at 11:35
LPChip
34.9k54983
34.9k54983
add a comment |
add a comment |
up vote
-1
down vote
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country. If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
add a comment |
up vote
-1
down vote
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country. If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
add a comment |
up vote
-1
down vote
up vote
-1
down vote
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country. If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away
ISP does not have enough IP's in it's current IP pool, and it borrows IP range from larger ISP from some other region/country. If you get such IP, until IP pool geolocation data propagates, it will show you are somewhere else, and that somewhere MAY be wildly far, far away
answered Nov 26 '17 at 20:39
solid
1
1
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
add a comment |
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
2
2
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
Any references for this? Why wouldn't an ISP do some administration and fix the meta data of the IP range? It seems to me that routing might even require that meta data to be correct.
– Arjan
Nov 26 '17 at 20:49
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1080836%2fmobile-hotspot-ip-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can easily find this out.
– jpaugh
Oct 9 '17 at 21:05