I use PIA across 3 boxes and I've not seen any issues.
Filtering will cause a reconnect to happen, but won't change the way the connection is made. I guess if there was an authentication issue, or a network issue, that re-connect might fail.
Share a log if it happens again.
No not everything can be filtered by addon, but you can filter on window ids which may work with pvr type applications. It's documented on the GitHub wiki
The repo is up to 5.0.6. I'm slacking updating the Github releases though - I'll get around to it when life is less hectic.
They're general Kodi coding standards, not add-on settings documentation, unless I'm missing something.
lusephur I can make the page open, but there are still many things broken in the compatibility code for the existing settings layout - such as conditional displays not working, and the filtering not displaying the selected values. If this code is not going to receive any further changes as you suggest, then there are going to be a lot of add-ons broken.
There's also no documentation for the new settings approach and I'm not going to guess at what changes to make based on some example XML.
So what I said before...
Providian623 - In Settings/Utilities there's a "Remove all downloaded VPN provider files". This will force it to fetch the latest files from Github.
I don't use betas - I don't even use the standard skin - if there are problems when a final release is made, I'll fix them then.
The API returns the servers dynamically so I don't need to store/update the them. If they change, then it doesn't matter - each time you connect it finds the best available server.
Pushed 5.0.5 onto the repo which re-introduces support for NordVPN using their API. You can now select which country you want to connect to and it'll do the right thing.
They also have their own branded add-on if you'd prefer to use that and want some friendly support.
BBC are good at not playing when you have a UK VPN (or rather are good at blocking VPNs). I get failures when I use a UK VPN from within the UK.
I always run with a static IP because I want to know where my box is when I want to ssh into it. DHCP will assign different IP addresses to it which I want to avoid. I also run exclusively IPv4 on my network because I like the 80s and only have a dozen devices to connect. I'm guessing that neither of these settings will affect the transfer speed.
The fact you're seeing crappy speeds on 2 different VPNs, which are generally well used (I think), suggests it's more like to do with your hardware or your network or even your ISP.
If you want to eliminate the addon, start the vpn using the command line using a profile downloaded from the VPN provider. All said, it's just a (well crafted) Linux box and your provider should be able to help using openvpn on the command line.
The log suggests all sorts of connectivity problems around the time that VPN Mgr notices the connection has gone away (no surprises there). There's nothing there to show you needing to run the wizard - I'd want to see that log too, with debug switch on.
You're also running a bunch of banned addons. If you want support to determine why the system is crashing (which I'd suggest is your biggest issue), you'd need to remove those and get a log with this behaviour in without them enabled. This probably needs it own thread.
Don't connect at start otherwise it'll revert to that - that'll be the default state. Then create a filter for just the addon you want to use the VPN with.
Yes, use filtering, it's documented on the wiki
Ok, thanks for the clarification chewitt. I "understand" the use of the up/down scripts, and had been looking at GitHub - jonathanio/update-systemd-resolved: Helper script for OpenVPN to directly update the DNS settings of a link through systemd-resolved via DBus. which is why I was asking about resolved support. Previously it had been GitHub - masterkorp/openvpn-update-resolv-conf: Script that updates DNS settings are pushed by the OpenVPN server, but everything I've ready says update-systemd-resovled since version 229 of systemd.
My initial read of the script is that it *somehow* gets the DNS settings returned from the VPN provider, and then updates the system with these settings. Assuming I can work out the bit which retrieves the DNS settings, is there some legitimate way I can update the DNS settings as if I was changing it in the LE configuration interface which wouldn't fight against whatever LE is doing to set the DNS settings?
I'm looking at a problem with my VPN add-on that sees the DNS not get updated to the VPN provider DNS servers on connection.
I *think* that the openvpn team have basically decided that it's not their job to do it, so there's a script to go run on connection which appears use systemd-resolved to force the update to happen. I'm far from an expert on Linux and systemd, but it looks like systemd-resolved is not included with the standard LE build (I'm using the RPi one) so the script basically fails.
Am I right? Is there a reason why this was excluded? Is there an alternative way (short of rolling my own build which is a rat hole I don't want to go down just now).
Thanks for any shoves in any direction, I'm totally at a loss.
I think you can remount it as read/write (might be wrong) and fix it that way. I suspect it'll be lost next time you upgrade though.
You could also create your own APPEND.txt by reading the wiki. There's not really enough info there to do this without a bunch of googling though - I should fix that but real-life will stop that happening for a couple weeks.
Likewise, I should also think about how to fix this for LE - but this won't be for a few weeks.
