Skip to content

wcnspect does not clean up the previous pktmon capture #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
daschott opened this issue Sep 20, 2022 · 0 comments
Open

wcnspect does not clean up the previous pktmon capture #14

daschott opened this issue Sep 20, 2022 · 0 comments
Assignees

Comments

@daschott
Copy link
Contributor

Describe the bug
Sometimes, the wcnspect server does not clean up a previous pktmon capture, leaving behind a running pktmon instance. Despite this, future captures still work since wcnspect will terminate any idle captures when attempting to start a new capture.

Component:
Server

To Reproduce
wcnspect capture -t "tcp_SYN" -i "my_ip" all

Expected behavior
I expect the server to clean up the output

Windows OS Version (please complete the following information):

  • Server 2022 (20348.1006)

Orchestrator and Version (e.g. Kubernetes v1.24, ContainerD v1.6.8):

  • containerD 1.6.6, K8s v1.23

Anything else we need to know?:
You can issue a pktmon stop on any of the nodes to clean up any actively running pktmon instances manually.

The actively running capture does not take up disk space since the pktmon capture is executed in interactive mode only (output to stdout).

@daschott daschott self-assigned this Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant