Messages

Verify the boot device is ok, then reinstall. If it fails SMART and possibly bad block tests, replace it before reinstalling.

Warum sollte sie den fragmentieren? Sind nicht alle beteiligten Netze Ethernet mit einer MTU von 1500?

ethtool --show-eee igc0
ethtool -i igc0

Code Select Expand

root@opnsense:~ # ethtool
ethtool: Command not found.

OPNsense isn't Linux.

No? Just go ahead and do it. It's not rocket science.

There's a bug in the boot loader in FreeBSD that under specific circumstances with the plugin installed makes the system hang at boot.
There is a workaround in the updated plugin in 26.7.1, so you should IMHO definitely re-add that. Also consider updating your boot loaders.

Running without microcode updates for known CPU bugs is probably not a good idea.

@JohnSchnee try:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/9412fa3bd8

Reference: https://github.com/opnsense/core/issues/10553

net.link.bridge.inherit_mac=1 makes the bridge inherit the MAC address of the first member interface the moment it is added.

Try net.link.bridge.inherit_mac=1

@meyergru It looks to me similar to creating a lagg with only one member to "abstract away" different interface names in a HA setup with different hardware.
@lmoore Clever one!

*deleted*

If the modem has two ethernet ports you could use two interfaces on OPNsense (or VLANs distributed via a switch) to connect to

- the modem network
- the proper uplink

Just a thought. I do this. I do not piggyback the modem network on top of the PPPoE interface. I use two completely separated ones. I think this could be even more important for DHCP instead of PPPoE.

About right.

Probably they are simply not supported by FreeBSD.

Hardware compatibility list:

https://www.freebsd.org/releases/15.1R/hardware/#ethernet
https://man.freebsd.org/cgi/man.cgi?query=re&sektion=4&format=html

I cannot find any 2.5G Realtek adapers in there, only 1G Realtek and 2.5G Intel.

Scrub yes. TRIM yes, if you do bot have autotrim enabled.

Code Select Expand

zpool get autotrim zroot


Also, if the kernel/zfs implementation was just updated, you cannot use older snapshots if you upgrade the zpool.

You mean in the context of OPNsense and boot environments, not ZFS in general, right?

To elaborate: you cannot boot an older boot environment (what the UI calls "snapshots") because that contains an older kernel from before your upgrade which is not compatible with the new ZFS features and won't import the "new" pool.

But of course from a strictly ZFS point of view you can copy an older snapshot to another system, you can mount it, you can copy files from it, etc. Snapshots from a previous ZFS version continue to work as snapshots. But they cannot be bootet, anymore once the pool is upgraded.

N.B. ZFS snapshots are not necessarily boot environments. You can snapshot any dataset, e.g. for backup purposes. Only rarely happens in OPNsense.