Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Reassembly error, How to explain New fragment overlaps old data?

Can anyone help me to analyze the packet file and give a concrete explaination about "New fragment overlaps old data"? https://www.cloudshark.org/captures/b0b369af1cf7

There must be something wrong with the network between client and server of postgresql. The discontinuous change about IPID from server to client can help to prove it.

But I failed to understand the Expert Info on TCP layer.

The related code lines: https://gitlab.com/wireshark/wireshark/-/blob/master/epan/reassemble.c

Reassembly error, How to explain New fragment overlaps old data?

Can anyone help me to analyze the packet file and give a concrete explaination about "New fragment overlaps old data"? https://www.cloudshark.org/captures/b0b369af1cf7

There must be something wrong with the network between client and server of postgresql. The discontinuous change about IPID from server to client can help to prove it.support this suppose.

But I failed to understand the Expert Info on TCP layer.

The related code lines: https://gitlab.com/wireshark/wireshark/-/blob/master/epan/reassemble.c

Reassembly error, How to explain New fragment overlaps old data?

Can anyone help me to analyze the packet file and give a concrete explaination about "New fragment overlaps old data"? https://www.cloudshark.org/captures/b0b369af1cf7https://www.cloudshark.org/captures/cb0f7fb681ae

There must be something wrong with the network between client and server of postgresql. The discontinuous change about IPID from server to client support this suppose.

But I failed to understand the Expert Info on TCP layer.

The related code lines: https://gitlab.com/wireshark/wireshark/-/blob/master/epan/reassemble.c

Reassembly error, How to explain New fragment overlaps old data?

Can anyone help me to analyze the packet file and give a concrete explaination about "New fragment overlaps old data"? https://www.cloudshark.org/captures/cb0f7fb681ae

There must be something wrong with the network between client and server of postgresql. The discontinuous change about IPID from server to client support this suppose.

But I failed to understand the Expert Info on TCP layer.

The related code lines: https://gitlab.com/wireshark/wireshark/-/blob/master/epan/reassemble.c