DNP 3 reassemble fragments while sequence number is resetting to 0
Hi, I encounter a PCAP with a fragmented DNP message that reach TL sequence number 63 in a fragment and continue with next fragment of the message with sequence number 0 and so forth. After looking at the reassemble code I assume fragment_add_seq_single_aging() is not supporting sequence number reset while fragments are received. Is there a specific reason for that or the traffic I am looking at is not legal. I could not find in any place restrictions regarding DL fragment sequence number behavior. Thanks, Igal