wireguard troubleshooting : no reply

  • I have done the setup as described in the wiki, but I get no response.

    Instead the following error:


    KODI-TV4:~ # connmanctl services

    *AO Wired ethernet_dca63226ebf3_cable

    * WireGuard VPN Tunnel vpn_kodi4_tv


    KODI-TV4:~ # connmanctl connect vpn_kodi4_tv

    Error /net/connman/service/vpn_kodi4_tv: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.



    my conf file looks like this:


    [provider_wireguard]

    Type = WireGuard

    Name = WireGuard VPN Tunnel

    Host = myname.dyndns.org

    Domain kodi4.tv

    WireGuard.Address = 192.168.6.6/24

    WireGuard.ListenPort =

    WireGuard.PrivateKey = ghgghh

    WireGuard.PublicKey = vhjjnbvv

    WireGuard.PresharedKey =

    WireGuard.DNS = 8.8.8.8

    WireGuard.AllowedIPs = 0.0.0.0/0

    WireGuard.EndpointPort = 45467

    WireGuard.PersistentKeepalive = 25


    Any ideas?

    LibreELEC (Leia) on Raspberry Pi 4B

    Edited once, last by novalis ().

  • Hello,


    Having same issue.


    Having this configuration currently:


    When running connman I get this:

    Code
    1. $ connmanctl connect vpn_pl2_wireguard_mullvad_net_my_home_network
    2. Error /net/connman/service/vpn_pl2_wireguard_mullvad_net_my_home_network: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


    I ran connman with debug:


    This one is strange to me:


    Code
    1. connmand[8613]: Connect reply: Invalid arguments (net.connman.Error.InvalidArguments)


    I can add that I've tried with setting server IP instead of hostname, and removed IPv6 for local address as well, and tried few modification, always got same errors.

    Edited once, last by elgatito ().

  • This is a known issue. See Add Wireguard support.


    Additional it is reported that the default route is always set to the wireguard device.



    Just a thought for a workaround: use wireguard without connman.


    Do cp /etc/connman/main.conf /storage/.config/connman_main.conf and add ,wg to the NetworkInterfaceBlacklist line. Reboot.


    Then configure wireguard using the wg command.

  • try to remove the line:

    WireGuard.PresharedKey =


    it helped for me, obviously it must not be empty.


    ... silly if true...

    LibreELEC (Leia) on Raspberry Pi 4B

  • I've reported the PresharedKey issue so that bad config handling can be improved. The routing issue remains unresolved. It's been reported but the main connman developer working on WireGuard has been offline for a while. He's resurfaced in the last week so hopefully we might see some progress.

  • I've reported the PresharedKey issue so that bad config handling can be improved. The routing issue remains unresolved. It's been reported but the main connman developer working on WireGuard has been offline for a while. He's resurfaced in the last week so hopefully we might see some progress.

    Maybe we can do something manually? Maybe manage routes after setting up the interface.

  • The challenge with routing is that connman manages the WireGuard interface, so you can make changes, and connman can simply overwrite them again. Connman support for WireGuard is still rather new and initial testing was limited to specific use-cases. Now that a wider audience started to use it other ways, we're sure to find some things that need code changes. I'm sure it will be resolved, but don't ask when.

  • Please leave us a note here if anything happens so that we get informed.

    LibreELEC (Leia) on Raspberry Pi 4B

  • Well I think bash is already installed.

    The busybox version though.


    Here is my .profile


    SHELL=/bin/bash

    PATH=/storage/bin:$PATH

    TERM=xterm-color

    exec bash & source /storage/.bashrc

    LibreELEC (Leia) on Raspberry Pi 4B

  • Thank you very much for this. Connman also didnt work for me with

    Connect reply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (org.freedesktop.DBus.Error.NoReply)


    Your idea saves a day. Not sure, why connman doesnt work for me and some others, and for some yes. I dont use pre-shared key nor config line.

    2x VIM3L, 3x X96 Air P3, 6x C2; 6x RPi2; 3x Win7 Kodi + vPeter's mariaDB plugin as Library DB

    Edited once, last by JimmySmith ().