USB adapter doesn't connect with NetworkManager.

[Yahvek]

Hi, I have an issue with my AWUS036NHA USB adapter on Debian 9 installed in a Lenovo t450s, the system recognizes the USB adapter and can see the wifi networks that it scan, but it doesn’t possible to connect to any of them from the KDE or Gnome network manager.

When I was installing the system I could connect with the adapter to my networks, I used Debian 9 non-free firmware version. But now with the network manager from KDE or Gnome, it doesn't possible connect.

I can connect with wpa_supplicant directly from the console using the settings remarked in this web page: https://shapeshed.com/linux-wifi/ and setting the driver to nl80211 or wext. If I don’t set this driver in the wpa_supplicant -D parameter I cannot connect anyway, basically doing:

Code: Select all

wpa_supplicant -i wlx00c0ca9233e3 -c /etc/wpa_supplicant/wpa_supplicant.conf -D nl80211

Code: Select all

wpa_cli

But even using this last method, setting nl80211 or wext drivers, the adapter disconnect from the network around 10 minutes later and is unable to connect itself.

I found this temporary solution but at this stage, I don’t know why works and it is not a comfortable alternative for me because I cannot connect to the desired network on the fly later the system is started:

Code: Select all

/etc/network/interfaces:
auto wlx00c0ca9233e3
iface wlx00c0ca9233e3 inet dhcp
wpa-driver nl80211
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Code: Select all

/etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/run/wpa_supplicant
update_config=1
 network={
 ssid="10"
 psk="password"
}

To connect I do:

Code: Select all

dhclient -r
dhclient wlx00c0ca9233e3

Now the network remains connected but as I said this method is not comfortable. I need to connect from the network manager especially from KDE, as a normal final user.

I researched how I can set the network manager using the nl80211 driver to be connected, I “think” this is the issue, but until now I don’t find the way to do it.
I need help, how can I found what is the exact conflict?

[orythem27]

but it doesn’t possible to connect to any of them from the KDE or Gnome network manager
auto wlx00c0ca9233e3

Describe as detailed as possible. How is it not possible? What did you see?
You probably would like to try the workarounds in these threads first:
http://forums.debian.net/viewtopic.php?f=7&t=133597
http://forums.debian.net/viewtopic.php?f=5&t=133495
http://forums.debian.net/viewtopic.php?f=7&t=133518
http://forums.debian.net/viewtopic.php?f=5&t=133809

Hi, I have an issue with my AWUS036NHA USB adapter on Debian 9

Plug in the USB adapter and post the outputs of the following commands

Code: Select all

uname -a
lsusb
lsusb -t

how can I found what is the exact conflict?

Watch the syslog(journalctl) carefully until it disconnects. Post the full log before and after disconnection.

[Yahvek]

Thank you, I want to say with:

but it doesn’t possible to connect to any of them from the KDE or Gnome network manager

That the adapter cannot connect from the GUI network widget of KDE for example:






With this solution, the link that you posted here: http://forums.debian.net/viewtopic.php?f=7&t=133597 I can connect from the GUI network widget of KDE That was a good move.

But is interesting even important to use MAC Address Spoofing and take advantage of this feature of NetworkManager. I tried to change the mac manually with the same widget which has this option but when I did it the adapter could not connect again, I used Macchanger and could not connect either.

Do you have some idea how can I involve into the system to allow to works fine MAC Address Spoofing feature included in NetworkManager?

These are the outputs of the corresponding seggested commands:

Code: Select all

uname -a
Linux x 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) x86_64 GNU/Linux

Code: Select all

lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 002 Device 008: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: Select all

lsusb -t
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 2: Dev 8, If 0, Class=Vendor Specific Class, Driver=ath9k_htc, 480M
    |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M