So it's simply not worth the additional CPU load you need on IPv6 switches to calculate the checksum for every single packet they route. And that is a scenario which doesn't really happen all that often. You have mentioned that Configuring NIC under the Windows, if you want change the setting about TCP checksum, you may follow the steps below:Open network and sharing center change adapter settings - right click the adapter and click properties - advanced. A bit of bandwidth got wasted, and that's it.

So what's the worst that could happen if an IPv6 router tries to route a corrupted packet? The packet will either not get routed at all, because the header contains invalid values or the destination address doesn't exist, or the address is a valid one (which might or might not be the intended one), so it will arrive at a destination, which will then discard it because the transport layer checksum doesn't add up. And these checksums often cover parts of the IP header as well, even though those aren't technically part of the transport layer segment (like source and destination address). But almost all transport protocols based on IPv6, like TCP or UDP, also have error checking to catch logical errors.

What's left are logic errors in the packet itself. Al seleccionar Internet Protocol, la pestaa inferior nos muestra el frame que utilizaremospara calcular el checksum del IP.Dentro de este marco ya aparece el checksum. All the common link-layer protocols, like Ethernet or WiFi, have their own error checking and error correction mechanisms, so physical transmission errors are already unlikely. Podremos tomar como ejemplo cualquier paquete de datos, posteriormente, nos dirijimos a Internet Protocol, abrimos la pestaa y veremos el checksum que nos entrega Wireshark.

Wireshark ip header checksum