Messages

How about testing Dnsmasq 2.92 instead?

# opnsense-revert -z dnsmasq

if this is no workie you can go back to the latest with

# opnsense-revert dnsmasq


Cheers,
Franco

Possibility of hostwatch exhausting the memory can be a factor. I'm assuming it's enabled and it's not growing too big in memory?

The bigger question is are we talking PPPoE in both cases? from _2 to _9 there's no reboot, very few changes. Wondering about the timing of these reports and what they would point to. Not seeing any reasonable explanation yet.


Cheers,
Franco

Well it looks wedged, but I haven't seen this before and now it's on 25.7.11 too?


Cheers,
Franco

I'm a bit at a loss where the bug would come from if components are back on 25.7.11 and it's still happening.  It was working on 25.7.11, totally and normally?


Cheers,
Franco

Well, these two are interesting when this happens:

# ifconfig pppoe0
# pgrep mpd5

Can't rule out that a kernel change causes this. You could try downgrading the kerne:

# opnsense-update -zkr 25.7.11

(reboot)


Cheers,
Franco

Took a quick look. Nothing around this code changed in the last 3 years. I'm assuming this is one of those teardown races which PPPoE is especially prone to (mpd5 removes and recreates devices on a restart). If it's not crashing it's good. If it stalls traffic now that's a bit weird. Is your pppoe0 still there?


Cheers,
Franco

Can you raise a ticket on GitHub about this? This may require a bit of discussion.


Thanks,
Franco

And the base system?

# opnsense-update -zbr 25.7.11

(also needs a reboot)


Cheers,
Franco

There are likely a few more bugs to squash so sit back for now.  Next week we're going to do a small 26.1.1 for mildly related reasons (mostly updating OpenSSL and Python).


Cheers,
Franco

Not sure what the issue here is but you really don't have to migrate anything on day 2 of the release.


Cheers,
Franco

Can you send me the diff shown in System: Configuration: History for the latest "run_migrations.php" change?  Best via mail to franco AT opnsense DOT org.


Thanks,
Franco

We changed the location of the hardware disables in the config.xml... I assume Zenarmor is still reading the old one.

We did, however, flip the default for "Disable VLAN Hardware Filtering".  I'm not sure if there is a bug in the migration but I'll take a look for sure.

I'll move this to the Zenarmor forum for more visibility.


Cheers,
Franco

Reports are piling up.  I'm wondering if the kernel has a bad change?

# opnsense-update -zkr 25.7.11

And reboot?


Cheers,
Franco

Sounds like intrusion detection or Zenarmor active? Not sure if this is the issue, but it can cause traffic drops.


Cheers,
Franco

Nothing comes to mind.  Just make sure you have a config.xml downloaded somewhere so you are prepared.  :)


Cheers,
Franco