Hi,

let see - so when Client firewall is disabled you can ping the client? So your problem is Windows firewall, not WireGuard. Everything looks to me normal.

@orkopaede said in Can't connect to Clients within LAN via Wireguard:

What i find out so far:

When the client Firewall (Windows Firewall) is disabled i can ping the client

I hope someone have an idea what i could try to fix this problem.
Thank you in advance.

I am as well. I couldn't figure out what it was so I just went and used NordVPN's OpenVPN protocol instead, which seems to work just fine.

@slkamath

Thank you everyone.

No proper support for Wireguard, So I have uninstalled WG.

Thanks & Regards
Lokesh Kamath

@jim-bob-the-grand I've just set up with my VPN provider (vpnunlimited) and wrote an instruction here. I believe it could apply to most VPN provider:

WireGuard to VPN provider

@chudak Thanks. Updated and got it.

@dross The instruction regarding gateway automatically created is wrong. You have to add gateway manually.

For peer (the VPN provider side), the instruction is correct. The only address you need to input is the end point public address you obtain from the provider; and the allowed ips, which is usually 0.0.0.0/0

@nogbadthebad Thanks. I got it working with only a few steps, without any routing. Just create a new tunnel, new peer, new interface, and a new vpn gateway, based on setup config obtained from vpnunlimited. Then just create a firewall rule to allow, in my case, a whole subnet address to access all via the new vpn gateway. The chosen subnet belongs to one ssid I created just for Wireguard vpn connection.

I will write a more detailed instruction and post it here very soon.

Update: I've just posted my more detailed instruction here:
Instruction-WireGuard to VPN Provider only for a specific subnet

@bcruze pfsense forwarded 1.1.1.1 by itself. i tired regeneration, no luck.

edit: no pihole... I think it forwarded 1.1.1.1 because I have forward dns servers checked.

A small mistake on my part. Changed the subnet from /32 to /24
254e828c-e599-41fe-878d-76442129949d-image.png

Now it´s working again :)