[saosebastiao]

I've been using one pretty consistently ever since the legislation passed allowing ISPs to sell your browsing history. I generally don't have any problems with it, but that isn't to say it is not problematic:

* Connection issues are really annoying. At home it is manageable, but reconnecting to a different wifi network with a phone introduces a delay that sometimes lasts minutes before it becomes functional again

* Some websites make you enter captchas in order to use them, probably due to VPN abuse by malicious users. Others outright block traffic to any detectable VPN traffic.

* It is slower in general, but the worst case slowness seems much worse and more common. Unavoidable really, you're introducing another potential point of failure.

* Useful LAN functions (like *.local domains) become non-functional

[derefr]

> Useful LAN functions (like .local domains) become non-functional

Is that true if you 1. disable the "force all DNS traffic over VPN" setting, but then 2. have a local resolver (e.g. dnsmasq) that resolves LAN domains but forwards all other traffic to a DNS server on an IP that will end up routed through the VPN?

[saratogacx]

I'm not sure if your methods would fix the issue but you can get around it if your router supports acting as a VPN client. After you configure the connection it becomes invisible to all your lan clients and you can use all of your local network goodies.

[spccdt]

Do you happen to have a link to the legislation you mention?

[0xfeba]

https://www.cnbc.com/2017/03/28/congress-clears-way-for-isps...

Congress removed FCC regs. that would have prevented it. ISPs have been claiming both the regulation is unneeded but that they won't sell your data.

[vlod]

Googling this gives you lots of links: "isp sell browsing history"

Here's arstechnica: https://arstechnica.com/information-technology/2017/03/how-i...