VPN doesn't allow acess to Lan (or internet), but does connect properly.
-
I'm not very used to forums, so forgive me if I make a foux pas.
So I have been trying to use a VPN to connect my phone (and later other devices) to my home network, but I have run into an issue. The VPN connects (I have tried both IPsec and OpenVPN), but when connected it doesn't seem like any traffic goes through. I can't ping the remote device, but I can check and see that it is allocated an IP address and is connected. I have check all of the firewall rules for both VPNs and the LAN as well. I have tried to figure out the issue but I can't identify what it could be. My only thoughts are that it could be an issue with the subnetting, but I don't see what the issue would be. The default subnet I use for my LAN devices is 10.27.27.0/24, with 10.27.26.0/24 for IPsec and 10.27.25.0/24 for OpenVPN. I have gone through and check the firewall logs at the time of the connections and it seems fine, but I just can't tell what the issue would be.
For IPsec I have tried both having the P2 using the Local Subnet as both "LAN Subnet", 10.27.0.0/16, and 10.27.27.0/24. None has worked.
Firewall rules for both VPNs are set to allow all traffic, with IPsec having both IPv6 and IPv4, and OpenVPN having only IPv4.
All of this is on PFSense CE, 2.9.0-RELEASE.
I am working on learning computer networking in a more hands on way, so I tried a lot to fix this, but I just haven't found what the issue could be so I'm posting to see if someone who knows a bit more could give me a hand here or point me in a good direction.
-
@Unique does your ISP rotate the IP on the modem?
Because if you have dynamic IP, you need to setup Dynamic DNS and point your VPN endpoint at that domain instead of hardcoding the IP.
-
@dmcc I don't think so, but the issue isn't really the connection. I have always (aside from user error haha) been able to establish a connection, just not able to access the Lan Subnet, including the router (which is the VPN concentrator). I can see in the logs and other places that the remote device is connected and assigned an IP.
-
@Unique are you able to ping the gateway once you've connected to the tunnel?
-
I have it setup on my phone so I just setup Termux and did a ping on my Wi-Fi where it does work (as a control), and then I went to mobile data + VPN and there is no response on the ping. The VPN connection is successful, and I can see in the Status > IPsec page that my phone has been given an IP.
The router is 10.27.27.1 and the mobile client (my phone) is 10.27.26.1
So to answer the question, no.
Sorry about the delay.
-
The router is 10.27.27.1 and the mobile client (my phone) is 10.27.26.1
10.27.27.1 is your pfSense LAN interface.
You don't need to do anything with the LAN.I'll take my pfSense as an example.
My LAN : 192.168.1.1/24 (I never bothered to change it, it's the default).
This isn't important.
I have another 'LAN (OPT1) using 192.168.2.1/24. - 'who cares ?' ^^
So, this seems logic to me : the OpenVPN server :

Note that I 'force' traffic through the VPN connection (redirect IPv4 Gateway).
This means that when I connect my phone, using the OpenVPN app, to my pfSense, I see this :

Where "92.184.98.176" is the IPv4 of my phone on the phone network.
And 192.168.3.20 is the OpenVPN 'client' = my phone - IPv4.The OpenVPN server assigned upon connection my phone client tunnel IPv4 192.168.3.20, very much like a dhcp server should do.
Both server and client must be in the 192.168.3.0/24 network, and they are.
My OpenVPN firewall rules :

"VPNS Network" is a pfSense alias for the 192.168.3.0/24 network = my OpenVPN tunnel, see image above.
Note that I don't use the generic "OpenVPN" firewall rule page, it's empty.
I created a :
where 'opvpns1" is my OpenVPN server.
My VPN > OpenVPN > Servers settings are pretty default.

means no password/user, just a certificate to identity.
Btw : only the VPN firewall rule(s) matter.
Nothing on LAN is needed. LAN firewall rules are only used for incoming (INTO) the LAN NIC.
Like OpenVPN rules, WAN rules etc.My WAN does contain of course this rule :

because incoming VPN traffic (UDP, port 1194) needs to get 'into' pfSense so it can reach the openvpn server process running on pfSense.
-
@Gertjan
I appreciate the response, but the issue I'm having is specifically the LAN routing. I can establish a tunnel just fine on both IPsec and OpenVPN.I do have an OpenVPN setup similar to yours, just with User Auth.
Here are the rules for OpenVPN:

And for IPsec:

And for the WAN:

The issue I am having is not a connection to the concentrator, but rather the fact that once connected it is impossible to communicate with any other device, even the gateway. I have done this successfully before on an older version of PFsense, but I had to reset the device so now I am doing it again and now it doesn't work.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy