WireGuard prevents Kodi to start if wifi changes

    Hi All

    I followed this to configure WireGuard

    https://wiki.libreelec.tv/configuration/wireguard

    It works like a charm I thank the team for that :)

    But when my wifi connection changes, the boot sequence stops on the LibreElec startup screen. ( before kodi).
    I think WireGuard is trying to start but there is no network.

    Is it possible to set a timeout somewhere to stop WireGuard in that case ?

    Then I will be able to change the wifi setup and restart to have a nice boot sequence.


    Thanks

    Cyril

    Edited once, last by cyr06 (May 6, 2025 at 1:12 PM).

    I think the key is in the /storage/.config/systemd/wireguard.service file. But I'm not systemd fluent

    the manuel says

    Code
    [Unit]
Description=WireGuard VPN Service
After=network-online.target nss-lookup.target wait-time-sync.service connman-vpn.service
Before=kodi.service

    The original file says

    Code
    [Unit]                                                                                                                                 Description=WireGuard VPN Service                                                                                                      After=network-online.target nss-lookup.target connman-vpn.service time-sync.target                                                     Wants=network-online.target nss-lookup.target connman-vpn.service time-sync.target

    in both cases if network fails, kodi never shows

    if I use

    After=network-online.target nss-lookup.target connman-vpn.service time-sync.target kodi.service 

    Kodi shows but wireguard doesn't seems to start

    Do you have any clue ?

    Thank you

    when I remove time-sync.target from the Wants line, indeed Kodi starts without any network connection

    Unfortunately , the wireguard connection never starts automatically when I have a network

    WireGuard uses symetric keys for encryption but other elements of the protocol like handshaking and key-rotation that are essential for perfect-forward secrecy are time-based: thus the host needs to have correct time before starting, and on most LE devices correct time is obtained via NTP, so removing the time-sync.target dependency would be wrong.

    If "when my wifi connection changes" means you have a poor wifi signal resulting in disconnects or failure to connect? the correct solution is always going to be fixing the poor signal.

    Thank you for this info about time sync. The problem is when I change the wifi password for instance or if I put it in a new place with a différent ssid

    The only solution is a rj45 cable for now