On 2/25/19 3:00 AM, Ken Moffat via blfs-support wrote:
On Mon, Feb 25, 2019 at 12:37:36AM -0600, Bruce Dubbs via blfs-support wrote:
I don't use a laptop very often, but as I built a fresh 8.4 system there, I
thought I'd try network manager.
I can't get it to work. I first tried the applet, but then fell back to
trying nmcli and nmtui, None of that worked.
What does work us the BLFS method of using ifup which in turn uses
wpa_supplicant and dhcpcd.
Using nmcli, I can get:
# nmcli device wifi list
IN-USE SSID MODE CHAN RATE SIGNAL BARS SECURITY
blfs3 Infra 1 195 Mbit/s 100 ▂▄▆█ WPA2
blfs4 Infra 52 405 Mbit/s 99 ▂▄▆█ WPA1
extend24 Infra 1 195 Mbit/s 95 ▂▄▆█ WPA2
extend50 Infra 149 405 Mbit/s 64 ▂▄▆_ WPA2
DIRECT-P1-Fire Infra 149 130 Mbit/s 34 ▂▄__ WPA2
MySpectrumWiFi Infra 11 195 Mbit/s 24 ▂___ WPA2
MurphaCat Infra 3 260 Mbit/s 20 ▂___ WPA1 WPA2
Then I get failure:
# nmcli device wifi connect blfs3 password (redacted) ifname wifi0
Error: Connection activation failed: (5) IP configuration could not be
reserved (no available address, timeout, etc.).
Checking the log:
Feb 24 23:59:04 laptop84 NetworkManager[730]: <info> [1551074344.5205]
device (wifi0): supplicant interface state: 4-way handshake -> completed
Feb 24 23:59:04 laptop84 NetworkManager[730]: <info> [1551074344.5206]
device (wifi0): Activation: (wifi) Stage 2 of 5 (Device Configure)
successful. Connected to wireless network "blfs3"
Feb 24 23:59:04 laptop84 NetworkManager[730]: <info> [1551074344.5208]
device (wifi0): state change: config -> ip-config (reason 'none',
sys-iface-state: 'managed')
Feb 24 23:59:04 laptop84 NetworkManager[730]: <info> [1551074344.5213]
dhcp4 (wifi0): activation: beginning transaction (timeout in 45 seconds)
Feb 24 23:59:49 laptop84 NetworkManager[730]: <warn> [1551074389.7344]
dhcp4 (wifi0): request timed out
So it appears to be connecting, but not getting a dhcp ip address.
I did try to tell nm what to use for dhcp:
$ cat /etc/NetworkManager/conf.d/dhcp-client.conf
[main]
dhcp=dhcpcd
But that didn't seem to help.
Nothing useful, except to suggest you look at the Arch wiki.
I think our wireless knowledge is unfortunately lacking. On my new
laptop I couldn't get wpa_supplicant itself working (and for some
reason, the encrypted password was different from my 4½-year old
netbook system where I'm typing this : far too underpowered to
update things, so now only used to ssh locally and for a binary
firefox).
In the last two days I completely failed to get our wpa_supplicant
instructions working (with dhclient) on my new laptop. Connected,
but no offers. Trying wpa_cli failed, strace showed it couldn't
open the runtime directory (I forget if it defaulted to
/var/run/wpa_supplicant or /run/wpa_supplicant).
Then I looked at the Arch wiki, wondering if dbus was the problem
(according to that: no, NM -> dbus -> wpa_supplicant uses a
different approach). I followed their instructions for using
wpa_cli (create run directory, and very different config file) and
got wpa_cli working, then ran 'dhclient wlp2s0'. All as root which
is obviously not ideal longterm. This is on a binary install of
LFS/BLFS with a distro-derived kernel config (currently only 2900
modules ;-)
For the moment, that is good enough for me. I'll be revisiting
after I've installed some of 8.4 (currently in LFS chapter 5).
Meanwhile, I'm expecting that for the early packages after booting I
might have to do attended builds (wired ethernet - the connector
does not lock and is easily dislodged).
I'm glad wpa_supplicant is working well for you, and I hope you get
NM working. Good luck!
I did get it working. Sometimes sleeping on it causes a solution to
arise. As above I had set [main] dhcp=dhcpcd, but I was assuming that
nmcli or nmtui was using it. Wrong. When I restarted the NM daemon,
things started working,
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
