| 2018-06-13 17:23:53 |
Thomas |
bug |
|
|
added bug |
| 2018-06-13 17:26:26 |
Thomas |
description |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lives after a reboot.
Any way I can debug this problem?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lives after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-13 17:27:41 |
Thomas |
affects |
plan (Ubuntu) |
netplan.io (Ubuntu) |
|
| 2018-06-13 17:36:29 |
Thomas |
description |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lives after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lives after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-13 17:36:41 |
Thomas |
description |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lives after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lifes after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-13 17:38:50 |
Thomas |
description |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lifes after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
systemd-network stucks at
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lifes after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-13 17:39:59 |
Thomas |
description |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
systemd-network stucks at
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lifes after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
Hi,
when I use netplan with a match statement, my network is not fired up after reboot. I have to manually run "netplan apply" and than the interfaces are ready.
Without the interface get not renamed and also not applied to the bridge.
And systemd-networkd.service stucks at boot and is waiting for the network to get ready, but fails at least...
root@host:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp1s0:
match:
macaddress: 00:22:4d:b1:b6:ac
set-name: lan1
wakeonlan: true
dhcp4: no
dhcp6: no
enp2s0:
match:
macaddress: 00:22:4d:b1:b6:a8
set-name: lan2
dhcp4: no
dhcp6: no
optional: true
ovpn0:
dhcp4: no
dhcp6: no
optional: true
bridges:
br0:
interfaces: [enp1s0]
dhcp4: true
dhcp6: true
parameters:
stp: false
forward-delay: 5
The funny thing is, when I not use netplan to rename the interfaces (so I commend out match, macaddress and set-name) the network lifes after a reboot.
Any way I can debug this problem?
root@host:~# dpkg -l | grep netplan
ii netplan.io 0.36.2 amd64 YAML network configuration abstraction for various backends
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 13 19:17:40 2018
InstallationDate: Installed on 2018-06-12 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-09-13 12:44:36 |
Nicorac |
marked as duplicate |
|
1770082 |
|
