Site to Site, OpenVPN config file
-
Today I setup VLAN with trunking and all in Cisco command line + pfsense, not too bad, proud of that.. a tech-orgasm. And OpenVPN seemed easy aswell!.. that is until I am not configuring two Pfsense boxes it seems…
That OpenVPN client program for Windows blows my mind, It's GUI, yet there is a somewhat tricky config file. (is there another program?)
I found examples of how the config file should be, but it doesn't seem to have all the input field examples id want it to have?, in the examples i've seen atleast. I have a good idea on how to setup a Pfsense client, but this, no. Server side is already setup.
Could some give me an example of OpenVPN config file, Site-to-site with pfsense.
The key goes in seperate seperate file?, should all but the key itself be removed?.Any link to article or video that I haven't seen, which is awesome, would be great too.
-
Just use the client export package.
Go to whatever passes for Add/Remove programs these days and remove everything OpenVPN.
Install the OpenVPN Client Export package in System > Packages
Go to VPN > OpenVPN, Client Export
The users will be listed at the bottom. If there are none, you did something wrong.
Use Windows Vista or Later
Install the resulting package.
If nothing else, the resulting files will get you really close to making your own.
-
Just use the client export package.
Go to whatever passes for Add/Remove programs these days and remove everything OpenVPN.
Install the OpenVPN Client Export package in System > Packages
Go to VPN > OpenVPN, Client Export
The users will be listed at the bottom. If there are none, you did something wrong.
Use Windows Vista or Later
Install the resulting package.
If nothing else, the resulting files will get you really close to making your own.
Thanks, I didn't know there was such a package.
I couldn't see any clients to export, so yes, something must had been wrong.. trying to fix now :). Might have been conflicting tunnel network address.
**2 slightly off-topic questions.. **
When I see people setup Pfsense as a client they assign a interface in the interface/assignments tab. What about when you setup the server side?, I see there is a interface to assign now "ovpns1 ()" when just the server portion is configured, but you never need to do assign that?. They never do in articles or youtube guides.When server is setup, I see the service is running, but on dashboard panel it says Server is down with red arrow… it only shows as up when there is connection from client?.
-
Ok, a bit funny i think… I couldn't get anything to show in the "Client export" tab, which I could export... but the "Shared key export" seems to give me a good config file I can use... I imagined it only exported a key file, not a config.
-
If you were using SSL/TLS, then the exporter will only show users with certificates created by the same CA set in the OpenVPN server as the Peer Certificate Authority. Without that they wouldn't be able to log in anyway so they are not shown for export.
There is no Shared Key remote access server so I don't know what you actually did.
Why are we talking about the Windows client when you're dealing with a site-to-site?
