Franco Fichtner
Franco Fichtner
Then you simply cannot use a WireGuard host name in the setup you have set up.
The OPNsense simply needs a working DNS server in /etc/resolv.conf for WireGuard to work. The issue that Dnsmasq fails to use WireGuard is because it expects an IP address which...
But you select interfaces, right?
Ok, I cannot recommend doing that in your case.
You can (re)start any service with the rc.syshook facility with a tiny script.
Good question. > At least can this PR become some kind of plug-in? Let me answer with what I already wrote. > in all fairness it would make more sense...
> there are enough browser choices that support it Yet!
@allenlook thanks for the report! when you call "https://your.firewall/api/diagnostics/proofpoint_et/status" in the browser does it load correctly? And if so how long does the load of the API page take? Cheers,...
Thanks, there seems to be a CA chain issue with opnsense.emergingthreats.net not including the intermediate: ``` # echo | openssl s_client -no_ign_eof "opnsense.emergingthreats.net:443" CONNECTED(00000003) depth=0 C = US, ST =...
Looks fixed from my end. Now we can go back to https://github.com/opnsense/plugins/issues/4943#issuecomment-3306314947