Posts by zomboided

You can use just one VPN location, which is always on, or you can switch VPN locations by addon. If the addon doesn't have a location specified for it, it'll just use the existing one. You can also do switch by Window ID.

If you want a service (which is obviously always running) to use a particular route, then you need to specify each route the service will use in the APPEND.txt file (or the inverse?). You can see the GitHub wiki on how to do this, plus there's some words in here of someone who was trying to do the same thing Unable to get APPEND.txt working with NordVPN · Issue #216 · Zomboided/service.vpn.manager · GitHub. I've never tried this so can't give you any more help.

snakebilewine Read post 795 just above...this script won't work and I don't know what the answer is.

Quote from ChoppedTomato

PS It would be nice if you got chance to add couple UK servers as attached if possible, many thanks

UnitedKingdom-0-BBCiPlayer.ovpn

UnitedKingdom-0-NFLX.ovpn

Yes, I'll do that when I find some time. You'll see a notification in the addon when it's ready.

I've looked at VPNArea and it looks like someone provided me with the files, it doesn't look like I did them myself.

I've updated the template and checked the Coventry 2 location you were using and the built in support should be the same as if you supply your own. You should see a notification that updated files are available, or you can try deleting downloaded files and resetting the connection. I'll run an update to pick up all the locations when I have the energy to pick through them.

It really does look like a DNS problem though. The trace is saying that calls to different interweb resources just time out. I've seen this multiple times. It can be caused by the ISP pushing bad params at you after the connection (unlikely if you see this across multiple locations). It can be caused by the OS not refreshing the DNS (I had read that the openvpn team consider updating the DNS in the OS to be not their job, which can be addressed by using the up/down parameters).

If you look in the ovpn files that VPNArea provide you'll see this :

up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf

which is supposed to kick the OS into doing something. There's some stuff about this here on the GitHub wiki

LE doesn't have update-resolv-conf or update-resolved-systemd because they don't use the services they call, and actually I think LE just wants connman to be kicked. I've not worked out a way of doing that yet (nor do I understand why it's necessary in some circumstances but not others).

You could also switch openvpn verb to 4 (this is in the settings/advanced) and see if a DNS Is being pushed at you. You could opt to always use the VPNArea DNS by setting it in the LibreELEC config.

If you get no joy, and VPNArea can't work it out when you're using their service with their ovpn file via the command line, then maybe trying it on a full Linux install where update-resolv-conf or whatever exists might be a good step. I think OSMC might work for you here.

This log is from Kodi 16, from December 2016, which has an older level of openvpn in it to what's supported now. And you're using version 4.2.0 of my addon from 2017. There have been 100s of changes since that level of code was released. I don't wanna appear to be an asshat, but I'm not debugging code from the olden days. A recent 8.x LibreELEC with Kodi 17 and 5.0.7 of my addon either from the repository or downloaded as a released package from GitHub is your starting point.

Also, you're using the User Defined profile. This means that you supplied and uploaded the ovpn files which I'm definitely not about to start debugging for you. I have no idea what's in those ovpn files or how you've set things up - the reason that the User Defined stuff exists is for people that know what they're doing and can debug their own issues.

Regardless, for VPNarea, there's built in support, so I don't know why you're not using that. It does look slightly out of date, but you're not using it so I'm not going to update it, and nobody else that uses it (if there is anyone) is telling me it's broken either.

All that said, I'd guess at you not having DNS connectivity from the log. There's a lot of stuff written about that on the GitHub wiki in Trouble Shooting. If you try that and fail, then you can follow the advice about creating a VPN via the command line and asking VPNarea what's wrong.

It's a problem with beta releases of Kodi not working and loading/saving settings.

Nothing I can do to fix it unless you replicate the problem on Kodi 17

PIA haven't changed anything, and I've not changed the addon in some time. I've not noticed disconnects on my kodi boxes but I have seen semi-frequent disconnects using their windows app over the last couple months whereas it used to be a lot more solid for me.

It was trying to output a character to the log that couldn't print. It had nothing to do with the connection which showed success in connecting

Thanks for the log, I've found the problem and will fix this in the next release in the next few days.

Google "ip: RTNETLINK answers: File exists" and there's lots of (good?) advice

Quote from coaxx

Feature Request: Wouldt be nice to have multiple "User defined" settings renamed by user

Not gonna happen as it's such a limited use case. You can have multiple providers active in User Defined anyway, and call the different profiles/locations whatever you want.

romuald I agree that the User Import should resolve that line properly. Thanks for mentioning this, I've opened an issue on GitHub here to fix this User Import misses some files · Issue #211 · Zomboided/service.vpn.manager · GitHub

Until then, you can edit the files that are generated to the userdata directory to correct them with the right path yourself.

Regarding any warnings, it's up to you to ensure that you're happy with the way the User Defined is set up and determine whether it's an issue. The reason for User Defined existing is to allow a way of using unsupported providers without me having to repeatedly spend time and effort ensuring they work. Or more prosaically in the case of PureVPN, support their shoddy service for free.

Looks like that server no longer exists. I'll update IPVanish servers in the next day or two and you'll see a notification on connect that they're available.

I think the error is 'keepalive conflicts with ping'. They both do kinda the same thing, keeping the connection active. You can disable adding ping by using the settings GUI (I think it's in the advanced tab), or you can delete keepalive from the the file you're sharing.

Quote from speculatrix

That's a pretty snotty attitude. I'm not an expert in this stuff and have gone to some trouble to provide information that I thought might be pertinent. The simple fact is, when I tried the NordVPN option provided, it didn't work. I found a work-around that did and shared that information. So for you to brush this off with, 'hey it works for me...' is arrogant and unhelpful.

You're right. I should not have tested my account at all. And I should have guessed at your issue from the excellent debug you provided. Stop being so self-entitled. This is free software, which I'm happy for you not to use.

I have an expired Nord account and it works fine right up until the connection to the VPN service.

Who knows why it's not working for you, you've shared select entries you think are important from a log which may or may not have debug enabled.

I've just done this with a RPi3 and 3 Xbox One tuners with TVheadend running on a Libreelec install. I can send pictures around the network to other Kodi installs and watch it on the Pi at the same time. Uber happy with it, everything just worked out of the box with some relatively easy setup.

Recordings I put on a mounted drive and they're managed by tvheadend and they appear on all of my kodi installs automatically via the tvheadend EPG (and tablets via the tvheadend app). I set them to be .mkv and HD is about 2Gb an hour and decent quality if I want to keep it.

The only thing I'm not feeling is the remote button behaviour but I think that's fixable with some messing with the keyboard.xml when I get round to it.

Do it...better than a separate PVR with all of the limitations that come with it

Morphy This is a bit of a niche use case, and I'm guessing that different providers, even if they did offer this, would do this in different ways. I think your best approach here is to access the API via the up and down scripts (see the wiki) and output the port number returned to a known location.