Unable to ping internal devices after WireGuard config

1

Hi, I am on pfSense 2.6 and I followed the Tutorial: pfsense Wireguard For Remote Access - YouTube to the letter but I am unable to ping the internal devices:

I am on a Mac and am using the WG app:

[Interface]

PrivateKey = Private_KEY

Address = 17.18.18.2/24

[Peer]

PublicKey= PUBLIC KEY FROM WG Server

AllowedIPs = 17.18.18.0/24, 192.168.55.0/24, 192.168.10.0/24, 10.1.20.0/24

Endpoint= WAN:51420

Any ideas ?

2

Could it be due to FW rules:

Lawrence:
WAN firewall rules:

2726×814 195 KB

Mine:

2416×1126 248 KB

3

WG done.

Thanks…

4

Does it handshake? Is your WAN a public IP?

5

It’s ok now … the tutorial was perfect

6

Hello,

Just curious how you resolved this issue?

In Allowed IP’s I used 0.0.0.0/0 as noted by the wireguard configurator.

All though I can see the network, I find I cannot ping computers on the network other than my AD server for some odd reason.

My question is, do I need the IP of the server that could be pinged, in the list of Allowed IP’s or should the 0.0.0.0 network setting allow all traffic?

7

allowed IP of 0.0.0.0 is a full tunnel vpn, where all traffic is send down the vpn tunnel and any internet will go out of the pfsense router.

Access to local devices is down on the wireguard filewall rules, do you have allow allow rules

image
image1144×60 5.43 KB
(rule is disabled, as I have other rules allowing internal access, yours should be enabled)

If you change the allowed IP to your network range x.x.x.x/24 are you able to ping devices

8

Well, I’m a dumbass. I just happened to be pinging computers that didn’t respond :blush:

Ping works. Carry on :smiley: