Messages

https://github.com/opnsense/plugins/issues/5050#issuecomment-3591354876

We do offer branding as a service.  :)


Cheers,
Franco

Note that you can disable sounds via System: Settings: Misc: System Sounds because that is easy to forget and nobody mentioned it.  ;)

"When this is checked, startup and shutdown sounds will no longer play."



Cheers,
Franco

We use "service" once for restarting configd on package updates. I'm not sure what's going on in your install, but 25.7.x shouldn't make a difference.

"pulseway" is not in FreeBSD ports either if I checked correctly. That means it's highly unlikely the update did anything.


Cheers,
Franco

> wasted space seems the same

No, it's not the same.


Cheers,
Franco

Easy with the fatalism there.

# opnsense-patch https://github.com/opnsense/core/commit/c11efa62bda8a

You may also like

# opnsense-patch https://github.com/opnsense/core/commit/d698b4e5a

I haven't seen or heard from any main mirror issues but if it's solved that's good.


Cheers,
Franco

> I still get netmap_transmit ixl0 full from time to time.

It's expected when the system can't push the traffic it's supposed to forward. It's probably a CPU bottleneck you're hitting.

> My question is: Does the lease drop-down only show interfaces that have been assigned IPs? Could it be that if an interface doesn't register an IP, it doesn't show up in the list? And if that's the case, how do you explain the two VLANs that are showing up under WAN?

Cedrik would know better how the lease view works. To me it sounds like they are being misattributed either by our backend or Dnsmasq itself, but without the data, a brief network description (to check for overlapping subnets) and/or a screenshot it's hard to tell.


Cheers,
Franco

Try a different mirror perhaps. If pkg.opnsense.org is blocked somewhere that's obviously not very useful.


Cheers,
Franco

It's just your IPv6 connectivity that's busted. Try System: Settings: General: check "Prefer IPv4" option.

Can you do a connectivity audit from the firmware status page?

> truncated: 0/1332 bytes

This could happen due to long DNS timeouts for example.


Cheers,
Franco

Great, thanks for doing this.


Cheers,
Franco

I'm sorry to say you are, but for an unexpected reason: you haven't given a single example of what you are talking about.

I'd like to comment, but this feels hollow.


Cheers,
Franco

https://github.com/opnsense/update/commit/4a0f4301adb9a

If you weave that into opnsense-update package with a revision change it should work again :)


Cheers,
Franco

There's no strict science behind it. Best to pull them once a day if that's ok for you.

Let me remove the pin thing.