Dpinger/DNS problem after upgrade - wireguard related?
-
Hi,
had that situation a few times with different customers already: It seems that if one installes/upgrades the Wireguard package that the last steps of the package (re)installation process seem to throw off or irritate the dpinger and DNS resolver services. Both are offline afterwards and the systems have problems afterwards - not that surprising with dpinger off and DNS unusable. Don't know why/how but that seems related to the last few WG versions. Also had a system and a lab VM upgrade to 22.01 or 22.05 and after rebooting saw the system in limbo with dpinger/DNS problems but didn't had a clue then why that happened. Today checked various customer systems and the last one had an upgrade for wireguard pending that I installed - boom, could see the impact afterwards. Package manager was unusable, clients didn't work as DNS was down etc. etc.
So perhaps if something is weird/running strange after updating/upgrading check if the wireguard package was updated and if dpinger and unbound (DNS resolver) are running properly or if those are stopped.
Cheers
\jens -
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
That's reinstalling the Wireguard package with an assigned Wireguard interface enabled?
Not sure I've ever tried that...Steve
-
@stephenw10 It's not only reinstalling, it's every update, too. Just happened today again as per a support session with a customer. Had 3 package updates pending, one of them was Wireguard. He klicked it, we watched, update completed, back to dashboard - bam - unbound and dpinger services down.
That's every time you reinstall or update the package. And no, he doesn't even have wireguard configured yet! No config, no tunnel, no peer nothing :)
-
Hmm, OK. I'm seeing that on a 4100. Digging....
-
@stephenw10 said in Dpinger/DNS problem after upgrade - wireguard related?:
Hmm, OK. I'm seeing that on a 4100. Digging....
Great job as always :)
-
@stephenw10 Just as a side note: still seeing that phenomenom in current snapshots / dev versions of the package. Install seems fine I guess (no immediate DNS/dpinger problem) but after upgrading/reinstalling the package you'll get it again.
