LE 11 and Wireguard VPN to my Unifi Dreammachine

QBJack · October 11, 2023 at 12:59 PM

Hello guys,

I need help to get a working VPN connection from Rpi4 with LE 11 (latest as today) to my Unifi Dreammachine.

I used this instruction to setup the LE side: WireGuard - LibreELEC.wiki

On my Unifi DM I created a new WG client and downloaded the provided config file. This files contains most data for the config on LE side like privatekey, publickey, allowed-ips and so on. UDM version is the latest release as well.

From that information given I created the following wireguard.config file :

Code

[provider_wireguard]
Type = WireGuard
Name = myvpn
Host = <public ip of my UDM>
WireGuard.Address = 192.168.4.2/32
WireGuard.PrivateKey = <private key here>
WireGuard.PublicKey = <pubic key here>
# WireGuard.PresharedKey =
WireGuard.DNS = 192.168.4.1
WireGuard.AllowedIPs = 192.168.4.1/32,192.168.4.2/32,0.0.0.0/0
WireGuard.EndpointPort = 51820
WireGuard.PersistentKeepalive = 25

Display More

When starting the VPN connection I get:

Code

LibreELEC:~/.config/wireguard # connmanctl connect vpn_my_ip_here
Connected vpn_my_ip_here

but trying to ping the VPN gateway's private IP or anything else on my private network gives me this:

Code

LibreELEC:~/.config/wireguard # ping 192.168.4.1
PING 192.168.4.1 (192.168.4.1): 56 data bytes
ping: sendto: Required key not available

Simple ping is not possible and my UDM shows no VPN clients connected at all.

Using this exact config from my UDM on my Wireguard Windows Installation just works without issues and I can ping and access my network stuff.

Please help on that. Thanks in advance.

Best regards

Thomas

QBJack · October 11, 2023 at 2:12 PM

Of course I have already searched the forums and other discussions about that but did not found any working solution.

**chewitt** · October 11, 2023 at 9:50 PM

Code

WireGuard.Address = 192.168.4.2/24

What happens with /24 instead of /32 ?

QBJack · October 13, 2023 at 8:41 AM

Unfortunately the same behaviour - could not ping anything. My UDM does not see this VPN client connected anyway. When I connect my Windows client I can see this on my UDM. So I think the VPN connection is not really established at that moment.

Scritch · October 15, 2023 at 9:25 PM

This sounds very similar to the behavior which I observe with my Wireguard VPN server hosted on my Fritzbox.

Connections work 100% reliable when connecting other networks via Fritzbox or clients eg from my Android mobile device.

When connecting from LE on my Raspberry PI 3, the connection is reported to be established.

However, the connections is available only sporadically.

Using ping, I see that for 80% of the connection attempts, the connection is not available. Sometimes ping works after establishing the connection. But only for a limited time. After less than 5 minutes (exact timing is random) ping stops working, and never recovers afterwards.

Checking the connection on LE using "wg" command, the connection is reported as established, even though the connection obviously dropped.

Code

gaeste:~ # wg
interface: wg0
  public key: <edited - removed>
  private key: (hidden)
  listening port: <edited - removed>

peer: <edited - removed>
  preshared key: (hidden)
  endpoint: <edited - removed>
  allowed ips: (none)
  transfer: 444 B received, 1016 B sent
  persistent keepalive: every 25 seconds

Display More

In the Fritzbox connection details the connection sometimes even gets a green checkmark.

However, in contrast to the working connections, the LE connection never receives a timestamp in the "last negotiation" column: