Firewall logging randomly stopping

qubit

I've noticed this on previous snapshots and now my most recent one (June 22, running no packages). I would log in and check things out in the GUI and notice that firewall logging had stopped and the system log states:

kernel: pflog0: promiscuous mode disabled

Going into system log settings, clicking save and applying brings pflog0 promiscuous mode back up but it would eventually stop later on. I've seen this happen from a few hours after reapplying to a day or two later late at night. When it does stop nothing odd is in the system log and the firewall log shows nothing blocked directly before it stops. There's plenty of free space so I don't think that's the issue. 2.0.3 works solid and has never done this and other than upgrading to 2.1 network traffic and usage hasn't changed so it's difficult to try to reproduce this.

However I've seen pflog0 die within minutes after logging into the GUI during my testing in May:

May 29 21:34:14	php: /index.php: Successful login for user 'admin' from: 192.168.1.102
May 29 21:34:14	php: /index.php: Successful login for user 'admin' from: 192.168.1.102
May 29 21:36:04	kernel: pflog0: promiscuous mode disabled
May 29 21:38:51	sshd[8769]: Accepted publickey for admin from 192.168.1.102 port 7476 ssh2
May 29 21:39:09	check_reload_status: Syncing firewall
May 29 21:39:09	syslogd: exiting on signal 15
May 29 21:39:09	syslogd: kernel boot file is /boot/kernel/kernel
May 29 21:39:09	kernel: pflog0: promiscuous mode enabled
May 29 21:39:21	check_reload_status: Syncing firewall
May 29 21:39:21	syslogd: exiting on signal 15
May 29 21:39:21	syslogd: kernel boot file is /boot/kernel/kernel
May 29 21:39:23	kernel: pflog0: promiscuous mode enabled
May 29 21:41:55	php: /index.php: User logged out for user 'admin' from: 192.168.1.102

It hasn't stopped upon login on a June build yet, but I had firewall logging stop yesterday. So other than that one login, I can't seem to pinpoint what's going on when promiscuous mode disables.