Bug #11893
closedIPsec Dashboard widget only displays first P2 subnet when using a single traffic selector
100%
Description
The IPSec Dashboard Widget only shows the first P2 tunnel when the tunnels are "grouped" like the new way Strongswan to Strongswan connections work. As such only the first subnet and it's description shows even if three subnet P2s are established. This shows normally in Status --> IPSec --> Child SAs, but not on the widget. See attached screenshots for a more visual representation.
Files
Updated by Jim Pingle over 3 years ago
- Project changed from pfSense Plus to pfSense
- Subject changed from IPSec Dashboard Widget Only Shows First P2 Subnet to IPsec Dashboard widget only displays first P2 subnet when using a single traffic selector
- Category changed from Web Interface to Dashboard
- Affected Plus Version deleted (
21.02.2)
Since there is only one child SA here with multiple traffic selectors I'm not sure how viable it would be to break that all back out.
Fixing up subject and since it's not specific to Plus, moving it out of Plus.
Updated by Kris Phillips over 3 years ago
- File StatusIPSec.png StatusIPSec.png added
Adding sanitized Status IPSec Page for Comparison.
Updated by Steve Wheeler over 3 years ago
- File deleted (
DashboardIPSecWidget.png)
Updated by Kris Phillips over 3 years ago
- File DashboardIPSecWidget.png DashboardIPSecWidget.png added
Adding sanitized Dashboard Widget Example.
Updated by Viktor Gurov over 3 years ago
- File Screenshot from 2021-05-06 07-59-43.png Screenshot from 2021-05-06 07-59-43.png added
- File Screenshot from 2021-05-06 08-00-59.png Screenshot from 2021-05-06 08-00-59.png added
much better now (see screenshots)
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/241
Updated by Jim Pingle over 3 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.6.0
Updated by Anonymous over 3 years ago
- Status changed from Pull Request Review to Feedback
Updated by Viktor Gurov over 3 years ago
- % Done changed from 0 to 100
Applied in changeset 21e146119fb995e4b9b7fadf41b367fa3a1a0d41.
Updated by Kris Phillips over 3 years ago
Tested in 21.05 RC build from May 15th. Looks good. This can be closed out.
Updated by Jim Pingle over 3 years ago
- Status changed from Feedback to Closed
- Assignee set to Viktor Gurov
Updated by Adam Goldberg about 3 years ago
This issue still appears for me on 21.09.a.20210524.0100. Let me know what other specific information I can provide, if any, to assist.
Updated by Jim Pingle about 3 years ago
- Target version changed from 2.6.0 to 2.5.2