[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wireless without network-manager... is it still possible?

Maybe nmcli is available for debian I don't know and I don't know what results you'll get using it either. Also debian is still using iwconfig which was supposed to have been replaced by iw a while ago. Wireless-tools is also missing and you're not the only one that can't get a wireless configuration up and talking with xfinity with provided command line tools either. That's happening over here.
Now, if you get archlinux or talkingarchlinux, one of the packages you can install is netctl and I have got my wifi adapter usb up using command line tools only on talkingarchlinux and that is far easier than fighting with debian. The thing you need to understand though is archlinux is a rolling release system.d system though. Debian could really do with a workable version of netctl which allows use of wifi-menu -o to obfuscate wifi credentials and then netctl list to find the access point string then netctl enable access point string then systemctl enable accesspoint.service string and your wifi is up and running. 

On Sat, 21 May 2016, Britton Kerin wrote:


Date: Sun, 22 May 2016 01:02:15
From: Britton Kerin <britton.kerin@gmail.com>
To: debian-user@lists.debian.org
Subject: wireless without network-manager... is it still possible?
Resent-Date: Sun, 22 May 2016 05:02:30 +0000 (UTC)
Resent-From: debian-user@lists.debian.org

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.

Britton




--
Reply to: