Project

General

Profile

Actions

Bug #11950

closed

Wireguard Package Errors and DNS problem

Added by RED SKULL 2 months ago. Updated 25 days ago.

Status:
Resolved
Priority:
Normal
Category:
WireGuard
Target version:
-
Start date:
05/23/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.6.0
Affected Plus Version:
Affected Architecture:
amd64

Description

Updated from Wireguard Package version 0.0.8 to 0.1.1 and receive the following error after every reboot:
@
Crash report begins. Anonymous machine information:

amd64
12.2-STABLE
FreeBSD 12.2-STABLE devel-12-n226634-bdf0424cb2b5 pfSense

Crash report details:

PHP Errors:
[23-May-2021 07:58:17 US/Central] PHP Warning: flock() expects parameter 1 to be resource, null given in /usr/local/pkg/wireguard/wg_service.inc on line 324
[23-May-2021 07:58:17 US/Central] PHP Warning: fclose() expects parameter 1 to be resource, null given in /usr/local/pkg/wireguard/wg_service.inc on line 327

No FreeBSD crash data found.@

Also DNS requests do not work at all unless I go to Wireguard assigned interface, click Save, then Apply. I also have to do this after every reboot.

Note: I have all TCP/UDP 53/853 requests from WAN to ANY blocked and only allow pass of aforementioned ports outbound over Wireguard interface. This may be useful when diagnosing. I have query forwarding enabled on resolver to DoH IP and domain but also notice the issue with regular port 53 DNS queries since upgrading to newest WG version.

Let me know if you need to know anything else about my setup

Actions #1

Updated by Christian McDonald 2 months ago

I actually caught the flock and fclose bugs last night and have them resolved. I will be submitting a PR tonight or tomorrow with a fix for that. It is cosmetic and was trivial to solve...seems like newer versions of PHP are more chatty than older versions when passing null resource handlers to these functions instead of just failing silently.

Let me explore the DNS issue a bit. Feel free to reach out to me directly rcmcdonald91 @ gmail

btw, thanks for the feedback! It is much appreciated

-CM

Actions #2

Updated by Christian McDonald 2 months ago

I'm not able to replicate the DNS issue, but I might not be completely understanding your configuration.

Can you try explaining it again

Actions #3

Updated by RED SKULL 2 months ago

Christian McDonald wrote:

I'm not able to replicate the DNS issue, but I might not be completely understanding your configuration.

Can you try explaining it again

Thanks for the quick response. Upon rebooting, I cannot resolve any website host name until I got th Interfaces -> 'WG' interface, click 'Save', and click 'Apply'. After that, I can resolve host names just fine.

Actions #4

Updated by RED SKULL about 2 months ago

No more DNS issue at boot after using MSS Clamp so disregard the DNS portion of this ticket

Actions #5

Updated by Renato Botelho about 1 month ago

  • Status changed from New to Feedback
  • Assignee set to Renato Botelho

WireGuard package version 1.1.3 was merged into 2.6.0 and 2.5.2

Actions #6

Updated by Kris Phillips 25 days ago

  • Status changed from Feedback to Resolved

PHP messages are gone in latest package in 2.5.2/21.05. Marking as resolved.

Actions

Also available in: Atom PDF