2.3 stops routing traffic every 1 og 2 days.
-
Could you get me a status tgz from your system? Browse to status.php and click the link to download the tgz. Email the file or a link to it to cmb at pfsense dot org.
-
Email is now sent to you.
-
Just experienced another of these fw breakdowns even with the new kernel from CMB :-(
it came at the same time that a big transfer of data started through a site to site vpn tunnel…
I also experienced the same issue even using the new kernel. Also I don't think this is related to SIP traffic because one of the sites that's had the issue doesn't use SIP.
-
Just experienced another of these fw breakdowns even with the new kernel from CMB :-(
it came at the same time that a big transfer of data started through a site to site vpn tunnel…
I also experienced the same issue even using the new kernel. Also I don't think this is related to SIP traffic because one of the sites that's had the issue doesn't use SIP.
I don't think it's strictly related to SIP traffic, but there are tons of RTP UDP packets that are sent during a call. So for whatever reason that payload over the VPN is exacerbating the underlying issue.
-
Just has yet another insident, it seems that everytime it happends it is on the hour, eg. 21.00, 23.00, 01.00. or 05.00 are the times i've noticed this problems starts.
I can see it on my MRTG traffic graphs, when traffic stops comming through the FW.
-
Just has yet another insident, it seems that everytime it happends it is on the hour, eg. 21.00, 23.00, 01.00. or 05.00 are the times i've noticed this problems starts.
I can see it on my MRTG traffic graphs, when traffic stops comming through the FW.
Do you have any cron jobs that run on the hour? pfblocker for instance.
-
I used to have PF Blocker installed, but have removed the package.
Just checked crontab, and there still was two jobs in cron from pfblocker.
I have now disabled both of the jobs…
yesterday i was very desperate, so i tried to upgrade to the latest development version 2.3.1, and this morning i had no problems yet...
Not sure if this was a good move to upgrade to 2.3.1-development? -
I have set pfblocker to now only update once a day. Other than that there are no other custom cron jobs. We shall see.
-
pfBlocker is not the issue. I've been running with no packages and still have in the issue. (see my thread: https://forum.pfsense.org/index.php?topic=110525)
I've started rolling mine back to 2.2.6. Too many headaches and sleepless nights with 2.3.
-
It looks like disabling SMP is an immediate workaround for the problem while we track down and fix the root cause.
https://forum.pfsense.org/index.php?topic=110953.0