Open federicoaaguirre opened 2 years ago
Hello @federicoaaguirre
The version of OSW you are using is older and we have had addressed several issues since then.
As such I woudl recommend upgrading to a more recent version of OSW. If the issue still occurs, I would request you provide the results of running ipsec barf
Openswan is installed a lot of OEM network devices subject to the OEM's upgrade paths. If the OEM doesn't update Openswan, then we are stuck on the current version. If the segmentation fault is a known issue in an old version, providing some context and even some configuration settings that may work around the issue would be far more helpful than telling users to upgrade when that isn't always an option for them.
Openswan has been abandoned about 10 years ago, see https://nohats.ca/wordpress/blog/2021/04/23/please-stop-using-openswan/
And
Openswan has had multiple releases over the last 10 years. While it is true it has been forked, it has had bug fixes and new features over the years.
On Fri, 10 Feb 2023, Samir wrote:
Openswan has had multiple releases over the last 10 years. While it is true it has been forked, it has had bug fixes and new features over the years.
I monitor https://github.com/xelerance/Openswan/blob/master/CHANGES and haven't seen any new features. Just many bugfixes and bug introductions.
The mailing lists see 0 messages in the last few years. And all issue reports are closed with "try the latest version".
No Linux distro recommends openswan.
It's dead Jim
Openswan: 1:2.6.38-1 Error:
We have the configuration file that cause the segfault, after removed it, openswan stops to constantly restarts.
Config file:
This was working well until the right side put their VPN down.
Any idea about this? Regards