|
|
|
@@ -13,14 +13,14 @@ works as expected, and that the features it claims to implement are |
|
|
|
properly implemented. |
|
|
|
|
|
|
|
A non-exhaustive list of features that could be listed as supported, but |
|
|
|
not working are jumbo frames (large MTU), hardware VLAN tagging, and |
|
|
|
checksum offload. In the case of the last two, a driver can claim to |
|
|
|
support these, but if the underlying bits in ifnet structure are not set, |
|
|
|
nothing will happen. Another example is that a driver could just always |
|
|
|
set that the checksum is valid, even when it is not. In most cases, this |
|
|
|
won't be noticed, and with many protocols doing their own verification |
|
|
|
(ssh and TLS), it will just result in a dropped connection, but in other |
|
|
|
cases it will cause data corruption. |
|
|
|
not working are jumbo frames (large MTU), hardware VLAN tagging, multicast |
|
|
|
filters, and checksum offload. In the case of the last two, a driver can |
|
|
|
claim to support these, but if the underlying bits in ifnet structure are |
|
|
|
not set, nothing will happen. Another example is that a driver could just |
|
|
|
always set that the checksum is valid, even when it is not. In most |
|
|
|
cases, this won't be noticed, and with many protocols doing their own |
|
|
|
verification (ssh and TLS), it will just result in a dropped connection, |
|
|
|
but in other cases it will cause data corruption. |
|
|
|
|
|
|
|
As part of this project, two sets of patches were developed, one is the |
|
|
|
[kvm_ctf branch](https://www.funkthat.com/gitea/jmg/freebsd/src/branch/kvm_ctf) |
|
|
|
|
