Article Source: http://hi.baidu.com/zyqq/blog/item/54bb905256546f040cf3e3a9.html
In fact, this problem is often found during packet capture. Today I went to Google with curiosity.
In a simple summary, the packet captured by Wireshark prompts a checksum error,It is only because it intercepts the overhead checksum of the operating system, and the Gigabit NIC will hand over the computing work to the NIC afte
as invalid, even though the packets will contain validChecksums when they leave the network hardware later.
Checksum offloading can be confusing and having a lot of [invalid]Messages on the screen can be quite annoying. As mentioned above,Invalid checksums may lead to unreassembled packets, makingAnalysis of the packet data much harder.
You can do two things to avoid this checksum offloading problem:*
features related to TCP chimney offload available on the network card. to access these options, choose the Configure button on the General Tab Of The adapters properties. this will bring up a window similar to what is displayed below. the Advanced tab is where the changes will be made.
The retriable options available vary depending on how the vendor implements the driver for Windows. using networ
happened.On a piece of white paper, draw a bunch of gate circuits, and then randomly combine them, slowly, I suddenly found that this circuit is the framework of TSO. I remember helping people fix the routing forwarding last week, but that kind of curing behavior could be too expensive to pass off, after all, now the soft implementation is enough. So only the core transmission network needs this curing of the forwarding, but TSO is the server domain of the first push, server too much, far more
Implementation principle of TCP Segment Offload (TSO), offloadtsoIt was so hot in the morning that I suddenly remembered that someone had talked to me about TSO three weeks ago. I also described the principle of TSO. This principle is also very simple. It is nothing more than segmentation by network card hardware, calculate the checksum to free up the CPU cycle.
At first, the private thought that the checksum is just a simple summation of the results, and later in TCP and UDP see the use of the checksum method is a bit strange-binary anti-code (cyclic carry) summation . The cognitive process of human beings is bound to be from simple to complex, to see what this binary inverse code loop summation means. Example with 16
Abbreviated as Tso,
TCPSEgmentationOFfloadIs used to reduce the CPU overhead of TCP/IP on fast
Networks. TSO breaks down large groups of data sent over a network into smaller segments that pass through all the network elements between the source and destination. this type of offload relies on the network interface controller (NIC) to segment the data and then add the
Release date:Updated on:
Affected Systems:Ibm aix 7.xIbm aix 6.xIbm aix 5.xDescription:--------------------------------------------------------------------------------Cve id: CVE-2012-0194
AIX is an open standard UNIX operating system that provides you with an enterprise information technology infrastructure.
Ibm aix has a security vulnerability in implementation. When the "TCP large send offload" option
Today, during the NEC test, my colleague found that the two devices could not work normally. Through packet capture, the following error was found in the TCP layer of the package:
Checksum: 0xe719 [incorrect, shocould be 0xc2f8 (maybe caused by "TCP checksum offload"?)]
I
1. Preface
Checksum calculation is the basic function of NAT and content modification. After performing these operations, you must modify the checksum in the Data header.
2. 16-bit checksum Calculation
2.1 Basic Principles
The IP, ICMP, IGMP, TCP, UDP, and other protocols have the same
I 've been reading IP, TCP checksum for half a day online. The following is the simplest command, no data 45 0 0 34 4D C5 40 0 72 6 20 E1 D3 93 4 CC C0 A8 1 16 4E 23 6 8F 36 CA 45 A3 EC 73 cb fb 80 10 1E E8 D0 2A 0 0 1 1 8 A 15 f ac fe 0 A1 EF the first line is the IP header, (2-3) byte 0 34 indicates the total package length hex (34) = 52. When calculating and verifying, set the (10-11) 16-bit IP header
1.1 Calculation of IP checksumIP check is for the IP header, that is, only the IP header, and for the IP data part of the verification, the corresponding four times the agreement to ensure that the IP head of the test and the field is 16bit.The calculation principle is as follows:1. Set the checksum field to 02. Calculate the sum of all 16bit words in the IP header3. Reverse the obtained and bitwise in 2 and get the checksum.Calculation principle of 1
The checksum Algorithm for IPv4, TCP, and UDP checksum calculation of the packet header is a 16-bit accumulated and backward code. The same verification algorithm is also used for TCP and UDP data headers, however, the data involved in the calculation is different from the IP grouping header. The structure of the IPv4
only used by the sender to calculate the initial checksum. In practice, for the intermediate forwarding router and the final receiver, you can directly add the received IPv4 packet header checksum part according to the same algorithm, if the result is 0 xFFFF, the verification is correct.
For TCP and UDP datagram, the header also contains a 16-bit
, 0xbb5e + 0 xfced = 0x1 b84b, put 1 in the forward position. The result is 0xb84c.
5. The result of adding all words should be a 16-bit number. If this number is reversed, we can get the test and checksum.
3. The answer is better than the argument. Let's take an example to analyze it. This example calculates a TCP test (consistent with the UDP algorithm)
The TCP
When I read "TCP/IP explanation", I saw that the IP header checksum algorithm is called "sum of every 16 bits." So I thought that every part of the algorithm was first summed up. The write process is as follows: (take the following array as an example: Unsigned short a [10] = {0x4500, 0x059a, 0x82b9, 0X4000, 0x3206, 0x4f79, 0xa66f, 0x08ee, 0xc0a8, 0x0126}; because the first IP Minister 20b is 10 hexadecimal
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.