On Fri, 12 Jul 2019 06:22:16 -0000 (UTC) Bert Riding <rerid...@xmission.com> wrote:
> Yes, I'm sorry I didn't mention that my device name was merely an Didn't have to. I understood. It's just wlan0 USED to be the default 1st wireless device, the last time I had to do this with another system about 15 years ago, and I used it as a first test to bring UP the device before reading the instructions. It failed, of course. Laziness. > example. I wonder if "ip link show" or "ls -l /sys/class/net" or the > obsolete "ifconfig a" give the same device name. Udevadm might > help, too. "udevadm info -e | grep .wl" for instance. The name you are > using is the name using the MAC address, which is the last match as udev > lists the names, and won't be used if udev finds another name first. See > https://major.io/2015/08/21/understanding-systemds-predictable-network-device-names/ > Here's what that all shows on my system (wireless parts only). Wireless USB dongle plugged in, but otherwise dormant. ip a 3: wlx00e04c2a23c4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:e0:4c:2a:23:c4 brd ff:ff:ff:ff:ff:ff ls -l /sys/class/net lrwxrwxrwx 1 root root 0 Jul 12 07:48 wlx00e04c2a23c4 -> ../../devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 /sbin/iw dev phy#0 Interface wlx00e04c2a23c4 ifindex 3 wdev 0x1 addr 00:e0:4c:2a:23:c4 type managed txpower 0.00 dBm udevadm info -e | grep .wl E: RFKILL_TYPE=wlan P: /devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3:1.0/net/wlx00e04c2a23c4 E: DEVTYPE=wlan E: ID_NET_NAME=wlp0s18f2u3 E: ID_NET_NAME_MAC=wlx00e04c2a23c4 E: ID_NET_NAME_PATH=wlp0s18f2u3 E: INTERFACE=wlx00e04c2a23c4 E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/wlx00e04c2a23c4 /sys/subsystem/net/devices/wlx00e04c2a23c4 As you can see, the wlx name is the only one that shows as far as I can find. ifconfig is not installed. FYI: systemd is not running on my system, except for udev. When I clean installed, I switched to sysvinit as the init as soon as I could. > "nl80211" is the correct name of the driver. I apologize for the error. An error, yes, but one I made a couple times myself during my trials to get wireless working. Thanks for the response. B > On Fri, 12 Jul 2019 04:30:02 +0200, Patrick Bartek wrote: > > > On Thu, 11 Jul 2019 21:02:44 -0000 (UTC) > > Bert Riding <rerid...@xmission.com> wrote: > > > >> You could try using the actual device for the -i option (interface)...like > >> wlan0 or, in the new notation wlp3s0, and use nl80122 as the -D > >> option (driver). > > > > iw dev or ip a report the device name to be wlx00e04c2a23c4. This > > designation never changes regardless of reboots or which USB port I > > plug the wireless device into. I examined the output of dmesg and noted > > that udev had reassigned wlan0 to this new name. Don't know why. And it > > does work when scanning or finding device info or bringing device up or > > down. But I initially tried wlan0 anyway. Got "No such > > device . . ." etc. > > > > I tried using -D nl80211 (did you transpose digits?) and not using it. > > wpa_supplicant failed with the same error noted below. Also, tried > > wext. Ditto. > > > > Haven't tried wlp3s0, but haven't found ANY reference to that name > > on the system regardless of which command I use to show network devices. > > > > Thanks for your input. > > > > B > > > >> On Thu, 11 Jul 2019 02:10:02 +0200, Patrick Bartek wrote: > >> > >> > A problem when trying to associate with a wireless router > >> > (WPA2). Get the following error when manually executing: > >> > > >> > wpa_supplicant -i wlx<hexnumber> > >> > -c /etc/wpa_supplicant/wpa_supplicant.conf > >> > > >> > Could not read interface wlx<hexnumber> flags: No such device > >> > nl80211: Driver does not support authentication/association or connect > >> > commands > >> > nl80122: [can't read my own writing on this one] > >> > > >> > Wpa_supplicant fails whether I use the -B (background) switch or not. > >> > > >> > Here's the wpa_supplicant.conf file: > >> > > >> > > >> > ctrl_interface=DIR=/run/wpa_supplicant > >> > update_config=1 > >> > > >> > network={ > >> > ssid="ROUTERNAME" > >> > # scan_ssid=1 > >> > # key_mgmt=WPA-PSK > >> > # psk="SECRETPASSPHRASE" > >> > psk=longhexnumber > >> > } > >> > > >> > I've tried with and without the commented lines. Same results. > >> > > >> > Here's the wifi portion of my /etc/network/interfaces > >> > > >> > allow-hotplug wlx<hexnumber> > >> > iface wlx<hexnumber> inet dhcp > >> > wpa-ssid ROUTERNAME > >> > # wpa-key-mgmt WPA-PSK > >> > # wpa-group TKIP CCMP > >> > # wpa-psk SECRETPASSPHRASE > >> > wpa-psk longhexnumber > >> > > >> > The wireless is a Rosewill USB RNX-N180UBEv3. It is UP after boot and > >> > scanning wifi routers works. System tries to associate to router at > >> > boot, but fails. Correct kernel module (rtl8192eu) is loaded. > >> > > >> > Anyone got an idea of why wpa_supplicant is failing? And how to fix > >> > it? All commands issued as root. > >> > > >> > FYI: I have an atypical Stretch install: No desktop environment, > >> > window manager only; sysvinit, but systemd libraries still installed. > >> > Boots to terminal, login there, then startx, if I want a GUI. Wifi UP > >> > at terminal and scanning works. This is not a laptop. Wired ethernet > >> > works and has always (12 years) worked. > >> > > >> > Thanks. > >> > > >> > B > >> >
