Skip to content

Npcap 1.71: Hardware packet filter may be ignored (e.g. promiscuous unset) when adapters are listed after capture starts. #647

Description

@dmiller-nmap

Introduced in 28b7307. Fixed in f7837ff.

While traversing the list of open instances (capture handles) to remove one and accumulate the packet filter values of the others, the Next pointer of the instance being removed was set to NULL, causing early termination of the loop. Any instances farther down the list (i.e. older instances) would have their packet filters ignored, resulting in incorrect capture parameters being used. This removal happens on every adapter during a call to pcap_findalldevs(), so it is reasonable to assume it will affect a significant number of users.

The next time any instance sets a packet filter, a different, unaffected loop will accumulate the previously ignored values, resolving the issue. Therefore in most cases where listing adapters is immediately followed by starting a capture, the interruption will be of short duration.

This issue affects Npcap 1.70 and 1.71.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions