Navigation

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

    Android 5 can't login pfsense 2.2.3 ipsec

    IPsec
    2
    2
    1147
    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.
    • A
      akong last edited by

      Hello,
      I have set ipsec for mobile client.But it's always show connecting.And I have fot some message for ipsec.

      Jul 9 17:43:45 charon: 11[CFG] <3> looking for XAuthInitPSK peer configs matching 219.85.218.78…203.74.122.103[pfsense.aspa.idv.tw]
      Jul 9 17:43:45 charon: 11[CFG] <3> selected peer config "con1"
      Jul 9 17:43:45 charon: 11[ENC] <con1|3>generating AGGRESSIVE response 0 [ SA KE No ID NAT-D NAT-D HASH V V V V V ]
      Jul 9 17:43:45 charon: 11[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:46 charon: 11[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:43:46 charon: 11[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:46 charon: 11[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:46 charon: 11[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:49 charon: 11[IKE] <con1|3>sending retransmit 1 of response message ID 0, seq 1
      Jul 9 17:43:49 charon: 11[IKE] <con1|3>sending retransmit 1 of response message ID 0, seq 1
      Jul 9 17:43:49 charon: 11[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:49 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:43:49 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:49 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:49 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:52 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:43:52 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:52 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:52 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:54 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:43:54 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:54 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:54 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:56 charon: 06[IKE] <con1|3>sending retransmit 2 of response message ID 0, seq 1
      Jul 9 17:43:56 charon: 06[IKE] <con1|3>sending retransmit 2 of response message ID 0, seq 1
      Jul 9 17:43:56 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:43:57 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:43:57 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:57 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:43:57 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:00 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:44:00 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:00 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:00 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:03 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:44:03 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:03 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:03 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:06 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:44:06 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:06 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:06 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:09 charon: 06[IKE] <con1|3>sending retransmit 3 of response message ID 0, seq 1
      Jul 9 17:44:09 charon: 06[IKE] <con1|3>sending retransmit 3 of response message ID 0, seq 1
      Jul 9 17:44:09 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:09 charon: 06[NET] <con1|3>received packet: from 203.74.122.103[500] to 219.85.218.78[500] (655 bytes)
      Jul 9 17:44:09 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:09 charon: 06[IKE] <con1|3>received retransmit of request with ID 0, retransmitting response
      Jul 9 17:44:09 charon: 06[NET] <con1|3>sending packet: from 219.85.218.78[500] to 203.74.122.103[500] (432 bytes)
      Jul 9 17:44:15 charon: 06[JOB] <con1|3>deleting half open IKE_SA after timeout</con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3></con1|3>

      I don't know why timeout.How to fix it?

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

        That's likely the mobile ipsec.secrets issue that affected iOS there as well. Upgrade to 2.2.4 and that'll work. Snapshots are stable. Or you can just replace /etc/inc/vpn.inc with the latest, then click Save under Status>IPsec to apply.

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

        Products

        • Platform Overview
        • TNSR
        • pfSense
        • Appliances

        Services

        • Training
        • Professional Services

        Support

        • Subscription Plans
        • Contact Support
        • Product Lifecycle
        • Documentation

        News

        • Media Coverage
        • Press
        • Events

        Resources

        • Blog
        • FAQ
        • Find a Partner
        • Resource Library
        • Security Information

        Company

        • About Us
        • Careers
        • Partners
        • Contact Us
        • Legal
        Our Mission

        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

        Subscribe to our Newsletter

        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

        © 2021 Rubicon Communications, LLC | Privacy Policy