@kamate said in how to import ovpn file: But i cannot find exact informations about how to import the ovpn file into pfsense. Hi, it is not literally an import, but that's the way to do it... these links (VPN services) describe the method and more... -simply apply to your own VPN client settings https://www.expressvpn.com/support/vpn-setup/pfsense-with-expressvpn-openvpn/ https://support.nordvpn.com/Connectivity/Router/1089079142/pfSense-2-4-4-setup-with-NordVPN.htm do not use special things that depend on the VPN provider BTW: if possible use cipher aes-256-gcm instead of aes-cbc

Thanks for the NSIS proposal. I will check it out.

@johnpoz Ha! No, it's AES-256-CBC

@wmcneil Ok then, the important thing is to have a pf working dns. Just remember not to block access to dns with rules.

[SOLVED] I'm going to resume the steps to help others: Clean installation of PfSense Add OpenVPN server in manual mode, not Wizard Try to connect a client and take a look at inbounds connections at firewall, select the rule to the 1194 port and Permit it. Modify the rule to allow any host to connect to the server That's all, at least for me. I have the OpenVPN server working and clients can ping a host through a second router behind PfSense. I hope it helps! Thank you very very much! special thanks to netblues without whom this wouldn't have been possible. Thanks!

@powerextreme Filtering with OpenVPN When the OpenVPN interface is assigned, a tab is present under Firewall > Rules dedicated to only this single VPN. These rules govern traffic coming in from the remote side of the VPN and they even get the pf reply-to keyword which ensures traffic entering this VPN interface will exit back out the same interface. This can help with some more advanced NAT and configuration scenarios. Note Rules added here are processed after the OpenVPN tab rules, which are checked first. In order to match the rules on an assigned VPN tab, the traffic must not match any rules on the OpenVPN tab. Remove any “Allow All” style rules from the OpenVPN tab and craft more specific rules instead.

Hello everyone, i think i found the solution for this. I will try to use the Mikrotik as the loadbalancer of the 3 Wan connections and pfsense as the lease handler as my initial setup is. Although i am going to physically Bypass the Mikrotik router, connect the second Wan interface of my pfsense directly to my service provider main router. This second Wan would act as the link for Openvpn only and not a gateway to the Lan clients on the pfsense box

@bomburly Even my plex server is capping video quality at 712kbps.. And this is through the PLEX app without the openVPN server active. It seems like a pfsense issue or maybe even a unraid issue?

@pwnell You are welcome.

@pfStew Just think of the VLAN and VPN as 2 separate interfaces and set up routing and rules accordingly. The fact that they're a VLAN and VPN is irrelevant. as they both provide an IP connection.

What type of OpenVPN are you running exactly with pfSense? S2S, RAS, Client? Maybe you can share some bit of your configuration. -Rico

A server configured that way (non default) will be hard to "import" into pfSense.

Yes, you can use them like you would do with Multi WAN. https://www.netgate.com/resources/videos/openvpn-as-a-wan-on-pfsense.html https://www.netgate.com/resources/videos/multi-wan-on-pfsense-23.html -Rico

Already done this on the SITE2 (VPN Client) but still no working [image: 1595282143051-capture1.png]

Addendum: you could try running your script with the up, up-restart etc hooks. Perhaps that also needs script-security 2 to be enabled, I'm a bit vague on that :) But if it does, it will say so in the logs. The up trigger keyword in your client config should run your script with info like <scriptname> OpenVPN 1 1500 1553 <IP> <mask> init You don't have the same sort of variables at your disposal as on the server side though. Check https://openvpn.net/community-resources/reference-manual-for-openvpn-2-4 for the exact ones :) (search for bytes_received for examples)

Got it, thanks for all the help!