[tor-talk] Tor and Google error / CAPTCHAs.

[Mirimir]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/07/2016 02:16 PM, Joe Btfsplk wrote:
> On 10/5/2016 11:23 AM, Mirimir wrote:
>> 
>> Yes, it's partly that residential IPs are (or have been, anyway) 
>> dynamic.
> I guess that depends on the provider and exact type of service.
> AT&T "digital" (Uverse) residential internet hasn't had dynamic
> IPa's for several yrs. In many places, they discontinued DSL
> service, forced you into Uverse, then jacked up prices.  As did
> some other providers, in some areas. Some people  near me say they
> also have static IPa on other providers.
> 
> I don't know if static IPa are now easier / cheaper for them to 
> provide.  Used to be the opposite - static cost more. Or, if static
> IPa's make it easier for all concerned to track users long term?

It's just that many ISPs are running low on IPv4 addresses, I think.

> I've tried to change IPa - to see if it's possible.  Didn't work.
> It may be possible (read quite a bit on it), but not easy.  AFAIK,
> not something that will happen in a few minutes or hours. Some say
> they power down modem / router / computer for days.  When they 
> restart, have the same IPa.
> 
> Apparently, the provider reserves that address, until maybe you 
> discontinue service.  I'm sure the company provided (required)
> modem has, or gets a unique identifier when you register  for the
> 1st time.

With static IPv4, ISPs typically assign based on your router's MAC.
And that's all typically related to your account. So changing router
MAC doesn't even work. If you want a new IPv4, just use VPNs :)

Look at <https://luminati.io/>. Access to 20,000 static (datacenter?)
IPv4s costs $1 per GB, with a $250/month minimum, whereas access to
13.5 million residential IPv4s (aka Hola users) costs $12.50 per GB,
with a $500/month minimum.

> I'm guessing, even if you found how to delete that, then you
> couldn't access their service, until you called & did the process
> again.

Probably not.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJX+PoVAAoJEGINZVEXwuQ+dAgH/112RTiJPaunFiWjcT6n9+U0
elHjyJN5uFbzb1J9bSyjDdoGspwzFvIvP9mqzvJgTecCQoa686uWkI/1ZVPCFL6P
C8X48CIKTfo4rj/AxCNkBl8c911NVOB9YrHQZ8uSTw4AJikaMQTbGWPWthEfVOKV
D82MmGaEsObXvIjz8MyHcx7bf59cpbvevo3fxHQ86OPoIhRgQiyTyVAX4ZIKy1sG
kEPgNjztpzgjwKqYMzYtVKs6xCWGE2xWumW9AOgstK1v4bB5WG/trTqvz+6w4KnY
kC+GOYQdilekcZnkOZCCoZTHA/UceuaRSmEe8U11ptFHaE15sQK2U4Q3DBGzIQU=
=1Q6N
-----END PGP SIGNATURE-----