Feature #4359
closed
IPsec controlling uniqueid value
Added by Ermal Luçi about 11 years ago.
Updated about 5 years ago.
Description
Strongswan allows ID behaviour to be controllable especially useful for multiple devices connecting with same ID.
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:908edbd3d17a6fac747b6583322be9e547026f7f.
Applied in changeset commit:86e1846f47bda6a1e2560c249994b47716fac4ad.
- Status changed from Feedback to Resolved
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
- Status changed from Resolved to New
- Target version changed from 2.2.1 to 2.2.2
- % Done changed from 100 to 50
- Status changed from New to Feedback
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=
- Status changed from Feedback to Resolved
- % Done changed from 50 to 100
Also available in: Atom
PDF