Revision history  [back]

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR https://ibb.co/Tm2GzJC

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12 https://ibb.co/6PspRdm

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR https://ibb.co/Tm2GzJC

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12 https://ibb.co/6PspRdm

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR https://ibb.co/Tm2GzJC

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12 https://ibb.co/6PspRdm

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR https://ibb.co/Tm2GzJC

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12 https://ibb.co/6PspRdm

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR https://ibb.co/Tm2GzJC

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12 https://ibb.co/6PspRdm

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?

When a client makes a Read request for approximately 7000 nodes of Uint16 Data type at once, the issue arises within the Read Request. In the same OPC UA protocol packet, it has been reported that a Malformed Packet occurs in version 4.2.x, whereas in version 4.0.x, no Malformed Packet occurs.

It seems that the latest version of Wireshark is not properly reassembling the ReadRequest, leading to incorrect interpretation of OPC UA. Despite an array size of 6999 nodes, Wireshark only shows confirmation of requests for 1923 nodes. This appears to be limited to the first message fragment. 4.2.1 https://ibb.co/7GPFmBR

Using the 4.0.12 version of the same packet, the interpretation could be verified correctly up to 6998 nodes, unlike the issue observed with the latest version. v.4.0.12

I am curious about the occurrence of Malformed Packets based on the version differences. Can you explain why this is happening?