CanonicalLtd / UCWifiConnect

The code of this project has been moved to https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/wifi-connect
GNU General Public License v3.0
2 stars 2 forks source link

Got "Device is not connected to external wifi AP" message when I'm connected #10

Closed rmescandon closed 7 years ago

rmescandon commented 7 years ago

Testing in Raspberry PI with snaps wifi-connect, wifi-ap and network-manager installed

knitzsche commented 7 years ago

puzzling that netman reports wlan0 is not managed and yet you apparently can ping a web name. in my case, if my device is connected to external wifi and I then set the wlan0 interface to NOT be managed by netman, it drops from the external wifi:

knitzsche@localhost:~$ nmcli d DEVICE TYPE STATE CONNECTION
wlan0 wifi connected astro_garden_2 20 eth0 ethernet unmanaged --
sit0 iptunnel unmanaged --
lo loopback unmanaged --
knitzsche@localhost:~$ nmcli d set wlan0 managed n HERE the connection drops and ssh fails. in ssh over ethernet: knitzsche@localhost:~$ nmcli d DEVICE TYPE STATE CONNECTION eth0 ethernet unmanaged --
sit0 iptunnel unmanaged --
lo loopback unmanaged --
wlan0 wifi unmanaged --
knitzsche@localhost:~$ wifi-connect.netman -check-connected-wifi Device is not connected to external wifi AP

Is it possible that you connected to the external AP through some means that does not involve network-manager? perhaps wlan0 was never managed by netman?

knitzsche commented 7 years ago

(strange strike-through font in previous comment...)

rmescandon commented 7 years ago

Forget. My bad. Wifi was set using wpa_suplicant and thus not managed by nmcli and even if tried to manage it using nmcli, nothing happened.