Interesting I'm on an even older version 2.8.8 - because frankly if it ain't broke don't fix it. Namely I had to go though some hell years back to get tunnel adapter driver version right for any decent throughput performance on winsrv2k8r2 in vm or out, got everything just right finally using older version tap and so was paranoid about the 2.10.x+ installers trying to automatically install a new one - or so I read at the time, along with auto enabling all this network lock stuff I don't need\want by default that I forever pushed off touching anything. Anyway, I've had no problems of late with 2.8.8 that the post is about.
That said I got the popup message today via the software that I should upgrade, and it's been on my mind anyway (was waiting for 2.16. with ip6 to get stable\mature before screwing with it) but will attempt to move to 2.15.x give the nudge from air and 2.0 infrastructure rolling out. Can anyone anwser off hand if 2.15.x it's going to try to install the newer tap driver and turn on network lock by default or are those options during\before install now in 2.15.x? Guess I should go find that old thread thread with the 9.something.2 and .3 driver before starting so I have it as a backup, cause I'm nearly positve the latest will be problematic - for me.
Network lock will not run at installation and by default does not run when the app is started. (you can enable it to run at app startup if you wanted to do so) So, you should be happy with that.
I haven't heard much complaining of tap drivers for a while now so the newest one may be OK??? Somebody else will have to answer that specific question.
I was connected to another AirVPN server the other day and rarbg was telling me my IP was banned. It wouldn't let me post comments to torrents, or vote on comments, or look past page 2 of the list of torrents.
But, I had no problems downloading torrent files.
I went to another AirVPN server and had no problems. Obviously there are users of AirVPN who are morons and cause problems for the rest of us.