Add Device Metadata Extraction (OUI, DHCP Hostname, User-Agent) #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ader protocol set
uses the working tshark in PATH rather than macOS app bundle version
- Included 'dhcp_hostname' in flow aggregation - Changed docstring to reflect DHCP hostname integration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for extracting and enriching device metadata from PCAP files, including:
eth.src.oui_resolvedbootp.option.hostnameChanges
dhcp_hostname,user_agent, andeth.src.oui_resolvedfieldsNote: While SSDP messages and mDNS PTR queries are visible in the traffic, XML-based device metadata (e.g.,
description.xml)cannot be fetched because the analysis is being performed offline—outside the local network. As a result, UPnP fields likemodel_name,manufacturer,etc., are not included.Resolves #19