Project

General

Profile

Actions
Copy link

Bug #12541

closed

IPsec remote side connection fails with: no maching peer if peer identifier is set to Any

Added by M. Pietersma about 4 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

It's currently a issue in version 2.5.2, can't test it in 2.6, because of a production status firewall.

IPsec between 2 sites, ours is pfSense 2.5.2 and other side is other brand. Other site ipsec has a nat ip (10.30.x.x) as peer identifier, the id changes when they failover. The external IP does not change when a failover occeurs.

IPsec does not function when remote peer id is set to Any, we must program the specific remote side peer id (10.30.x.x), otherwise pfSense tells me that there is no matching peer found, while the internet IP of the remote side is defined.

Files

clipboard-202111231157-2pp5e.png (71.3 KB) clipboard-202111231157-2pp5e.png IPsec up, but with specific peer id. M. Pietersma, 11/23/2021 04:57 AM
Actions
Copy link
 #1

Updated by M. Pietersma about 4 years ago

Setting the peer id to their remote gateway IP, is also not working

IPsec up, but with specific peer id.

Actions
Copy link
 #2

Updated by Jim Pingle about 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (2.6.0)

Unable to reproduce, tunnels connect OK with peer ID = any here. This is likely a configuration error but may also be an issue fixed on 2.6.0 already.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .

See Reporting Issues with pfSense Software for more information.

Actions
Copy link

Also available in: Atom PDF