Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    25.07-RELEASE (amd64) - Wireguard service reported stopped, yet tunnel trafic clearly is ok

    Scheduled Pinned Locked Moved WireGuard
    3 Posts 1 Posters 112 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • lvrmscL Offline
      lvrmsc
      last edited by

      Since my upgrade to 25.07-RELEASE (amd64)
      built on Tue Jul 22 22:24:00 CEST 2025
      FreeBSD 15.0-CURRENT,
      on one end of my most important tunnel, the tunnel still works fine, but the pfSense GUI keeps reporting the service as stopped. I had to remove its monitoring from the Service Watchdog which was also trying to start it, without success. Yet the trafic flows correctly.
      I'm holding off upgrading my other boxes.
      Is there something I could do to help diagnose?

      lvrmscL 1 Reply Last reply Reply Quote 0
      • lvrmscL Offline
        lvrmsc @lvrmsc
        last edited by

        Strangely enough, checking the system 4 days later, I now see that Wireguard service is reported running! The last thing I did 4 days ago was to disable Wireguard service monitoring by the Service Watchdog. Anyway, even when it was reported stopped at first, 4 days ago, the tunnels were working flawlessly.
        Very strange. I will keep an eye on it.

        lvrmscL 1 Reply Last reply Reply Quote 0
        • lvrmscL Offline
          lvrmsc @lvrmsc
          last edited by lvrmsc

          I took some days before reporting again... Since then I installed:
          25.07.1-RELEASE (amd64)
          built on Fri Aug 15 20:42:00 CEST 2025,
          and the issue re-appeared but did not (yet) clear by itself.
          Wireguard works well, that system has only one tunnel with another site, using interface assigned mode. I depend on it, and it works flawlessly.
          Yet the wireguard configuration page, its status page as well as the services widget on the dashboard, all report the Wireguard service as stopped, with the usual icon to start it. On the dashboard the gateways widget shows Pending for the IPv4 and IPv6 wireguard gateways.
          On the other hand, and it is logical as the packets do flow through the tunnel, the Wireguard widget on the dashboard shows the tunnel up with traffic.
          To be complete, the watchdog service, if wireguard is configured there, spend its life at detecting wireguard stopped and attempting to start it, which does not work.
          The other side of the tunnel is still on 25.07-RELEASE (amd64). I'm reluctant to upgrade that side too, with fear to loose the wireguard tunnel altogether.

          Aren't there any logs from that wireguard package? I can't find anything of that kind.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.