Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Network manager and wicked working at same time: two IPS for eth0

  1. #11

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    Quote Originally Posted by deano_ferrari View Post
    IIRC, NetworkManager can be started on demand via dbus. This might depend on the dekstop environment you're using. I don't get this behaviour with KDE. Try masking the unit like this
    Code:
    sudo systemctl mask NetworkManager
    then reboot.
    Code:
    andromeda:/home/fernando # systemctl mask NetworkManager
    Created symlink /etc/systemd/system/NetworkManager.service → /dev/null.
    Yes, it worked.
    It seems really a brute-force way but I don't need Network Manager, so it's fine for me.

  2. #12
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,466
    Blog Entries
    1

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    Quote Originally Posted by fperal View Post
    Code:
    andromeda:/home/fernando # systemctl mask NetworkManager
    Created symlink /etc/systemd/system/NetworkManager.service → /dev/null.
    Yes, it worked.
    It seems really a brute-force way but I don't need Network Manager, so it's fine for me.
    Yes, it's a "means to an end" for administrators to inhibit a service being started, either manually or as a dependency (by linking the unit file to /dev/null).

    I note that you have NetworkManager-wait-online.service active. You could chase the dependency chain further with
    Code:
    systemctl list-dependencies --reverse NetworkManager-wait-online
    There's likely another service (eg winbind.service) which is causing NetworkManager to start "on demand" perhaps.
    Last edited by deano_ferrari; 10-Feb-2019 at 10:50.
    openSUSE Leap 15.0; KDE Plasma 5

  3. #13

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    Quote Originally Posted by deano_ferrari View Post
    Yes, it's a "means to an end" for administrators to inhibit a service being started, either manually or as a dependency (by linking the unit file to /dev/null).

    I note that you have NetworkManager-wait-online.service active. You could chase the dependency chain further with
    Code:
    systemctl list-dependencies --reverse NetworkManager-wait-online
    There's likely another service (eg winbind.service) which is causing NetworkManager to start "on demand" perhaps.

    Code:
    andromeda:/home/fernando # systemctl list-dependencies --reverse NetworkManager-wait-online
    NetworkManager-wait-online.service
    ● └─teamviewerd.service
    andromeda:/home/fernando #
    UPS.... yes.
    I installed teamviewer but I only wanted to use the client, not the server. I guess I did something bad.
    I have just disabled it

    Code:
    andromeda:/home/fernando # systemctl disable teamviewerd
    Removed /etc/systemd/system/multi-user.target.wants/teamviewerd.service.
    I will try to unmask Network Manager again to see if now it keeps disabled.

  4. #14
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,466
    Blog Entries
    1

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    Yes, that should take care of the necessary.
    openSUSE Leap 15.0; KDE Plasma 5

  5. #15

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    It worked. After a reboot

    Code:
    andromeda:/home/fernando # systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
               └─NetworkManager-ovs.conf
       Active: inactive (dead)
         Docs: man:NetworkManager(8)
    andromeda:/home/fernando # systemctl status teamviewerd
    ● teamviewerd.service - TeamViewer remote control daemon
       Loaded: loaded (/etc/systemd/system/teamviewerd.service; disabled; vendor preset: disabled)
       Active: inactive (dead)
    andromeda:/home/fernando # ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 20:cf:30:c0:39:4b brd ff:ff:ff:ff:ff:ff
        inet 192.168.2.3/24 brd 192.168.2.255 scope global eth0
           valid_lft forever preferred_lft forever
    3: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
        link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
        inet 172.16.172.1/24 brd 172.16.172.255 scope global vmnet1
           valid_lft forever preferred_lft forever
    4: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
        link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
        inet 172.16.17.1/24 brd 172.16.17.255 scope global vmnet8
           valid_lft forever preferred_lft forever
    andromeda:/home/fernando #

  6. #16
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,466
    Blog Entries
    1

    Default Re: Network manager and wicked working at same time: two IPS for eth0

    As expected. Thanks for the update.
    openSUSE Leap 15.0; KDE Plasma 5

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •