pfSense

might be always been that way but this is very painful... all other brand do support this properly.
I just start using pfSense and this bug cause me quite a lot of trouble. You really need to fix this

Hi,

we had problems with one of our IPSecs. Sometimes it can connect, sometimes not. After a reboot of pfsense, pfsense can mostly connect.

When I read about this bug, I disabled all P2 entries except one. Now it always works...

Could it really be, that the entry with the same encryption multiple times (esp = aes256gcm128,aes256gcm128,aes256gcm128!) is making problems with the remote site? In our setup, only we establish the ipsec connection.

We be greate to see this fixed, as it can not do anything good.

thanks for your work!

Ran into this bug as well, though it appears to break things if you have too many phase 2 entries. After a certain number (currently appears to be around 85 or 90) phase 2 networks, things start becoming flakey. Sometimes the phase 2 entries at the bottom will work, and other times they don't.

If I modify the /var/etc/ipsec.conf file to make the esp config entries just have the single entry for the last few phase 2 sections, all the networks work / are stable.

If you need any additional info on our setup, let me know.

If someone can point me in the direction of what file creates the ipsec.conf file, I can take a look at it and see if I can figure out a fix. I'm going to try to get time to search for the file myself, but not sure when I'll be able to take a look.

thanks.

PJ Goodwin wrote:

Looked into this and the attached patch appears to fix the issue in 2.4.2. The comparable change also corrected a 2.3.1 version.

It simply resets the $ealgoESPsp2arr variable for each phase2 entry.

I didn't look into it but it's possible that $ealgoAHsp2arr may need to be reset at the appropriate point as well. I don't have a setup that uses that so I didn't look into it.

Same fix corrected the issue on version 2.4.3, though the section moved to line 1264.

pj.

Nice to see that this issue got resolved.
Nevertheless, I'm wondering if the changes could be backported to the branches RELENG_2_4_5 & RELENG_2_4_4? The changeset was only applied to master but those changes got reworked in the context of #9603. It would be really nice to see this patched in one of the next releases, otherwise people have to wait for 2.5/3.0.
Thanks in advance for your effort.