I'm running opnsense in a virtualized env and was aware about the problems that the vtnet driver had. Now that this is fixed in freebsd core and the patches have found their way into opnsense since 25.7.8, I'm not sure, why hw.vtnet.csum_disable="1" is still present in loader.conf. Shouldn't this go away now?
It's still disabled in the OPNsense default tunables. You can change this in System: Settings: Tunables.
Cheers
Maurice
I wanted to talk to Patrick about this, too. Our own testing was inconclusive.
Cheers,
Franco
From following freebsd-net I am not entirely convinced that this is fixed for good in releng/14.
I've now set hw.vtnet.csum_disable=0 on two OPNsense instances with vtnet interfaces (one amd64, one aarch64).
Will report back with anecdotal observations (remind me if I forget because everything works).
options=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS>
Cheers
Maurice
> fixed for good in releng/14
You mean stable/14?
releng/14.3 is likely not getting any better, but releng/14.4 could given stable/14 is complete ;)
Cheers,
Franco
Quote from: Maurice on December 07, 2025, 09:43:43 PMI've now set hw.vtnet.csum_disable=0 on two OPNsense instances with vtnet interfaces (one amd64, one aarch64).
Will report back with anecdotal observations (remind me if I forget because everything works).
options=ec07bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS>
No side effects observed in the last 6+ weeks.
Upstream it's now fixed in stable/14 but not in releng/14.3. I don't know if OPNsense cherry picked the fixes from -stable or rolled their own.
We should have all the patches in 25.7.x, but if not then definitely in 26.1.x.
Cheers,
Franco
Haven't looked into the details, but a quick search on GitHub reveals quite a few vtnet related cherry picks from upstream into stable/25.7, like this one: https://github.com/opnsense/src/commit/52cbb08
Yes there might be 1-2 missing that I picked up while creating stable/26.1... that was about 150 extra commits from stable/14 that we haven't picked up for 25.7.x for stability reasons.
Cheers,
Franco