Failed to connect to bebop and bebop2


#1

Am using ubuntu 14.04 on virtualBox
when i run the command
sudo sphinx /opt/parrot-sphinx/usr/share/sphinx/drones/bebop2.drone
i get this error
[Err] [Machine.cc:852] Failed to start bebop2 : net.hook/assign failed.
[Err] [Machine.cc:859] Probable cause for this error: the requested stolen interface (wlan0:eth0:192.168.42.1/24) does not exist
However, when i comment
<stolen_interface>wlan0:eth0:192.168.42.1/24</stolen_interface>
in my drone xml the simulator runs and no crashes but of course i cannot control the drone.

my iwconfig returns
wlan0 unassociated Nickname:"WIFI@REALTEK"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

enp0s3 no wireless extensions.

enp0s8 no wireless extensions.

lo no wireless extensions.

and lsusb returns
Bus 001 Device 003: ID 2001:3315 D-Link Corp.
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Anyone has an idea whats going on ?


#2

Hello,

We don’t recommend running sphinx in sudo mode and it would be preferable to use Ubuntu 16.04 (we plan to drop the support of 14.04 really soon).

Have you checked the wifi requirements for sphinx?
What is the reference of your wifi device?

In virtualbox, you may have to enable the wifi device under “Machine settings”.


#3

Now using Ubuntu 16.04 still the same issue.
If i run it without a sudo mode i get
terminate called after throwing an instance of 'boost::filesystem::filesystem_error’
what(): boost::filesystem::create_directory: Permission denied: “/home/majed/.gazebo/diagnostics/2018-03-08T14:17:59.115623”

Have you checked the wifi requirements for sphinx?
yes am using D-link Wireless AC1200 Dual Band USB Adapter
What is the reference of your wifi device?
wlan0

wifi is enabled in virtualbox


#4

As for your first error, you should probably run sudo rm -rf /home/majed/.gazebo before relaunching sphinx without sudo.

In virtualbox, you should configure your virtual machine network access in bridge mode and launch sphinx with the option --port-forwarding set to your host IP address:
sphinx --port-forwarding=<host_ip_address> /opt/parrot-sphinx/usr/share/sphinx/drones/bebop2.drone::with_front_cam=false


#5

hi Ocrave
Thank you for your help, now its working without sudo command and its up and running. However, there is no Access Point showing up.

i ran ifconfig before running sphinx
enp0s5 Link encap:Ethernet HWaddr 00:1c:42:5d:bd:52
inet addr:192.168.1.19 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::16e0:7c3b:3560:1ce3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:227 errors:0 dropped:0 overruns:0 frame:0
TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37587 (37.5 KB) TX bytes:8996 (8.9 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:240 errors:0 dropped:0 overruns:0 frame:0
TX packets:240 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19111 (19.1 KB) TX bytes:19111 (19.1 KB)

wlx9cd64394084a Link encap:Ethernet HWaddr 9c:d6:43:94:08:4a
inet addr:192.168.1.17 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::9d81:ff18:456:ac84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:80 errors:0 dropped:1 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16272 (16.2 KB) TX bytes:6826 (6.8 KB)

After
fd_veth0 Link encap:Ethernet HWaddr 92:df:f7:9e:83:09
inet addr:10.202.0.254 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::90df:f7ff:fe9e:8309/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6798 (6.7 KB) TX bytes:6678 (6.6 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:3663 errors:0 dropped:0 overruns:0 frame:0
TX packets:3663 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:502040 (502.0 KB) TX bytes:502040 (502.0 KB)

wlx9cd64394084a Link encap:Ethernet HWaddr 9c:d6:43:94:08:4a
inet addr:192.168.1.17 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::9d81:ff18:456:ac84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:670 errors:0 dropped:3 overruns:0 frame:0
TX packets:159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:137597 (137.5 KB) TX bytes:21610 (21.6 KB)

I got my host ip address from enp0s5. We can clearly see how It terminates enp0s5 and created fd_veth0.

Any idea how to figure that out ?

Thank you


#6

Are you sure that the interface of your USB adapter is enp0s5 and not wlx9cd64394084a in your example?
Ton configure it, you should just create a new filter in Configuration > USB filled with its vendor and product ID.


#7

Hi

Also, it seems you are using a D-Link AC1200 Dual Band USB Adapter (a.k.a D-Link DWA-182 rev C1).

This adapter is based on a Realtek RTL8812AU chipset and even if this particular chipset support AP mode (on Windows or Mac), the Realtek drivers included in the mainline Linux kernel don’t support the AP mode for this chipset.

As Ocrave already suggested it, you should really check the sphinx wifi requirements.

Regards


#8

Thank you ocrave & ndessart for your responses.
Yes the problem was with my USB Adapter. Even it supports AC mode but it didnt work for some reasons.
I just got a RT5370 and now all good.