Migration from wicked to NetworkManager

English Network/Internet
#21

Hello Karl here the output

hpprol2:~ # systemctl cat ppp@proximus.service 
# /usr/lib/systemd/system/ppp@.service
[Unit]
Description=PPP link to %I
Documentation=man:pppd(8)
After=network-pre.target network.service 
Before=network.target multi-user.target shutdown.target 

[Service]
Type=forking
PIDFile=/run/ppp-%I.pid
ExecStart=/usr/sbin/pppd call %I linkname %I updetach nolog
ExecReload=/usr/bin/kill -s HUP $MAINPID
Restart=always
RestartSec=10
SuccessExitStatus=1
RestartPreventExitStatus=3 4 5

[Install]
WantedBy=network-online.target multi-user.target 



hpprol2:~ # journalctl -b -u ppp@proximus.service
-- No entries --

As far as I see the journal file has rotated today

bash-5.1#  cd /var/log/journal
bash-5.1# ls -l *
total 11524
-rw-r-----  1 root systemd-journal 1310720 janv. 30 10:15 system@1526b251854549489e7eed6f7b629a73-0000000000022fec-0005d6c765b35042.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 10:19 system@1526b251854549489e7eed6f7b629a73-00000000000232be-0005d6c91c1cbcf8.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 17:40 system@1526b251854549489e7eed6f7b629a73-00000000000235c4-0005d6c9299e5f3d.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 22:41 system.journal

Probably because I installed today the last updates for tumbleweed:(

Regards
Philippe

#22

I guess you should use this:

**erlangen:~ #** systemctl cat pppoe.service 
**# /usr/lib/systemd/system/pppoe.service**
[Unit] 
Description=PPPoE 
After=network.target 
Wants=network.target 

[Service] 
Group=dialout 
Type=oneshot 
RemainAfterExit=true 
ExecStart=/usr/sbin/pppoe-start 
ExecStop=/usr/sbin/pppoe-stop 

[Install] 
WantedBy=multi-user.target 
**erlangen:~ #**

hpprol2:~ # journalctl -b -u ppp@proximus.service
-- No entries --

As far as I see the journal file has rotated today

bash-5.1#  cd /var/log/journal
bash-5.1# ls -l *
total 11524
-rw-r-----  1 root systemd-journal 1310720 janv. 30 10:15 system@1526b251854549489e7eed6f7b629a73-0000000000022fec-0005d6c765b35042.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 10:19 system@1526b251854549489e7eed6f7b629a73-00000000000232be-0005d6c91c1cbcf8.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 17:40 system@1526b251854549489e7eed6f7b629a73-00000000000235c4-0005d6c9299e5f3d.journal
-rw-r-----  1 root systemd-journal 1310720 janv. 30 22:41 system.journal

Probably because I installed today the last updates for tumbleweed:(

Regards
Philippe
I have no idea what happened. Some fine reading: https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs

Host erlangen has:

**erlangen:~ #** journalctl --disk-usage  
Archived and active journals take up 120.0M in the file system. 
**erlangen:~ #**


[FONT=monospace]**erlangen:~ #** journalctl --list-boots               
-30 62f899843f544a48bcee29eaff430c90 Fri 2022-01-14 22:26:36 CET—Sat 2022-01-15 05:01:29 CET 
...
 -1 d4c9a36446804e0793b480987cf8721d Sat 2022-01-29 21:39:38 CET—Sun 2022-01-30 04:58:46 CET
  0 c18d80dc83104381a1e42a01a80add52 Sun 2022-01-30 04:59:09 CET—Sun 2022-01-30 23:34:46 CET 
**erlangen:~ #**[/FONT]
#23

Hello Karl, Hello arvidjaar

I did a second test with systemd-networkd this morning after changing the ppp@proximus.service but there is still a problem

hpprol2:~ # systemctl status ppp@proximus
○ ppp@proximus.service - PPP link to proximus
     Loaded: loaded (/usr/lib/systemd/system/ppp@.service; enabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/ppp@proximus.service.d
             └─override.conf
     Active: inactive (dead)
       Docs: man:pppd(8)

Jan 31 07:17:07 hpprol2 systemd[1]: network.target: Found ordering cycle on ppp@proximus.service/start
Jan 31 07:17:07 hpprol2 systemd[1]: network.target: Found dependency on network.target/start
Jan 31 07:17:07 hpprol2 systemd[1]: network.target: Job ppp@proximus.service/start deleted to break ordering cycle starting with network.target/start

the change done for the ppp@proximus are

# cat override.conf
[Unit]
After=network.target 
Wants=network.target  
Before=
[Install]
WantedBy=multi-user.target

Maybe the Before= is not suffisant and need to be set as comment in the original service file. I’ll test this
I can manually start the service :slight_smile:

hpprol2:~ # systemctl start ppp@proximus
hpprol2:~ # systemctl status ppp@proximus
● ppp@proximus.service - PPP link to proximus
     Loaded: loaded (/usr/lib/systemd/system/ppp@.service; enabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/ppp@proximus.service.d
             └─override.conf
     Active: active (running) since Mon 2022-01-31 07:28:35 CET; 3s ago
       Docs: man:pppd(8)
    Process: 2714 ExecStart=/usr/sbin/pppd call proximus linkname proximus updetach nolog (code=exited, status=0/SUCCESS)
   Main PID: 2729 (pppd)
      Tasks: 1 (limit: 4915)
        CPU: 1.230s
     CGroup: /system.slice/system-ppp.slice/ppp@proximus.service
             └─2729 /usr/sbin/pppd call proximus linkname proximus updetach nolog

Jan 31 07:28:34 hpprol2 pppd[2714]: CHAP authentication succeeded: CHAP authentication success
Jan 31 07:28:34 hpprol2 pppd[2714]: CHAP authentication succeeded
Jan 31 07:28:34 hpprol2 pppd[2714]: peer from calling number 20:E0:9C:0A:CD:47 authorized
Jan 31 07:28:35 hpprol2 pppd[2714]: replacing old default route to vlan1 [192.168.1.1] with metric $d
Jan 31 07:28:35 hpprol2 pppd[2714]: local  IP address yy.yy.yy.yy
Jan 31 07:28:35 hpprol2 pppd[2714]: remote IP address xx.xx.xx.xx
Jan 31 07:28:35 hpprol2 pppd[2714]: primary   DNS address 195.238.2.21
Jan 31 07:28:35 hpprol2 pppd[2714]: secondary DNS address 195.238.2.22
Jan 31 07:28:35 hpprol2 systemd[1]: Started PPP link to proximus.
Jan 31 07:28:36 hpprol2 pppd[2729]: Script /etc/ppp/ip-up finished (pid 2730), status = 0x0
hpprol2:~ # ip route show
default dev ppp0 scope link 
default via 192.168.2.1 dev vlan2 proto static 
default via 192.168.3.1 dev vlan3 proto static 
default via 192.168.4.1 dev vlan4 proto static 
xx.xx.xx.xx dev ppp0 proto kernel scope link src yy.yy.yy.yy 
192.168.1.0/24 dev vlan1 proto kernel scope link src 192.168.1.1 
192.168.2.0/24 dev vlan2 proto kernel scope link src 192.168.2.1 
192.168.3.0/24 dev vlan3 proto kernel scope link src 192.168.3.1 
192.168.4.0/24 dev vlan4 proto kernel scope link src 192.168.4.1

https://forums.opensuse.org/images/misc/quote_icon.png Originally Posted by arvidjaar https://forums.opensuse.org/images/buttons/viewpost-right.png](https://forums.opensuse.org/showthread.php?p=3103080#post3103080)
Firewalls must be started before network is up, otherwise you have some unprotected windows.

You misunderstand how firewalld works. You can bind interface to zone statically in firewalld configuration or dynamically at run time. wicked and NM support dynamic assignment; systemd-networkd does not, but you can do it statically. As long as interface names remain the same and are always associated with the same zone it will work just fine.

firewalld is not aware of ifcfg* files. wicked interprets them and tells firewalld to bind interface to zone indicated there.

firewall-config shows only the ppp0 interface and the related eno3 in zone external. I added the interfaces for zone home

hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=vlan1
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=vlan2
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=vlan3
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=vlan4
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=eno2
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=br0
success
hpprol2:~ # firewall-cmd --permanent --zone=home --add-interface=eno1
success
hpprol2:~ # firewall-cmd --reload
success
hpprol2:~ # firewall-cmd --get-active-zone
docker
  interfaces: docker0
external
  interfaces: eno3 ppp0
home
  interfaces: vlan1 vlan2 vlan3 vlan4 eno2 br0 eno1
hpprol2:~ # firewall-cmd --info-zone=home
home (active)
  target: default
  icmp-block-inversion: no
  interfaces: br0 eno1 eno2 vlan1 vlan2 vlan3 vlan4
  sources: 
  services: apache2 apache2-ssl dhcp dhcpv6 dhcpv6-client dns dns-over-tls finger ftp http https imap imaps ipp ipp-client irc kdeconnect kerberos kpasswd ldap ldaps libvirt libvirt-tls libvirtd-relocation-server mdns minidlna mountd mysql nfs nfs3 ntp openvpn rpc-bind rsyncd samba samba-client samba-dc sane slp smtp smtps snmp ssh tftp tigervnc tigervnc-https transmission-client vnc-server
  ports: 67/udp 68/udp
  protocols: 
  forward: yes
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule family="ipv4" source address="192.168.3.0/24" destination address="192.168.2.0/24" protocol value="icmp" drop
        rule family="ipv4" source address="192.168.2.0/24" destination address="192.168.3.0/24" protocol value="tcp" drop
        rule family="ipv4" source address="192.168.2.0/24" destination address="192.168.3.0/24" protocol value="icmp" drop
        rule family="ipv4" source address="192.168.3.0/24" destination address="192.168.2.0/24" protocol value="tcp" drop

now the other pc in the different vlan have access to the internet :slight_smile:
Many thanks for your help with firewalld.

I need still to test with a reboot if the firewall is working and if my VM has internet and lan access
Philippe

#24

Great! We already discussed ordering: https://forums.opensuse.org/showthread.php/545542-Systemd-nss_lookup-target-deleted-to-break-ordering-cycle?p=2980087#post2980087 Have a detailed look at the new issue. Contradicting ordering is easily fixed. I presume ppp@proximus only needs After=… .

Some minor remarks:

  1. Don’t address two or more issues in a single comment as done above.

  2. Don’t use cat. Use systemctl cat instead:

erlangen:~ # systemctl cat wpa_supplicant@.service 
# /etc/systemd/system/wpa_supplicant@.service
[Unit]
Description=WPA Supplicant daemon (interface %i)
Requires=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=simple
ExecStart=/usr/sbin/wpa_supplicant -i%i -c /etc/wpa_supplicant/wpa_supplicant.conf -u -t -f /var/log/wpa_supplicant.log

[Install]
WantedBy=multi-user.target
erlangen:~ #
  1. General advice: Never change /usr/lib/systemd. Stick to /etc/systemd. The former will haunt you in the future.
#25

I have set the line “Before=network.target multi-user.target shutdown.target” in the ppp@proximus.service as comment
After a reboot all is working :slight_smile:

ppp@proximus is started
firewalld is correct
all pc have internet access

Unspecting the journalctl I see that there are still three start of ppp@proximus.service

hpprol2:~ # journalctl -b -u ppp@proximus.service
Jan 31 08:26:32 hpprol2 systemd[1]: Starting PPP link to proximus...
Jan 31 08:26:32 hpprol2 pppd[917]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:32 hpprol2 pppd[917]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:32 hpprol2 pppd[917]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:32 hpprol2 pppd[917]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:32 hpprol2 pppd[917]: /usr/sbin/pppd: In file /etc/ppp/peers/proximus: unrecognized option 'eno3'
Jan 31 08:26:32 hpprol2 pppd[917]: **In file /etc/ppp/peers/proximus: unrecognized option 'eno3'**
Jan 31 08:26:32 hpprol2 systemd[1]: **ppp@proximus.service: Control process exited, code=exited, status=2/INVALIDARGUMENT**
Jan 31 08:26:32 hpprol2 systemd[1]: ppp@proximus.service: Failed with result 'exit-code'.
Jan 31 08:26:32 hpprol2 systemd[1]: **Failed to start PPP link to proximus.**
Jan 31 08:26:42 hpprol2 systemd[1]: ppp@proximus.service: Scheduled restart job, restart counter is at 1.
Jan 31 08:26:42 hpprol2 systemd[1]: Stopped PPP link to proximus.
Jan 31 08:26:42 hpprol2 systemd[1]: Starting PPP link to proximus...
Jan 31 08:26:42 hpprol2 pppd[1207]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:42 hpprol2 pppd[1207]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:42 hpprol2 pppd[1207]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:42 hpprol2 pppd[1207]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:43 hpprol2 pppd[1207]: /usr/sbin/pppd: In file /etc/ppp/peers/proximus: unrecognized option 'eno3'
Jan 31 08:26:43 hpprol2 pppd[1207]: **In file /etc/ppp/peers/proximus: unrecognized option 'eno3'**
Jan 31 08:26:43 hpprol2 systemd[1]: **ppp@proximus.service: Control process exited, code=exited, status=2/INVALIDARGUMENT**
Jan 31 08:26:43 hpprol2 systemd[1]: ppp@proximus.service: Failed with result 'exit-code'.
Jan 31 08:26:43 hpprol2 systemd[1]: **Failed to start PPP link to proximus.**
Jan 31 08:26:53 hpprol2 systemd[1]: ppp@proximus.service: Scheduled restart job, restart counter is at 2.
Jan 31 08:26:53 hpprol2 systemd[1]: Stopped PPP link to proximus.
Jan 31 08:26:53 hpprol2 systemd[1]: Starting PPP link to proximus...
Jan 31 08:26:53 hpprol2 pppd[1587]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:53 hpprol2 pppd[1587]: Plugin rp-pppoe.so loaded.
Jan 31 08:26:53 hpprol2 pppd[1587]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:53 hpprol2 pppd[1587]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Jan 31 08:26:54 hpprol2 pppd[1587]: pppd 2.4.8 started by root, uid 0
Jan 31 08:27:00 hpprol2 pppd[1587]: PPP session is 1
Jan 31 08:27:00 hpprol2 pppd[1587]: Connected to 20:e0:9c:0a:cd:47 via interface eno3
Jan 31 08:27:00 hpprol2 pppd[1587]: Using interface ppp0
Jan 31 08:27:00 hpprol2 pppd[1587]: Connect: ppp0 <--> eno3
Jan 31 08:27:03 hpprol2 pppd[1587]: Warning - secret file /etc/ppp/chap-secrets has world access
Jan 31 08:27:03 hpprol2 pppd[1587]: CHAP authentication succeeded: CHAP authentication success
Jan 31 08:27:03 hpprol2 pppd[1587]: CHAP authentication succeeded
Jan 31 08:27:03 hpprol2 pppd[1587]: peer from calling number 20:E0:9C:0A:CD:47 authorized
Jan 31 08:27:04 hpprol2 pppd[1587]: replacing old default route to vlan1 [192.168.1.1] with metric $d
Jan 31 08:27:04 hpprol2 pppd[1587]: local  IP address YY.YY.YY.YY
Jan 31 08:27:04 hpprol2 pppd[1587]: remote IP address XX.XX.XX.XX
Jan 31 08:27:04 hpprol2 pppd[1587]: primary   DNS address 195.238.2.21
Jan 31 08:27:04 hpprol2 pppd[1587]: secondary DNS address 195.238.2.22
Jan 31 08:27:04 hpprol2 systemd[1]: Started PPP link to proximus.
Jan 31 08:27:05 hpprol2 pppd[1608]: Script /etc/ppp/ip-up finished (pid 1609), status = 0x0
hpprol2:~ #[FONT=Latin Modern Mono] systemd-analyze critical-chain [/FONT]
[FONT=Latin Modern Mono] The time when unit became active or started is printed after the "@" character. 
The time the unit took to start is printed after the "+" character. 

graphical.target @2min 11.410s 
└─multi-user.target @2min 11.409s 
 └─**dhcpd.service @2min 9.199s +2.209s**
   └─remote-fs.target @2min 9.186s 
     └─**iscsi.service @2min 9.074s +110ms**
       └─network-online.target @2min 9.060s 
         └─**ppp@proximus.service @29.938s +10.961s**
           └─network.target @8.799s 
             └─**systemd-networkd.service @8.330s +467ms**
               └─network-pre.target @8.324s 
                 └─**firewalld.service @5.064s +3.258s**
                   └─**polkit.service @3.981s +1.068s**
                     └─basic.target @3.913s 
                       └─sockets.target @3.912s 
                         └─pcscd.socket @3.911s 
                           └─sysinit.target @3.888s 
                             └─haveged.service @25.854s 
                               └─systemd-journald.socket 
                                 └─system.slice 
                                   └─-.slice[/FONT]

Not a big problem but seems that the service is starting too early.

But for now I can live with it.
The goal of replacing “wicked” is almost achieved:)

Many thanks to all for your help
Philippe

#26

Does “Requires=network-online.target” and “After=network-online.target” help? No premature start of backup-home observed:

**erlangen:~ #** systemctl cat backup-home.service  
**# /etc/systemd/system/backup-home.service**
[Unit] 
Description=Backup /home 
Requires=HDD.mount 
After=HDD.mount 
After=local-fs.target 
Conflicts=shutdown.target 

[Service] 
Type=oneshot 
ExecStart=/usr/bin/rsync -a --exclude=.cache --exclude=covid-19-data /home/ /HDD/backup/home/ 
ExecStartPost=/usr/bin/umount /HDD 
**erlangen:~ #**
#27

Hello,

Last info about the ppp@proximus restart

I solved the ppp@proximus restart:
in journalctl I saw that after the last failing restart of this service, there is a systemd-udevd start with default sheme v249 (? :slight_smile: which renames the interface from ethx to enox and thereafter only systemd-networkd set the inteface up


# journalctl
...
Feb 01 08:41:07 hpprol2 systemd[1]: ppp@proximus.service: Scheduled restart job, restart counter is at 2.
Feb 01 08:41:07 hpprol2 systemd[1]: Stopped PPP link to proximus.
Feb 01 08:41:07 hpprol2 systemd[1]: Starting PPP link to proximus...
Feb 01 08:41:07 hpprol2 pppd[1276]: Plugin rp-pppoe.so loaded.
Feb 01 08:41:07 hpprol2 pppd[1276]: Plugin rp-pppoe.so loaded.
Feb 01 08:41:07 hpprol2 pppd[1276]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Feb 01 08:41:07 hpprol2 pppd[1276]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Feb 01 08:41:08 hpprol2 pppd[1276]: /usr/sbin/pppd: In file /etc/ppp/peers/proximus: unrecognized option 'eno3'
Feb 01 08:41:08 hpprol2 pppd[1276]: In file /etc/ppp/peers/proximus: unrecognized option 'eno3'
Feb 01 08:41:08 hpprol2 systemd[1]: **ppp@proximus.service: Control process exited, code=exited, status=2/INVALIDARGUMENT**
Feb 01 08:41:08 hpprol2 systemd[1]: ppp@proximus.service: Failed with result 'exit-code'.
Feb 01 08:41:08 hpprol2 systemd[1]: Failed to start PPP link to proximus.
Feb 01 08:41:11 hpprol2 clamd[939]: Loaded 8541873 signatures.
Feb 01 08:41:11 hpprol2 systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
Feb 01 08:41:11 hpprol2 haveged[1280]: haveged: command socket is listening at fd 3
Feb 01 08:41:12 hpprol2 systemd-udevd[730]: Using default interface naming scheme 'v249'.
Feb 01 08:41:12 hpprol2 systemd-networkd[901]: br0: Link UP
Feb 01 08:41:12 hpprol2 kernel: tg3 0000:02:00.0 eno1: renamed from eth0
Feb 01 08:41:13 hpprol2 systemd-networkd[901]: eth0: Interface name change detected, renamed to eno1.
Feb 01 08:41:13 hpprol2 kernel: tg3 0000:02:00.1 eno2: renamed from eth1
....
Feb 01 08:41:14 hpprol2 systemd-networkd[901]: eth1: Interface name change detected, renamed to eno2.
Feb 01 08:41:14 hpprol2 systemd-udevd[733]: Using default interface naming scheme 'v249'.
Feb 01 08:41:14 hpprol2 kernel: tg3 0000:02:00.2 eno3: renamed from eth2
Feb 01 08:41:14 hpprol2 systemd-networkd[901]: eth2: Interface name change detected, renamed to eno3.
Feb 01 08:41:14 hpprol2 systemd-udevd[718]: Using default interface naming scheme 'v249'.
Feb 01 08:41:14 hpprol2 kernel: tg3 0000:02:00.3 eno4: renamed from eth3
Feb 01 08:41:14 hpprol2 systemd-networkd[901]: eth3: Interface name change detected, renamed to eno4.
Feb 01 08:41:15 hpprol2 systemd-udevd[758]: Using default interface naming scheme 'v249'.
Feb 01 08:41:15 hpprol2 systemd-udevd[719]: Using default interface naming scheme 'v249'.
....
Feb 01 08:41:15 hpprol2 kernel: br0: port 1(eno1) entered blocking state
Feb 01 08:41:15 hpprol2 kernel: br0: port 1(eno1) entered disabled state
Feb 01 08:41:15 hpprol2 kernel: device eno1 entered promiscuous mode
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: eno1: Link UP
Feb 01 08:41:15 hpprol2 kernel: 8021q: 802.1Q VLAN Support v1.8
Feb 01 08:41:15 hpprol2 systemd-udevd[734]: Using default interface naming scheme 'v249'.
Feb 01 08:41:15 hpprol2 systemd-udevd[715]: Using default interface naming scheme 'v249'.
Feb 01 08:41:15 hpprol2 systemd-udevd[724]: Using default interface naming scheme 'v249'.
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan3: netdev ready
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan2: netdev ready
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan1: netdev ready
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan4: netdev ready
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: eno2: Link UP
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan1: Link UP
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan2: Link UP
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan3: Link UP
Feb 01 08:41:15 hpprol2 systemd-networkd[901]: vlan4: Link UP
Feb 01 08:41:16 hpprol2 systemd-networkd[901]: eno3: Link UP
....

I first tried first updating the service with

**# /etc/systemd/system/ppp@proximus.service.d/override.conf**
 [Unit] 
After=network.target systemd-udevd.service

but this doesn’t solve the problem
I tried then starting ppp@proximus after systemd-networkd-wait-online

#systemctl cat ppp@proximus.service
...
**# /etc/systemd/system/ppp@proximus.service.d/override.conf**
[Unit]
After=network.target  systemd-networkd-wait-online.service

and this solve the restart problem :slight_smile:

hpprol2:~ # journalctl -b -u ppp@proximus
Feb 01 08:57:15 hpprol2 systemd[1]: Starting PPP link to proximus...
Feb 01 08:57:15 hpprol2 pppd[1570]: Plugin rp-pppoe.so loaded.
Feb 01 08:57:15 hpprol2 pppd[1570]: Plugin rp-pppoe.so loaded.
Feb 01 08:57:15 hpprol2 pppd[1570]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Feb 01 08:57:15 hpprol2 pppd[1570]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Feb 01 08:57:15 hpprol2 pppd[1570]: pppd 2.4.8 started by root, uid 0
Feb 01 08:57:16 hpprol2 pppd[1570]: PPP session is 1
Feb 01 08:57:16 hpprol2 pppd[1570]: Connected to 20:e0:9c:0a:cd:47 via interface eno3
Feb 01 08:57:16 hpprol2 pppd[1570]: Using interface ppp0
Feb 01 08:57:16 hpprol2 pppd[1570]: Connect: ppp0 <--> eno3
Feb 01 08:57:16 hpprol2 pppd[1570]: Warning - secret file /etc/ppp/chap-secrets has world access
Feb 01 08:57:16 hpprol2 pppd[1570]: CHAP authentication succeeded: CHAP authentication success
Feb 01 08:57:16 hpprol2 pppd[1570]: CHAP authentication succeeded
Feb 01 08:57:16 hpprol2 pppd[1570]: peer from calling number 20:E0:9C:0A:CD:47 authorized
Feb 01 08:57:17 hpprol2 pppd[1570]: replacing old default route to vlan1 [192.168.1.1] with metric $d
Feb 01 08:57:17 hpprol2 pppd[1570]: local  IP address yy.yy.yy.yy
Feb 01 08:57:17 hpprol2 pppd[1570]: remote IP address xx.xx.xx.xx
Feb 01 08:57:17 hpprol2 pppd[1570]: primary   DNS address 195.238.2.21
Feb 01 08:57:17 hpprol2 pppd[1570]: secondary DNS address 195.238.2.22
Feb 01 08:57:17 hpprol2 systemd[1]: Started PPP link to proximus.
Feb 01 08:57:18 hpprol2 pppd[1578]: Script /etc/ppp/ip-up finished (pid 1579), status = 0x0

One more problem solved
Regards
Philippe

#28

When interface renaming annoyed me I stopped it on the command line:

**erlangen:~ #** grep CMD /etc/default/grub                                   
GRUB_**CMD**LINE_LINUX_DEFAULT="quiet plymouth.enable=0 net.ifnames=0 mitigations=auto" 
GRUB_**CMD**LINE_LINUX="" 
GRUB_**CMD**LINE_XEN_DEFAULT="vga=gfx-1024x768x16" 
**erlangen:~ #**


**erlangen:~ #** journalctl -b -u systemd-networkd.service -o short-monotonic               
    3.600871] erlangen systemd[1]: Starting Network Configuration... 
    3.638832] erlangen systemd-networkd[696]: lo: Link UP 
    3.667264] erlangen systemd-networkd[696]: lo: Gained carrier 
    3.667322] erlangen systemd-networkd[696]: Enumeration completed 
    3.667448] erlangen systemd[1]: Started Network Configuration. 
    4.401713] erlangen systemd-networkd[696]: eth0: Link UP 
    7.056478] erlangen systemd-networkd[696]: eth0: Gained carrier 
    8.205844] erlangen systemd-networkd[696]: eth0: Gained IPv6LL 
   12.033727] erlangen systemd-networkd[696]: eth0: DHCPv4 address 192.168.178.24/24 via 192.168.178.1 
**erlangen:~ #**