547
edits
TCP flow chart: Difference between revisions
m
→Limitations
No edit summary |
m (→Limitations) |
||
| Line 45: | Line 45: | ||
# The analysis result is stored on internal storage instead of main memory to keep as much memory available for live processing. Therefore, there is a size limit on how large the connection can be. The maximum number of packets is 100,000, but it can be lower if not enough disk space is available. | # The analysis result is stored on internal storage instead of main memory to keep as much memory available for live processing. Therefore, there is a size limit on how large the connection can be. The maximum number of packets is 100,000, but it can be lower if not enough disk space is available. | ||
# Due to disk space limitations, the number of parallel opened analysis windows is limited to 5. Starting another TCP flow chart will invalidate the oldest one automatically. | # Due to disk space limitations, the number of parallel opened analysis windows is limited to 5. Starting another TCP flow chart will invalidate the oldest one automatically. | ||
# The analysis of a TCP connection starts at the beginning of the connection and stops either at the end of connection or the end time configured in BIT-Mode. Since the packets are extracted from ring buffer, the analysis may take some time especially if it is a long-lasting connection. A progress bar informs about the status of the analysis. | # The analysis of a TCP connection starts at the beginning of the connection and stops either at the end of connection or the end time configured in [[Back-in-Time functionality|BIT-Mode]]. Since the packets are extracted from ring buffer, the analysis may take some time especially if it is a long-lasting connection. A progress bar informs about the status of the analysis. | ||