Pfsense sudden failure common?



  • Hello, today i was sitting chatting with friends on teamspeak and one specific friend also runs pfsense. Well he noticed pfsense just stopped working, everything Internet (except established connections ex teamspeak) pfsense's http webadmin, pfsense's ssh you name it it was not reachable. He restarted pfsense and didnt help so he reset his config and it works again. About 15 hours later, same thing happened to me! This is what is happening (I am using my neighbors internet to write this) my pfsense box is not times out on when i ping it, and its not tracert able. Cant connect to http or ssh its like its not even there but it is. I did just so happen to have had a SHOUTcast stream up and it was still playing! i cant open any tcp connection to pfsense or the internet except that stream which is still playing on my desktop while i write this. Also, we were both in the web admin at the time of the problems, i just forwarded SIP ports when it happened to me. What do i do? i dont want to have to start my config over again. Thanks.



  • Sounds to me like state exhaustion.

    You could try to increase the number of concurrent states from the default 10'000 to 50'000. (System –> advanced --> Firewall Maximum States)



  • @GruensFroeschli:

    Sounds to me like state exhaustion.

    You could try to increase the number of concurrent states from the default 10'000 to 50'000. (System –> advanced --> Firewall Maximum States)

    Could be the NAT reflection inetd problem.

    I've encountered this on the April 4th build.  Disabling NAT reflection worked to solve it.  Wasn't a states exhaustion problem since I had both tables set to 500,000 and the WebGUI reflected about 50k states in total.  The NAT reflection was caused by my torrent program reflecting back onto itself.



  • Ok, i sloved the problem. The box died. I still have no clue why it allowed that single connection but the box was dead when i checked on it the following morning. I went to restart it and it couldnt even load BIOS.


Log in to reply