Project

General

Profile

Actions

Bug #5172

closed

Napatech stream mismanagement following non-transient error

Added by Jeff Lucovsky about 2 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0

Description

When a non-transient error, such as a "time merge error" occurs in the Napatech packet loop, the stream on which the error occurred is never closed. A new stream is opened, however.

Following a non-transient error from NT_NetRxGet, the stream should be closed with NT_NetRxClose before a new stream is opened.

Actions #1

Updated by Jeff Lucovsky about 2 years ago

Because the original stream is not closed, it'll fill up and then 100% packet loss follows.

A simple time change -- as shown below -- is enough to trigger the hard error

import subprocess
import time

shift = 0

print(f"Shifting time by {shift} seconds")
print("Current", time.time())
replacement = int(time.time()) + shift

expected = time.time() + 10
subprocess.check_call(["date"])
subprocess.check_call(["date", "-s", f"@{replacement}"])

Actions #2

Updated by Victor Julien about 2 years ago

  • Assignee changed from OISF Dev to Phil Young
Actions #3

Updated by Victor Julien almost 2 years ago

  • Label deleted (Needs backport to 5.0)
Actions #4

Updated by Victor Julien almost 2 years ago

  • Target version changed from 7.0.0-beta1 to TBD
Actions #5

Updated by Jeff Lucovsky 4 months ago

  • Status changed from New to In Review
  • Assignee changed from Phil Young to Jeff Lucovsky
Actions #6

Updated by Jeff Lucovsky about 1 month ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF