Not working on Raspberry pi linux OS

[DaniyalGeek]

only showing empty array

[friedrith]

Yes, after trying to resolve issue #2, I have noticed this bug. It seems to come from nmcli on raspbian. I don't know if it is a misconfiguration of wifi on rapsbian or a bug of nmcli on raspbian. I am investigating. If you have any idea how to use nmcli for scan on raspbian, do not hesitate to give your solution here.

[paul-em]

why was this issue closed? was a solution found? i still have the issue... :/

[friedrith]

@DaniyalGeek closed this issus himself. Don't know why too. This issue still remains. I don't know how to use nmcli on raspbian on raspberry pi. I already lost more than one day to try to understand why, without results. Unfortunately, Raspberry pi is not a priority (this project is managed by my company). But if you find a solution, do not hesitate to pull request, I will be happy to integrate it.

Which version of the raspberry pi do you use ? version 3 or an other one with dongle ?

[michael-palmes]

Just got node-wifi up and running on a Raspberry Pi 3 (Raspbian Jessie) and an Odroid XU4 (DietPi) . Below are the steps I followed if it helps:

• sudo apt-get install network-manager

• sudo nano /etc/NetworkManager/NetworkManager.conf

• Change "managed=false" to "managed=true"

• sudo service network-manager restart

• sudo nano /etc/network/interfaces

• Comment out any wlan interfaces. For example on Raspberry Pi 3:
  

• sudo reboot

• nmcli dev wifi connect 'wifi_ssid_here' password 'wfi_password_here'

Your node app using node-wifi should now work correctly.

[friedrith]

I have just tried on raspbian and it's working very well. Thx. So node-wifi works officially on raspbian. Except that I have to use the last command with as root. However I don't want that node-wifi users run their scripts as root because it is too dangereous.
Do you know how to setup nmcli to make it working as standard user ?

[friedrith]

Commenting the interfaces in the config file make them not managed anymore by network manager so it is normal (even if it is really confusing). Since most of raspberry pi uses are without user interfaces, it is not really a problem. Moreover when I install a user interface on my linux (gnome, etc...) the setup proposed by @michael-palmes seems to be not necessary.

[mmeendez8]

Have you found any solution to avoid the root use ?

[friedrith]

Unfortunately no, I think it is related to a a sudo configuration. node-wifi seems not to be the problem. Some users have experienced the same bug on standard linux distributions.

[jarrodbell]

Any solution for this issue requiring root?

[jarrodbell]

sudo chmod u+s,a-w /usr/bin/nmcli
This is working for my needs.

Taken from here:
https://unix.stackexchange.com/questions/364250/run-select-shell-commands-as-root-without-giving-the-user-sudo-permisions

[friedrith]

Ok thanks I will put this in the readme because it is very easy to apply. However, I think it would be safer to user sudoer file maybe.

[zimbora]

After doing something similar to what was discussed here, I noticed that when using "config.iface" parameter
the first line returned from the exec command was the own parameter and it was leading to a crash in 'for' loop because fields var will only have one position and the next code, consequently fails:

  ssid: fields[1].replace(/\&\&/g, ':'),
  bssid: fields[2].replace(/\&\&/g, ':'),
  mac: fields[2].replace(/\&\&/g, ':'), // for retrocompatibility with version 1.x
  mode: fields[3].replace(/\&\&/g, ':'),
  channel: parseInt(fields[4].replace(/\&\&/g, ':')),
  frequency: parseInt(fields[5].replace(/\&\&/g, ':')),
  //signal_level: networkUtils.dBFromQuality(fields[6].replace(/\&\&/g, ':')),
  security: fields[7].replace(/\&\&/g, ':') != '(none)' ? fields[7].replace(/\&\&/g, ':') : 'none',
  security_flags: {
    wpa:  fields[8].replace(/\&\&/g, ':'),
    rsn: fields[9].replace(/\&\&/g, ':'),
  }

This is very simple to solve. I solve that by changing the line:
if (lines[i] != '') {
to
if (lines[i] != '' && lines[i].includes(":")) {

I am using this lib in several platforms with success but raspbian took me 2 hours to set up nmcli and figure out this issue.
If you could commit it I would appreciate :)

My comment refers to
file: linux-scan.js
line: 25
and intends to fix a bug for raspbian os