PfSense 2.2 crashes (hard) when accessing Web Configurator from remote IPsec VPN
-
volandg (or anyone else who can replicate this), could you send me a backup of your config? Can be from status.php which removes keys, password hashes, etc. Can PM it to me here.
I'd especially like to get yours volandg, since I have an ALIX, to test on the same hardware.
-
@cmb:
volandg (or anyone else who can replicate this), could you send me a backup of your config? Can be from status.php which removes keys, password hashes, etc. Can PM it to me here.
I'd especially like to get yours volandg, since I have an ALIX, to test on the same hardware.
submitted via PM, happy to do any testing or provide any additional information if needed
-
it crashes (hard, with dump which I submitted).
Just noticed this part. Could you PM me the IP that crash report was submitted from? I looked for anything from the IP you're accessing the forum from, but nothing recent that's even close to that IP.
-
@cmb:
it crashes (hard, with dump which I submitted).
Just noticed this part. Could you PM me the IP that crash report was submitted from? I looked for anything from the IP you're accessing the forum from, but nothing recent that's even close to that IP.
Thanks!
Hehe… yeah the IP that submitted the crash dumps is about 9000kms away from me ;-) Will PM you the IP blocks it would've originated from shortly. -
Well, after two days of hard work to make my Windows 7 notebook connect to my pfSense 2.2 using IKEv2 and EAP-TLS I successfully connected just a few minutes ago for the first time.
My first test was to access the pfSense webGUI over the IPsec connection which resulted in the same hard crash of my pfSense machine (net6501, nanoBSD). I had to power cycle to restart it.
Regards,
Peter -
And if you need a fix while waiting 2.2.1, use openvpn.
-
And if you need a fix while waiting 2.2.1, use openvpn.
Yeah, OpenVPN is running since 2.0.1 without any issues and I like it much more because of the more straight forward concept. I just thought it would be nice to get familiar with IPsec as well. But all in all it's much harder to set up. And I have found another issue with CRL check, will open a thread soon. I strongly suppose, some of the IPsec problems are related to pfSense migrating from racoon to StrongSwan.
Regards,
Peter -
I suspect they ALL are… Gained some function but lost some stability.
However, CMB pointed out, some of the functioning IPSEC configs out there never should have worked in the 2.15 - they just happened to.
And so people with badly configured IPSEC on 2.15 that happen to work anyway break upon upgrade.
Anyway - sounds like a reasonable explanation.
I never found IPSEC that reliable compared to PPTP or openvpn and since PPTP isn't secure, the choice is clear for me.
-
Well, after two days of hard work to make my Windows 7 notebook connect to my pfSense 2.2 using IKEv2 and EAP-TLS I successfully connected just a few minutes ago for the first time.
My first test was to access the pfSense webGUI over the IPsec connection which resulted in the same hard crash of my pfSense machine (net6501, nanoBSD). I had to power cycle to restart it.
Regards,
PeterI'm having the exact same problem.
It's a clean 2.2 install on soekris net6501-70
I used this guide to setup ipsec. https://doc.pfsense.org/index.php/IKEv2_with_EAP-MSCHAPv2
I'm able to browse other clients on my network but as soon as i try to access the pfsense GUI it chrashes.
Regards.
-
What is the status of this issue? Is it recognized as a bug and being addressed ?
-
This is a VERY serious problem. Here's another topic which I bet is related: https://forum.pfsense.org/index.php?topic=88606
I guess you can try what's suggested there. I'm also expericing crashes but couldn't find a specific trigger
-
I've seen the same issue on v2.2 over VMware (both ends virtual, IPSec between them), so it's not a hardware problem. Worked fine for years on v2.0x before, even on beta versions and on the same host hardware.
In my case it SEEMS to be fixed by disabling IPcomp (IP Compression) on the Advanced tab under IPsec, and begins to fail again with a double fault as soon as I re-enable compression. Went from crashing more than once per hour to staying stable for more than 24h and counting.
I already submitted one of the crash dumps for evaluation. -
Should we report this as possible bug on pfSense bugtracker and refer to this thread ?
-
Exact same issue here on a Sokeris net6501. Does anyone know if this is in the bug tracker? I had a look but couldn't see it.
-
Just completed the upgrade to 2.2.1.
The issue is still there. Accessing the webUI while connected over IPSec VPN will crash the box.
-
https://redmine.pfsense.org/issues/4537
-
Could you all test by setting net.inet.ipsec.directdispatch to 0 as ermal outlined in this post? I believe this is all the same issue
-
I think I ran into the same problem (2.2.1-RELEASE on AMD G-T40E) and submitted a few crash dumps.
I set net.inet.ipsec.directdispatch to 0 and have not had another crash since then.
-
I have the exact same issue, my remote pfsense instantly crashes when I access it via remote ip. if I remote desktop to the server on the local network, I can access the box, but using ipsec and accessing the box from a different subnet the box crashes. I removed all squid and squid guard rebooted and It still crashes.
-
Nambi, did you try the fix that georgeman suggested??
