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

    Windows 10 Client, peer to aggressive

    Scheduled Pinned Locked Moved IPsec
    2 Posts 1 Posters 618 Views
    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.
    • M
      Macormick
      last edited by Macormick

      Seems like my P2 are failing

      Windows 10 client, and IKEv2 IPSec mobile in pfSense

      I get "peer to aggressive" in the IPSec logs in pfSense:
      ignoring IKE_SA setup from xxx.xxx.xxx.xxx, peer too aggressive

      Why is that?

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

        I have been testing DH group 19 and 20, but that resulted in "Peer to aggressive". Offcourse I had the same settings on both phase 1 and phase 2 and in Windows 10 and pfSense IKEv2 Mutual RSA config.

        Changed to DH Group 14, and that worked.

        What can be the reason?

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