Pete H

Hmmm. That makes sense. (BTW, I *do* disable all and selectively enable. It's a bad *.conf file containing references to invalid interfaces due to having deleted some VLANs. Thus, pimd...

So I will report this up-chain 😏

On further reflection... it's TRUE that userland "shouldn't" crash the kernel. At the same time, defense-in-depth design suggests that all layers are well served by handling things well. Can't be...

In my case, we're not dealing with dynamic change. Six months ago I removed some VLANs, and thus the associated interfaces. For whatever reason, now having those in pimd.conf leads...

I understand. Time for me to put on my coder/diagnosis hat and dig in. ;)

Sorry, Real Life got crazy... I will try to come back regularly. My setup: * pfSense 2.4.5 based on FreeBSD 11.3-STABLE * With pimd packaged up from pimd 2.3.2 *...

oh... pimd.conf (with command line disable-vifs) spt-threshold packets 0 interval 100 phyint re0.71 enable phyint re0.9 enable phyint re0.12 enable phyint re0.15 enable phyint re0.11 enable phyint re0.79 enable phyint...

As I noted, I do have logging on for all (?) related items, including the fall-through blocking. I'll check those links and see what I can find. THANKS!

Thanks for asking. I did some captures but haven't yet captured the actual issue... and then I had to take a break for the Real World (my wife will soon...

I am back on this, after a lot of Real World challenges. At a surface level, I do have allow-opts set "everywhere"... but we shall see. What I *REALLY* want...