[Plugin] WireGuard VPN by Madhouse

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

    Quote from jrbmw
    Quote from gigafox72

    sorry..a question for all...now im using nord vpn but it expires soon...what vpn do you suggest me?

    I use surfshark cheap very fast and reliable .Do a comparison nord v surfshark or

    mullvad v ....etc

    I used both surfshark..nord and now mullvad...surfshark stopped me a lot of time...so i cancelled it...nord vpn all ok but now its too much expensive..and now im using mullvad that seems to go well...

    Update online WireGuard VPN V.15.6 (ipk on the first post)


    * Changing the URL for the web interface "http://box_ip:port/wireguard".

    * Fixed a bug in the web interface when there is no internet connection.

    * Added Light/Dark theme to the web interface.

    * Minor graphical fixes.

    * Fixed file generation on cloudflare when saving to external devices.

    * Updated French translation (thanks gruick1).

    * Updated Greek translation (thanks giorbak).

    Dear Madhouse,

    the plugin works well and solves me a lot of problems.

    It really came at the right moment for me!

    Therefore, many kudos and thanks!


    But not all of them.

    If I am not doing something wrong, I see that you write the configuration file that is used by Wireguard in etc/wireguard, which is the usual location across Linux flavours.

    The problem is that you make the plugin overwrite it when the plugin starts or connects (I do not know exactly, but it does not matter).

    And it is overwritten with specific parameters, which do not reflect (they overrule) what I put in the configuration file in the user directory, or even changing this file directly (the file gets changed again after my modifications).

    As I wrote some posts above, I have my own WG server (long story why it is so) and I do not need the traffic to be all directed through it.

    I know how to deal with this situation, since I have now some 7 peers in the WG sub network and all works well, at least it works in the way I need.

    But if the configuration file gets always rewritten following rules that are very good for commercial VPN servers, I cannot configure it the way I need.

    Could it be possible to introduce a switch to avoid this and let the user tamper at its own risk on the wg0.conf file?


    Thank you again and please forgive me if some of the above is not totally correct (in that case, correct me! :-) )!

    Quote from gigafox72
    Quote from madhouse
    Quote from gigafox72

    sorry..a question for all...now im using nord vpn but it expires soon...what vpn do you suggest me?

    Hi, I've been using Mullvad for over a year, never had a problem, for me the best VPN provider.

    Hi mad...who is the best server for the streaming according to your opinion?

    thank you

    Did I not reply to this before every provider is different and sometimes you need to change servers just because a server works for one person does not mean it will work for all , it's a case of try and see.

    Hello, since I updated to version 15.6 the saving of the server in personal files reports an error in the directory /etc/WgConfig saves them in HD/WgConfig but then it is not visible in the panel. how do you solve this ?? Thank you

    Edited once, last by vrondena: I was able to put back the 15.2 and the saving is done correctly in /etc/WgConfig !! I solved it like this but we would have to check the new version. ().

    Everything works fine under OpenATV 7.5.1.

    With OpenATV 7.6, when connecting, you can't see anything on the left side indicating that it's connected. The VPN connection also fails. Surfshark VPN Gigablue Quad 4K Pro: There's no log or error message.

    Quote from speedy005

    Everything works fine under OpenATV 7.5.1.

    With OpenATV 7.6, when connecting, you can't see anything on the left side indicating that it's connected. The VPN connection also fails. Surfshark VPN Gigablue Quad 4K Pro: There's no log or error message.

    No problems here with openatv 7.5.1 and 7.6 beta latest builds with surfshark on Gigablue Quad 4K Pro.

    With OpenATV7.6, crash continous after update to wireguard 15.6

    No problems on OpenATV 7.5.1


    Crash log:


    rev=34422+fb467ac

    component=Enigma2


    model=vuuno4k

    machinebuild=vuuno4k

    imageversion=7.6-beta

    imagebuild=20250809


    kernelcmdline=kexec=1 rootfstype=ext4 rootflags=data=journal rootwait rw coherent_pool=2M vmalloc=633m bmem=637m@383m bmem=637m@2431m kernel=/linuxrootfs1/zImage root=/dev/mmcblk0p4 rootsubdir=linuxrootfs1


    nimsockets:

    NIM Socket 0:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 0

    NIM Socket 1:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 1

    NIM Socket 2:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 2

    NIM Socket 3:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 3

    NIM Socket 4:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 4

    NIM Socket 5:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 5

    NIM Socket 6:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 6

    NIM Socket 7:

    Type: DVB-S2X

    Name: Vuplus DVB-S NIM(45308X FBC)

    Frontend_Device: 7




    12:13:22.2989 [Enigma] Python path is '/usr/lib/enigma2/python'.

    12:13:22.2992 [Enigma] DVB API version 5, DVB API version minor 12.

    12:13:22.2992 [Enigma] Enigma debug level 3.

    12:13:22.2992 [Enigma] sourcedate 2025-08-09 / master 34422+fb467ac.



    dmesg


    <4>[ 153.424226] [VID]: VIDEO_SET_STREAMTYPE 0

    <4>[ 153.428645] [VID]: VIDEO_SELECT_SOURCE 1 0

    <4>[ 153.433094] [VID]: VIDEO_PLAY 1 2 0

    <4>[ 153.442102] [VID]: VIDEO_CONTINUE 1 1

    <4>[ 153.446111] [VID]: VIDEO_CLEAR_BUFFER 1 1 0

    <4>[ 153.723085] [VID]: VIDEO_STOP 0 1

    <4>[ 153.727550] [VID]: VIDEO_SELECT_SOURCE 0 0

    <3>[ 153.917887] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 153.968259] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.027401] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.077297] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.138272] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.188279] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.248854] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    <3>[ 154.299525] BRCM brcm_dvb0: dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 21

    Hi, using personal files you have the possibility to choose the path where to keep your personal .conf files safe, you simply have to run the files that are populated in the plugin list.

    You do not need to edit the wg0.conf file in /etc/wireguard, that file is overwritten every time a new server is started.

    Quote from madhouse

    Hi, using personal files you have the possibility to choose the path where to keep your personal .conf files safe, you simply have to run the files that are populated in the plugin list.

    You do not need to edit the wg0.conf file in /etc/wireguard, that file is overwritten every time a new server is started.

    Thank you madhouse.
    Nevertheless there is something I still do not fully understand.

    I have actually been trying to put the right things in configuration file in my own directory, as suggested.

    But then, as far as I understand, the parameters are read from there and translated (especially routing and AllowedIPs) in a way I cannot control in the /etc/wireguard/wg0.conf file. Which is the one that wireguard eventually uses and is therefore the one that counts in the end.

    And that does not fully suit my needs.

    Which are a bit different from the majority of users here, since I am not using in this circumstances the VPN to cross geofencing and specifically I do not need (and I do not want) to route any general Internet traffic through the VPN.

    Inserting bazillions of exceptions is not a very elegant solution (and nevertheless as of now even a few test domains do not work for some reason).


    I fully understand why you make it this way, in order to make the configuration task easy even for inexperienced users, but I am hitting a wall here because of this.

    Just to describe my "frustration" I had even tried to disable root writing privilege to the wg0.conf file, but of course this brings to nothing, since there must be a wise check about writing errors and plugin initialisation stops! :face with head bandage:

    Actually, at the moment I am reaching 90% of what I need, which is a lot, especially when compared to the 0% level I was only few days ago when I had not yet got to know about your plugin.

    But I would be very happy to be able to reach the 100% finish line! :smiling face with halo:


    Thank you!

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