for future reference, this was an unexpected self made problem, I selected the dev channel as was tempted to try the latest pfplus 22.05 beta but never upgraded, this however I found sets packages to the same channel so 0.1.6_2 isn't compatible with 22.01

Many thanks !!

On the Windows box with the share, goto firewall. Inbound connections.

Find File and print share, SMB. Hit scope tab and allow all. Was set to Local IP only.

She logs in and is asking for credentials. Perfect, exactly the direction I was looking for. I normally only log into linux box's via VPN. So I forgot all about that.

Again thanks for quick response!

@joshhboss I hit this same issue today. I found https://redmine.pfsense.org/issues/11494 and the system tunable you used is mentioned there as well.

I hope for a proper fix at some point but this seems harmless enough.

Solved by watching a video from Christian McDonald. The change was to the settings in the peer (client) app. I set the DNS address to the tunnel address (192.168.85.1) rather than my pfSense address.

Yes that's how I do it also. I'm experimenting with FRR now to dynamically discover the routes instead of having to manually define them.

@crowfather said

What does the WG config file look like? (Redacting private information obviously)

IMG_3487.PNG

@ofloo Figured it out, bgp raw configuration was overwriting the configuration. So basically never got updated kept running old config.

Must of updated configuration and hit save at some point in the past.

I figured it out. I had State Killing on Gateway Failure enabled under System/Advanced/Miscellaneous. Disabling it resolved my issue

@skippythemagnificent
This could be a hosted vpn with many clients and allowing client2client communications.

@cmcdonald Wireguard ignores my static routes, even after a reboot. It seems to always use the default route. Might be a bug? Btw, thanks for your work with Wireguard.