> 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 changes including the same for aliases. I was the only one accessing the UI and I had only one session. I have never seen it before so it's certainly not a consistent issue anyway. > There isn't enough detail in your description to speculate about why a > VLAN might have stopped passing traffic, but it's unlikely to be related > to a filter reload or pf in general unless you were changing rules on > the interface at the time. At the time we noticed the vlan stop passing dhcp requests there were no changes. In this scenario, all the devices had leases so when the issue truly manifested is hard to say. There had not been any rule changes on that interface anyway and neither with the dhcp relay on it. Given the nature of the traffic being broadcasts, I am not clear on how that became affected. Possibly some other technique could have resolved it but without knowing a reboot was my only option at the time. Thanks, jlc _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
