In this article:
    Applicable to:
    • Twingate Component: Client
    • Platform: Linux

    Overview

    The Twingate Linux Client requires resolved-systemd or Network Manager. If Network Manager is installed/running, it needs to be configured to manage the interfaces . Without such configuration, the Twingate Linux Client will not be able to manage the interfaces as needed.

    Symptoms

    • Twingate Linux Client does not start.
    • The command $ /usr/bin/twingate-notifier console immediately returns the below error:
      22:12:40 [ERROR] twingate_notifier::notifier::Notifier::start message process error: auth.sock socket is not found
    • Reviewing the Twingate Client Logs the below error is seen: 
      twingated[1706]: [ERROR] nm_wait_for_device: it was not possible to activate sdwan0 device. Please make sure NetworkManager is running and it's the current system network renderer
      ...
      twingated[1706]: [FATAL] Failed to initialize Network Controller
      systemd[1]: twingate.service: Main process exited, code=exited, status=1/FAILURE
      systemd[1]: twingate.service: Failed with result 'exit-code'.

    Troubleshooting

    1. Check to see if Network Manager is installed. Example command and results via Ubuntu utilizing aptitude package manager below:
      ~$ sudo apt list --installed | grep network-manager
      network-manager-pptp/jammy,now 1.2.10-1 amd64 [installed,automatic]
      network-manager/jammy,now 1.36.4-2ubuntu1 amd64 [installed]
    2. Check to see if Network Manager service is running. Example command via below:
      ~$ sudo systemctl status NetworkManager
      ● NetworkManager.service - Network Manager
      Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
      Active: active (running) since Fri 2022-06-10 22:11:13 UTC; 8min ago
    3. Check to see if Network Manager is configured to manage the interfaces. Below we can see  sdwan0  is unmanaged.  
      ~$ sudo nmcli d
      DEVICE TYPE STATE CONNECTION
      enp0s3 ethernet unmanaged --
      lo loopback unmanaged --
      sdwan0 tun unmanaged --

    Resolution

    Depending on your environment and configuration needs, any of the below options will resolve this issue. 

    • Configure the sdwan0 interface to be managed by Network Manager.
    • If systemd-resolved is installed, enabled, and running, disable Network Manager. Ensure systemd-resolved is enabled/running if you proceed this route. Example command below.  
      sudo systemctl disable NetworkManager 
    • Uninstall Network Manager. Example command via Ubuntu utilizing aptitude package manager below: 
      sudo apt remove network-manager -yq

    Related