addon-wireguard: Update from 0.5.0 to 0.5.1 breaks tunnel

Problem/Motivation

Tunnel does not work with the latest upgrade.

Expected behavior

Some configurations should be showing in the logs:

[#] ip -4 address add 172.27.66.1/24 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j

Actual behavior

The above logs do not show and I assume are not being setup.

Steps to reproduce

Upgrade

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

OS: Debian 10 HA: 2021.4.3 Hardware: Intel NUC Supervisor: 2021.04.0

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 2
Comments: 31 (5 by maintainers)

Most upvoted comments

It seems like all cases here involve Debian 10. Have you guys installed the kernel modules for WireGuard on your host system?

frenck on Apr 16, 2021

I am running supervised on Debian 10 so installing wireguard on the native OS is really not an option to stay “healty and supported”

The previous reports show that installing the kernel module resolves the issue, as the addon wraps Wireguard, not sure what can be done. If you are concerned about support I would suggest using HassOS which has the support installed.

My concern stems from the fact that the goal is to work toward a stable product. Falling back and only being able to install one way is a step backwards not forwards. I am running 0.5.0 and will as long as I can and then will install it on a standalone Pi.

mattlward on May 13, 2021

Could you please provide your system information? ha info?

frenck on Apr 10, 2021