> The two are unlikely to be related.
>
> The "pf wedged" message can happen in some race conditions if multiple
> actions are happening, attempting to hit pf in the same way at the same
> moment. In most cases it's noteworthy but otherwise harmless.
I had made several rule additions, removals and
Ref: https://doc.pfsense.org/index.php/Remote_Config_Backup
The above mentioned page seems to advocate using wget with
--no-check-certificate to poll the configuration from a pfSense box.
This means a man in the middle can easily obtain the password of a user
with access to the diag_backup pag
On 08/09/2016 09:46 PM, Joseph L. Casale wrote:
> I recently received an error that the pf table was wedged and had been reset
> while making changes. A few days later, a vlan stopped passing dhcp traffic
> and filter reload did not resolve it, I actually had to reboot the unit.
>
> Has anyone see
> A few years ago, we built a number of such units for customers, and for
> our own use. 4x 10GbE NIC ports on 2 NICs, 4x 1GbE NIC ports on 2
> NICs. LAGed (actually multiple LAGs, typically ~4 per unit). Units
> handled multiple gigabit inbound speeds without issue for a long time
> (custome
> Check your states table size.
Low, right now it is only at %0.002 full and while I don't have that info
from the time of the failure I think it is safe to say it wasn't much different.
Thanks,
jlc
___
pfSense mailing list
https://lists.pfsense.org/mai
