[SOLVED] Help - how can I remove Network Manager safely?

Sector11 · 2019-07-06 21:23:52

Old Subject: Stupid move - lost net connect.
New Subject: Help - how can I remove Network Manager safely?

Question now at Post: # 11

========================

In my other install I have NO network manager.

So in a stupid move I changed: /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug enp9s0
#iface enp9s0 inet dhcp

which matches what I have on my backup system (now in it) that has no network-manager

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

and then deleted network-manager*

 06 Jul 19 @ 17:42:41 ~
   $ aremv network-manager*
[sudo] password for sector11:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'network-manager-pptp' for glob 'network-manager*'
Note, selecting 'network-manager-iodine' for glob 'network-manager*'
Note, selecting 'network-manager-iodine-gnome' for glob 'network-manager*'
Note, selecting 'network-manager-strongswan' for glob 'network-manager*'
Note, selecting 'network-manager-openconnect-gnome' for glob 'network-manager*'
Note, selecting 'network-manager-ssh' for glob 'network-manager*'
Note, selecting 'network-manager-vpnc' for glob 'network-manager*'
Note, selecting 'network-manager-gnome' for glob 'network-manager*'
Note, selecting 'network-manager' for glob 'network-manager*'
Note, selecting 'network-manager-openvpn' for glob 'network-manager*'
Note, selecting 'network-manager-ssh-gnome' for glob 'network-manager*'
Note, selecting 'network-manager-dev' for glob 'network-manager*'
Note, selecting 'network-manager-openvpn-gnome' for glob 'network-manager*'
Note, selecting 'network-manager-vpnc-gnome' for glob 'network-manager*'
Note, selecting 'network-manager-openconnect' for glob 'network-manager*'
Note, selecting 'network-manager-pptp-gnome' for glob 'network-manager*'
Package 'network-manager-dev' is not installed, so not removed
Package 'network-manager-iodine' is not installed, so not removed
Package 'network-manager-iodine-gnome' is not installed, so not removed
Package 'network-manager-openconnect' is not installed, so not removed
Package 'network-manager-openconnect-gnome' is not installed, so not removed
Package 'network-manager-openvpn' is not installed, so not removed
Package 'network-manager-openvpn-gnome' is not installed, so not removed
Package 'network-manager-pptp' is not installed, so not removed
Package 'network-manager-pptp-gnome' is not installed, so not removed
Package 'network-manager-ssh' is not installed, so not removed
Package 'network-manager-ssh-gnome' is not installed, so not removed
Package 'network-manager-strongswan' is not installed, so not removed
Package 'network-manager-vpnc' is not installed, so not removed
Package 'network-manager-vpnc-gnome' is not installed, so not removed
The following packages will be REMOVED:
  libjansson4* libndp0* libnm0* libnma0* libteamdctl0* network-manager* network-manager-gnome*
  wpasupplicant*
0 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
After this operation, 21.0 MB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 142570 files and directories currently installed.)
Removing network-manager-gnome (1.4.4-1+deb9u1) ...
Removing network-manager (1.6.2-3+deb9u2) ...
Removing libndp0:amd64 (1.6-1+b1) ...
Removing libnma0:amd64 (1.4.4-1+deb9u1) ...
Removing libnm0:amd64 (1.6.2-3+deb9u2) ...
Removing libteamdctl0:amd64 (1.26-1+b1) ...
Removing wpasupplicant (2:2.4-1+deb9u4) ...
Removing libjansson4:amd64 (2.9-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for libglib2.0-0:amd64 (2.50.3-2) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.28-0+deb9u1) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
(Reading database ... 142188 files and directories currently installed.)
Purging configuration files for network-manager-gnome (1.4.4-1+deb9u1) ...
Purging configuration files for wpasupplicant (2:2.4-1+deb9u4) ...
Purging configuration files for network-manager (1.6.2-3+deb9u2) ...
dpkg: warning: while removing network-manager, directory '/etc/NetworkManager/system-connections' not empty so not removed
Processing triggers for systemd (232-25+deb9u11) ...
Processing triggers for dbus (1.10.28-0+deb9u1) ...

 06 Jul 19 @ 17:44:22 ~
   $

... and of course borked my system.

YEA!!!!!

Anyway to get "Net Connected" back via CLI?

Last edited by Sector11 (2019-07-10 05:10:56)

damo · 2019-07-06 21:39:56

From my netinstall notes (you already have the interfaces file, so ignore that line. And change "wlp3s0" to your device name)...

3) If using wireless, "win an internet" by using one of the pre-prepared interfaces setups.

		sudo cp /media/usbstick/interfaces-home /etc/network/interfaces
		sudo ifup wlp3s0

(possibly: sudo systemctl restart networking.service)

From scratch:

sudo su
wpa_passphrase myssid my_very_secret_passphrase >> /etc/network/interfaces

Then edit to look like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
				
	source /etc/network/interfaces.d/*
		
	# The loopback network interface
	auto lo
	iface lo inet loopback
				
	auto wlan0
	iface wlan0 inet dhcp
        wpa-ssid myssid
        wpa-psk verylongnumber

Sector11 · 2019-07-07 02:50:28

3) If using wireless,

I loose right there...

wired - cable modem/router.

Colour me: DUH!!!!!

glittersloth · 2019-07-07 12:00:44

The lack of ssid and psk related lines in your first post implies that enp9s0 is your wired ethernet adapter. If that's the case, then your /etc/network/interfaces should read like this if you're just using dhcp;

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
				
# source /etc/network/interfaces.d/*
			
auto enp9s0
allow-hotplug enp9s0
iface enp9s0 inet dhcp

Last edited by glittersloth (2019-07-07 14:43:28)

Sector11 · 2019-07-07 13:54:47

I heel like a stupid noob here. I should have known better and installed ceni first.

OK I changed my /etc/network/interfaces to what glittersloth said since enp9s0 is correct.
The message I get on boot:

[FAILED] failed to start Raise network interface

The /etc/network/interfaces I'm using on this version of BL is:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto eth0
iface eth0 inet dhcp

glittersloth · 2019-07-07 14:20:54

^ Wait, I don't follow. What's "this version of BL" mean? Is that the system you're currently posting from, which is not the borked system, I assume? Are you sure your wired interface on the borked machine is enp9s0?

...and I goofed a bit
Put a # in front of source /etc/network/interfaces.d/* in the config on my previous post. (I edited it to match), or try the same on the first config posted in your opening post.

Last edited by glittersloth (2019-07-07 14:42:07)

PackRat · 2019-07-07 15:17:11

Sector11 wrote:

I heel like a stupid noob here. I should have known better and installed ceni first.
OK I changed my /etc/network/interfaces to what glittersloth said since enp9s0 is correct.
The message I get on boot:
[FAILED] failed to start Raise network interface

The /etc/network/interfaces I'm using on this version of BL is:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto eth0
iface eth0 inet dhcp

Verify that enp9s0 is correct for the borked system; glitersloth's solution should have worked.

Verify that the NetworkManager service is no longer active on the borked system; you uninstalled it, but I don't see a message that the service was deactivated. If it's still running, you won't connect using /etc/network/interfaces.

Are these separate computers, or do you have multiple BL installs on one?

Have you tried to copy the /etc/network/interfaces file that is working to the BL-install that is borked?

Last edited by PackRat (2019-07-07 15:18:01)

Sector11 · 2019-07-07 15:17:37

I have 3 Linux systems here, have had it like this for years.

sda1 & sda2 are Debian Jessie - /ROOT and ~/ respectively
sda5 - one of my data areas - all 3 systems access it it has;
- my emails, claws-mail and thunderbird
- wallpapers,
- FF fookmarks
- conkys - in the thousands
- etc
sda6 & sda7 - the borked system with 99% of my personal tweaks complete
sda8 & sda9 - an almost out of the box BL Helium install
sda10 - another data storage area

Currently I am on sda8 & 9

Wish ceni was still around.

...and I goofed a bit
Put a # in front of source /etc/network/interfaces.d/* in the config on my previous post. (I edited it to match), or try the same on the first config posted in your opening post.

OK, done .... brb

Sector11 · 2019-07-07 15:29:30

PackRat wrote:

Verify that enp9s0 is correct for the borked system; glitersloth's solution should have worked.
Verify that the NetworkManager service is no longer active on the borked system; you uninstalled it, but I don't see a message that the service was deactivated. If it's still running, you won't connect using /etc/network/interfaces.
Are these separate computers, or do you have multiple BL installs on one?
Have you tried to copy the /etc/network/interfaces file that is working to the BL-install that is borked?

Confirmed it is enp9s0, had to pop that into a network conky, which means it doesn't work on this system, as here it is: enp2s0. Hate that system will bring back my eth0 on all systems.

See above - multiple on one.

Sector11 · 2019-07-07 15:49:25

Well, I think smell a reinstall again. {sigh}

Sector11 · 2019-07-07 20:05:46

↑↑ in light of that post ↑↑ Reinstalled.

So change this to a help request.

network-manager has set up /etc/network/interfaces like this:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

but "nmcli" tells me: interface: enp2s0

Now since I have a hard-wired cable network connection on a desktop computer that never moves to some restaurant and really do not need (nor want) network-manager, is there a safe way to get rid of it and start using "dhcp" that come with the net install CD and also Debian Installer that BL uses.

IMHO: network-manager | wicd | dhcp should be options.
ceni of course is gone, it was ACE!

But this is interesting from the Debian Wiki on Network Manager:

Wired Networks are Unmanaged
As of Debian 6.0 "Squeeze", NetworkManager does not manage any interface defined in /etc/network/interfaces by default.
Unmanaged devices means NetworkManager doesn't handle those network devices. This occurs when two conditions are met:
The file /etc/network/interfaces contains anything about the interface, even:
allow-hotplug eth0
iface eth0 inet dhcp
And /etc/NetworkManager/NetworkManager.conf contains:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false

So now it would seem that DCHP set up /etc/network/interfaces and NM is doing nothing because BOTH of those conditions are met.

So why can't I simply remove network-manager?

Last edited by Sector11 (2019-07-07 20:19:12)

PackRat · 2019-07-07 20:48:37

Based on what you've posted, it doesn't look like both those conditions are met. You still need:

allow-hotplug eth0
iface eth0 inet dhcp

In your /etc/network/interfaces file (change eth0 to your actual interface); looks like your only entry is for the loopback.

In the past, I have always stopped then disabled the Network Manager service(s), added the entries for dhcp in the /etc/network/interfaces file, then reboot.

You should then have networking via dhcp with no Network manager services running. If it's working the way you want, use apt to remove/purge Network Manager if you want to; remember to remove nm-applet from any autostart files.

PackRat · 2019-07-07 20:50:17

There is a brief entry for networking setup via dhcp on the Debian Wiki.

Sector11 · 2019-07-07 21:50:23

PackRat wrote:

There is a brief entry for networking setup via dhcp on the Debian Wiki.

Yes that's where I quoted the section above from.

So since nmcli tells me:

 07 Jul 19 @ 17:57:36 ~
   $ nmcli
enp2s0: connected to Wired connection 1

I should have an interfaces file like:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

allow-hotplug enp2s0
iface enp2s0 inet dhcp

I notice the Debian Wiki does not talk about the newer "Predictable Interface Names"

That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
Classic, unpredictable kernel-native ethX naming (example: eth0)

I am guessing this "enp2s0" will work.

PackRat wrote:

I have always stopped then disabled the Network Manager service(s)

OK, I found this:

To disable Network Manager on Debian 8 or later:
$ sudo systemctl stop NetworkManager.service
$ sudo systemctl disable NetworkManager.service

then a reboot and X-fingers?

I will miss "nmcli"

and if X-ing fingers doesn't work let's hope:

sudo systemctl restart network-manager

does.

Now, let's pretend (hate: assume) with the new "interfaces" file and the "stop - disable - reboot" sequence that everything works.

Should I "remove" or "autoremove" network-manager?
SIMULATION:

 
 07 Jul 19 @ 18:42:11 ~
   $ sremv network-manager
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libjansson4 libndp0 libnm0 libnma0 libteamdctl0 libxnvctrl0 wpasupplicant
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  network-manager network-manager-gnome
0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
Remv network-manager-gnome [1.4.4-1+deb9u1]
Remv network-manager [1.6.2-3+deb9u2]
 
 07 Jul 19 @ 18:42:27 ~
   $ saremv network-manager
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libjansson4* libndp0* libnm0* libnma0* libteamdctl0* libxnvctrl0* network-manager* network-manager-gnome*
  wpasupplicant*
0 upgraded, 0 newly installed, 9 to remove and 1 not upgraded.
Purg network-manager-gnome [1.4.4-1+deb9u1]
Purg network-manager [1.6.2-3+deb9u2]
Purg libjansson4 [2.9-1] [libnm0:amd64 ]
Purg libndp0 [1.6-1+b1] [libnm0:amd64 ]
Purg libnma0 [1.4.4-1+deb9u1] [libnm0:amd64 ]
Purg libnm0 [1.6.2-3+deb9u2]
Purg libteamdctl0 [1.26-1+b1]
Purg libxnvctrl0 [390.116-1]
Purg wpasupplicant [2:2.4-1+deb9u4]
 
 07 Jul 19 @ 18:43:01 ~
   $

Thank to damo, glittersloth and PackRat

EDIT: Leary of the "*" in the auto-remove list: libjansson4* libndp0* libnm0* libnma0* libteamdctl0* libxnvctrl0* network-manager* network-manager-gnome* wpasupplicant*

Last edited by Sector11 (2019-07-07 21:52:14)

PackRat · 2019-07-07 22:18:27

Your /etc/network/interfaces file should look like:

# The loopback network interface
auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet dhcp

the system uses the loopback interface.

That seems to be overkill on the removal, what's the actual command for that bash alias? wpasupplicant is for wireless, so I don't see why that would get uninstalled as well. Unless you're starved for hard drive space, leave it installed.

unklar · 2019-07-09 09:22:13

I don't know if I understood your request correctly...

In times of systemd are no longer necessary /etc/network/interfaces .
Whenever I had problems with my network, I decided to use systemd-networkd because of these instructions.
I can recommend this decision to everyone, because it works excellently.

Attention in german

- Conversion of the wired network to systemd-networkd
(Umstellung des kabelgebundenen Netzwerkes auf systemd-networkd)

- wlan with systemd-networkd and wpa_supplicant
(wlan mit systemd-networkd und wpa_supplicant)

HoaS has also already described this in 2015/16

My /etc/systemd/eth.network looks like this:

[Match]
Name=enp2s0

[Network]
DNS=192.168.178.1

[Address]
Address=192.168.178.45/24

[Route]
Gateway=192.168.178.1

My desktop gets a fixed ip (192.168.178.45) assigned by the router in the home network.

Last edited by unklar (2019-07-09 09:26:57)

Sector11 · 2019-07-09 20:55:49

PackRat wrote:

Your /etc/network/interfaces file should look like:
# The loopback network interface
auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet dhcp
the system uses the loopback interface.
That seems to be overkill on the removal, what's the actual command for that bash alias? wpasupplicant is for wireless, so I don't see why that would get uninstalled as well. Unless you're starved for hard drive space, leave it installed.

Sorry for the delay I was unceremoniously unsubscribed from the thread and waiting an answer.

alias remv='sudo apt remove'

Is only removing the two:

Remv network-manager-gnome [1.4.4-1+deb9u1]
Remv network-manager [1.6.2-3+deb9u2]

but:

alias aremv='sudo apt-get autoremove --purge'

is a killer taking them all out:

Purg network-manager-gnome [1.4.4-1+deb9u1]
Purg network-manager [1.6.2-3+deb9u2]
Purg libjansson4 [2.9-1] [libnm0:amd64 ]
Purg libndp0 [1.6-1+b1] [libnm0:amd64 ]
Purg libnma0 [1.4.4-1+deb9u1] [libnm0:amd64 ]
Purg libnm0 [1.6.2-3+deb9u2]
Purg libteamdctl0 [1.26-1+b1]
Purg libxnvctrl0 [390.116-1]
Purg wpasupplicant [2:2.4-1+deb9u4]

wpasupplicant is one of network-manager's depends:

 09 Jul 19 @ 17:52:21 ~
   $ dep network-manager
alias dep=apt-cache depends
network-manager
  Depends: libaudit1
  Depends: libbluetooth3
  Depends: libc6
  Depends: libglib2.0-0
  Depends: libgnutls30
  Depends: libgudev-1.0-0
  Depends: libjansson4
  Depends: libmm-glib0
  Depends: libndp0
  Depends: libnewt0.52
  Depends: libnl-3-200
  Depends: libnm0
  Depends: libpolkit-agent-1-0
  Depends: libpolkit-gobject-1-0
  Depends: libreadline7
  Depends: libselinux1
  Depends: libsoup2.4-1
  Depends: libsystemd0
  Depends: libteamdctl0
  Depends: libuuid1
  Depends: init-system-helpers
  Depends: lsb-base
  Depends: wpasupplicant
  Depends: dbus
  Depends: udev
  Depends: adduser
  Depends: libpam-systemd
  Depends: policykit-1
  Breaks: ppp
  Breaks: ppp
  Recommends: ppp
  Recommends: dnsmasq-base
  Recommends: iptables
  Recommends: modemmanager
    wader-core
  Recommends: crda
  Recommends: isc-dhcp-client
  Recommends: iputils-arping
  Suggests: libteam-utils
 
 09 Jul 19 @ 17:53:16 ~
   $

 09 Jul 19 @ 17:56:47 ~
   $ rdep wpasupplicant
alias apt-cache rdepends filename
wpasupplicant
Reverse Depends:
  wpagui
  wpagui
  network-manager
  wifi-radar
  wicd-daemon
  task-laptop
  connman
  network-config
  netscript-2.4
  ifplugd
  geoclue-2.0
 
 09 Jul 19 @ 17:56:56 ~
   $

Last edited by Sector11 (2019-07-09 20:57:24)

Sector11 · 2019-07-09 21:07:01

PackRat wrote:

Your /etc/network/interfaces file should look like:
# The loopback network interface
auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet dhcp
the system uses the loopback interface.

That ↑↑↑↑ .... plus:

 09 Jul 19 @ 18:00:32 ~
   $ sudo systemctl stop NetworkManager.service
[sudo] password for sector11:

 09 Jul 19 @ 18:00:51 ~
   $ sudo systemctl disable NetworkManager.service
Removed /etc/systemd/system/multi-user.target.wants/NetworkManager.service.
Removed /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service.

 09 Jul 19 @ 18:01:11 ~
   $

Worked, I'm still here.

Last edited by Sector11 (2019-07-09 21:07:41)

BLizgreat! · 2019-07-10 04:45:12

Just a babble note. Someone can get ceni from the Siduction gnu/Linux repos. Long since taken to grabbing it from there. Still runs fine. Using it on my old crusty laptop on a Debian 9.8 and a 9.7 install. Still runs great. Agree with you Sector, like ceni the best out of what nm's I've dorked with.

Last edited by BLizgreat! (2019-07-10 04:55:32)

Sector11 · 2019-07-10 05:05:01

I kiss ya, but pixels ya know {pitooie!}

TY

#1 2019-07-06 21:23:52

[SOLVED] Help - how can I remove Network Manager safely?

#2 2019-07-06 21:39:56

Re: [SOLVED] Help - how can I remove Network Manager safely?

#3 2019-07-07 02:50:28

Re: [SOLVED] Help - how can I remove Network Manager safely?

#4 2019-07-07 12:00:44

Re: [SOLVED] Help - how can I remove Network Manager safely?

#5 2019-07-07 13:54:47

Re: [SOLVED] Help - how can I remove Network Manager safely?

#6 2019-07-07 14:20:54

Re: [SOLVED] Help - how can I remove Network Manager safely?

#7 2019-07-07 15:17:11

Re: [SOLVED] Help - how can I remove Network Manager safely?

#8 2019-07-07 15:17:37

Re: [SOLVED] Help - how can I remove Network Manager safely?

#9 2019-07-07 15:29:30

Re: [SOLVED] Help - how can I remove Network Manager safely?

#10 2019-07-07 15:49:25

Re: [SOLVED] Help - how can I remove Network Manager safely?

#11 2019-07-07 20:05:46

Re: [SOLVED] Help - how can I remove Network Manager safely?

#12 2019-07-07 20:48:37

Re: [SOLVED] Help - how can I remove Network Manager safely?

#13 2019-07-07 20:50:17

Re: [SOLVED] Help - how can I remove Network Manager safely?

#14 2019-07-07 21:50:23

Re: [SOLVED] Help - how can I remove Network Manager safely?

#15 2019-07-07 22:18:27

Re: [SOLVED] Help - how can I remove Network Manager safely?

#16 2019-07-09 09:22:13

Re: [SOLVED] Help - how can I remove Network Manager safely?

#17 2019-07-09 20:55:49

Re: [SOLVED] Help - how can I remove Network Manager safely?

#18 2019-07-09 21:07:01

Re: [SOLVED] Help - how can I remove Network Manager safely?

#19 2019-07-10 04:45:12

Re: [SOLVED] Help - how can I remove Network Manager safely?

#20 2019-07-10 05:05:01

Re: [SOLVED] Help - how can I remove Network Manager safely?

Board footer