<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Windows 10 Client, peer to aggressive]]></title><description><![CDATA[<p dir="auto">Seems like my P2 are failing</p>
<p dir="auto">Windows 10 client, and IKEv2 IPSec mobile in pfSense</p>
<p dir="auto">I get "peer to aggressive" in the IPSec logs in pfSense:<br />
ignoring IKE_SA setup from xxx.xxx.xxx.xxx, peer too aggressive</p>
<p dir="auto">Why is that?</p>
]]></description><link>https://forum.netgate.com/topic/158540/windows-10-client-peer-to-aggressive</link><generator>RSS for Node</generator><lastBuildDate>Tue, 16 Jun 2026 08:44:36 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/158540.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 22 Nov 2020 14:58:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Windows 10 Client, peer to aggressive on Tue, 24 Nov 2020 19:03:54 GMT]]></title><description><![CDATA[<p dir="auto">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.</p>
<p dir="auto">Changed to DH Group 14, and that worked.</p>
<p dir="auto">What can be the reason?</p>
]]></description><link>https://forum.netgate.com/post/947383</link><guid isPermaLink="true">https://forum.netgate.com/post/947383</guid><dc:creator><![CDATA[Macormick]]></dc:creator><pubDate>Tue, 24 Nov 2020 19:03:54 GMT</pubDate></item></channel></rss>