Everyone,
Netgate helped me solve it. As usual, operator error.
It had wireguard on it, and I didn't know it. It was an ip conflict.
Yes, the firewall was open to make it easier to troubleshoot. I can close it down now.
Thanks !
Gary
@joshgreyz
Again we're off topic. Security updates. Period.
The other releases are mostly unrelated to what CE wants and needs. Only thing I can really think of is moving to new dhcp service...and that isn't exactly a severe security related thing just moving a very slight piece of the stack.
A large quantity of built in bsd vulns (of which there are few) don't exist here because they're compiled out - remember this is primarily a firewall/router that is designed to live in a hostile environment.
We're like 33 posts in and whining about release quantity. Specific patches are available when necessary, and they're available very quickly. Period.
@Patch yeah...development work is happening in areas that corp customers have been stating that are stoppers for a decade. Again...CE is not behind on security. You're measuring commits that include UI typos and saying that something that is completely unrelated to that is dead.
Moderators can we please lock this thread as it is literally just wandering in the desert complaining.
@bluecovenant said in getting DNS leaks:
hmmm i just rebooted with the "dns server override" unchecked, and got a leak again. any other suggestions? could this be a problem with how the vpn interface is set up?
@bluecovenant said in getting DNS leaks:
"dns server override"
I had same issue as you, and i resolved it by using DoT. See my thread here. The other not so elegant solution is to configure your DHCP server so it hands out proton DNS IP`s to your clients directly.
@patient0 said in Is it possible to access the pfsense console remotely?:
@jriofrio there are KVM-Over-IP available but they are mostly not cheap.
Like TinyPilot Voyager for $350 is an example.
Or a new one on Kickstarter is JetKVM for $69 according to their website (Lawerence System did a review on it). But be careful with Kickstarter projects, they may not come alive.
Or build a PiKVM... https://docs.pikvm.org/v2/
All you need is a Pi4 (preferably) and a HDMI to CSI module.
@comet424 resolving local resources that are listed in unbound be it via dhcp registration or static dhcp registration or host overrides has zero to do with any public dns service you would forward too.. They are not going to resolve your local resources, nor should they even i you put records up there because any ns you forward or that is not actually unbound itself that returns a rfc1918 address would be a rebind and is dangerous behavior.
Your issue has nothing to do with those patches. Please start a new thread about your issue specifically, not what you think caused them, because it is not the new patches.
Nothing in the new patches touches PPPoE either. You need to start a new thread with an appropriate title in the appropriate category and start with what your issue is not what you speculate the cause might be.
