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

    IPsec v2 - EAP-TLS Support

    General pfSense Questions
    10
    46
    22.6k
    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
      hege
      last edited by

      Windows Phone 8.1
      and
      Windows 8.1 Pro

      Please let me know, if i can test something for you

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        I just pushed the first implementation for EAP-TLS.
        Though please do testing and see if anything can be fixed or made working.

        1 Reply Last reply Reply Quote 0
        • Raul RamosR
          Raul Ramos
          last edited by

          Mannnnnn (ermal). I lost a lot of hours trying to connect my WP8.1 through Iosec VPN. I mentions this earlier, a month ago? :P.

          OK i will test this to and report back.

          A BIG Thanks for this.

          pfSense:
          ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
          Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
          NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

          1 Reply Last reply Reply Quote 0
          • H
            hege
            last edited by

            @ermal:

            I just pushed the first implementation for EAP-TLS.
            Though please do testing and see if anything can be fixed or made working.

            Thank you!

            It seems that there is a lot more work needed for get this working.

            With original config by pfsense

            Sep 13 14:55:08 	charon: 11[IKE] configured EAP-only authentication, but peer does not support it
Sep 13 14:55:08 	charon: 11[IKE] <con1|11> configured EAP-only authentication, but peer does not support it</con1|11>

            With customized config
            leftauth =  pubkey
            rightauth = eap-tls

            Sep 13 14:56:57 	charon: 11[TLS] sending fatal TLS alert 'certificate unknown'
Sep 13 14:56:57 	charon: 11[TLS] no trusted certificate found for '(ClientLanIP)' to verify TLS peer
Sep 13 14:56:57 	charon: 11[TLS] received TLS peer certificate 'C=AT, ST=Austria, L=XXXX, O=XXXXX, OU=XXXXXX, CN=(PCName), E=XXXXXX'

            With customized config2
            leftauth = pubkey
            rightauth = eap-tls
            eap_identity = "C=AT, ST=Austria, L=XXXX, O=XXXXX, OU=XXXXXX, CN=(PCName), E=XXXXXX"

            With above changes in the config, i can connect with WP8 and Win8, but there is no traffic throughput - FW Rules are ok.
            Same issue here?: https://forum.pfsense.org/index.php?topic=80300.0

            Sep 13 15:00:13 	charon: 11[IKE] CHILD_SA con1{1} established with SPIs c11f9fdf_i 7d19592a_o and TS (pfSenseLANNET)/24|/0 === 10.11.12.0/24|/0
Sep 13 15:00:13 	charon: 11[IKE] <con1|13> CHILD_SA con1{1} established with SPIs c11f9fdf_i 7d19592a_o and TS (pfSenseLANNET)/24|/0 === 10.11.12.0/24|/0
..
Sep 13 15:00:13 	charon: 11[IKE] <con1|13> assigning virtual IP 10.11.12.1 to peer 'C=AT, ST=Austria, L=XXXX, O=XXXXX, OU=XXXXXX, CN=(PCName), E=XXXXXX'
Sep 13 15:00:13 	charon: 11[CFG] reassigning offline lease to 'C=AT, ST=Austria, L=XXXX, O=XXXXX, OU=XXXXXX, CN=(PCName), E=XXXXXX'
Sep 13 15:00:13 	charon: 11[IKE] peer requested virtual IP %any
..
Sep 13 15:00:13 	charon: 11[IKE] authentication of '(ClientLanIP)' with EAP successful
Sep 13 15:00:13 	charon: 11[IKE] <con1|13> authentication of '(ClientLanIP)' with EAP successful
..
Sep 13 15:00:13 	charon: 11[IKE] EAP method EAP_TLS succeeded, MSK established
Sep 13 15:00:13 	charon: 11[IKE] <con1|13> EAP method EAP_TLS succeeded, MSK established</con1|13></con1|13></con1|13></con1|13>

            IPv4 Routes: (seems wrong for me)

            10.11.12.0/24 	(pfSense-WAN-GW) 	US 	0 	1500 	hn0

            IPsec Overview:

            IPsecOverview.png
            IPsecOverview.png_thumb

            1 Reply Last reply Reply Quote 0
            • Raul RamosR
              Raul Ramos
              last edited by

              Hi

              Can i use PEAP-MSCHAPv2 now? or have to be in config to? I see EAP-TLS but not PEAP-MSCHAPv2. I can't connect even less pass traffic.

              @hege what are your config on pfsense phase 1,2, mobile in Algorithms and proposal? have you information of this on a MS Site i see in one place this information, i can't find it.

              Thanks

              pfSense:
              ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
              Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
              NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

              1 Reply Last reply Reply Quote 0
              • H
                hege
                last edited by

                No, that requires a different config.

                Edit:

                Required Config:
                        leftauth=pubkey
                        rightauth=eap-mschapv2
                        eap_identity=%any

                and secret in ipsec.secrets:
                user@domain.loc : EAP "password"

                ipsec rereadall
                ipsec reload

                just tested it with WP8 + Win8, but still no traffic throughput

                1 Reply Last reply Reply Quote 0
                • Raul RamosR
                  Raul Ramos
                  last edited by

                  I will play with certs and try EAP-TLS but have you the Algorithms proposal and hashes compatible with WP8.1?

                  Thanks

                  pfSense:
                  ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                  Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                  NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                  1 Reply Last reply Reply Quote 0
                  • H
                    hege
                    last edited by

                    @mais_um:

                    ..have you the Algorithms proposal and hashes compatible with WP8.1?

                    You can find the available proposals in the log files (with higher loglevel)
                    I use this one: (Windows 8 and WP8)

                    Phase1:
                    AES 256
                    SHA 256
                    DH2

                    Phase2:
                    AES 256
                    SHA1
                    PFS 2

                    1 Reply Last reply Reply Quote 0
                    • E
                      eri--
                      last edited by

                      @hepe,

                      i used a config from strongswan samples for eap-tls.
                      Though i will see to allow specifying different left and right auth.

                      1 Reply Last reply Reply Quote 0
                      • H
                        hege
                        last edited by

                        @ermal:

                        i used a config from strongswan samples for eap-tls.

                        This one?
                        https://wiki.strongswan.org/projects/strongswan/wiki/EapTls

                        By default, the Gateway uses IKEv2 certificate authentication to prove its identity to the clients. But as EAP-TLS is a mutual authentication protocol, EAP-only authentication can be used by specifying leftauth=eap.

                        As far as I understand it's possible to use eap-tls on the gateway, but usually it's pubkey.

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

                          Hi there,

                          I'm relatively new to pfSense. I have managed to get MSCHAP-v2 with IPSec working on Windows Phone 8.1 Update 1 by editing the files mentioned in this topic. I have been running pfSense 2.2 RC for a while now, so I was just wondering whether this kind of configuration will be implemented directly by pfSense, seeing as it is possible by the underlying software? If not, is there any way to prevent the configuration files from being auto re-generated by pfSense?

                          1 Reply Last reply Reply Quote 0
                          • H
                            hege
                            last edited by

                            Hi,

                            I just created a bounty for eap-tls.

                            https://forum.pfsense.org/index.php?topic=86727.0

                            @kathode
                            I think an implementation of mschap-v2 will be a lot of work, because it requires a different format in  ipsec.secrets.

                            1 Reply Last reply Reply Quote 0
                            • E
                              eri--
                              last edited by

                              kathode can you explain how you did so i can give a look to integrate in master branch?

                              1 Reply Last reply Reply Quote 0
                              • H
                                hege
                                last edited by

                                @hege:

                                Required Config:
                                        leftauth=pubkey
                                        rightauth=eap-mschapv2
                                        eap_identity=%any

                                and secret in ipsec.secrets:
                                user@domain.loc : EAP "password"

                                ipsec rereadall
                                ipsec reload

                                1 Reply Last reply Reply Quote 0
                                • E
                                  eri--
                                  last edited by

                                  Can you post the full ipsec.conf?

                                  1 Reply Last reply Reply Quote 0
                                  • H
                                    hege
                                    last edited by

                                    Sorry, this ok?

                                    
conn con1
        aggressive = yes
        fragmentation = yes
        keyexchange = ikev2
        reauth = no
        rekey = no
        reqid = 1
        installpolicy = yes
        type = tunnel
        dpdaction = clear
        dpddelay = 10s
        dpdtimeout = 60s
        auto = add
        left = My WAN IP
        right = %any
        leftid = my.cert.CN
        ikelifetime = 28800s
        lifetime = 3600s
        rightsourceip = 10.12.34.0/24
        rightsubnet = 10.12.34.0/24
        leftsubnet = My LAN NET/24
        ike = aes256-sha256-modp1024!
        esp = aes256-sha1-modp1024,aes192-sha1-modp1024,aes128-sha1-modp1024,aes128gcm128-sha1-modp1024,aes128gcm96-sha1-modp
1024,aes128gcm64-sha1-modp1024,aes192gcm128-sha1-modp1024,aes192gcm96-sha1-modp1024,aes192gcm64-sha1-modp1024,aes256gcm128-sh
a1-modp1024,aes256gcm96-sha1-modp1024,aes256gcm64-sha1-modp1024!
        leftauth=pubkey
        rightauth=eap-mschapv2
        leftcert=/var/etc/ipsec/ipsec.d/certs/cert-1.crt
        eap_identity=%any

                                    and in ipsec.secrets:
                                    user@domain.loc : EAP "password"

                                    I modified the config, generated by your eap-tls implementation.

                                    1 Reply Last reply Reply Quote 0
                                    • E
                                      eri--
                                      last edited by

                                      Ok this is merged on to master branch.
                                      You have a config option to configure EAP-MSchapv2 and it will generate this config.
                                      The preshared-keys entries can be specified the type PSK/EAP now.

                                      You can either use the patch with the patch package or gitsync to master since at this times the differences are not huge with 2.2

                                      1 Reply Last reply Reply Quote 0
                                      • H
                                        hege
                                        last edited by

                                        Sorry I forgot one important thing:

                                        The link to the private key has to be in ipsec.secrets (not only eap-mschapv2)
                                        " : RSA /var/etc/ipsec/ipsec.d/private/cert-3.key"

                                        (space at start)
                                        https://wiki.strongswan.org/projects/strongswan/wiki/RsaSecret

                                        I applied your patch, added the RSA key to the ipsec.secrets, and used this commands:
                                        ipsec rereadall
                                        ipsec reload

                                        eap-mschapv2 WORKING on Win 8.1 Pro and Windows Phone 8.1!
                                        Config:
                                        Phase1: AES256/SHA1/DH2
                                        Phase2: AES256/SHA1/PFS

                                        1 Reply Last reply Reply Quote 0
                                        • E
                                          eri--
                                          last edited by

                                          That is already done according to me though i will double check.

                                          Done it was just forgotten.
                                          Test it and let me know.

                                          1 Reply Last reply Reply Quote 0
                                          • E
                                            eri--
                                            last edited by

                                            FYI,

                                            this has been merged into 2.2 as well.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.