```
a@localhost ~> cat /etc/netplan/00-installer-config.yaml
# This is the network config written by 'subiquity'
network:
ethernets:
ens192:
dhcp4: true
version: 2
a@localhost ~>
````
And
```
a@localhost ~> networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens192 ether routable failed
2 links listed.
```
And
```
a@localhost ~> ip a
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 00:50:56:1b:ea:c9 brd ff:ff:ff:ff:ff:ff
inet 82.223.122.106/32 scope global dynamic ens192
valid_lft 42258sec preferred_lft 42258sec
inet6 fe80::250:56ff:fe1b:eac9/64 scope link
valid_lft forever preferred_lft forever
```
And
```
a@localhost ~> networkctl status
● State: routable
Address: 82.223.122.106 on ens192
fe80::250:56ff:fe1b:eac9 on ens192
Gateway: 10.255.255.1 (VMware, Inc.) on ens192
DNS: 212.227.123.16
212.227.123.17
May 10 03:10:35 localhost systemd-networkd[938]: Enumeration completed
May 10 03:10:35 localhost systemd-networkd[938]: ens192: IPv6 successfully
enabled
May 10 03:10:35 localhost systemd[1]: Started Network Service.
May 10 03:10:35 localhost systemd[1]: Starting Wait for Network to be
Configured...
May 10 03:10:35 localhost systemd-networkd[938]: ens192: Link UP
May 10 03:10:35 localhost systemd-networkd[938]: ens192: Gained carrier
May 10 03:10:35 localhost systemd-networkd[938]: ens192: DHCPv4 address
82.223.122.106/32 via 10.255.255.1
May 10 03:10:35 localhost systemd-networkd[938]: ens192: Could not set DHCPv4
route: Nexthop has invalid gateway. Network is unreachable
May 10 03:10:35 localhost systemd-networkd[938]: ens192: Failed
May 10 03:10:35 localhost systemd[1]: Finished Wait for Network to be
Configured.
```
I've used the following cmd:
```
sudo add-apt-repository ppa:ddstreet/lp1860926
sudo apt-get update
```
But the issue still exist !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1860926
Title:
Ubuntu 20.04 Systemd fails to configure bridged network
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Eoan:
In Progress
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
In Progress
Bug description:
[impact]
A bridged interface with static ipv4 address and gateway configuration
will fail to properly add the route via the gateway, leaving the
system without a globally working network.
[test case]
On a Focal system, remove all network configuration and create this
netplan:
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
bridges:
br0:
interfaces: [enp4s0]
dhcp4: no
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
Replace the interface name 'enp4s0' with the actual interface name on
the test system.
Reboot the system, and check the route to the gateway, which will be
missing:
root@lp1860926-f:~# ip r
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
The route is expected to be present, e.g.:
ubuntu@lp1860926-e:~$ ip r
default via 192.168.0.1 dev br0 proto static
192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4
[regression potential]
Any regression would likely involve incorrectly configured network
after an interface carrier gain/loss.
[scope]
This is needed for Focal, Eoan, and Bionic.
While this only reproduces at boot for Focal, the general loss of
configuration on carrier loss even when ConfigureWithoutCarrier=true
is reproducable on all releases except Xenial, which does not have the
ConfigureWithoutCarrier= parameter.
[original description]
Freshly installed Ubuntu 20.04 fully patched to days date with static
IP address works fine and survives a reboot
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
however when converted to a bridged network for kvm
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
dhcp4: false
bridges:
br0:
interfaces: [enp4s0]
dhcp4: no
addresses: [192.168.0.4/24]
gateway4: 192.168.0.1
nameservers:
search: [mydomain]
addresses: [192.168.0.1,192.168.0.2,192.168.0.3]
will not survive a reboot and required systemd-network to be restarted or
@reboot /usr/sbin/netplan apply
added to the crontab
after a reboot the network can not b eaccseed and a
systemctl status systemd-networkd produces
systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 979 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 57662)
Memory: 4.1M
CGroup: /system.slice/systemd-networkd.service
└─979 /lib/systemd/systemd-networkd
Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for
link '5' we don't know about, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.
systemctl restart systemd-networkd resolved the issue and a
systemctl status systemd-network producessystemd-networkd.service - Network
Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 1650 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 57662)
Memory: 1.6M
CGroup: /system.slice/systemd-networkd.service
└─1650 /lib/systemd/systemd-networkd
Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev ready
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: Gained IPv6LL
Jan 26 16:39:28 firebolt systemd-networkd[1650]: Enumeration completed
Jan 26 16:39:28 firebolt systemd[1]: Started Network Service.
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev exists, using
existing without changing its parameters
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: IPv6 successfully
enabled
a journalctl -u systemd-network produces
Jan 26 16:36:28 firebolt systemd[1]: Starting Network Service...
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: netdev ready
Jan 26 16:36:28 firebolt systemd-networkd[979]: Enumeration completed
Jan 26 16:36:28 firebolt systemd-networkd[979]: wlp3s0: Interface name change
detected, wlp3s0 has been renamed to wlan0.
Jan 26 16:36:28 firebolt systemd[1]: Started Network Service.
Jan 26 16:36:28 firebolt systemd-networkd[979]: wlan0: Interface name change
detected, wlan0 has been renamed to wlp3s0.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: rtnl: received neighbor
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: IPv6 successfully enabled
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Link UP
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Gained carrier
Jan 26 16:36:28 firebolt systemd-networkd[979]: enp4s0: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: enp4s0: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: rtnl: received neighbor
message with invalid family, ignoring.
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Lost carrier
Jan 26 16:36:28 firebolt systemd-networkd[979]: enp4s0: Link UP
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Gained carrier
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Could not set route:
Network is unreachable
Jan 26 16:36:28 firebolt systemd-networkd[979]: br0: Failed
Jan 26 16:36:30 firebolt systemd-networkd[979]: br0: Lost carrier
Jan 26 16:36:31 firebolt systemd-networkd[979]: enp4s0: Gained carrier
Jan 26 16:36:31 firebolt systemd-networkd[979]: br0: Gained carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for
link '5' we don't know about, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received
neighbor message with invalid family, ignoring.
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.
Jan 26 16:39:28 firebolt systemd[1]: Stopping Network Service...
Jan 26 16:39:28 firebolt systemd[1]: systemd-networkd.service: Succeeded.
Jan 26 16:39:28 firebolt systemd[1]: Stopped Network Service.
Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev ready
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: Gained IPv6LL
Jan 26 16:39:28 firebolt systemd-networkd[1650]: Enumeration completed
Jan 26 16:39:28 firebolt systemd[1]: Started Network Service.
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: netdev exists, using
existing without changing its parameters
Jan 26 16:39:28 firebolt systemd-networkd[1650]: br0: IPv6 successfully
enabled
the network should restart properly after a reboot liek in earlier
version of ubuntu 18.04 for example
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1860926/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
