Network manager cli only?

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Network manager cli only?

Post#1 by nanZor » 07 Nov 2021, 23:04

I know this is in a faq somewhere, but I can't find it. Not sure if this is an actual bug, or more likely me.

It seems that in the RC3 I'm currently running, network manager gui will automatically run with a wired system no problem. It will also see all the access points I also use around me. Not sure if this is rc3 specific or not.

Code: Select all

guest@porteus:~$ uname -a
Linux porteus.example.net 5.12.14-porteus #1 SMP Sat Jul 3 13:15:49 MSK 2021 i686 Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GenuineIntel GNU/Linux

But when I try to access one, I get the notification that "The network connecton has been disconnected" even before I get a chance to enter the passwords. I can see it restart, and then rescan all over again. Wired works fine all the time. Graphical or always-fresh, same result.

HOWEVER, if I use network-manager from the commandline using nmcli commands, wifi works fine. For reference, this was a good one:

https://wiki.archlinux.org/title/NetworkManager


This has to be a major pebcak right? Someone will spot what I'm doing wrong...
That's a UNIX book - cool. -Garth

User avatar
M. Eerie
Moderator
Moderator
Posts: 620
Joined: 31 Aug 2017, 21:18
Distribution: Nemesis Xfce/MATE x64

Network manager cli only?

Post#2 by M. Eerie » 07 Nov 2021, 23:31

nmtui ?
> Does not compute_ 🖖

https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584

nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Network manager cli only?

Post#3 by nanZor » 07 Nov 2021, 23:54

Hi M.! Nothing to see here kids. Total PEBCAK as I suspected.

Instead of being prompted for credentials upon clicking on an available access point, one simply has to EDIT the desired connection FIRST with your password credentials, (and any other desired features like auto-connect) and save it. That means right-clicking on the NM icon and choosing edit connections as your first step if you are not using wired ethernet.

Once that's done, it works just fine. In a home environment, I also tend to set IPV6 for "Ignore" as seen on another handy tip here in the forum.

Cool - it keeps my younger kid-brother from walking by and trying to change my connection to a neighbor's wireless printer. At least until he learns a little bit of bash. :)

Whew. I knew I had forgotten something simple.
That's a UNIX book - cool. -Garth

Jack
Contributor
Contributor
Posts: 1857
Joined: 09 Aug 2013, 14:25
Distribution: Porteus and Nemesis
Location: USA

Network manager cli only?

Post#4 by Jack » 08 Nov 2021, 02:12

nanZor wrote:
07 Nov 2021, 23:54
Hi M.! Nothing to see here kids. Total PEBCAK as I suspected.

Instead of being prompted for credentials upon clicking on an available access point, one simply has to EDIT the desired connection FIRST with your password credentials
If I think what you wrote here then you need to find another WiFi card to get it to work.

I had the same problem as soon as change the WiFi card it work. Porteus should see your connection when you type nmtui all you will need to do is enter your password.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

nanZor
Shogun
Shogun
Posts: 381
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.01 x86-64 LXQT

Network manager cli only?

Post#5 by nanZor » 08 Nov 2021, 22:37

It all works ok now, I never really needed the commandline nmcli / nmtui after all. I tried other known working dongles too.

I just had to adjust a little. When I click on the toolbar nm gui, I see a list of available access points.

But instead of clicking immediately on the access point, I right click on the nm gui in the toolbar instead, edit the desired access point connection with my credentials. And any other options I want for it.

Bingo. Works fine. Total control.

Actually it was the nmcli that tipped me off "What am I doing different here vs using toolbar gui control?"

Aha, I was PRE-configuring my password to the access point I wanted to connect to. Editing my connection first, rather than expecting to be prompted to do so.

If it's not a bug, I looked at it as kind of low-level obscurity feature! :)
That's a UNIX book - cool. -Garth

Post Reply