You are not logged in.

#1 2019-07-04 21:51:36

AndrewSmart
Member
Registered: 2019-06-10
Posts: 9

[SOLVED] USB Ralink wifi fails via network-manager, but works manually

Network-manager won't connect to my wifi with the Ralink USB, but I am able to use the Ralink USB if I stop network-manager and use wpa_supplicant manually. The stock wifi (ath5k) works with network-manager, but it's a poor signal so I don't use it.

wlp2s0 is stock Ath5k interface.
wlxe84e064cf189 is Ralink USB interface.

This is bl-Helium-4-i386.iso running in live+persistence on USB drive.

$ uname -a
Linux debian 4.9.0-8-686-pae #1 SMP Debian 4.9.130-2 (2018-10-27) i686 GNU/Linux
$ rfkill list
0: eeepc-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: phy1: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
$ lspci -k
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
        Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Memory Controller Hub
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)
        Subsystem: ASUSTeK Computer Inc. Mobile 945GSE Express Integrated Graphics Controller
        Kernel driver in use: i915
        Kernel modules: i915
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
        Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family High Definition Audio Controller
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
        Kernel driver in use: pcieport
        Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci_hcd
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci_hcd
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci_hcd
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB UHCI Controller
        Kernel driver in use: uhci_hcd
        Kernel modules: uhci_hcd
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. NM10/ICH7 Family USB2 EHCI Controller
        Kernel driver in use: ehci-pci
        Kernel modules: ehci_pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
        Subsystem: ASUSTeK Computer Inc. 82801GBM (ICH7-M) LPC Interface Bridge
        Kernel driver in use: lpc_ich
        Kernel modules: intel_rng, lpc_ich, leds_ss4200
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02)
        Subsystem: ASUSTeK Computer Inc. 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode]
        Kernel driver in use: ata_piix
        Kernel modules: ata_piix, ata_generic
01:00.0 Ethernet controller: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
        Subsystem: ASUSTeK Computer Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
        Kernel driver in use: ATL1E
        Kernel modules: atl1e
02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
        Subsystem: AzureWave AW-GE780 802.11bg Wireless Mini PCIe Card
        Kernel driver in use: ath5k
        Kernel modules: ath5k
$ lsusb
Bus 001 Device 004: ID 0457:0151 Silicon Integrated Systems Corp. Super Flash 1GB / GXT  64MB Flash Drive
Bus 001 Device 002: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 046d:c061 Logitech, Inc. RX1500 Laser Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Here is dmesg, I made line comments with #### to show when I reconfigured things with network-manager and finally manually connected:

$ sudo dmesg
....
[   42.231067] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[   42.268601] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
[   42.429098] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   42.430852] usbcore: registered new interface driver rt2800usb
[   42.591870] ath: EEPROM regdomain: 0x0
[   42.591877] ath: EEPROM indicates default country code should be used
[   42.591879] ath: doing EEPROM country->regdmn map search
[   42.591883] ath: country maps to regdmn code: 0x3a
[   42.591887] ath: Country alpha2 being used: US
[   42.591890] ath: Regpair used: 0x3a
[   42.592531] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   42.593828] ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[   42.666816] rt2800usb 1-4:1.0 wlxe84e064cf189: renamed from wlan0
[   42.745921] ath5k 0000:02:00.0 wlp2s0: renamed from wlan1
[   56.981385] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[   56.982340] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[   56.982415] ATL1E 0000:01:00.0 enp1s0: NIC Link is Up <100 Mbps Full Duplex>
[   56.982470] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[   57.007720] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[   57.008137] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   57.287015] rt2800usb 1-4:1.0: firmware: direct-loading firmware rt2870.bin
[   57.287037] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[   57.799523] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[   58.727131] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[   58.757960] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   58.768852] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   58.793399] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   62.846560] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   62.866099] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[   63.700477] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
######
###### I booted up and networkmanager automatically connected with wlp2s0 (not Ralink USB) because it is in network manager's confguration
######
[   63.844388] wlp2s0: authenticate with 24:f5:a2:07:d7:7f
[   63.848907] wlp2s0: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[   63.852960] wlp2s0: authenticated
[   63.856209] wlp2s0: associate with 24:f5:a2:07:d7:7f (try 1/3)
[   63.880773] wlp2s0: RX AssocResp from 24:f5:a2:07:d7:7f (capab=0x1431 status=0 aid=1)
[   63.880931] wlp2s0: associated
[   64.139816] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 24:f5:a2:07:d7:7f
[   64.142086] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  104.642222] fuse init (API version 7.26)
[  314.019690] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[  405.915237] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[  706.023397] perf: interrupt took too long (3161 > 3131), lowering kernel.perf_event_max_sample_rate to 63250
[  721.903476] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1037.899247] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1243.013880] perf: interrupt took too long (3991 > 3951), lowering kernel.perf_event_max_sample_rate to 50000
[ 1353.907319] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
######
###### Here I disconnect from wlp2s0 and keep trying to connect with wlxe84e064cf189 (Ralink USB)
###### Network manager icon in system bar has spinning symbol as it tries to connect, and eventually it gives up. I tried multiple times (many times in days past on other boots as well).
######
[ 1459.080513] wlp2s0: deauthenticating from 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1459.228954] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1482.691277] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1500.023841] perf: interrupt took too long (4995 > 4988), lowering kernel.perf_event_max_sample_rate to 40000
[ 1504.667792] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1504.733756] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1504.735801] wlxe84e064cf189: authenticated
[ 1511.396608] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1511.462340] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1511.469504] wlxe84e064cf189: authenticated
[ 1516.465375] wlxe84e064cf189: aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1518.565116] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1518.625791] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1518.732098] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1518.734796] wlxe84e064cf189: authenticated
[ 1526.196553] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1526.266212] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1526.372106] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1526.374412] wlxe84e064cf189: authenticated
[ 1528.217730] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1529.127591] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1570.483502] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1572.260414] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1572.340744] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1572.448144] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1572.450454] wlxe84e064cf189: authenticated
[ 1590.400975] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1590.478206] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1590.588090] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1590.590568] wlxe84e064cf189: authenticated
[ 1596.034923] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1596.939308] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1617.195393] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1618.909512] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1618.973487] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1619.084105] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1619.086284] wlxe84e064cf189: authenticated
[ 1635.517522] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1635.590253] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1635.696070] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1635.699879] wlxe84e064cf189: authenticated
[ 1640.591069] wlxe84e064cf189: aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1643.064874] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1644.003753] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1804.019964] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1810.060345] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1811.762615] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1811.841600] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1811.944085] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1811.946168] wlxe84e064cf189: authenticated
[ 1828.397124] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 1828.458097] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 1828.564068] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 1828.566096] wlxe84e064cf189: authenticated
[ 1835.077957] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1836.009388] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 1844.025657] perf: interrupt took too long (6259 > 6243), lowering kernel.perf_event_max_sample_rate to 31750
######
###### Here I stopped network manager and connected manually
######
[ 2015.343249] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[ 2016.961567] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[ 2017.033801] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[ 2017.140099] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[ 2017.143469] wlxe84e064cf189: authenticated
[ 2017.144303] wlxe84e064cf189: associate with 24:f5:a2:07:d7:7f (try 1/3)
[ 2017.156343] wlxe84e064cf189: RX AssocResp from 24:f5:a2:07:d7:7f (capab=0x1431 status=0 aid=1)
[ 2017.163737] wlxe84e064cf189: associated
[ 2017.187655] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe84e064cf189: link becomes ready
[ 2017.243723] wlxe84e064cf189: Limiting TX power to 30 (30 - 0) dBm as advertised by 24:f5:a2:07:d7:7f

Here are steps to get it working manually:

$ sudo /etc/init.d/network-manager stop
$ sudo wpa_supplicant -iwlxe84e064cf189 -Dnl80211 -c/etc/wpa_supplicant/panelistssid.conf
Successfully initialized wpa_supplicant
wlxe84e064cf189: SME: Trying to authenticate with 24:f5:a2:07:d7:7f (SSID='panelist-ssid3' freq=2452 MHz)
wlxe84e064cf189: Trying to associate with 24:f5:a2:07:d7:7f (SSID='panelist-ssid3' freq=2452 MHz)
wlxe84e064cf189: Associated with 24:f5:a2:07:d7:7f
wlxe84e064cf189: WPA: Key negotiation completed with 24:f5:a2:07:d7:7f [PTK=CCMP GTK=CCMP]
wlxe84e064cf189: CTRL-EVENT-CONNECTED - Connection to 24:f5:a2:07:d7:7f completed [id=0 id_str=]
wlxe84e064cf189: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
wlxe84e064cf189: WPA: Group rekeying completed with 24:f5:a2:07:d7:7f [GTK=CCMP]
$ sudo dhclient wlxe84e064cf189
$ ip route
default via 10.106.25.108 dev wlxe84e064cf189
default via 10.106.25.108 dev enp1s0 proto static metric 100
10.106.25.0/24 dev wlxe84e064cf189 proto kernel scope link src 10.106.25.122
10.106.25.108 dev enp1s0 proto static scope link metric 100
192.168.2.0/24 dev enp1s0 proto kernel scope link src 192.168.2.1 metric 100
$ sudo ip route del 10.106.25.108 metric 100
$ ip route
default via 10.106.25.108 dev wlxe84e064cf189
default via 10.106.25.108 dev enp1s0 proto static metric 100
10.106.25.0/24 dev wlxe84e064cf189 proto kernel scope link src 10.106.25.122
192.168.2.0/24 dev enp1s0 proto kernel scope link src 192.168.2.1 metric 100
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=2.87 ms
^C
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.876/2.876/2.876/0.000 ms

Present connection:

$ iw dev
phy#0
	Interface wlp2s0
		ifindex 4
		wdev 0x1
		addr 00:22:43:30:14:37
		type managed
		txpower 30.00 dBm
phy#1
	Interface wlxe84e064cf189
		ifindex 3
		wdev 0x100000001
		addr e8:4e:06:4c:f1:89
		type managed
		channel 9 (2452 MHz), width: 20 MHz (no HT), center1: 2452 MHz
		txpower 30.00 dBm

So I just do wpa_supplicant, dhclient, and have to fix the routing table a bit for my setup, I don't think the routing thing is the issue with network-manager. In network-manager connection properties I do set IPv6 to ignore.

I don't know where the issue is, I guess hidden network-manager configuration or bug? The problem has existed in a much older BunsenLabs release network-manager on this same hardware as well. It is one reason I updated to the newest BunsenLabs, I'd hoped that network-manager would work with this Ralink USB.

EDIT: Any other logs to look at or diagnosis suggestions much appreciated. So strange that wpa_supplicant works manually yet network-manager can't succeed doing that. I will try the SUPPLICANT logging domain mentioned in networkmanager.conf.

Last edited by AndrewSmart (2019-07-10 21:01:24)

Offline

#2 2019-07-05 04:03:10

AndrewSmart
Member
Registered: 2019-06-10
Posts: 9

Re: [SOLVED] USB Ralink wifi fails via network-manager, but works manually

Ok, I think I found answer after improving network-manager logging and then looking in dmesg/journalctl:

#/etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[logging]
level=DEBUG
domains=ALL

New line with the increased verbosity:
aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)

$ sudo dmesg
[43253.960180] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[43254.041652] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[43254.052828] wlxe84e064cf189: authenticated
[43260.709750] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[43260.777724] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[43260.884075] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 2/3)
[43260.888677] wlxe84e064cf189: authenticated
[43265.780090] wlxe84e064cf189: aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
[43267.867462] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[43267.949532] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[43267.952726] wlxe84e064cf189: authenticated
[43272.954092] wlxe84e064cf189: aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
[43275.535423] wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
[43275.597603] wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
[43275.599595] wlxe84e064cf189: authenticated
[43278.030815] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
[43278.923541] IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
$ sudo journalctl
Jul 04 21:00:25 debian wpa_supplicant[1015]: wlxe84e064cf189: SME: Trying to authenticate with 24:f5:a2:07:d7:7f (SSID='panelist-ssid3' freq=2452 MHz)
Jul 04 21:00:25 debian kernel: wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
Jul 04 21:00:25 debian kernel: wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
Jul 04 21:00:25 debian kernel: wlxe84e064cf189: authenticated
Jul 04 21:00:29 debian sudo[8601]:     user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/bin/dmesg
Jul 04 21:00:29 debian sudo[8601]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 04 21:00:29 debian sudo[8601]: pam_unix(sudo:session): session closed for user root
Jul 04 21:00:30 debian kernel: wlxe84e064cf189: aborting authentication with 24:f5:a2:07:d7:7f by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 04 21:00:32 debian sudo[8606]:     user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/bin/dmesg
Jul 04 21:00:32 debian sudo[8606]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 04 21:00:33 debian sudo[8606]: pam_unix(sudo:session): session closed for user root
Jul 04 21:00:33 debian kernel: wlxe84e064cf189: authenticate with 24:f5:a2:07:d7:7f
Jul 04 21:00:33 debian wpa_supplicant[1015]: wlxe84e064cf189: SME: Trying to authenticate with 24:f5:a2:07:d7:7f (SSID='panelist-ssid3' freq=2452 MHz)
Jul 04 21:00:33 debian kernel: wlxe84e064cf189: send auth to 24:f5:a2:07:d7:7f (try 1/3)
Jul 04 21:00:33 debian kernel: wlxe84e064cf189: authenticated
Jul 04 21:00:35 debian wpa_supplicant[1015]: wlxe84e064cf189: CTRL-EVENT-DISCONNECTED bssid=24:f5:a2:07:d7:7f reason=3 locally_generated=1
Jul 04 21:00:35 debian NetworkManager[8518]: <warn>  [1562295635.6170] sup-iface[0x1e45528,wlxe84e064cf189]: connection disconnected (reason -3)
Jul 04 21:00:35 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready
Jul 04 21:00:36 debian dhclient[1924]: receive_packet failed on wlxe84e064cf189: Network is down
Jul 04 21:00:36 debian kernel: IPv6: ADDRCONF(NETDEV_UP): wlxe84e064cf189: link is not ready

Issue seems to be Network-Manager can't handle the longer interface names, or something else I guess, many fixes suggested.

EDIT: Solved with this answer, interface names now appear as wlan0 and wlan1 instead of wlxe84e064cf189 and wlp2s0. Now network-manager works fine.

Last edited by AndrewSmart (2019-07-10 20:59:54)

Offline

#3 2019-07-05 16:16:20

DeepDayze
Member
From: In Linux Land
Registered: 2017-05-28
Posts: 740

Re: [SOLVED] USB Ralink wifi fails via network-manager, but works manually

Most USB wifi dongle firmwares seem to only accept names no longer than 12 characters and yours has 15.


Real Men Use Linux

Offline

#4 2019-07-22 18:00:00

brogild
Member
Registered: 2019-07-04
Posts: 7

Re: [SOLVED] USB Ralink wifi fails via network-manager, but works manually

I was having exactly the same problem, I could connect wirelessly during install, but at the 'desktop' (and in 'live') Networkmanager wouldn't connect, so I could see it wasn't a driver problem.
This might be the same problem as outlined in SunTzuTech's thread.

I used the fix regarding long interface names in Andrew's post above, and it solved the problem, but then I discovered there is a much simpler solution that needs no symbolic links to be created. Simply add the following to networkmanager.conf, and restart the network manager service. Works fine after that.:

[device]
wifi.scan-rand-mac-address=no


I can't claim any clever detective work here, I just compared /etc/NetworkManager in a Lubuntu installation with the bunsenlabs one, and noticed the difference. I'm too lazy (now that it's fixed) to look into exactly why this works, but someone else may be interested.

Last edited by brogild (2019-07-22 18:06:53)

Offline

#5 2019-07-23 17:49:52

AndrewSmart
Member
Registered: 2019-06-10
Posts: 9

Re: [SOLVED] USB Ralink wifi fails via network-manager, but works manually

brogild wrote:

I used the fix regarding long interface names in Andrew's post above, and it solved the problem, but then I discovered there is a much simpler solution that needs no symbolic links to be created. Simply add the following to networkmanager.conf, and restart the network manager service. Works fine after that.:

[device]
wifi.scan-rand-mac-address=no


I just compared /etc/NetworkManager in a Lubuntu installation with the bunsenlabs one, and noticed the difference.

Thank you that works for me too. Better than the fix I had with the wlan0/wlan1 renaming so I'll use your fix.

The reason I think yours works better is because each boot my Ralink USB is randomly labeled with either wlan0 or wlan1, so I have to type 'iw dev' to figure out which is which then run some other commands with the right interface name. Now it is always wlxe84e064cf189 again instead of random wlan0/wlan1.

Offline

Board footer

Powered by FluxBB