Random panic on wan interface.

theglu

Hello,

I have random panic on the process who manage the wan interface. I tried to change it, the process changed to new wan interface.

It's random. Nothing can happen during hours, then it's begin to crash and reboot for every 10 minutes, or 2 minutes, or even when pfsense is rebooting. And then after a while it's ok…

I'm using openvpn and NAT. And specific routes. Pfsense 1.2.3, alix alix2d3.

I didn't had the problem before (using pfSense without Openvpn, nat and custom routes, just firewalling)

Infos are always the same :

http://www.upload-it.fr/files/1079440900/pagefautl1.png

And sometime I see this in logs, when rebooting:

http://www.upload-it.fr/files/1779571886/reset.png

Any help ? ???

jimp

Random panics and reboots that start out of the blue are almost always hardware or power related.

Plug into a different outlet or UPS. If that doesn't help, try a different power supply. If that doesn't help, it may be the unit itself. You might try another CF, but that is less likely to help.

theglu

Well, it's start when I started using OpenVpn, and happen only on the wan interface, so it's not so random ;)

I will turn off OpenVpn for a while and check what's happen.

jimp

OpenVPN implies encryption, encryption drives a system harder (especially a little embedded unit like an ALIX), which means more power draw, more intense memory/cpu usage, etc.

Turning off OpenVPN wouldn't been a good indicator really. It would just go easier on the system, which doesn't tell you much if the problem happens only under general system stress.

theglu

It's was a WPA2 access point before (I removed the card just in case), I think it's ~ equivalent no ?

jimp

I haven't seen an access point drive an ALIX so hard that it falls over from intense CPU usage and interrupts. I have seen OpenVPN do this several times. (And IPsec, or just lots of throughput)

theglu

Ok. I will investigate about hardware's problems :)

theglu

New alix, new CF, new power supply. Same config, same core dumps :)

This is obviously a software problem.

theglu

Using beta 2. Dosen't seem to have the problem… yet :)