i wouldnt know.. why cant pfsense know if the WAN connection is a private or public IP... so much for just simple Asus router.. you set it for DHCP or PPPOE no problems it does it for you you dont need to know anything i know basics 192.168.x.x is private network.. 174.x.x.x is public NordVpn said its a issue with Pfsense i posted in the forums and no one could answer the question.. one guy wouldnt even look at the video to see my problem he didnt try to help if he watched it then he would see what problem i having.. just get bashed more for even trying.. its like taking your car to a mechanic you tell him what your issue is you video tape your issue but he cant be bothered to look at it and say your wrong you dont know what your talking about your not having a problem i didnt scream bug i asked a question there is no screaming i never wrote caps i wasnt the person that said i i not going to watch your video to see what problem im having from other guy.. and you say the difference from Public and Private.. shouldnt pfsense know what a Private IP and Public IP on the Wan connection and route it properly by just choosing your options PPP PPPOE STATIC DHCP etc as i figured once you set your WAN interface thats your internet.. and when you set your lan or the OpenVPN Server to connect to the WAN interface its like WAN interface is like an interperter you speak english to the interpertor and the WAN connection automaiclly interpertes like french it to the internet accordling but im guessing this stuff is more complex then just choosing guess ill do more research since there are no discussions on to set WAN interface for OpenVPN not to use PPPOE as i dont understand why i get blasted for using PPPOE what is wrong with using pfsense to log in PPPOE its like a death using it.. but its option when you setup pfsense from a factory reset or new install.. choose dhcp or pppoe etc and OpenVPN server remote access works fine in PPPOE but doesnt in dhcp mode and NordVPN cant use PPPOE as it ruins there connection they say guess they need a private ip address not your public ip address.. but i didnt cause problems like i said guy from start was disrespecting me not even bothering to read i stated i had 2 problems didnt wanna look at a video to see what problems i dealing with.. all i got was basiclly bashing.. i ask for serious help and i get bashed that i idiot for using PPPOE we simple home user people arent using this pfsense software day in day out like you networking people.. but thanks for the reply.. since i apparently screaming i not going to get help from the other forum.. and like i said i never screammed nothing i get blasted by the other guy... where is the help to novice home users i just gonna keep my mouth shut in the other forms not reply i dont wanan cause problems i didnt ask to get in trouble didnt mean to sound screaming i just wanted to be respected and i didnt get respect right from the get go thanks for your replies.. i wont distrub you either.. sorry i caused so much problems

not sure what a RasPi is but i guess ill google how to port forward so OpenVPN Server REmote access setup then

and i followed the CrossTalk video steps to do this and there is no 1194 in it that i set https://www.youtube.com/watch?v=Q6YbCQEiC3c

@gertjan client vpn is behind the firewall and it is blocking the traffic ..now it is working fine ...thanks for your support

@p9wgnzxcsd said in OpenVPN Service not running: remore-cert-tls Did you add any extra options in the advanced config? Maybe mistyped remote as remore?

@johnpoz said in To VPN or not to VPN?: "I think I read that you can bind specific applications to a specific NIC." Good luck with that ;) If you want to bypass using your vpn, easy way to do it is based upon policy routing.  So where you want to go bbc iplayer - what is the url you connect to?  I could be as simple as creating an alias putting in the sites you want to go to and using that alias as your dest in rule that send that traffic out your normal wan. Depending on the site you may need to do some investigation on what exact networks they use via some CDN in the backgroun that is not really clear in just the url you use to get started, etc. Other option to this is to do it the other way around, use your normal wan for most of your access and just send the traffic you want out the vpn - sometimes it is easier this way since sites you want to vpn might be smaller, etc. Not sure where you got the idea that applications allow you tie them to specific nic or IP - this is pretty rare in the windows world for sure, and in client applications.  Server applications are more likely allow you to tie them to a specific nic or IP.. There may be some addons for the browser your using that add this sort of feature..  But to be honest policy routing better solution if you ask me, since then doesn't matter if the application supports it or not. Thank you to both of you, I just went online to see if someone is also experiencing the same thing with VPN and I'm happy I found a solution.

No, that is correct. AES-NI is not available here in the droptown, but it is used anyway. In pfSense 2.3 it was still available there, however the recommended selection for AES-NI capable CPUs was to select "No hardware crypto". But it has to be enabled in the System > Advanced options.

FreeBSD 11 isn't technically supported until ESX 6.5 so it's possible you have a compatibility issue causing stability there as well.

@protar Nope, nothing to do with Android. the pfSense is a OpenVPN client to a few servers. It was indeed a DNS issue then getting stuck in a routing or nat loop. I'm still looking into ways to delay the other vpn connections to start so that I can use my internal DNS server that utilizes the first VPN connection outbound.

Thanks.

@maverick_slo said in How to block access from roadwarriors: @unaibg You can totally do it with rules and client overides. Assign static IP to that client, and make rules that fit your situation. Its just as secure as separate tunnel.. IF rules are smart designed of course I assign clients specific IP addresses via Freeradius. "ipsec-test" Cleartext-Password := "PASSWORD-WAS-HERE", Simultaneous-Use := "1", Expiration := "Jan 01 2020", NAS-Identifier == strongSwan Framed-IP-Address = 172.16.8.254, Framed-IP-Netmask = 255.255.255.0, Framed-Route = "0.0.0.0/0 172.16.8.1 1"

Yes. Fairly advanced OpenVPN concept though. You have to assign an interface to the OpenVPN client instance at Site A and be sure that the port-forwarded traffic does not match the firewall rules on the Site A side's OpenVPN tab and only matches a firewall rule on the assigned interface tab at Site A. This gets reply-to working there preventing the reply traffic from the port-forward target host from being routed out the default gateway at Site A and routing back through the tunnel instead. I am not certain this specific use case was covered but you might do well to watch this: https://www.youtube.com/watch?v=ku-fNfJJV7w

@philw Thanks. I also currently have a fully working OpenWRT (LEDE) setup. This does the job very well. But, there are certain little things that can be annoying (for me at least). So I am wanting to replicate all my existing LEDE setttings with pfsense and will be comparing which I like better.