Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Tutorial: Configuring pfSense as VPN client to Private Internet Access

    OpenVPN
    99
    348
    383.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      humungus
      last edited by

      @AndrewZ:

      We're not limited to AES-128 and 2048 bit cert, higher values - 256 and 4096 - are supported already, see https://forum.pfsense.org/index.php?topic=103934.msg634754#msg634754

      These strong settings are available on UDP port 1197 and on TCP port 501 (at least).

      Cool I'm using it now with aes-256 and port 1197 as stated default in openvpn file. This appears to be a new CA as well although made quite awhile ago. Can you verify as I wasn't using it before? Valid From: Thu, 17 Apr 2014 10:40:33 -0700 Valid Until: Wed, 12 Apr 2034 10:40:33 -0700

      https://www.privateinternetaccess.com/openvpn/openvpn-strong.zip

      1 Reply Last reply Reply Quote 0
      • M
        mhertzfeld
        last edited by

        The cert contained within the compressed file you linked to has been out for a while.  I've been using it for 4 months or more.

        1 Reply Last reply Reply Quote 0
        • K
          killerb81
          last edited by

          I'm wondering if someone can help clear up some confusion I'm having… that being said, my PIA is setup and working fine in pfSense.
          My question is regarding some confusion with CA / certificate setup.

          In this post on the PIA forums:  https://www.privateinternetaccess.com/forum/discussion/18111/openvpn-step-by-step-setup-for-pfsense-firewall-router-with-video

          They say to:

          Certificate Setup

          - Click "System"
              - Click "Cert Manager"
              - Click "CAs"
              - Click "add or import ca" (icon is a "+" symbol on a small lined sheet of paper)
              - "Descriptive name" type in "PIA-internal-CA"
              - "Method" select "Create an internal Certificate Authority"
              - "Key length" use "2048" bits
              - "Digest Algorithm" use "SHA256"
              - "Lifetime" type in "3650" days (10 years)
              - "Country Code :" (your choice)
              - "State or Province :" (your choice, can be invalid data)
              - "City :" (your choice, can be invalid data)
              - "Organization :" (your choice, can be invalid data)
              - "Email Address :" (your choice, can be invalid data)
              - "Common Name :" = internal-ca
          Now click "Save"

          System: Certificate Manager

          - Click "System"
              - Click "Cert Manager"
              - Click "Certificates"
              - Click "add or import ca" (icon is a "+" symbol on a small lined sheet of paper)
              - "Method:" select "Create an internal Certificate"
              - "Descriptive name" type in "PIA-Certificate"
              - "Key length" use "2048" bits   
              - "Digest Algorithm" use "SHA256"
              - "Lifetime" type in "3650" days (10 years)
              - "Country Code :" (your choice)
              - "State or Province :" (your choice, can be invalid data)
              - "City :" (your choice, can be invalid data)
              - "Organization :" (your choice, can be invalid data)
              - "Email Address :" (your choice, can be invalid data)
              - "Common Name :" type in "PIA-Certificate"
          Now click "Save"

          In this post in pfSense forums, it makes no mention to these two steps… no need to make an internal-CA (not clear on what that is)... and apparently no need to add a certificate.
          So, what are these two extra steps for that are listed in the PIA forums?

          Also, when adding a client, both posts agree that:
          "Client Certificate" = "webConfigurator default *In use"

          If you follow the guide on the PIA forum, why wouldn't you choose the client certificate that you made in the above two steps that I quoted?
          If you're not choosing that, then why even make it (like in the guide posted in this thread)?

          Any insight would be lovely... as I want to also setup another VPN (from another provider) in pfSense but this provider doesn't have any guides for pfSense.
          I figure I can use these guides as a template if I understood the difference here.

          Anyone?

          Thanks!

          1 Reply Last reply Reply Quote 0
          • M
            mhertzfeld
            last edited by

            @killerb81:

            I'm wondering if someone can help clear up some confusion I'm having… that being said, my PIA is setup and working fine in pfSense.
            My question is regarding some confusion with CA / certificate setup.

            In this post on the PIA forums:  https://www.privateinternetaccess.com/forum/discussion/18111/openvpn-step-by-step-setup-for-pfsense-firewall-router-with-video

            They say to:

            Certificate Setup

            - Click "System"
                - Click "Cert Manager"
                - Click "CAs"
                - Click "add or import ca" (icon is a "+" symbol on a small lined sheet of paper)
                - "Descriptive name" type in "PIA-internal-CA"
                - "Method" select "Create an internal Certificate Authority"
                - "Key length" use "2048" bits
                - "Digest Algorithm" use "SHA256"
                - "Lifetime" type in "3650" days (10 years)
                - "Country Code :" (your choice)
                - "State or Province :" (your choice, can be invalid data)
                - "City :" (your choice, can be invalid data)
                - "Organization :" (your choice, can be invalid data)
                - "Email Address :" (your choice, can be invalid data)
                - "Common Name :" = internal-ca
            Now click "Save"

            System: Certificate Manager

            - Click "System"
                - Click "Cert Manager"
                - Click "Certificates"
                - Click "add or import ca" (icon is a "+" symbol on a small lined sheet of paper)
                - "Method:" select "Create an internal Certificate"
                - "Descriptive name" type in "PIA-Certificate"
                - "Key length" use "2048" bits   
                - "Digest Algorithm" use "SHA256"
                - "Lifetime" type in "3650" days (10 years)
                - "Country Code :" (your choice)
                - "State or Province :" (your choice, can be invalid data)
                - "City :" (your choice, can be invalid data)
                - "Organization :" (your choice, can be invalid data)
                - "Email Address :" (your choice, can be invalid data)
                - "Common Name :" type in "PIA-Certificate"
            Now click "Save"

            In this post in pfSense forums, it makes no mention to these two steps… no need to make an internal-CA (not clear on what that is)... and apparently no need to add a certificate.
            So, what are these two extra steps for that are listed in the PIA forums?

            Also, when adding a client, both posts agree that:
            "Client Certificate" = "webConfigurator default *In use"

            If you follow the guide on the PIA forum, why wouldn't you choose the client certificate that you made in the above two steps that I quoted?
            If you're not choosing that, then why even make it (like in the guide posted in this thread)?

            Any insight would be lovely... as I want to also setup another VPN (from another provider) in pfSense but this provider doesn't have any guides for pfSense.
            I figure I can use these guides as a template if I understood the difference here.

            Anyone?

            Thanks!

            I am wondering the same thing.

            This is what I can figure out with the little research I did.

            With OpenVPN the Client Certificate is used to authenticate the client.  Since PIA is using a Username and Password for authentication the Client Certificate ignored.

            Here's a quote from the OpenVPN how to documentation.

            Using username/password authentication as the only form of client authentication

            By default, using auth-user-pass-verify or a username/password-checking plugin on the server will enable dual authentication, requiring that both client-certificate and username/password authentication succeed in order for the client to be authenticated.

            While it is discouraged from a security perspective, it is also possible to disable the use of client certificates, and force username/password authentication only. On the server:

            client-cert-not-required

            Such configurations should usually also set:

            username-as-common-name

            which will tell the server to use the username for indexing purposes as it would use the Common Name of a client which was authenticating via a client certificate.

            Note that client-cert-not-required will not obviate the need for a server certificate, so a client connecting to a server which uses client-cert-not-required may remove the cert and key directives from the client configuration file, but not the ca directive, because it is necessary for the client to verify the server certificate.

            For the Client Cert to work, PIA would need to either.
                1. generate a client certificate for each user account
                2. have each user generate a CSR and submit it to PIA who would return a client certificate to the user

            Source: https://openvpn.net/index.php/open-source/documentation/howto.html

            1 Reply Last reply Reply Quote 0
            • S
              squiggie
              last edited by

              I'm wondering if someone could offer some advice. I just followed this to setup PIA and openvpn on my pfsense. My setup is like this;

              at&t router –> pfsense box --> wireless AP/switch

              I got everything working with the exception of getting the openvpn client to connect via dns name. When I enter in the dns name us-midwest.privateinternetaccess.com, I get the following error in the openvpn connection logs.

              Aug 23 09:28:49 openvpn[78359]: ifconfig_pool_persist_refresh_freq = 600
              Aug 23 09:28:49 openvpn[78359]: ifconfig_ipv6_pool_defined = DISABLED
              Aug 23 09:28:49 openvpn[78359]: ifconfig_ipv6_pool_base = ::
              Aug 23 09:28:49 openvpn[78359]: ifconfig_ipv6_pool_netbits = 0
              Aug 23 09:28:49 openvpn[78359]: n_bcast_buf = 256
              Aug 23 09:28:49 openvpn[78359]: tcp_queue_limit = 64
              Aug 23 09:28:49 openvpn[78359]: real_hash_size = 256
              Aug 23 09:28:49 openvpn[78359]: virtual_hash_size = 256
              Aug 23 09:28:49 openvpn[78359]: client_connect_script = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: learn_address_script = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: client_disconnect_script = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: client_config_dir = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: ccd_exclusive = DISABLED
              Aug 23 09:28:49 openvpn[78359]: tmp_dir = '/tmp'
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_defined = DISABLED
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_local = 0.0.0.0
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_remote_netmask = 0.0.0.0
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_ipv6_defined = DISABLED
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_ipv6_local = ::/0
              Aug 23 09:28:49 openvpn[78359]: push_ifconfig_ipv6_remote = ::
              Aug 23 09:28:49 openvpn[78359]: enable_c2c = DISABLED
              Aug 23 09:28:49 openvpn[78359]: duplicate_cn = DISABLED
              Aug 23 09:28:49 openvpn[78359]: cf_max = 0
              Aug 23 09:28:49 openvpn[78359]: cf_per = 0
              Aug 23 09:28:49 openvpn[78359]: max_clients = 1024
              Aug 23 09:28:49 openvpn[78359]: max_routes_per_client = 256
              Aug 23 09:28:49 openvpn[78359]: auth_user_pass_verify_script = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: auth_user_pass_verify_script_via_file = DISABLED
              Aug 23 09:28:49 openvpn[78359]: port_share_host = '[UNDEF]'
              Aug 23 09:28:49 openvpn[78359]: port_share_port = 0
              Aug 23 09:28:49 openvpn[78359]: client = ENABLED
              Aug 23 09:28:49 openvpn[78359]: pull = ENABLED
              Aug 23 09:28:49 openvpn[78359]: auth_user_pass_file = '/etc/openvpn-passwd.txt'
              Aug 23 09:28:49 openvpn[78359]: OpenVPN 2.3.8 i386-portbld-freebsd10.1 [SSL (OpenSSL)] [LZO] [MH] [IPv6] built on Aug 21 2015
              Aug 23 09:28:49 openvpn[78359]: library versions: OpenSSL 1.0.1l-freebsd 15 Jan 2015, LZO 2.09
              Aug 23 09:28:49 openvpn[78359]: WARNING: file '/etc/openvpn-passwd.txt' is group or others accessible
              Aug 23 09:28:49 openvpn[78634]: MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client1.sock
              Aug 23 09:28:49 openvpn[78634]: NOTE: the current –script-security setting may allow this configuration to call user-defined scripts
              Aug 23 09:28:49 openvpn[78634]: LZO compression initialized
              Aug 23 09:28:49 openvpn[78634]: Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:3 ]
              Aug 23 09:28:49 openvpn[78634]: Socket Buffers: R=[42080->65536] S=[57344->65536]
              Aug 23 09:28:49 openvpn[78634]: RESOLVE: Cannot resolve host address: us-midwest.privateinternetaccess.com: hostname nor servname provided, or not known Aug 23 09:28:49 openvpn[78634]: Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:143 ET:0 EL:3 AF:3/1 ]
              Aug 23 09:28:49 openvpn[78634]: Local Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-client'
              Aug 23 09:28:49 openvpn[78634]: Expected Remote Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-server'
              Aug 23 09:28:49 openvpn[78634]: Local Options hash (VER=V4): '41690919'
              Aug 23 09:28:49 openvpn[78634]: Expected Remote Options hash (VER=V4): '530fdded'
              Aug 23 09:28:49 openvpn[78634]: RESOLVE: Cannot resolve host address: us-midwest.privateinternetaccess.com: hostname nor servname provided, or not known
              Aug 23 09:28:54 openvpn[78634]: RESOLVE: Cannot resolve host address: us-midwest.privateinternetaccess.com: hostname nor servname provided, or not known
              Aug 23 09:28:59 openvpn[78634]: RESOLVE: Cannot resolve host address: us-midwest.privateinternetaccess.com: hostname nor servname provided, or not known

              If I enter in the IP address, it will connect and everything will work. However this isn't acceptable as every couple days the IP address changes.

              I've tried setting up my DNS servers to be the at&t router as well as the PIA DNS servers and neither seems to work.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Looks like your firewall can't resolve names. Or at least that name.

                What is your DNS configuration in System > General?

                Can you resolve names in Diagnostics > DNS Lookup?

                When you bring up Status > Dashboard does the update checker complete? Can you bring up System > Package Manager and get a list of packages?

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • S
                  squiggie
                  last edited by

                  @Derelict:

                  Looks like your firewall can't resolve names. Or at least that name.

                  What is your DNS configuration in System > General?

                  Can you resolve names in Diagnostics > DNS Lookup?

                  When you bring up Status > Dashboard does the update checker complete? Can you bring up System > Package Manager and get a list of packages?

                  DNS is pointing to 209.222.18.218 and 209.222.18.222 and both are using the WAN interface as gateway.

                  I can resolve names when I connect to the VPN via IP address but when it's trying to connect vie DNS name, it will not resolve. I get…
                  127.0.0.1 0 msec
                  209.222.18.218 No response
                  209.222.18.222 No response

                  I"m not able to see the update nor see packages when this happens.

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by

                    209.222.18.218  No response
                    209.222.18.222  No response

                    Have to figure that out…

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 0
                    • johnpozJ
                      johnpoz LAYER 8 Global Moderator
                      last edited by

                      ;; QUESTION SECTION:
                      ;218.18.222.209.in-addr.arpa.  IN      PTR

                      ;; ANSWER SECTION:
                      218.18.222.209.in-addr.arpa. 300 IN    PTR    resolver2.privateinternetaccess.com.

                      So your saying pfsense can not use them..  Well pfsense doesn't go out the vpn for its own traffic..

                      I can use them from non privateinternaccess.  Does your normal isp block/redirect dns traffic and only allow you to use their dns?

                      that fqdn your trying to connect resolves just fine

                      ;; QUESTION SECTION:
                      ;us-midwest.privateinternetaccess.com. IN A

                      ;; ANSWER SECTION:
                      us-midwest.privateinternetaccess.com. 300 IN A  104.207.136.87
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.62
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.54
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.80
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.27
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.79
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.20
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.140
                      us-midwest.privateinternetaccess.com. 300 IN A  104.207.136.7
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.101.131
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.116
                      us-midwest.privateinternetaccess.com. 300 IN A  108.61.228.69
                      us-midwest.privateinternetaccess.com. 300 IN A  104.207.136.9

                      ;; AUTHORITY SECTION:
                      privateinternetaccess.com. 86400 IN    NS      ns2.p28.dynect.net.
                      privateinternetaccess.com. 86400 IN    NS      ns4.p28.dynect.net.
                      privateinternetaccess.com. 86400 IN    NS      ns3.p28.dynect.net.
                      privateinternetaccess.com. 86400 IN    NS      ns1.p28.dynect.net.

                      How do you have your pfsense setup for dns.. Looks like you point to loopback which would be a normal setup if using the resolver, but then why do you have the PIA dns listed there as well??  How do you have pfsense setup for dns, forwarder, resolver, resolver in forward mode?

                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                      If you get confused: Listen to the Music Play
                      Please don't Chat/PM me for help, unless mod related
                      SG-4860 24.03 | Lab VMs 2.7.2, 24.03

                      1 Reply Last reply Reply Quote 0
                      • S
                        squiggie
                        last edited by

                        Ok, I think I know what's going on here now. My pfSense WAN interface is receiving a bridged connection from the router. I'm not for sure how this was resolved but I figured that my ISP might not allow alternate DNS servers and thus the PIA servers I put in weren't being allowed. So what I did was remove those PIA DNS servers under system –> general setup and then check the box for Allow DNS server list to be overridden by DHCP/PPP on WAN. After doing that, I rebooted and then reran the test and it was successful and connected to the VPN via the DNS name instead of the IP address.

                        However, that allowed a DNS Leak and I don't want that. So I simply redid my settings, adding the PIA DNS entries back again under system –> general setup and unchecked the box. I'm not really sure if something is operating off a cached IP address or value but things are working now. I guess we'll see if things blow up again in a few days.

                        1 Reply Last reply Reply Quote 0
                        • johnpozJ
                          johnpoz LAYER 8 Global Moderator
                          last edited by

                          So your using the forwarder not the resolver?

                          You can force the resolver to use the vpn connection I do believe.  In the resolver settings pick your vpn interface for the outgoing connection, put it in forwarder mode and put your pia nameservers in general setup and make sure you uncheck allow dhcp override your dns, etc.  dnssec prob doesn't work with their nameservers, would have to check.

                          So I put in that IP you listed, changed my resolver to forwarder and picked the vpn interface that I have setup to one of my vps as the outgoing interface.  Did a simple test of what is the IP of what is doing dns for me and

                          
> dig whoami.akamai.net

; <<>> DiG 9.10.4-P2 <<>> whoami.akamai.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36815
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;whoami.akamai.net.             IN      A

;; ANSWER SECTION:
whoami.akamai.net.      180     IN      A       209.222.18.218

;; Query time: 150 msec
;; SERVER: 192.168.9.253#53(192.168.9.253)
;; WHEN: Thu Aug 25 13:58:05 Central Daylight Time 2016
;; MSG SIZE  rcvd: 62

                          I put it back to resolver

                          
> dig whoami.akamai.net

; <<>> DiG 9.10.4-P2 <<>> whoami.akamai.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11143
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;whoami.akamai.net.             IN      A

;; ANSWER SECTION:
whoami.akamai.net.      180     IN      A       24.13.snipped

;; Query time: 12 msec
;; SERVER: 192.168.9.253#53(192.168.9.253)
;; WHEN: Thu Aug 25 14:02:01 Central Daylight Time 2016
;; MSG SIZE  rcvd: 62

                          And as expected comes back with my public IP since I am doing the resolving directly, etc.

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 24.03 | Lab VMs 2.7.2, 24.03

                          1 Reply Last reply Reply Quote 0
                          • N
                            nitdawg1
                            last edited by

                            Hello,

                            I've been trying to configure a setup where my Plex servers torrent traffic is routed through openVPN/PIA. I would also like still access my plex server remotely. I run the plex server on a different VLAN than the rest of my network (ex. VLAN30). So, I guess in essence what I'm trying to do is setup split tunneling so all my torrent traffic is secure using openvpn/PIA and all other traffic is sent over the network as usual.

                            I tried to use the tutorial in this post however, after following the instruction I lost all my Vlan interfaces and only had access to the LAN interface. I used a backup config.xml to restore my old settings but I really need some help.

                            I'm not sure what logs or screenshots I could offer to assist with troubleshooting. Let me know and I will provide then ASAP.

                            1 Reply Last reply Reply Quote 0
                            • U
                              User1503
                              last edited by

                              Great this is still alive and thanks again to everyone contributing. My [nflx-movies] were using an alias for IP's going through PIA and working fine.  Then all of a sudden quit; along with my [amzn-jungle] box which gives geo-restriction.  What changed?  Jungle always worked, didn't complain like movies which was blocked for everyone a while back.  Is there a simple setup so I can check my DNS to be correct?  Currently I have DNS Srvr 1 as PIA with the PIAopt1 interface assigned.  DNS 2 is google with the WAN_DHCP interface assigned.  My setup is ISP provider router to PFsense box which controls local Lan.  Some clients [jungle/movies] are under a firewall alias that routes everything through PIA.  Other clients just bypass PIA and go out ISP router.  All this is tested and works.  I find it hard to believe that jungle all of the sudden is geo-blocking due to PIA?  If others are seeing this please post.  Otherwise, what did I change that I need to correct?  Thanks!

                              1 Reply Last reply Reply Quote 0
                              • F
                                Finger79
                                last edited by

                                I'm able to connect just fine to PIA, but I'm seeing this in the logs every 10-15 seconds or so.  Can someone help me interpret this?

                                Oct 18 01:25:46 openvpn 13031 MANAGEMENT: CMD 'state 1'
                                Oct 18 01:25:46 openvpn 13031 MANAGEMENT: CMD 'status 2'
                                Oct 18 01:25:46 openvpn 13031 MANAGEMENT: Client disconnected
                                Oct 18 01:25:51 openvpn 13031 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
                                Oct 18 01:25:51 openvpn 13031 MANAGEMENT: CMD 'state 1'
                                Oct 18 01:25:51 openvpn 13031 MANAGEMENT: CMD 'status 2'
                                Oct 18 01:25:51 openvpn 13031 MANAGEMENT: Client disconnected
                                Oct 18 01:25:58 openvpn 13031 MANAGEMENT: Client connected from /var/etc/openvpn/client1.sock
                                Oct 18 01:25:58 openvpn 13031 MANAGEMENT: CMD 'state 1'
                                Oct 18 01:25:58 openvpn 13031 MANAGEMENT: CMD 'status 2'
                                Oct 18 01:25:58 openvpn 13031 MANAGEMENT: Client disconnected

                                Advanced options as follows:

                                persist-key
                                persist-tun
                                remote-cert-tls server
                                auth-nocache
                                script-security 2
                                tls-version-min 1.2

                                I see the same "Management" things anyways with or without some of the above advanced options.

                                1 Reply Last reply Reply Quote 0
                                • DerelictD
                                  Derelict LAYER 8 Netgate
                                  last edited by

                                  I believe those are simply logging of the Status > OpenVPN page or the OpenVPN status dashboard widget.

                                  Turning down logging should clear those if they bother.

                                  Chattanooga, Tennessee, USA
                                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    thethrow
                                    last edited by

                                    Leaving this note for myself for 6 months when I forget.  8). Unsure if it was discussed prior, but may be worth adding to the tutorial.

                                    I was struggling with the routing part, as I expected the traffic to stop when my gateway went down, once I assigned a VPN gateway to the "Default allow LAN to any rule"

                                    In order to make this work how I expected, I had to make the following change:

                                    (System | Advanced | Miscellaneous)
                                    Do not create rules when gateway is down
                                    By default, when a rule has a gateway specified and this gateway is down, the rule is created omitting the gateway. This option overrides that behavior by omitting the entire rule instead.

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      CTrax
                                      last edited by

                                      While I appreciate the detail of the original PIA VPN tutorial and all of the subsequent contributions, I've not been able to combine all of that into a working VPN + Bypass configuration. PIA VPN works; it's the 'bypass' exception that does not.

                                      Problem:
                                      I've successfully configured PIA VPN and ipecho.net confirms a PIA IP address but something is preventing any Firewall exception Rule I create (to 'bypass' VPN) from having those IP routed around VPN – such rules appear to be just ignored. I've read, searched and tried every config modification I can find; no luck. All IPs for devices are static IPs on the same 192.168.1.X network but they all just use the tunnel.

                                      Any idea of what to observe or what config to check or change would be appreciated. Thanks!

                                      Intent:
                                      Run the entire local 192.168.1.X net through the PIA VPN -- except a few specific static IP devices.

                                      Network:
                                      ISP - (108.x.x.x) - ISP ADSLmodem - (108.x.x.x) - SG-2440 - (172.28.x.x) - Router/SW - 192.1681.X local net
                                      SG-2440 is at 2.3.2.p1, no added packages

                                      Gateways:
                                      DSLGW(default) / WAN / 108.x.x.x / 108.x.x.x / ADSL Gateway
                                      PIAVPN_VPNV4 / WAN / 10.64.10.5 / 10.64.10.5 / Interface PIAVPN_VPNV4 (the 10.x.x.x appears dynamic)
                                      PIAVPN_VPNV6 / WAN / <blank>/ <blank>/ Interface PIAVPN_VPNV4

                                      Interfaces:
                                      Existing defaults: WAN, LAN
                                      Deleted: OPT2 (unused)

                                      / Name: PIAVPN / Network port: ovpnc1(PIA openVPN)

                                      Firewall:
                                      NAT:
                                      Existing: (6) WAN Mappings
                                      Copied: (6) and rename Interface: PIAVPN

                                      Aliases:
                                      Roku / 192.168.1.209
                                      VPNPath / 192.168.1.200-208 range

                                      Rules: WAN: (only existing block private and bogon)
                                      Rules: PIAVPN: (no rules)
                                      Rules: OpenVPN: (no rules)

                                      Rules: LAN:
                                      Added: Roku / any port,dest / DSLGW gateway
                                      Added: VPNPath / any port,dest / PIAVPN gateway</blank></blank>

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        thethrow
                                        last edited by

                                        @CTrax:

                                        While I appreciate the detail of the original PIA VPN tutorial and all of the subsequent contributions, I've not been able to combine all of that into a working VPN + Bypass configuration. PIA VPN works; it's the 'bypass' exception that does not.

                                        Problem:
                                        I've successfully configured PIA VPN and ipecho.net confirms a PIA IP address but something is preventing any Firewall exception Rule I create (to 'bypass' VPN) from having those IP routed around VPN – such rules appear to be just ignored. I've read, searched and tried every config modification I can find; no luck. All IPs for devices are static IPs on the same 192.168.1.X network but they all just use the tunnel.

                                        Any idea of what to observe or what config to check or change would be appreciated. Thanks!

                                        Intent:
                                        Run the entire local 192.168.1.X net through the PIA VPN -- except a few specific static IP devices.

                                        Network:
                                        ISP - (108.x.x.x) - ISP ADSLmodem - (108.x.x.x) - SG-2440 - (172.28.x.x) - Router/SW - 192.1681.X local net
                                        SG-2440 is at 2.3.2.p1, no added packages

                                        Gateways:
                                        DSLGW(default) / WAN / 108.x.x.x / 108.x.x.x / ADSL Gateway
                                        PIAVPN_VPNV4 / WAN / 10.64.10.5 / 10.64.10.5 / Interface PIAVPN_VPNV4 (the 10.x.x.x appears dynamic)
                                        PIAVPN_VPNV6 / WAN / <blank>/ <blank>/ Interface PIAVPN_VPNV4

                                        Interfaces:
                                        Existing defaults: WAN, LAN
                                        Deleted: OPT2 (unused)

                                        / Name: PIAVPN / Network port: ovpnc1(PIA openVPN)

                                        Firewall:
                                        NAT:
                                        Existing: (6) WAN Mappings
                                        Copied: (6) and rename Interface: PIAVPN

                                        Aliases:
                                        Roku / 192.168.1.209
                                        VPNPath / 192.168.1.200-208 range

                                        Rules: LAN:
                                        Added: Roku / any port,dest / DSLGW gateway
                                        Added: VPNPath / any port,dest / PIAVPN gateway</blank></blank>

                                        3 things to check:
                                        -See my post above, make the change.
                                        -RE: LAN rules Roku is set at your "source"
                                        -put your alias under Firewall | Aliases | IP

                                        Also may want to try just plugging in the address to the source (e.g. 192.168.1.209 for roku), and not using an alias, just for testing.

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          bartgrefte
                                          last edited by

                                          Just now I went through this howto to set up a virtualized pfSense as VPN client. Since I do not want all traffic to go through VPN, just one or two specific programs, I figured I'd set up a virtual pc with pfSense and Squid and set the programs in question to connect to Squid so that the traffic goes through pfSense and it's VPN client.

                                          I got a bit confused at the compression setting, there is nothing to check, instead there's a drop down menu with 5 options, I set it to "enabled with adaptive compression". Not sure if it's the right choice though…

                                          Plus option "Auth digest algorithm" is not listed in the howto, I left the default setting as it was, SHA1 (160-bit)

                                          After finishing following the howto, I ended up with "reconnecting; tls-error" as status and this in the log:

                                          Aug 30 14:25:40 openvpn 26470 TLS: Initial packet from [AF_INET]46.166.137.250:1194, sid=95cdf14a 8a04e2c6
                                          Aug 30 14:25:40 openvpn 26470 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: C=US, ST=OH, L=Columbus, O=Private Internet Access, CN=Private Internet Access CA, emailAddress=secure@privateinternetaccess.com
                                          Aug 30 14:25:40 openvpn 26470 OpenSSL: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
                                          Aug 30 14:25:40 openvpn 26470 TLS_ERROR: BIO read tls_read_plaintext error
                                          Aug 30 14:25:40 openvpn 26470 TLS Error: TLS object -> incoming plaintext read error
                                          Aug 30 14:25:40 openvpn 26470 TLS Error: TLS handshake failed
                                          Aug 30 14:25:40 openvpn 26470 TCP/UDP: Closing socket
                                          Aug 30 14:25:40 openvpn 26470 SIGUSR1[soft,tls-error] received, process restarting
                                          Aug 30 14:25:40 openvpn 26470 Restart pause, 2 second(s)

                                          I solved that by changing the port from 1194 to 1198 and the encryption algorithm from BF-CBC (128-bit) to AES-128-CBC (for standard certificates), see https://www.privateinternetaccess.com/forum/discussion/comment/42294/#Comment_42294 for more info.

                                          After that, the VPN showed as "up", so I accessed pfSense's console and ran both```
                                          curl -s checkip.dyndns.org | sed -e 's/.Current IP Address: //' -e 's/<.$//'

                                          curl ipinfo.io/ip

                                          Both show an IP-address that's not my public IPv4-address issued by my ISP, nor the private address issued by my router to pfSense's WAN-interface, so I guess its working :)

I have some questions though.
- Should I disable IPv6 on pfSense? Since PIA doesn't seem to support it.
- As for the NAT-rules part of the howto, I doubled all the rules while setting the VPN as interface as instructed. Since there are now rules for two outbound interfaces, how will I know if the traffic always goes through the VPN?
                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            DaveB
                                            last edited by

                                            @CTrax:

                                            While I appreciate the detail of the original PIA VPN tutorial and all of the subsequent contributions, I've not been able to combine all of that into a working VPN + Bypass configuration. PIA VPN works; it's the 'bypass' exception that does not.

                                            Problem:
                                            I've successfully configured PIA VPN and ipecho.net confirms a PIA IP address but something is preventing any Firewall exception Rule I create (to 'bypass' VPN) from having those IP routed around VPN – such rules appear to be just ignored. I've read, searched and tried every config modification I can find; no luck. All IPs for devices are static IPs on the same 192.168.1.X network but they all just use the tunnel.

                                            Any idea of what to observe or what config to check or change would be appreciated. Thanks!

                                            Intent:
                                            Run the entire local 192.168.1.X net through the PIA VPN -- except a few specific static IP devices.

                                            Network:
                                            ISP - (108.x.x.x) - ISP ADSLmodem - (108.x.x.x) - SG-2440 - (172.28.x.x) - Router/SW - 192.1681.X local net
                                            SG-2440 is at 2.3.2.p1, no added packages

                                            Gateways:
                                            DSLGW(default) / WAN / 108.x.x.x / 108.x.x.x / ADSL Gateway
                                            PIAVPN_VPNV4 / WAN / 10.64.10.5 / 10.64.10.5 / Interface PIAVPN_VPNV4 (the 10.x.x.x appears dynamic)
                                            PIAVPN_VPNV6 / WAN / <blank>/ <blank>/ Interface PIAVPN_VPNV4

                                            Interfaces:
                                            Existing defaults: WAN, LAN
                                            Deleted: OPT2 (unused)

                                            / Name: PIAVPN / Network port: ovpnc1(PIA openVPN)

                                            Firewall:
                                            NAT:
                                            Existing: (6) WAN Mappings
                                            Copied: (6) and rename Interface: PIAVPN

                                            Aliases:
                                            Roku / 192.168.1.209
                                            VPNPath / 192.168.1.200-208 range

                                            Rules: WAN: (only existing block private and bogon)
                                            Rules: PIAVPN: (no rules)
                                            Rules: OpenVPN: (no rules)

                                            Rules: LAN:
                                            Added: Roku / any port,dest / DSLGW gateway
                                            Added: VPNPath / any port,dest / PIAVPN gateway</blank></blank>

                                            Hi

                                            Just been struggling with a similar problem and concluded that it was my settings under Firewall/NAT/Outbound - Manual Outbound that were wrong. I had overwritten the existing rules with my VPN rules rather than duplicating and then modifying.

                                            Copy of Rules that sorted it for me is shown below.
                                            Hope you can get it sorted.

                                            OutboundRules.png
                                            OutboundRules.png_thumb

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post