Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  [solved]network manager  (Read 2923 times)

Offline jyp

  • User
  • Posts: 118
[solved]network manager
« on: 2017/01/28, 20:21:51 »
I am haapily running siduction paint-it-black (fully upgraded) on my thinkpad-t460.
But a little annoying item: there is an icon in the system tray with reddish contour that is labelled _Nertworks_.
I guessed that it is related to plasma-nm.

I tried to configure it to at least store the usual wifi networks that I use but it does not work at all; it accept the ssid and the associated password but does not offer to
connect to any of them. I have to use _ceni_ everytime I move around and change network; a little bit annoying. Even my little raspbian system is detecting the wifi networks!!

I search a lot about that and found nothing valuable.

Any clue?

Here are some info about my system
Code: [Select]
===============================
System:    Host: delta Kernel: 4.9.5-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.8.4
           Distro: siduction 15.1.0 Paint It Black - kde - (201601162135)
Network:   Card-1: Intel Ethernet Connection I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: c8:5b:76:91:49:76
           Card-2: Intel Wireless 8260 driver: iwlwifi
           IF: wlp4s0 state: up mac: f0:d5:bf:1d:ad:8a
           
======================
jy@delta#  lshw -C Network
  *-network                 
       description: Wireless interface
       product: Wireless 8260
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: wlp4s0
       version: 3a
       serial: f0:d5:bf:1d:ad:8a
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.9.3-towo.1-siduction-amd64
       firmware=22.361476.0 ip=192.168.1.100 latency=0 link=yes multicast=yes wireless=IEEE 802.11

=====================================
jy@delta# systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2017-01-27 15:53:11 EST; 20min ago
     Docs: man:NetworkManager(
 Main PID: 628 (NetworkManager)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─628 /usr/sbin/NetworkManager --no-daemon

Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6088] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6098] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6101] (wlp4s0): using nl80211 for WiFi device control
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6103] device (wlp4s0): driver supports Access Point (AP) mode
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6110] manager: (wlp4s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6224] manager: startup complete
Jan 27 15:53:11 delta NetworkManager[628]: <info>  [1485550391.6225] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 27 15:53:12 delta NetworkManager[628]: <info>  [1485550392.3821] bluez: use BlueZ version 5
Jan 27 15:53:12 delta NetworkManager[628]: <info>  [1485550392.3838] ModemManager available in the bus
Jan 27 15:53:12 delta NetworkManager[628]: <info>  [1485550392.3885] supplicant: wpa_supplicant running

===============
jy@delta$ groups
jy lp dialout cdrom floppy audio dip video plugdev users systemd-journal lpadmin netdev scanner

=============
jy@delta$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether c8:5b:76:91:49:76 brd ff:ff:ff:ff:ff:ff
3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether f0:d5:bf:1d:ad:8a brd ff:ff:ff:ff:ff:ff
« Last Edit: 2017/01/30, 08:23:21 by devil »

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.842
Re: network manager
« Reply #1 on: 2017/01/28, 20:45:04 »
Did you find out the name of that widget. It is not default with siduction kde. Tne current Version of the standard plasma-nm is 5.8.4. I it is fully configurable and does not have a reddish contour. Maybe you want to add a screenshot of what you have.

Offline jyp

  • User
  • Posts: 118
Re: network manager
« Reply #2 on: 2017/01/28, 21:12:07 »
Hi devil

The plasma-nm version is 5.8.4-1
The name of the widget is _Networks_ and from it we can open a window called _connection editor_
I do not remember adding this widget in the system tray myself... but maybe I did ;-( . This widget is available in the _add widgets_ in the panel configuration window.

I don't mind removing it as it is useless but how to see available wifi connections without using _ceni_?

The widget icon is the first, second row on the attached screenshot

Thanks

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.842
Re: network manager
« Reply #3 on: 2017/01/28, 21:35:09 »
Oh, I see. That is plasma-nm, but in a not working state. You need to right-click  and configure it to your liking. Let us know what kind of problems you run into, if any.


p.s.: before I forget: NetworkManager and the treaditional /etc/network/interfaces, that Ceni sets up, do not go together.  So to be able to use nm, after configuring the system with Ceni or manualy,  you need to delete all but
Code: [Select]
# The loopback interface
auto lo
iface lo inet loopback
from /e/n/i
« Last Edit: 2017/01/28, 21:39:12 by devil »

Offline jyp

  • User
  • Posts: 118
Re: network manager
« Reply #4 on: 2017/01/29, 16:55:47 »
Does it mean that I have to use either _ceni_ or _plasma-nm_?
Will configuring /etc/network/interfaces as you indicated make _ceni_ unusable?

thanks

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.842
Re: network manager
« Reply #5 on: 2017/01/29, 20:39:28 »
 The name Ceni stands for configure /etc/network/interfaces and so most of what it does is set up that file. The stub I indicated as needed above is just for the loopback device aka local host. The rest will be handled by NM. And yes, as long as you use NM, Ceni cannot be used. If later you want to return to Ceni, it will prompt you to get rid of NM.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.842
Re: network manager
« Reply #6 on: 2017/01/29, 20:52:58 »
Just learned that NM got even more picky over time. You need to
Code: [Select]
rm -rf /etc/network to activate NM.

Offline jyp

  • User
  • Posts: 118
Re: [closed] network manager
« Reply #7 on: 2017/01/30, 01:14:31 »
Thank you devil

I will think about that a bit: ceni is a good tool after all.
Mainly I was just wondering why that icon (plasma-nm widget) was inactive in spite of my effort to configure the network through it.

I mark that thread as [closed]

ps
You and your team deserved a donation; coming soon...  from a poor man ;-))