Regression #16513
closed
WireGuard service show status stopped but peers can still connect
Added by Bart Schapendonk 28 days ago.
Updated 14 days ago.
Plus Target Version:
25.11
Release Notes:
Force Exclusion
Description
- On the services page, WireGuard show status stopped, starting it doesn't work and I can't find anything in the logs. Peers can still connect and WireGuard seems to work.
- The ServiceWatchdog plugin keeps trying to start WireGiard.
This is on pfSense+ 25.11.b.20251028.1838
Re-installing the wireguard plugin did not work.
- Has duplicate Regression #16519: The service show not running but client can connect to wireguard server added
- Assignee changed from Christian McDonald to Marcos M
- Priority changed from Low to Normal
- Target version set to 2.9.0
- Plus Target Version set to 25.11
- Release Notes changed from Default to Force Exclusion
Marcos and I investigated this earlier today and he has the fix to commit at some point.
- Status changed from New to Feedback
- Affected Version set to 2.9.0
- % Done changed from 0 to 100
- Subject changed from WireGuard service show status stopped, but peers can stil connect to WireGuard service show status stopped but peers can still connect
just in case anyone wants to patch early using System Patches...
you have to remove the references to the Makefile since that won't be present on a normal system
add commit ID https://github.com/pfsense/FreeBSD-ports/commit/d569b16238046272ba2ef58552743e41e800df3d.patch
set Path strip count to 4
Use this Patch Content
--- a/net/pfSense-pkg-WireGuard/files/usr/local/pkg/wireguard/includes/wg_service.inc
+++ b/net/pfSense-pkg-WireGuard/files/usr/local/pkg/wireguard/includes/wg_service.inc
@@ -326,7 +326,8 @@ function wg_restart_extra_services($force = false) {
// TODO: This is where we will add facilities for users to pick what services to restart
- return true;
+ // 0 means success
+ return 0;
}
// Main WireGuard service loop
- Status changed from Feedback to Resolved
Also available in: Atom
PDF