Posts by Mickeyluv

    I've now found what's happening; when wg0 closes the default route is not restored, but connman assumes that it was. The fix is to force-restore the default route afterwards using;

    ip route replace default via 192.168.1.254 dev eth0

    I want to start/stop wireguard using scripts and have this as my connect (wgconnect.sh);

    #!/bin/sh
    connmanctl connect <vpn_service_name>

    and this as my disconnect (wgdisconnect.sh);

    #!/bin/sh
    connmanctl disconnect <vpn_service_name>
    sleep 1
    ip route replace default via 192.168.1.254 dev eth0

    These work perfectly when input line by line as commands (and the status is reflected in the LibreELEC connections list), but despite the scripts being located in /storage/.config and executable, run as root, I get 'file not found' when I run them (created in ubuntu). I know it's a real beginners question, but that's exactly what I am. Any assistance appreciated.

    Here's a further update if anyone has an idea of what to try next;

    System boots with wireguard intentionally disconnected and operates as intended.
    LibreELEC correctly shows wired LAN, wireless (idle), and wireguard (idle).
    When wireguard is connected, wired & wireless LAN show as idle, and wireguard as connected. Everything operates as intended.
    When wireguard is disconnected, the connections screen reverts exactly to how it looked after initial boot, but no plugins will connect.

    If I connect from my laptop using SSH;

    LAN 192.168.1.254 is reachable
    8.8.8.8 not reachable
    DNS points to router
    Flushing IP table/neighbour table does nothing
    Restarting Kodi or Connman does nothing.

    To my limited understanding, is this a LibreELEC issue? Maybe I'm wrong, but it doesn't now look to be a Kodi or connman problem as I would have though resetting them both would restore internet access. Is there a way to script a forced connection refresh without a full reboot?

    I've now got this working to the degree that when I start wireguard it actually works with Kodi. It was a Mullvad DNS problem - as soon as I changed to a public DNS rather than Mullvad's own it solved the connection problems.

    However, when I disconnect, none of the Kodi plugins connect unless LibreELEC is restarted (a Kodi restart via SSH doesn't fix this).

    If I examine the IP route after disconnecting it all resoves to the wired connection eth0 and /etc/resolv.conf looks fine. This to me looks like a Kodi or maybe connman issue.

    I got a lot further with this today, but at the moment the connection isn't working. I used the Mullvad generator to provide the keys and endpoint server credentials and transposed these into the required LibreELEC format.

    The wireguard connection now appears in my connections list and available for manual connect/disconnect but when connected no Kodi plugins will work and it appears that traffic stops altogether.

    However, all the command line connman checks as per the wiki show that the connection is up and running with no errors at a LibreELEC level. I'm pretty stumped what to try for the time being.

    This is technically less secure (as they generated and thus could know/store the private key of the remote device) but that doesn't seem to bother most users who only care about a connection that hides their presumably dodgy activity.

    I used to get a lot of buffering when watching TV in the evening without a VPN, made worse if there's a big sporting event. With a VPN there's no buffering at all, but a couple of channels refuse connection with the VPN anyhow even though I'm a registered user and can otherwise view them.

    I'll take another look tomorrow at the Mullvad key generator and try out the suggestions, as its getting late now.

    I updated my Ubuntu laptop to use wireguard yesterday and it was easy, but despite trying hard to understand how to install wireguard on LibreELEC, I'm pretty lost how this relates to the Mullvad device generator. Do I need to generate a private key for LibreELEC and upload this to Mullvad to generate a new device? The LibreELEC wiki says "Most users will not need to generate WireGuard keys as they will be in the configuration file provided by a VPN service provider" but I can't see how this would work for Mullvad.

    If there are any Mullvad users, could you give me some help with this and explain the procedure in simple terms.

    Ultimately I want to boot into LibreELEC with wireguard turned off and toggle the VPN from Kodi via a script.

    I've now got the SSD working again. It was previously NTFS formatted which worked perfectly before, but I reformatted to Ext4 on my Ubuntu machine and when I plugged it into the RPi it mounted it right away. Does 11.x no longer support NTFS?

    I still need my memory sticks to work across platforms, though.

    Also, my memory sticks that previously worked fine are no longer accessible, but again, when removed I get the message saying the device is removed. I noticed occasionally I get the message 'Remote Share - couldn't connect to network server' after the 'invalid argument' message, but not every time.

    I just updated my RPi 4 to the latest Kodi Nexus and Libreelec 11.03. My SSD drive plugged into the USB port was working fine immediately beforehand, but now when I try to connect I get 'Invalid Argument'. If I unplug it the system says it's removed, so the hardware is detected.


    I usually can see the drive remotely from my Ubuntu laptop, but the drive no longer shows there either. I can plug it into the laptop and it works perfectly, so no problem with the drive.


    Can anyone assist?

    I'm showing a warning in the OVPN log;

    WARNING: file '/storage/.kodi/addons/service.vpn.manager/UserDefined/pass.txt' is group or others accessible

    When I look in the folder, that file isn't shown. What is the consequence of the warning, and what do I need to do to fix this?

    I'm getting a permission error 13 when running /storage/.kodi/userdata/addon_data/service.vpn.manager/UserDefined/up.sh (from Zomboided OVPN)

    i connected using SSH and ran chmod +x /storage/.kodi/userdata/addon_data/service.vpn.manager/UserDefined/up.sh which was successful, but still get the permission error. What am I doing wrong?


    Here's the script


    #!/bin/bash

    iptables -F

    iptables -A INPUT -i tun0 -m state --state ESTABLISHED,RELATED -j ACCEPT

    iptables -A INPUT -i tun0 -j DROP


    I'm in the UK and have been using Mullvad with the Zomboided plugin for over two years without problems - until recently. Over the past few weeks the OVPN connection to any USA servers has become unreliable. Connection attempts repeatedly fail (with both UDP and TCP) and once connected can disconnect after a few minutes. Once I do get a stable connection this is maintained without further problems. Ping time is usually 80ms, upload speed 10Mb/s and download 36Mb/s (50Mb/s connection).

    If I connect to local UK servers (Manchester and London) there's no problem at all - connection is made on the first attempt every time and is perfectly stable.

    The OVPN was previously configured as 'User Defined' and I've now updated OVPN to 7.0.0 and selected Mullvad for the configuration. Kodi version is 19.4, LibreELEC 10.0.03. The log shows the failure as, for example - 'Cannot resolve host address:us-nyc-2006.mullvad.net:443(Name or service not known)'

    The same error occurs with Canadian or Ireland connections.

    Testing the USA servers with my laptop running Ubuntu and there's no problem.

    I emailed Mullvad support and they said that the server addresses need updating they've converted them to RAM storage. I downloaded a single configuration for NYC to try and that gives the same error as before. Oddly, I have not needed to update anything on my Ubuntu machine.

    The questions I have are;

    1. Is the Mullvad server list imported into OVPN the most up to date?

    2. I may be installing an incorrect file into OVPN when using 'User Defined' - on the Mullvad site, which do I need? I've been trying the Linux versions, but I vaguely recall that I may have used Android files when I originally set this up over two years ago.

    3. Is there anything else that could cause this problem? My provider does not block or filter VPN connections, so I think it's something local.

    EDIT: This morning I couldn't connect to any USA servers no matter how many attempts. I reinstalled the Linux files downloaded today off the Mullvad site and none would connect. Tried again, but this time using the Android files and everything is now working OK.