Feature #4359
closed
IPsec controlling uniqueid value
100%
Description
Strongswan allows ID behaviour to be controllable especially useful for multiple devices connecting with same ID.
Updated by Ermal Luçi almost 10 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 908edbd3d17a6fac747b6583322be9e547026f7f.
Updated by Ermal Luçi almost 10 years ago
Applied in changeset 86e1846f47bda6a1e2560c249994b47716fac4ad.
Updated by Steve Wheeler over 9 years ago
There appears to be a bug in this. The setting is written to the config.xml file but never ends up in ipsec.conf which always reads 'yes'. Tested on 2.2.1-rel 64bit
Updated by Jim Pingle over 9 years ago
- Status changed from Resolved to New
- Target version changed from 2.2.1 to 2.2.2
- % Done changed from 100 to 50
Updated by Benjamin von Mossner over 9 years ago
This pull request https://github.com/pfsense/pfsense/pull/1593 should fix the issue
Updated by David Harrigan over 9 years ago
Hi,
There appears to be a bug with pfSense 2.2.1. Following on from the initial topic:
https://forum.pfsense.org/index.php?topic=87857.new;topicseen#new
Specificially:
"
Hi,
pfSense 2.2.1
I've been looking to test out this patch that was applied then came out with pfSense 2.2.1 - but it doesn't appear to set the value! :-(
VPN...IPsec...advanced settings...Configure Unique IDs as.
If I set as "no" and click apply, the value in /var/etc/ipsec/ipsec.conf remains as "uniqueips = yes".
Indeed, if I refresh the page, the NO changes to YES.
Am I doing something incorrect?
=david=
"
It appears that there is a bug in that the setting is not applied or maintained.
Thank you.
=david=
Updated by David Harrigan over 9 years ago
Hi,
Oops, just noticed that this has hopefully fixed with this PR: https://github.com/pfsense/pfsense/pull/1593.
Thanks!
=david=
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Resolved
- % Done changed from 50 to 100
works