On Sat, 2020-06-27 at 13:38 -0700, Patrick Mansfield via networkmanager-list wrote: > Hi - > > I had my wifi working as an AP at one point, but had to alter things > to get my wired > network working (had a bad PCI dual port card and replaced it). > > Running up to date Fedora 31, kernel 5.6.19-200.fc31.x86_64. > > # nmcli -v > nmcli tool, version 1.20.12-1.fc31 > > I completely removed and added back the interface using nmcli. > > Now when I try to bring it up, I get: > > # nmcli con up nm_wifi0 > Error: Connection activation failed: No suitable device found for > this connection (device lan0 not available because profile is not > compatible with device (mismatching interface name)).
Hi, NetworkManager didn't find *any* device that was suitable to activate the profile. It somewhat arbitrarily said that for example "device lan0 was not suitable due to reasons"). It should be smarter to recogonize that device wlan0 would be the better one to report in the error message. You'd get a better message if you do: nmcli con up my_wifi0 ifname wlan0 to tell NetworkManager to activate the profile on that device. But that still wouldn't succeed, it would just give a more suitable error message. What does `nmcli device` say? If the device TYPE is not "wifi", you didn't install the Wi-Fi plugin (install it and restart NetworkManager). If the device of type wifi but in state "unavailable", probably something is wrong with wpa_supplicant. Check the logs. Consider enabling level=TRACE logging (and restart NetworkManager to get the relevant messages picture). See https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 for hints about logging. best, Thomas > > I don't see how my lan0 is in any way connected to the wifi > networking. > > I have: > > # ifconfig wifi0 > wifi0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether d8:3b:bf:5a:16:53 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 104 bytes 17426 (17.0 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > I created it using the following: > > nmcli con add type wifi ifname wifi0 con-name nm_wifi0 autoconnect > yes ssid alt_umbrella > nmcli con modify nm_wifi0 802-11-wireless.mode ap 802-11- > wireless.band bg ipv4.method share d > nmcli con modify nm_wifi0 wifi-sec.key-mgmt wpa-psk > nmcli con modify nm_wifi0 wifi-sec.psk "yeahright" > > lan0 is an ethernet connection for my internal lan: > > # ifconfig lan0 > lan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 192.168.1.1 netmask 255.255.255.0 broadcast > 192.168.1.255 > ether 80:61:5f:05:0c:8e txqueuelen 1000 (Ethernet) > RX packets 34093347 bytes 48957495346 (45.5 GiB) > RX errors 2 dropped 0 overruns 0 frame 1 > TX packets 4145306 bytes 3332686109 (3.1 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device memory 0xf6820000-f683ffff > > I'm re-naming interfaces using .link files: > > # ls /etc/systemd/network/*link > /etc/systemd/network/10-lan0.link /etc/systemd/network/10-wan0.link > /etc/systemd/network/10-lan1.link /etc/systemd/network/10-wifi0.link > > Any ideas? > > Let me know if you want more details etc. > > Thanks :) >
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
