SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264
MantisBT - Endian Firewall
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002705||Endian Firewall||Network related (VPN, uplinks)||public||2010-02-21 14:16||2010-02-22 11:01|
|Target Version||Fixed in Version|
|Summary||0002705: IPSEC (pluto) causes kernel panics|
|Description||This crash is always reproducable, but perhaps only with the particular peers we have. Within seconds of an IPSEC tunnel coming up, there's a Kernel Panic and a 10 second delay before a reboot. If a peer is actively trying to connect, you have just a few seconds to log in and 'killall pluto' before the crash.|
I have loaded Endian 2.3 on quite different hardware with the same results (an HP Proliant DL360G5 server). It may still be some common hardware but the 'killall pluto' that prevents the crash points at Openswan.
I am surprised there are not more reports of this issue, if anyone can give me a work-around I'd love to be able to stay with Endian 2.3.
I have run Endian 2.2 on the same hardware and had an IPSEC tunnel come up for about 15 minutes without a crash.
|Steps To Reproduce|
|Tags||No tags attached.|
|2010-02-21 14:16||lesliev||New Issue|
|2010-02-22 11:01||peter-endian||Relationship added||duplicate of 0000013|
|2010-02-22 11:01||peter-endian||Relationship deleted||0000013|
|2010-02-22 11:01||peter-endian||Relationship added||duplicate of 0001359|
|2010-02-22 11:01||peter-endian||Status||new => closed|
|2010-02-22 11:01||peter-endian||Resolution||open => duplicate|
|There are no notes attached to this issue.|