On Sat, 21 May 2016 21:02:15 -0800 Britton Kerin <britton.ke...@gmail.com> wrote:
> somehow network-manager makes it work. But I've had it with gnome, > and none of the command line tools or references I've found work. > That includes /etc/network/interfaces, > direct use of ifconfig,iw,ip,rfkill,wpa_supplicant,dhclient, and > wicd-client (though it's not really what I want. > > Is this even still possible or have the systemd assholes decided we > shouldn't be doing it? > > I believe the problem with the traditional wpa_supplicatn approach is > related to syslog entries like > these: > > May 21 17:00:06 debian kernel: iwlwifi 0000:02:00.0: can't access the > RSA semaphore it is write protected > > But as I say somehow network-manager makes it work. > > I just got a new laptop after 10 years, I didn't realize how bad the > situation has become with systemd udev gnome etc. > Datum: Network Manager GUI (network-manager-gnome plus any necessary plugins, network-manager-XXXX-gnome) works fine under other DEs, I use it with Xfce and have previously done with LXDE. By necessity, it pulls in various bits of gnome, but disc space is cheap. It used to be known as Notwork Manager, but seems to have been useful for some years now. If you use a more complex OpenVPN configuration than the default, NM probably can't handle it, but it is fine with the default, and OK with wifi and mobile dongles. -- Joe
