Bonjour
J’utilise les DNS Jeedom (xxx.eu.jeedom.link) en mode Openvpn et les accès externes fonctionnent bien
J’ai voulu essayer le plugin Wiregard et l’accès externe aboutit à « 502 bad gateway »
Quelques précisions :
- Plugin Wireguard : j’ai installé la version stable 2022-09-22 14:07:25
J’ai bien remarqué sur le market que le plugin ne comporte pas la mention « officiel ».
NB : c’est peut-être la raison pour laquelle je n’ai pas trouve de tag correspondant dans Community ?
Comme il est indiqué « Compatible uniquement avec le DNS Jeedom pour le moment », j’ai fait l’essai - Logs :
wireguard_DNS_Jeedom
Warning: `/var/www/html/plugins/wireguard/data/wg_588.conf' is world accessible
[#] ip link add wg_588 type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported
[#] ip link delete dev wg_588
Cannot find device "wg_588"
wireguard_packages
+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_wireguard
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/wireguard/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/wireguard/resources/pre-install.sh
+ echo 3
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Get:1 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:2 http://deb.debian.org/debian buster-backports InRelease [51.4 kB]
Hit:3 http://ftp.fr.debian.org/debian buster InRelease
Get:4 http://ftp.fr.debian.org/debian buster-updates InRelease [56.6 kB]
Hit:5 https://deb.nodesource.com/node_16.x buster InRelease
Get:6 http://security.debian.org/debian-security buster/updates/main Sources [273 kB]
Get:7 http://security.debian.org/debian-security buster/updates/main amd64 Packages [369 kB]
Get:8 http://security.debian.org/debian-security buster/updates/main Translation-en [200 kB]
Get:9 http://deb.debian.org/debian buster-backports/main amd64 Packages [487 kB]
Get:10 http://deb.debian.org/debian buster-backports/main Translation-en [411 kB]
Get:11 http://deb.debian.org/debian buster-backports/contrib amd64 Packages [9196 B]
Get:12 http://deb.debian.org/debian buster-backports/contrib Translation-en [8080 B]
Get:13 http://deb.debian.org/debian buster-backports/non-free amd64 Packages [37.2 kB]
Get:14 http://deb.debian.org/debian buster-backports/non-free Translation-en [39.5 kB]
Fetched 1978 kB in 3s (648 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
233 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 4
+ sudo apt install -o Dpkg::Options::=--force-confdef -y wireguard
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
linux-image-5.10-rt-amd64 linux-image-5.10.0-0.deb10.17-rt-amd64
wireguard-tools
Suggested packages:
linux-doc-5.10 debian-kernel-handbook openresolv | resolvconf
The following NEW packages will be installed:
linux-image-5.10-rt-amd64 linux-image-5.10.0-0.deb10.17-rt-amd64 wireguard
wireguard-tools
0 upgraded, 4 newly installed, 0 to remove and 233 not upgraded.
Need to get 54.8 MB of archives.
After this operation, 316 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster-backports/main amd64 wireguard-tools amd64 1.0.20210223-1~bpo10+1 [87.7 kB]
Get:2 http://security.debian.org/debian-security buster/updates/main amd64 linux-image-5.10.0-0.deb10.17-rt-amd64 amd64 5.10.136-1~deb10u3 [54.7 MB]
Get:3 http://deb.debian.org/debian buster-backports/main amd64 wireguard all 1.0.20210223-1~bpo10+1 [8284 B]
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 linux-image-5.10-rt-amd64 amd64 5.10.136-1~deb10u3 [1080 B]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 54.8 MB in 1s (58.3 MB/s)
Selecting previously unselected package linux-image-5.10.0-0.deb10.17-rt-amd64.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 66262 files and directories currently installed.)
Preparing to unpack .../linux-image-5.10.0-0.deb10.17-rt-amd64_5.10.136-1~deb10u3_amd64.deb ...
Unpacking linux-image-5.10.0-0.deb10.17-rt-amd64 (5.10.136-1~deb10u3) ...
Selecting previously unselected package linux-image-5.10-rt-amd64.
Preparing to unpack .../linux-image-5.10-rt-amd64_5.10.136-1~deb10u3_amd64.deb ...
Unpacking linux-image-5.10-rt-amd64 (5.10.136-1~deb10u3) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack .../wireguard-tools_1.0.20210223-1~bpo10+1_amd64.deb ...
Unpacking wireguard-tools (1.0.20210223-1~bpo10+1) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_1.0.20210223-1~bpo10+1_all.deb ...
Unpacking wireguard (1.0.20210223-1~bpo10+1) ...
Setting up linux-image-5.10.0-0.deb10.17-rt-amd64 (5.10.136-1~deb10u3) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-0.deb10.17-rt-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-0.deb10.17-rt-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-0.deb10.17-rt-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-0.deb10.17-rt-amd64
Found initrd image: /boot/initrd.img-5.10.0-0.deb10.17-rt-amd64
Found linux image: /boot/vmlinuz-4.19.0-13-amd64
Found initrd image: /boot/initrd.img-4.19.0-13-amd64
done
Setting up wireguard-tools (1.0.20210223-1~bpo10+1) ...
wg-quick.target is a disabled or a static unit, not starting it.
Setting up linux-image-5.10-rt-amd64 (5.10.136-1~deb10u3) ...
Setting up wireguard (1.0.20210223-1~bpo10+1) ...
Processing triggers for man-db (2.8.5-2) ...
+ echo 5
+ sudo chmod +x /var/www/html/core/class/../../plugins/wireguard/resources/post-install.sh
+ sudo /var/www/html/core/class/../../plugins/wireguard/resources/post-install.sh
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.19.0-13-amd64
+ echo 6
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end wireguard
+ rm /tmp/jeedom_install_in_progress_wireguard
+ echo '*******************End of package installation******************'
*******************End of package installation******************
- Paramétrage réseau :
Dans Réglages/Système/Réseaux j’ai sélectionné le mode « Wireguard »
A noter qu’il est mentionné « alpha » ce qui peut expliquer le problème que je rencontre
Après redémarrage de la gestion DNS, le statut DNS était au vert et un équipement wireguard a bien été créé
Extrait :
Suite à cet essai infructueux je suis revenu au mode openvpn qui fonctionne bien
Il n’y a donc aucune urgence
Compléments :
Merci par avance