-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Custom 802.11 Vendor Specific packet #4659
Comments
Currently you're right, this isn't super extensible. |
Hoolean
added a commit
to Hoolean/scapy
that referenced
this issue
Feb 7, 2025
See secdev#4659 This commit allows the Dot11EltVendorSpecific packet to dispatch to its subclasses based on their OUI, with the same idiom that the parent Dot11Elt uses to select subclasses based on their ID already: https://github.com/secdev/scapy/blob/c15a670926185f6ddb9b3330ed1f947ff6f14b92/scapy/layers/dot11.py#L1057-L1074 This is just a rough sketch, so feedback very welcome to make sure it is heading in the right direction :)
Hoolean
added a commit
to Hoolean/scapy
that referenced
this issue
Feb 7, 2025
See secdev#4659 This commit allows the Dot11EltVendorSpecific packet to dispatch to its subclasses based on their OUI, with the same idiom that the parent Dot11Elt uses to select subclasses based on their ID already: https://github.com/secdev/scapy/blob/c15a670926185f6ddb9b3330ed1f947ff6f14b92/scapy/layers/dot11.py#L1057-L1074 This is just a rough sketch, so feedback very welcome to make sure it is heading in the right direction :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! Thank you for the excellent library :)
Scapy has specialised subclasses of
Dot11EltVendorSpecific
that interpret and parse the genericinfo
field of the parent class:scapy/scapy/layers/dot11.py
Lines 1428 to 1456 in c15a670
For a project using Scapy as a library, how easiest can this be extended to cover an additional custom subclass? Is this possible with the current implementation and, if not, is another workaround accessible?
The text was updated successfully, but these errors were encountered: