Lan crashes every day or so, nothing in logs version 2.3.1_p5, only 1 processor

dinaras

Hello,
I have been experiencing the problem where lan interface stops routing. Although other users say it has been resolved in latest 2.3.1-p5 i still have the issue.

My hardware is with only 1 processor
Version 2.3.1-RELEASE-p5 (i386)
built on Thu Jun 16 12:53:31 CDT 2016
FreeBSD 10.3-RELEASE-p3

The system is on the latest version.
Platform pfSense
CPU Type VIA Eden Processor 500MHz
Hardware crypto VIA Padlock

memory 512 MB

I am using vpn IPSEC, looking at the logs, i cannot find why it is crashing everyday.

I am not an expert on pfsense or freebsd so please let me know if you would like me to provide any more information

My NIC are realtech and built in on the motherboard.
My crash i matching this bug report
https://redmine.pfsense.org/issues/6296

Please help resolve this as it is causing major problems. Problems started after creating the IPsec vpn, but now i am unable to remove it
Thank you in advance for your help

cmb

It doesn't match that bug report. It was already fixed for one, and two it never affected single core CPUs.

That's probably the issue with VIA Padlock, it seems to have driver issues. Using something other than AES, so Padlock isn't touched, was reported to workaround by a couple people who ran into that issue.

dinaras

Hello and thank you for your reply,

I seem to be unable to change vpn configuration, as it is difficult to be done on the other side.

Is there anyway i can disable via padlock so it will not mess up pfsense connectivity?

Thank you in advance

dinaras

Hello,
I made the change you instructed me. I disables in phase 2 AES 256 and only left 3des as encryption algorithm.

Again today lan was not accessible from anywhere

May i also say here that this happens exactly after 24 hours from last reboot.

Does this give any hint?

Now firewall is upgraded to 2.3.2
Thank you in advance

dinaras

unfortunately i have had enough with pfsense.

I am unable to solve this as it has been torturing me for months.

Firewalls shouldn't do things like that, it is nowhere near for production use, especially for datacenter where physical access is limited

Thanks for your help so far

jimp

From the sound of it, your hardware was the problem and not pfSense. I hope you can find something that will run stable on there, but if you decide to try again on newer/better hardware, you are more likely to succeed.

dinaras

hello Jimp,

You were right,

i bought some new hardware using intel network cards. It has been up for 2 days with no problem.

I hope it stays that way…... it was sooooo frustrating.

Thank you very much