[Plugin] WireGuard VPN by Madhouse

There are 1,092 replies in this Thread which was already clicked 229,297 times. The last Post () by robertjust.

    This plugin has an issue whereby it keeps waking up the HDD every few minutes even when USB is selected for holding the Private.key


    If you delete the wireguard folder on the HDD the HDD will then go to sleep and remain so, but as soon as you restart E2 the folder on the HDD is created again and the HDD once again keeps waking up.


    Can anything be done about this in the settings ?


    If not is it possible to have an updated version please that doesnt keep calling upon the HDD once USB is selected in the settings ?


    And i f u just change it to the flash ? why is it so important to do this on usb stick/hdd.


    regards

    Edited once, last by fsky1 ().

    It makes no difference if you have your Private.Key on the flash, the wireguard plugin still creates the folder on both the HDD and USB after an E2 restart. Of course the files within it are empty because in settings its set to use flash, but the very fact its creating the folder on the HD means it wakes the HDD up, but worse than that its persistantly checking that folder meaning the HDD can never go to sleep.


    If flash or USB are selected in the plugins settings we need an update to the plugin to stop it constantly trying to read from the HDD, the HDD should be ignored by the plugin entirely if flash or USB are selected as the storage location of the Private.Key and bypasses files.


    The plugin it should only ever try to read from the HDD if that has been selected as the storage location in settings.

    • New

    I found a workaround for the boot issue on OpenATV 7.6 with VU+ Solo SE.


    After the first reboot with the killswitch enabled, the network is not working anymore and needs to be restarted manually. After the second reboot, the box doesn't boot at all.


    I suspect that the WireGuard routes (0.0.0.0/1 and 128.0.0.0/1) are not properly cleared during shutdown, causing the network to fail on the next boot.


    Workaround: Adding `/etc/init.d/networking restart` at the beginning of `/etc/init.d/wireguard` before WireGuard starts. This restores the default route before WireGuard initializes.


    This is not a clean solution but it works. Maybe the real fix should be in the `stop)` section of the init script to properly clean up all WireGuard routes on shutdown.


    Receiver: VU+ Solo SE

    Image: OpenATV 7.6

    • New
    Quote from robertjust

    Good morning friends,

    I tried to install the plugin via telnet on a DM920 with an OpenPLi kernel 3.14-1.17 Python 3.14.5 image, but at the end of the upload process, I received this error:

    I am using the same homebuild PLi dm920 image (Python 3.14.5) and WireGuard VPN 16.2 plugin installs and works.

    Everything is retrieved from the feed properly.

Egami Team Images based on OE-Alliance

Egami Supported Models ~ Anadol Multibox 4k - SE, Ax multibox 4k - SE, Novaler Multibox 4k - SE, Maxytec Multibox 4k - SE and Zgemma H9 SE - Zgemma H9.2H SE - Zgemma H9 Twin - Zgemma H9Combo - Zgemma H9.2S - Zgemma H9.2H - Zgemma H9.T - Zgemma H9.S - Zgemma H7 / H7C / H7AC - Zgemma H8.2H - Zgemma H9.2H Se Android.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login