OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: Andreas_ on March 29, 2019, 04:07:15 pm

Title: 19.1.x ipsec phase2 edit problem with old entries
Post by: Andreas_ on March 29, 2019, 04:07:15 pm

I'd like to add a third phase2 entry to an ipsec definition, so I pressed "clone" on an existing phase2 entry. The fields of the page coming up are not prefilled, and if filled and saved the entry won't show up. Looking at a config backup, the entry misses the ikeid, but has a uniqueid instead.

Investigating further, apparently editing is affected as well: parameters shown are not the one reflecting the phase2 entry to edit.
Only adding a fresh entry seems to work.

Version 19.1.2 and 19.1.4 tested, after refreshing with F5.

Title: Re: 19.1.x ipsec phase2 edit regression
Post by: franco on March 29, 2019, 04:15:48 pm

Regression from where? Missing a data point here.


Cheers,
Franco

Title: Re: 19.1.x ipsec phase2 edit regression
Post by: Andreas_ on March 29, 2019, 04:20:29 pm

The last time I edited/cloned phase2 Entries was with 18.7.x

Title: Re: 19.1.x ipsec phase2 edit regression from 18.7
Post by: franco on March 29, 2019, 04:31:50 pm

Can't reproduce. Still missing something here, but entirely unsure what.


Cheers,
Franco

Title: Re: 19.1.x ipsec phase2 edit regression from 18.7
Post by: Andreas_ on March 29, 2019, 05:05:38 pm

I now have 3 phase2 entries: 2 old and one new.

When clicking on 'clone' on an old entry, I get
<fw-addr>/vpn_ipsec_phase2.php?dup=
the new entry has
<fwaddr>/vpn_ipsec_phase2.php?dup=5c9e3fd2320ae

Checking further:
It seems that p2 entries I entered last year are ok, while the problem only exists with entries that are some years old.
Looking at a config backup, it seems that older entries miss the uniqid property. Seems I have to add the uniqid manually in a config and restore from there?