Client Device says it connected. But pfSense doesn't seem to agree.....
-
I have my Android phone (Google Pixel 6 Pro) setup with the Wireguard app. When I activate it within the Wireguard app, it says it connected fine. But even though allowed IPs is set to 0.0.0.0/0, it won't connect to any websites and when I look within pfSense at the peer, it shows that it's NEVER had a handshake.
I'm at a loss as to where I should begin troubleshooting this. In the first screenshot below, you can see that it's connected and transmitting data but doesn't receive a response. In the second screenshot, you'll see that pfSense indicates that it's never had a handshake with either client. The pixel 6 is the one that is shown as connected in the first screenshot.
-
I got it resolved. I have a bit of an unusual situation. The modem provided by my ISP has a built-in router which I don't want to use. I had originally planned to downgrade it to pass-through mode (so it would only function as a modem). I had the ISP make the change for me as they are the only ones who can do so.
But no matter what I did, pfSense refused to connect to the internet that way. So I had them put it back the way it was. pfSense uses it as the gateway but it sees the ip address assigned to in internally as its "public IP address".
Dynamic DNS still works because we're making external calls to update the DDNS and the remote DDNS server knows the external IP address.
It's been running like this for more than a year without a hiccup. Anyway -- I had to login to the ISP router and tell it to forward port 51820 to the pfSense router. As soon as I did that, my phone was able to connect without a hitch and access my home assistant server via the VPN (I turned off WiFi on my phone for the test).