Skip to content
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

Parsing wireshark manuf instead of oui.dat #303

Closed
ghost opened this issue Jul 21, 2018 · 2 comments
Closed

Parsing wireshark manuf instead of oui.dat #303

ghost opened this issue Jul 21, 2018 · 2 comments

Comments

@ghost
Copy link

ghost commented Jul 21, 2018

In order to properly handle vendors bettercap needs some changes in MAC ranges logic. Smaller vendors sometimes are given MAC ranges, just like an IP network. Ex:

00:50:C2:6E:E0:00/36	Interact	Interactive Electronic Systems
00:50:C2:6E:F0:00/36	Pneumopa	Pneumopartners LaenneXT SA
00:50:C2:6F:00:00/36	StanleyS	Stanley Security Solutions, Inc.

Also, the wireshark manuf list in more complete as it includes IEEE public OUI listing (which is partially included now in .dat) with community contributions. We can then exclude .dat from this repo and only download a file from wireshark.org while running make_oui.py script.
What do you think?

The file itself is in:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob_plain;f=manuf;hb=HEAD

PS. the list is published under GPL-2.0-or-later

@evilsocket
Copy link
Member

@alexmozzhakov this feature update has been great, I can finally lookup 99.9% of the MACs on my test networks, that's great! :D Thanks Alex

@ghost
Copy link
Author

ghost commented Sep 26, 2018

@evilsocket have fun with that, Simone 😄

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

No branches or pull requests

1 participant