Very Confusing is OpenVPN Setup
-
Hello. I'm sorry to have to write this, but all the documentation and tutorials on the internet do not explain properly the step-by-step procedure for creating a user > assigning a cert > creating a client and making the configuration downloadable from Client Export. Can someone well-versed in pfSense give the masses a step-by-step guide that we can follow?
Thank you!
-
@rwhitney I followed this tutorial on YouTube many years ago. https://www.youtube.com/watch?v=VdAHVSTl1ys
Worked a treat, as the Brits say. IIRC, there was a point where he used the wrong cert, but if I could figure it out... LOL
-
@provels Thanks for the link! Looks promising.
-
@provels - sorry but this seems too old
-
is there no one who has been through this before? I know it is very cryptic, what steps to take. I had the entire thing setup a one point - was able to see the remote network (other servers), but waited about 6 weeks to try again, and something must have changed - now I can see the firewall and make changes, fortunately, but no other servers. I'm going Titanic! Please help me!
-
So your connection is established successfully.
If you are able to access the remote pfSense by its LAN address, maybe you are blocked by the destination hosts firewall.
-
how does this look? Wait viragomann, I see what you mean. - None of the other hosts use a f/w
-
That's the WAN rule allowing access to the OpenVPN server. Since the connection is up, as you say, i'm not in doubt, that this rule is working.
So what? Are you able to access pfSense by using its LAN address?
Is pfSense the default gateway in your LAN?
-
@viragomann yes I am able to connect to 10.0.8.1 (the pfSense F/W) thru the vpn and can see no other devices
-
I was asking for the LAN IP! You didn't mention what 10.0.8.1 is, so I don't know.
Are you able to access pfSense from the remote client by using the LAN IP?
-
-
@viragomann no I am not able to see the LANip
-
So the routes on the client aren't set as the should be.
Have you watched the hangouts?
In the OpenVPN server settings you have to put your LAN network into the "Local Network/s" box to get the route pushed to the client. Have you done this?
-
@viragomann yes I have set the route LAN network to 192.168.0.1/24
-
It would be helpful to have a look at the clients routing table.
-
Is the LAN network on the client also 192.168.0.0/24?
-
@viragomann I'll try to get to it tonight or tomorrow morning I'm in Arizona And I can send you a screenshot And thanks for your help
-
@viragomann I'm sorry, yes pfSense is the default gateway to my LAN
-
@Derelict yes I believe so If I follow you correctly the client LAN is 192.168.0.1/24
-
@viragomann interesting is the static routes table is blank. Could it be that there needs to be at least one entry there for the VPN to- work properly?
-
The clients LAN must not overlap the remote LAN, least of all it can be the same subnet. If so it's not possible to access the remote site.
I've never seen an empty routing table on a device which has internet access. There must be at least one gateway and one route.
When a OpenVPN connection is established and a route is pushed by the server to its LAN network, you should see this route pointing to the servers IP, probably 10.0.8.1, as you mentioned above you can access pfSense by that IP.
-
@viragomann again my apologies - my local LAN is 192.168.1.1/24; the LAN I am trying to remote into is 192.168.0.1/24
-
I am attaching a screenshot:
this is the default gateway and the Static Routes table is again blank
-
The routing table is the key here, but that one of the client!
-
@viragomann How do I display the client routing table or which one do you need to see?
-
@viragomann does this help?
-
The first step to configuring a VPN is understanding what it is you are actually doing.
On the client, connect the VPN. Then print the routing table.
Some common command lines:
Windows:
route print
Mac:netstat -rnfinet
Linux:netstat -rn4You can use Diagnostics > Routes in the pfSense software.
-
@rwhitney said in Very Confusing is OpenVPN Setup:
I have set the route LAN network to 192.168.0.1/24
That should be 192.168.0.0/24 in the local subnets field. Unless you have set
Redirect IPv4 Gatewayin which case that should be not set anywhere as everything is routed.Steve
-
@Derelict please pardon my dust as I AM learning!
=========================================================================== Interface List 4...d0 17 c2 02 fb 3e ......Realtek PCIe GBE Family Controller 18...16 c6 3b 02 82 0f ......Microsoft Wi-Fi Direct Virtual Adapter 13...26 c6 3b 02 82 0f ......Microsoft Wi-Fi Direct Virtual Adapter #2 19...00 ff f9 1a 4d b8 ......TAP Adapter OAS NDIS 6.0 16...00 ff e2 a9 d8 ab ......TAP-Windows Adapter V9 10...74 c6 3b 02 82 0f ......Qualcomm Atheros AR9485 Wireless Network Adapter 1...........................Software Loopback Interface 1 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.12 55 0.0.0.0 128.0.0.0 10.0.8.1 10.0.8.3 291 10.0.8.0 255.255.255.0 On-link 10.0.8.3 291 10.0.8.3 255.255.255.255 On-link 10.0.8.3 291 10.0.8.255 255.255.255.255 On-link 10.0.8.3 291 98.174.x.x 255.255.255.255 192.168.1.1 192.168.1.12 311 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 128.0.0.0 128.0.0.0 10.0.8.1 10.0.8.3 291 192.168.1.0 255.255.255.0 On-link 192.168.1.12 311 192.168.1.12 255.255.255.255 On-link 192.168.1.12 311 192.168.1.255 255.255.255.255 On-link 192.168.1.12 311 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 10.0.8.3 291 224.0.0.0 240.0.0.0 On-link 192.168.1.12 311 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 10.0.8.3 291 255.255.255.255 255.255.255.255 On-link 192.168.1.12 311 =========================================================================== Persistent Routes: None
-
@stephenw10 setting it to 192.168.0.0/24 does not seem to make a difference - I did have it set to Redirect IPv4 Gateway, but have removed that
-
Just to indicate my gratitude to everyone who has offered advice in this thread - thank you! (I am not yet connected to internal LAN however)
-
It's still sending route all and not just 192.168.0.0/24.
Try restarting the server end to be sure that new setting in place and then check the Windows client routing table.
Steve
-
@stephenw10 so reboot the netgate server? I will have to wait a couple of hours first
-
No. Restart the OpenVPN process. (Status > Services, stop it and start it. This is restarted when you make a change like disabling the redirect gateway push but Steve is just being thorough.)
-
@Derelict I just restarted the running process for openvpn. I did just notice that I am getting a connection error: key registration failed to occur within 60 seconds... I am trying this from a Windows laptop at work through an external wirelass network. I don't have this connectivity problem from home on my linux box - just from there I still cannot see the local LAN here at work. All I can see is the firewall
-
@viragomann Here is my server setting for Tunnel:
I do not see a setting for Remote Network in OpenVPN > Server
-
@rwhitney
That was wrong. It should be "Local Networks".
I'll correct it above.
-
@viragomann Oh, so I do have something correct?!!
-
@rwhitney
Yeah!
-
@viragomann
If I were to start from scratch, what would be the first thing to do? (setup the Cert?)
second: setup an openvpn server: (I think I have this set).
Third: setup a user?
Fourth: setup a user cert?
Fifth: download config from Client Export
What am I missing?
