Open mhct opened 8 years ago
Hi,
I'm not sure that I'm experiencing the same problem that you are describing here but maybe we are having a similar problem.
Can you tell what is the output of
iwconfig eth0
on the Bebop after running the connect script?
Below is what I see and it doesn't look good (ESSID is blank and Access Point is Not-Associated):
IEEE 802.11 ESSID:"" Nickname:"" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:130 Mb/s Tx-Power:32 dBm Retry min limit:7 RTS thr=1 B Fragment thr:off Power Management:off Link Quality=5/5 Signal level=0 dBm Noise level=-92 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:3 Invalid misc:0 Missed beacon:0
Hi,
We tried to connect the Bebop to two different Access Points (TP-LINK AC1750, and Android phone with tethering) but the wpa_supplicant process always behaves exactly the same.
The wpa_supplicant process associates with the Access Point, and manages to change to a state CONNECTED, but simply DISCONNECTING afterwards.
Any ideas on how to solve this issue? The Bebop has firmware 3.3.0, the other binaries needed for connecting to the Access Point are the ones linked in multiple_drones repository.
I uploaded a logfile from one execution of wpa_supplicant here http://pastebin.com/YsUduFtV
Thanks a lot, for any feedback.