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

Random behaviour with opendrop receive #24

Closed
lucferbux opened this issue Oct 1, 2019 · 6 comments
Closed

Random behaviour with opendrop receive #24

lucferbux opened this issue Oct 1, 2019 · 6 comments

Comments

@lucferbux
Copy link

Hi, I've tried in multiple virtual machines with the following configuration the "receive" command with no success:

  • Ubuntu 18.04, network card: Alpha AWUS052NH
  • Debian 9, network card: Alpha AWUS052NH
  • Kali Linux 2019, network card: Alpha AWUS052NH

In all of the environments, I've managed to set up the network with the card in monitor mode, although I have only been able to run the owl process with the -N flag sudo owl -i [iface] -N
When i run the process (both with the daemon process or without it) I've been able to use the opendrop find command all the time, discovering all the devices but when i try to run opendrop receive there are some random issues:

  • Most of the time it does not work, freezing and sending random zerconf mdns packets but not receiven anything.
  • Sometimes it captures the devices and my iDevices display the new device created by opendrop with the given name.
  • Sometimes it captures the devices but it does not appear in my iDevices.

So I don't know what to do to fix those issues.
Thanks in advance.

@lucferbux
Copy link
Author

There's another setup I've tried:

  • Ubutnu 18.04 but fresh installed in a host machine (not virtual machine) with another alpha card.

@lucferbux
Copy link
Author

Ok, I think I've found the error. If you run opendrop in a virtual machine in a mac host, the airdrop service will override the opendrop service, in order to make it work, it is mandatory to disable both Wifi and Bluetooth in the host machine (mac) and use an external card in the VM.

@schmittner
Copy link
Member

Hmm, that does not sound very plausible to me since you are using for own physical Wi-Fi card within the guest. The erratic behavior seems to have to to with the fact that your card does not support active monitor mode (see seemoo-lab/owl#9, why else would you need -N?)

@lucferbux
Copy link
Author

Yes it’s true, I don’t know why the bad performance somehow made me believe it was the problem, so that’s the reason, please could you suggest me any card that supports active monitor?
It’s the first time I’ve heard of that and I don’t know where to start to test this mode now that i know my alpha card doesn’t support it.

Thanks again, really appreciate your work.

@lucferbux
Copy link
Author

Ok, I’ve read the docs of owl, any other external card that could possibly support active monitore mode? Thank you in advance.

@schmittner
Copy link
Member

According to seemoo-lab/owl#10, the TP-Link Archer T1U (mt76 driver) seems to work.

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

2 participants