Project

General

Profile

Actions
Copy link

Bug #11951

closed

IPsec status fails when many tunnels are connected

Added by Maxim A over 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jim Pingle
Category:
IPsec
Target version:
2.6.0
Start date:
05/24/2021
Due date:
% Done:

100%

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

Description

How to reproduce:

1. Set wan address 172.16.1.2/24.
2. Create IPSEC IKEv1 P1 with remote 172.16.1.3 and 11 P2 tunnels (or load attached config).
3. Go to Status\IPsec and click "connect"
You will see "Collecting IPsec status information.". After that all web interface will be responding "504 Gateway Time-out".

Tested versions:
2.5.1
2.6.0-DEV

Files

ipsec-config-pfSense.home.arpa-20210524071409.xml (8.24 KB) ipsec-config-pfSense.home.arpa-20210524071409.xml Maxim A, 05/24/2021 02:40 AM
Actions
Copy link
 #1

Updated by Jim Pingle over 3 years ago

  • Subject changed from IPSEC stuck on large configuration (more than 10 P2 tunnels) to IPsec status fails on large configurations
  • Status changed from New to In Progress
  • Assignee set to Jim Pingle
  • Target version set to 2.6.0
  • Plus Target Version set to 21.09

I'm working on optimizations for this as a part of ongoing IPsec work, should be solved soon.

Actions
Copy link
 #2

Updated by Jim Pingle over 3 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Jim Pingle over 3 years ago

  • Subject changed from IPsec status fails on large configurations to IPsec status fails when many tunnels are connected

Updating subject for release notes.

Actions
Copy link
 #4

Updated by Jim Pingle about 3 years ago

  • Plus Target Version changed from 21.09 to 22.01
Actions
Copy link
 #5

Updated by Jim Pingle almost 3 years ago

  • Status changed from Feedback to Closed

No sign of slowness or failures with many tunnels on the IPsec status page since the fix went in. I've tested with ~20 tunnels connected and it still loads in a reasonable amount of time (~15 seconds at most).

Actions
Copy link

Also available in: Atom PDF