wireguard site-to-site problem in 0.2.0_2 -

mooncaptain

Sorry about the vague description.

I had this working in an older version and I also had it recently working in version 0.2.0_2. However I had to rebuild my home pfsense recently (operator error) and since that time I can't remote desktop or access local web sites on the office side of the VPN.

I followed the setup steps as described by Christian McDonald's video covering that subject. (https://youtu.be/2oe7rTMFmqc)

The WireGuard status indicates both peers are connected and passing bytes.
WireGuard tunnel is up.
Gateways are online on both sides.
Interfaces up on both sides.
traffic moving back and forth on both Interfaces.

I can't ping target hosts on the other site from a workstation but I can ping from the pfsense utility.

Also using trace route pfsense utility and can see the correct routing.
trace route from my desktop fails.

Also ping utility fails when I select localhost as the source.

I have rules configured for the vpn interfaces to allow all traffic.
Also rules on the WAN to forward UDP traffic to 51820 - both sides

Any ideas how to debug this?

mooncaptain

so... In WireGuard settings I disabled keep config
uninstalled on both office and home router
I left all the routing and firewall rules in place
recreated tunnels and peers
And... that worked

Same setup as previously but I recreated the office from scratch this time.

JustAnotherUser

@mooncaptain

I had the same problem. HERE was my fix-

https://forum.netgate.com/topic/181857/solved-wireguard-interfaces-ping-but-can-t-get-actual-data-through