Bug #4164
closedIPsec dashboard status wrong for connections with multiple P2s
100%
Description
"ipsec statusall" reports connections with multiple P2s as being a single connection, which breaks the active/inactive count on the dashboard widget and the up/down status on the Tunnels tab.
Updated by Ermal Luçi almost 10 years ago
- Status changed from Confirmed to Feedback
I do not think is anymore an issue now that the connections with multiple phase2 on IKEv1 get split on their own connection profile in ipsec.conf!
I will put this in feedback cause it works correctly here!
Updated by Eskild Skaar almost 10 years ago
I'm one of the people initially have this issue:
https://forum.pfsense.org/index.php?topic=86056.msg472022#msg472022
There is one ph1 and seven ph2 present, but only one tunnel is listed as active in the widget even if all seven tunnels are active.
I have just tested "2.2-RC (i386) built on Wed Jan 07 02:45:02 CST 2015", and the problem is still present on this system. I have edited and saved the ipsec config and restarted ipsec, but the status is still the same in the widget. Only one tunnel active.
Updated by Chris Buechler almost 10 years ago
- Status changed from Feedback to Confirmed
as suspected after previous fixes, this doesn't work, it only shows the first up.
Updated by Ermal Luçi almost 10 years ago
- Status changed from Confirmed to Feedback
Updated by Eskild Skaar almost 10 years ago
Tested with "2.2-RC (i386) built on Sun Jan 11 18:19:43 CST 2015", but the problem is still present.
Updated by Chris Buechler almost 10 years ago
- Status changed from Feedback to Confirmed
same status, seems fine for everything except multiple P2s.
Updated by Chris Buechler almost 10 years ago
- Status changed from Confirmed to Feedback
- Assignee changed from Ermal Luçi to Chris Buechler
Renato committed something that seems to work for this, to me for further testing.
Updated by Renato Botelho almost 10 years ago
- % Done changed from 0 to 100
Applied in changeset f285d039255f8536d135578125be4f5c76ccd24a.
Updated by Renato Botelho almost 10 years ago
Applied in changeset d71f97947553897f8ae6b0bb1f5145f9456f20bc.
Updated by Chris Buechler almost 10 years ago
- Status changed from Feedback to Resolved
this looks good now