I´m a new user of navio+ and i´m trying to setup a wifi network. I already installed the Real-time Linux for Rpi1 and connected with my laptop using SSH via ethernet. I also instelled the APM and I’m able to send telemetry info via radio modem.
What I can’t do yet is to setup a wifi network. I followed the instructions on http://docs.emlid.com/Navio-APM/configuring-raspberry-pi/ but i can´t get access to the network. I’m using a Airlink 101 wifi dongle model AWLL6075, wich is on the supported adapters list.
The RPi can find the adapter as shown in picture below, as well as the driver.
The iwlist scan output makes us believe that a dongle functions as expected since it shows your network.
I think that the wpa_supplicant.conf seems to be just a little bit wrong. It appears that key_mgmt field must be set to NONE like this:
This connects to a normal network with wpa security. If the AP you are connecting to has a DHCP server it is completely automatic, even if you take off your wireless dongle and put it back.
I am using wicd-curses. It is really easy to use and has always worked for me.
Install it with "sudo apt-get install wicd-curses"
Run it with "sudo wicd-curses"
It has a user interfaces, so it should be self explaining.
You’re missing a lot of the standard settings. Important values you should always know (not assume/leave blank) are ap_scan at the root level, and ssid_scan and mode at the network level. Also you should delete the other networks which don’t physically exist (emlidltd plus a couple of other developer networks hidden when you page down in the file).
Here’s a link to documentation for the wpa_supplicant.conf file:
Seems like a lot to read with all the crappy plain text format, but if you step through slowly it makes sense. Alternatively you can just scroll down to the bottom and copy some examples if you don’t have time.
p.s. some drivers simply don’t support certain modes, either due to hardware or manufacturer (software) limitations. One benefit of Linux drivers (if you can ignore the 1000% over complexity of having to be a developer just to use them) is that they are always open source so a software limitation is less likely. Use the iwlist frequency for example because many hardware limitations only occur on certain frequencies, it’s usually documented next to the frequency/channel.