PfSense 2.2 crashes (hard) when accessing Web Configurator from remote IPsec VPN
-
no clue what causes that issue … that's for the devs to find out.
but why run i386? x64 is more stable and tested.
@heper - Unfortunately I have to run i386 because I cannot run a x64 guest in VMWare ESXI when the host PC does not supprt the VT-x and related XD/NX extensions (It's an old dual Intel Xeon 1U server).
Squid3 package did NOT install, however the SquidGuard3 package did install.
I bet it wouldn't crash if these were not installed.
@kejianshi OK Thanks - I've got a small maintenance window coming up, and can switch in a different virtual hard disk with the 2.2 build on. I'll try that to rule that in or out and post back when I know.
-
I removed the Squid3 and SquidGuard3 packages and rebooted.
Unfortunately it still crashes the moment I access the web configurator via the IPSec VPN.
I'll try a clean pfSense 2.2 install (i.e. without restoring any configuration) and then manually create a IPSec setup and test that scenario to try and isolate the conditions. I've run out of time available, so I'll post back here with the resuls, when I have managed to do that too.
-
Seems strange. Just wondering… Is there a reason you prefer IPSEC to Openvpn?
-
It looks like we are having similar issue here:
Running i386 on alix2d13.Since an upgrade - connecting via IPSec VPN(mobile client) and then tying to access the IP address of the pFsense box will core dump the box. SSH & HTTP are the same.
ICMP requests are not affecting the box. The Hosts on the remote network can be accessed with no problems.the same behavior is observed on the box with upgraded image as well as on the box with clean install+restore backup config
Any recommendations ?
-
It looks like we are having similar issue here:
Running i386 on alix2d13.Yeah, this thread is about ESXi; no idea why did you jump in here. As a quick guess, disable the glxsb crypto accelerator, might be completely toast. And move to your own thread.
-
It looks like we are having similar issue here:
Running i386 on alix2d13.Yeah, this thread is about ESXi; no idea why did you jump in here. As a quick guess, disable the glxsb crypto accelerator, might be completely toast. And move to your own thread.
the thread is about pFsense crashing upon using the IPSec VPN(site to site) and accessing the the remote IP address of the box. That is the main problem. Isn't it?
Due to the fact i can see the same behavior when doing mobile IPSec it looks like both cases are related somehow. don't you think?
P.S crypto accelerator is disabled
-
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.