Messages

It looks like ntopng was definitely the root cause of my issues. I haven't had any problems since uninstalling ntopng. @letsief thanks for providing that github link, it seems to be the behavior I was experiencing. I'll look at adding it back again down the road, I don't think I was utilizing it at all since installing it so I'm fine without it for now.

Well, I don't think ntopng itself is really the root cause. Ntopng triggers the problem by putting the interface in promiscuous mode, but that shouldn't kill the ipv4 stack.

It is probably a driver issue, but it also seems like opnsense should be more resilient of whatever failure is going on. It appears that something is tripping up dhclient. And whatever that is, it is probably screwing up other stuff, too.

I switched ntopng to only run on the LAN interface, so the WAN doesn't end up in promiscuous mode. It seems to be working for now. We'll see if it creates other problems, though, on the LAN side.

Things were running stable after I disabled ntopng.  Turning it back on very quickly broke the ipv4 stack again.

It seems to be related to ntopng putting the interface in promiscuous mode.
https://github.com/opnsense/core/issues/7478

Not sure if there is any way to work around this problem.

I've been struggling with something similar all day. I'm just setting up opnsense for the first time (migrating from pfsense), so I've been making a lot of config changes.  It seemed like things were working ok yesterday, but the IPv4 stack on my WAN interface keeps breaking. Oddly, IPv6 keeps working fine.

The ntopng angle is interesting. I'm running that too and will try to turn it off.  I was running that yesterday without problems, but I've been playing around with the ntopng config today.  HAproxy, too.

One interesting thing I've observed is running `dhclient igc0` fixes it, but only for another ~15 minutes.

I'm running opnsense on a N305 box with I226-V NICs, too, but on bare metal.