Our documentation has a few recipes:

https://docs.netgate.com/pfsense/en/latest/recipes/index.html#id1

@Bob-Dig Thanks for replying. Here are screenshots of the config. Let me know if you need any more.
WG1.png WG2.png WG3.png WG4.png WG5.png

It wasn't a DNS problem. After reviewing the logs and error notifications, I believe there were problems with pfBlockerNG DNSBL service and pfBlockerNG firewall filter service. Once I disabled these services Wireguard and OpenVPN worked like a charm. I tried to reinstall pfBlockerNG, unfortunately pfBlockerNG DNSBL and pfBlockerNG firewall filter services did NOT restart. Any suggestions?

It is working now. It is just the MAC. When I use a Windows and use AllowedIPs = 0.0.0.0/0 it is working now: both full tunnel and split tunnel.

However, in my case (BTW-I found the backup and note), for some reasons, in the NAT Outbound, I use the LAN and not WAN as the Outgoing then everything is working as I expected. Strange but it is WG and experimental package.

Seems to work ;-) thanks again @Bob-Dig

@griffo Same thing happened to me. Glad this thread was in the forums because, yeah (head slap), of course I should have set the client's DNS address to the Wireguard interface on the server. Thanks for posting!

@paczka I also encountered this situation. Need to restart the wireguard service

@dma_pf

Are you talking about the dns server in wireguard or dns server on the wan port of the 6100? My lan ip for the 6100 is 192.168.2.1 and the wireguard vpn is 10.1.1.1. In my peer config I have allowed ips = 10.1.1.1/32, 192.168.2.0/24

@_rp No, I tried a couple sets of scripts but gave up trying to get them to work. I'm sticking with OpenVPN until the WireGuard process improves.

Still having this problem.
Thinking about ditching most of the peers, as it is hindering functionality.
Back to OpenVPN by the looks, disappointing Wireguard implementation as a complete package.

The problem is well known
There is no solution I know of.

https://forum.netgate.com/post/1081694

https://forum.netgate.com/topic/177255/wireguard-site-to-site-gateways-disabled-after-reboot-service-not-starting/7

@edjusted Sorry, I never found anything. I had to setup the tunnel fron scratch.

@bob-dig said in Strange login from another country:

@pastic said in Strange login from another country:

I realise something as I write this: are there 'two levels' involved here? The wireguard rule will let everyone through the firewall on the specified port, but having passed the firewall block then the wireguard service will still refuse everyone that does not have the configured keys?

Yes. Hard to believe that this is news to you, you are setting up a graylog server, which is advanced stuff in my book.

Let's call it a blind spot. :-) I don't work with networks, it's just a hobby. And until this Wireguard 'project' I always had pfsense blocking everything from the outside.
And yes, I did struggle a bit setting up graylog, but it was fun.
Thanks!

I have two internet connections on my pfsense.
I also noticed sometimes the VPN connection stays up but it stops routing data over the wireguard link till i restart the wireguard service.