SOLVED: Wiregurad trouble after install and apply system_patches 2.2.11_16 in 2.7.2,
-
Thanks to @Bob.Dig and @slu for your help.
The Problem with my Wiregurad after after install and apply system_patches 2.2.11_16 in 2.7.2 is solved and honestly i have no clue why.
What was happen:
After update and reboot my Service Status was looks like above. Some more reboots of pfsense did not help. Still the same. Then i did shutdown the pfsense an did also reboot its host computer (pfsense runs in a VM).
No idea what makes the difference between just reboot the pfsense in its VM and shut down the pfsense and also reboot the host but that seems to be the solution.So hopefully this will help others in a similar situation.
-
@eagle61 My guess, it will come back.
-
we don´t see any issue with WG and the patch.
Maybe the reboot of the host had something to do with this gateway?
Nov 27 14:59:30 php_wg 6516 /usr/local/pkg/wireguard/includes/wg_service.inc: Static Routes: Gateway IP could not be found for 192.168.9.0/27 -
@slu said in SOLVED: Wiregurad trouble after install and apply system_patches 2.2.11_16 in 2.7.2,:
we don´t see any issue with WG and the patch.
Maybe the reboot of the host had something to do with this gateway?
Most likely you are right.
This is the Gateway:
It's as it was since month before. Nothing changed.I think the difference before reboot the host and after makes the blue line in this log parts:
That and the following line was missing before -
-
@Bob-Dig
But why is the Enabled all WireGuard gateways also mised before and now its there? -
@Bob-Dig said in SOLVED: Wiregurad trouble after install and apply system_patches 2.2.11_16 in 2.7.2,:
My guess, it will come back
It was coming back today after rebooting host and start the pfsense in its VM.
At least i now fond a solution without reboot the host and the pfsense.
Solution was to go to Interfaces -> WGTun0 (tun_wg0) and disable the interface, safe that and the enable the interface gain.
So i gust the WGTun0-Interface will not every time comes up correctly after rebooting pfsense. Something went wrong.
