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

Guessing the NAP #532

Open
nir-ontar opened this issue Oct 12, 2024 · 0 comments
Open

Guessing the NAP #532

nir-ontar opened this issue Oct 12, 2024 · 0 comments

Comments

@nir-ontar
Copy link

Ubertooth is a great device and tool to discover the UAP+LAP.
For my needs, I must have the entire BD_ADDR correct. The most common way to find the missing part (NAP) is to bruteforce the OUI list with addresses that ends with the UAP and try to smartly relate to the type of device. That way you minimize the number of potential addresses to check (averaging around 30-40 addresses).

If I try to establish a connection with a wrong address and it falls (which is good) I can try another, but the device will show a notification (that's bad).

So bruteforcing with connection is not the right way.
Ping is better.

My problem is that I don't know how to ping an exact address. All the tools are working even if the NAP is wrong (if the UAP+LAP are correct it's enough). Tools like l2ping, hcitool etc.
For example, if my device's address is 01:02:03:04:05:06 I can ping to xx:xx:03:04:05:06 (x can be any value) and the ping will still work.

I want to ping and address and receive an answer only if the entire address is correct.

Anyone knows how can I achieve that?
Which tool? Maybe a different way?

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