help with usage about goopendrop HOT 56 CLOSED

To install it, you have to first install the required apt packages (see README) and clone the repository.
This is said to keys in the README:
Copy the Extracted keys and validation_record to "Keys" Folder, and run the script: RemovePassphraseKey.sh to remove the passphrase
On Mobile Side, you just add a contact with the same email address used for the extracted Apple ID used for extraction
Then run inside the folder ./Build_Pi.sh. To run it, you have to run sudo ./goopendrop ./config.json. GoOpenDrop will automatically accept every received file and put it in to a folder inside of the folder INBOX. If you want to send a file, you have to create a folder inside the folder OUTBOX with the device name of the device which should receive the file. GoOpenDrop will automatically send it when it discovers the device. That should be how it works according to the README.

from goopendrop.

Ubuntu is based on Debian so it's the same. OWL is an open source implementation of Apples Protocol - that section just mentions that you don't need to install OWL since GoOpenDrop already ships with it.

This step I didn't understand well, if I want to send it to someone who doesn't have my contact, what happens?

It probably won't work but I can't test it.

from goopendrop.

Looks like the goopendrop file should be somewhere in the folder out/arm*. You have to copy it to the normal goopendrop folder.

from goopendrop.

Ok, OWL isn't running. You have to follow the guide in the file RequiredPacakes.txt in Compiled_OWL/arm(or arm64 depending on your distro type) and run OWL via the command owl

from goopendrop.

Hi @lucasromeiro ,

We tested this on Raspian OS and it was working fine. Can you try it with Raspian OS?

from goopendrop.

@lucasromeiro Go isn't installed. You can install it via sudo apt install golang

from goopendrop.

To install it, you have to first install the required apt packages (see README) and clone the repository. This is said to keys in the README: Copy the Extracted keys and validation_record to "Keys" Folder, and run the script: RemovePassphraseKey.sh to remove the passphrase On Mobile Side, you just add a contact with the same email address used for the extracted Apple ID used for extraction Then run inside the folder ./Build_Pi.sh. To run it, you have to run sudo ./goopendrop ./config.json. GoOpenDrop will automatically accept every received file and put it in to a folder inside of the folder INBOX. If you want to send a file, you have to create a folder inside the folder OUTBOX with the device name of the device which should receive the file. GoOpenDrop will automatically send it when it discovers the device. That should be how it works according to the README.

Hello, thanks for the reply.
I'm new to using codes like this and would like to understand better.
Perhaps the documentation is too complex for my understanding.

In the instructions, in the part "Required APT Packages:"
Talk about Debian, but I'm using ubuntu, even so I used the requested command and the answer was this:

In the "Required OWL Binaries:" topic, I was confused if it's just inclusion information or if I need to include something.

This step I didn't understand well, if I want to send it to someone who doesn't have my contact, what happens? "On the mobile side, just add a contact with the same email address used for the extracted Apple ID used for extraction"

Thanks a lot for the help

from goopendrop.

sudo ./goopendrop ./config.json

I managed to install the libraries, clone git, download the keys, but I can't execute what you told me...

from goopendrop.

To install it, you have to first install the required apt packages (see README) and clone the repository. This is said to keys in the README: Copy the Extracted keys and validation_record to "Keys" Folder, and run the script: RemovePassphraseKey.sh to remove the passphrase On Mobile Side, you just add a contact with the same email address used for the extracted Apple ID used for extraction Then run inside the folder ./Build_Pi.sh. To run it, you have to run sudo ./goopendrop ./config.json. GoOpenDrop will automatically accept every received file and put it in to a folder inside of the folder INBOX. If you want to send a file, you have to create a folder inside the folder OUTBOX with the device name of the device which should receive the file. GoOpenDrop will automatically send it when it discovers the device. That should be how it works according to the README.

Every time I run it, this happens:

from goopendrop.

so it worked!

But running config.json didn't work.

from goopendrop.

You're not supposed to run config.json alone. Please use sudo ./goopendrop ./config.json. Maybe you first have to run chmod +x ./goopendrop

from goopendrop.

sudo ./goopendrop ./config.json

hi @PhilDevProg !

i try, but dont work...
see:

from goopendrop.

Looks like the goopendrop file should be somewhere in the folder out/arm*. You have to copy it to the normal goopendrop folder.

you are right! it ran, but this happened, it is stuck there...

from goopendrop.

Ok, OWL isn't running. You have to follow the guide in the file RequiredPacakes.txt in Compiled_OWL/arm(or arm64 depending on your distro type) and run OWL via the command owl

in the RequiredPacakes.txt has:
sudo apt install libpcap0.8 libev4
sudo cp owl /usr/local/bin/

i run it!

when i run OWL:

i dont understand why

from goopendrop.

That means that your WiFi card doesn't support the active monitor mode which is required to listen to Airdrop. So either you buy a WiFi Adapter that supports active monitor mode or you can't use it.

from goopendrop.

That means that your WiFi card doesn't support the active monitor mode which is required to listen to Airdrop. So either you buy a WiFi Adapter that supports active monitor mode or you can't use it.

That's weird. i'm using a raspberry pi zero 2. figured it worked fine. I'm going to have to look at compatible cards and eat one to test.

from goopendrop.

You can check if a WiFi card supports active monitor mode with iw phy phy0 info. If you see the line Device supports active monitor (which will ACK incoming frames) your WiFi card supports active monitor mode if not, it doesn't support it. There's this repo which has information about many WiFi dongles including whether they do support active monitor mode.

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

from goopendrop.

Hello, thanks! I bought a usb dongle for this, I'm waiting for it to arrive!

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

hi, i extract the keys.

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

hi, i extract the keys.

I know. I just wanted to know (out of curiosity) if you had to use an Apple Developer Account.

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

hi, i extract the keys.

I know. I just wanted to know (out of curiosity) if you had to use an Apple Developer Account.

Oh, sorry for the confusion. Yes, you need to have a developer account. It was a little difficult because there were some errors with the certificate, but in the end I managed to solve the problem and the certificate was accepted and the keys extracted successfully.

Have you ever used this library to send something? I would still like to understand a little more about how it works. I would like to send a photo to a number that does not have my contact saved.

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

hi, i extract the keys.

I know. I just wanted to know (out of curiosity) if you had to use an Apple Developer Account.

Oh, sorry for the confusion. Yes, you need to have a developer account. It was a little difficult because there were some errors with the certificate, but in the end I managed to solve the problem and the certificate was accepted and the keys extracted successfully.

Have you ever used this library to send something? I would still like to understand a little more about how it works. I would like to send a photo to a number that does not have my contact saved.

No, I didn't because I don't have a Developer Account and won't pay 90$ for that but since the README mentions that you have to save your contact on the devices to which you want to send something it probably won't work without it.

from goopendrop.

@lucasromeiro Btw, did you extract the keys from an Apple Developer Account or did it work without it?

hi, i extract the keys.

I know. I just wanted to know (out of curiosity) if you had to use an Apple Developer Account.

Oh, sorry for the confusion. Yes, you need to have a developer account. It was a little difficult because there were some errors with the certificate, but in the end I managed to solve the problem and the certificate was accepted and the keys extracted successfully.
Have you ever used this library to send something? I would still like to understand a little more about how it works. I would like to send a photo to a number that does not have my contact saved.

No, I didn't because I don't have a Developer Account and won't pay 90$ for that but since the README mentions that you have to save your contact on the devices to which you want to send something it probably won't work without it.

I read somewhere, I think it was in some issue that has already been closed. I read that it is possible to use the library without the keys, but you have some limitations.

from goopendrop.

@PhilDevProg see this: https://www.idownloadblog.com/2015/12/24/how-to-create-a-free-apple-developer-account-xcode/

from: #6 (comment)

from goopendrop.

Thanks, I'll look into that :-)

from goopendrop.

Thanks, I'll look into that :-)

please, If you get something, let me know. It will be good to know

from goopendrop.

You can check if a WiFi card supports active monitor mode with iw phy phy0 info. If you see the line Device supports active monitor (which will ACK incoming frames) your WiFi card supports active monitor mode if not, it doesn't support it. There's this repo which has information about many WiFi dongles including whether they do support active monitor mode.

Hello everything is fine?

I received the adapter and installed it.
But I can't use it.
Is there anything else that needs to be done?
It appears on LSusb. but it is not listed in my WLAN networks
Look at the print:

I don't know how to use this usb wifi adapter with OWL

from goopendrop.

You can check if a WiFi card supports active monitor mode with iw phy phy0 info. If you see the line Device supports active monitor (which will ACK incoming frames) your WiFi card supports active monitor mode if not, it doesn't support it. There's this repo which has information about many WiFi dongles including whether they do support active monitor mode.

Hello everything is fine?

I received the adapter and installed it.
But I can't use it.
Is there anything else that needs to be done?
It appears on LSusb. but it is not listed in my WLAN networks
Look at the print:

I don't know how to use this usb wifi adapter with OWL

Hmm... Sorry but I don't know how I can help you. Maybe search on the internet how to set up your adapter on your distro.

from goopendrop.

could you please show the output of this:

ifconfig -a

from goopendrop.

ifconfig -a

Hi @bodaay

here:

from goopendrop.

iw phy phy0 info:

root@raspberrypi:/home/pi/open-ath9k-htc-firmware# iw phy phy0 info
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 10
max scan IEs length: 2048 bytes
max # sched scan SSIDs: 16
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports roaming.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1020
HT20
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_wiphy_netns
* set_channel
* start_sched_scan
* start_p2p_device
* connect
* disconnect
* crit_protocol_start
* crit_protocol_stop
* update_connect_params
software interface modes (can always be added):
valid interface combinations:
* #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
total <= 3, #channels <= 2
* #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
Device supports scan flush.
Device supports randomizing MAC-addr in sched scans.
max # scan plans: 1
max scan plan interval: 508
max scan plan iterations: 0
Supported TX frame types:
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in station mode
* [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in station mode
* [ SAE_OFFLOAD ]: SAE offload support
root@raspberrypi:/home/pi/open-ath9k-htc-firmware#

from goopendrop.

@bodaay @PhilDevProg

Could something change if I change the installed operating system?
i am using ubuntu server on rpi zero2.

from goopendrop.

Hi @lucasromeiro ,

We tested this on Raspian OS and it was working fine. Can you try it with Raspian OS?

Hi @imashoksundar
I was trying to do what you asked me to do, use Raspian OS.
But I'm not able to run Build_Pi_Arm5.sh.
I don't understand why you don't accept it.

from goopendrop.

sudo ./goopendrop ./config.json
Thanks! That was it.
I ran it and got the same error.
I went to check and the OWL command is not recognized. I think it didn't install for some reason.
I am unable to install it.

from goopendrop.

@bodaay
Despite the OWN not being found, now with the command "ifconfig -a" it finds my wifi dongle!!!

from goopendrop.

@bodaay Despite the OWN not being found, now with the command "ifconfig -a" it finds my wifi dongle!!!

Run and tnd share the output of:

sudo owl -i wlan1

from goopendrop.

sudo owl -i wlan1

See:

from goopendrop.

sudo owl -i wlan1

See:

Please install owl

Its included in

https://github.com/bodaay/GoOpenDrop/tree/master/Compiled_OWL

Read the file RequiredPackages and follow it

from goopendrop.

sudo owl -i wlan1

See:

Please install owl

Its included in

https://github.com/bodaay/GoOpenDrop/tree/master/Compiled_OWL

Read the file RequiredPackages and follow it

Hi, nice!
i forgot this!

See:

from goopendrop.

Try

`
sudo ifconfig wlan1 down

sudo owl -i wlan1

`

from goopendrop.

Try

` sudo ifconfig wlan1 down

sudo owl -i wlan1

`

Sure:

from goopendrop.

I'm not sure why it cannot control the interface

but the first question I have, is why did you connect wlan1 to your access point? I can see from the ifconfig output its already connected and has an IP address

and please include the output of this command:

iw wlan1 info

from goopendrop.

I'm not sure why it cannot control the interface

but the first question I have, is why did you connect wlan1 to your access point? I can see from the ifconfig output its already connected and has an IP address

and please include the output of this command:

iw wlan1 info

Hi, I have a wifi modem connected on usb (dongle). This was connected together with the RPI, the choice of the wifi modem was made by the RPI, I didn't configure it that way. My RPI has wifi, can I use it to connect to wifi and leave the other usb modem free?

ifconfig -a

from goopendrop.

I'm sorry, include the full output of this:

iw list

check in capabilities part, does it have:

support active monitoring mode

from goopendrop.

I'm sorry, include the full output of this:

I have a Raspberry pi zero 2 and a usb modem that is on the list of boards: Bus 001 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n

The output:

iw list

check in capabilities part, does it have:

support active monitoring mode

root@raspberrypi:/home/pi/GoOpenDrop/out/arm# iw list
Wiphy phy1
wiphy index: 1
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x1 RX 0x1
Configured Antennas: TX 0x1 RX 0x1
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* outside context of a BSS
Band 1:
Capabilities: 0x116e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* set_multicast_to_unicast
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 2,
total <= 2, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports configuring vdev MAC-addr on create.
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xb0 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ RRM ]: RRM
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ DEL_IBSS_STA ]: deletion of IBSS station support
* [ MULTICAST_REGISTRATIONS ]: mgmt frame registration for multicast
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 10
max scan IEs length: 2048 bytes
max # sched scan SSIDs: 16
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports roaming.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1020
HT20
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_wiphy_netns
* set_channel
* start_sched_scan
* start_p2p_device
* connect
* disconnect
* crit_protocol_start
* crit_protocol_stop
* update_connect_params
software interface modes (can always be added):
valid interface combinations:
* #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
total <= 3, #channels <= 2
* #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
Device supports scan flush.
Device supports randomizing MAC-addr in sched scans.
max # scan plans: 1
max scan plan interval: 508
max scan plan iterations: 0
Supported TX frame types:
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in station mode
* [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in station mode
* [ SAE_OFFLOAD ]: SAE offload support
root@raspberrypi:/home/pi/GoOpenDrop/out/arm#

from goopendrop.

I bought this modem only for this project, because it was on the compatibility list:
Bus 001 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n

from goopendrop.

I don't see the support for active monitoring, you are right, its on the list at:

https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

I tested two adapters from that list which are on README page.

I did some search, and aparently that adapter is not working properly

morrownr/USB-WiFi#73 (comment)

from goopendrop.

I don't see the support for active monitoring, you are right, its on the list at:

https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md

I tested two adapters from that list which are on README page.

I did some search, and aparently that adapter is not working properly

morrownr/USB-WiFi#73 (comment)

Thanks.
Excellent tip!
I was curious to know what happened to the SoniaMalki case.
I'll ask her.
I'm returning this adapter I bought.
I'm going to buy a mt7612u. Because the guy who sent the link reports that it works.

What do you suggest?

from goopendrop.

mt7612u is an awesome chipset, and for me was working perfectly in this adapter:

ALFA AWUS036ACM

if you want a dongle size small adapter, Linksys AE600 worked great as well

from goopendrop.

mt7612u is an awesome chipset, and for me was working perfectly in this adapter:

ALFA AWUS036ACM

if you want a dongle size small adapter, Linksys AE600 worked great as well

Received the adapter!

from goopendrop.

@bodaay @PhilDevProg

I finally managed to run the software.
how much work. thank you.
I'm getting some errors, can you help me to know if there's something wrong?
I need to put a file to send to the cell phones that are found, how do I do that? I didn't find a way

from goopendrop.

@bodaay

I need to send files to company employees. For those who have already received it, I don't need to resend it.

So what I need is to send a photo to every discovered device and after sending it, add it to a sent list so as not to send it again. It would be just that.
Can you help me?

from goopendrop.

i dont understand this....

from goopendrop.

i dont understand this....

Maybe the binary file isn't executable. Try sudo chmod +x /usr/local/bin/owl

from goopendrop.

@bodaay

I need to send files to company employees. For those who have already received it, I don't need to resend it.

So what I need is to send a photo to every discovered device and after sending it, add it to a sent list so as not to send it again. It would be just that. Can you help me?

please start this as new issue, since its not related to the same issue

from goopendrop.