HELP NEEDED - OPENVPN NO LAN ACCESS!!***
-
I started the packet capture and could see the replies from my 10.1.10.2 device (server which PfSense is hosted on). However when trying to ping my RDP server (10.1.10.13) there was no response i just get 'Request timed out' on my command prompt. The packet capture can see the echo request but no response. I have posted the results from the packet capture below:
So either 10.1.10.13 sends the responses to another gateway (improbably; I presume that pfSense is set as default gateway on the device) or it doesn't respond (block) to the requests (presumably, cause the request packets have a source IP which belongs to a different subnet).
You can easily demonstrate this with the ping tool from the pfSense Diagnostic menu. Try do ping the device with automatically selected source address (that's the LAN address if you're pinging a LAN device) and then select another interface address and try to ping again. Both come from the same interface (LAN), but with different source addresses.
Presumably you get no response from 10.1.10.13 if you select a different source address. -
Hi Viragomann,
I used the 'ping' diagnostic tool from within pfSense and when using Automatically selected source address or LAN as the source address i can successfully ping the 10.1.10.13 address. I'm unsure why but i had a seperate interface called OPENVPN, when pinging from this as the source address i couldn't contact the 10.1.10.13 address. However, there was another one in the list called OpenVPN Server: when pinging from this i DO receive replies from the 10.1.10.13 address! Not sure why this interface was created so i just deleted it. However if i change the source address to the WAN interface i get no responses from the ping. This is as you suspected but i'm unsure what this tells us? Does this give us anything further to go on?
Thanks
-
Can you show-
/status_openvpn.php
/firewall_rules.php?if=openvpn
/vpn_openvpn_server.php
/vpn_openvpn_client.php
~~You can make your tunnel network a /30. There is no need to have more than that. ~~
Nevermind that statement.. I was thinking site to site. You only need enough here for the number of devices you have. A /28 would be better. -
What is the client side device?
On the pfSense box you do not have OpenVPN assigned as an interface do you?
-
Hi,
I've attached the outputs that you requested in picture form below this post. I am connecting using OpenVPN client on my windows 10 Laptop. I connect to my phone's hotspot in order to not be on the LAN.
I am not sure whether i need to have OpenVPN as an interface? Currently i don't have it set up as one. Are you able to tell me whether this needs to be done? When i go to 'assignments' under the interfaces tab, it allows me to add OPT1 as it says 'Available network ports - ovpns1 (). Should i add this?
Thanks
-
However, there was another one in the list called OpenVPN Server: when pinging from this i DO receive replies from the 10.1.10.13 address! Not sure why this interface was created so i just deleted it. However if i change the source address to the WAN interface i get no responses from the ping. This is as you suspected but i'm unsure what this tells us? Does this give us anything further to go on?
That's truly strange.
The "OpenVPN Server" has 10.120.0.1. So 10.1.10.13 responses if the source address is 10.120.0.1, but it doesn't if the source is 10.120.0.2. ???Maybe something messed up with the network settings on the LAN computer?
The "OPENVPN" in the source dropdown of the ping tool was the interface you've assigned to the server. Have you also assigned an IP to it?
Assigning an interface to the OpenVPN server isn't needed in your setup.If you don't find a working solution you can get access by natting the VPN traffic as a workaround.
-
The "OpenVPN Server" has 10.120.0.1. So 10.1.10.13 responses if the source address is 10.120.0.1, but it doesn't if the source is 10.120.0.2. ???
10.120.0.1 is just part of his tunnel address.. has nothing to do with his actual networks. Just required address for the VPN tunnel.
I am not sure whether i need to have OpenVPN as an interface?
No- don't.
When your connected- is your laptop in the same subnet as your pfSense LAN?
What does your Windows 10 configuration file look like?On your open VPN firewall rule- make "Destination" LAN Net. Ive seen issues before with "allow all"
-
Hi Guys,
Sorry for my late reply, i've been trying to scour the internet all day but haven't been able to get nowhere with it. I haven't assigned an IP to the interface as i have now deleted the interface as you mentioned it wasn't required in my setup. How would we go about NATTing the traffic as you mentioned? Would that affect anything else & is it complicated to do?
When connected my laptop is in the 10.120.0.0/24 subnet (as per the Tunnel Address Subnet) whilst my LAN is 10.1.10.0/24 but i didn't think this would make a difference? I have changed the VPN firewall rule to make Destination as the LAN subnet as you mentioned but doesn't seem to have resolved the issue. My windows 10 configuration file is below with my IP Removed:
dev tun
persist-tun
persist-key
cipher AES-256-CBC
ncp-ciphers AES-256-GCM:AES-128-GCM
auth SHA1
tls-client
client
resolv-retry infinite
remote (MY IP IS HERE SO BEEN REMOVED) 1194 udp
auth-user-pass
ca pfSense-udp-1194-ca.crt
tls-auth pfSense-udp-1194-tls.key 1
remote-cert-tls serverUPDATE: I Don't seem to be able to ping ANY LAN devices now when connected to the VPN. I can see my connection in the clients list on the pfsense router however i'm unable to communicate with anything when connected. So i know the connecting is authenticating with the LDAP server and also being seen by pfSense as a connected client, but no communication is happening between my LAN devices over my VPN connection? Back to the drawing board i guess guys!
Hope somebody can help me resolve this, as it's turning into a real headache :-\
-
If you do NAT, the source address in packets coming from a VPN client and destined to a LAN device is translated to the routers LAN address. So the device sees the packets coming from its own network segment and will trust the access.
It's not difficult to enable it: Go to Firewall > NAT > Outbound, if you've never changed the NAT mode it will still be in automatic rule gen mode, so change it to hybrid mode and save this.
Then add a new NAT rule:
Interface: LAN
Source: Network - 10.120.0.0/24 (your VPN tunnel subnet)
Leave all other options at their defaults, just enter a description and save it. -
Hi Viragomann,
I did what you said with the NAT Rule however that didn't seem to work for my either. :'(
However, i just went into my OpenVPN Settings again and ticked the boxes 'Block Outside DNS' & 'Force DNS cache update'.
It now seems to be working great! Thanks again for your help with this.
-
So the problem was on hostnames?
You didn't mentioned that you use hostnames for trying to access. -
Then add a new NAT rule:
Interface: LAN
Source: Network - 10.120.0.0/24 (your VPN tunnel subnet)
Leave all other options at their defaults, just enter a description and save it.@viragomann
thanks, that solution worked for me :) -
I registered just to say thanks! What took me hours upon hours to figure out, this one thread did it for me. NATs! All the other sites failed to suggest that! They got into the weeds about tun vs. tap yadda yadda. But NATting is the fix. Thanks again!
-
@viragomann This is exactly the fix for me. I spent hours trying to figure out where the stop was.
Thank you. -
This post is deleted! -
@viragomann said in HELP NEEDED - OPENVPN NO LAN ACCESS!!***:
If you do NAT, the source address in packets coming from a VPN client and destined to a LAN device is translated to the routers LAN address. So the device sees the packets coming from its own network segment and will trust the access.
It's not difficult to enable it: Go to Firewall > NAT > Outbound, if you've never changed the NAT mode it will still be in automatic rule gen mode, so change it to hybrid mode and save this.
Then add a new NAT rule:
Interface: LAN
Source: Network - 10.120.0.0/24 (your VPN tunnel subnet)
Leave all other options at their defaults, just enter a description and save it.This solved my problem. Thank you very much
-
@viragomann 10x. Hours on google and your solution make my day. NETGATE should advertise this solution.
-
@fabiancj said in HELP NEEDED - OPENVPN NO LAN ACCESS!!***:
NETGATE should advertise this solution.
Don't agree. It's only a workaround at the end. I'd only recommend it if there is no other way to communicate with the remote device, like no gateway option on the device.
But I don't approve to use NAT to bypass firewall restictions on the destination device as lang as there is an ability to add the needed rules to it. -
Hi everyone! I just wanted to pitch in what worked for me when I ran into this problem. Perhaps this wasn't exactly the problem that any of you experienced, but it might be one more thing to consider when troubleshooting.
In my case, I unknowingly set up my VPN server to use TCP, rather than UDP. Using the wizard, I thereby automatically generated a firewall rule for that VPN server that specified TCP.
After reading through some other posts, I figured that I couldn't get access to my LAN subnet because I was trying to use TCP. So, I switched over my VPN server to UDP (and eventually figured out I also needed to change the firewall rule to UDP as well), and I finally was able to access my LAN subnet.
I don't know if this is really a solution, but it's ultimately what got my setup working how I wanted it to. Perhaps someone with more technical knowledge could explain why it wouldn't work on TCP (or why it should have).
-
What your vpn connection used be it tcp or udp had nothing to do with access to lan devices..
