@gautier-avril I tested your exact netplan yaml and it works fine for me
with the latest package versions. This bug is fix released, so you
should open a new bug if you believe there is a new problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Can you confirm that this issue is solved for routes (not default
gateway).
my config :
network:
version: 2
renderer: networkd
ethernets:
eth1:
dhcp4: no
dhcp6: no
mtu: 9000
bridges:
br11:
optional: false
mtu: 9000
dhcp4: no
dhcp6: no
This bug was fixed in the package systemd - 237-3ubuntu10.42
---
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
bionic:
ubuntu@lp1860926-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.42 amd64system and service manager
ubuntu@lp1860926-b:~$ ip a
1: lo: 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
Hello Andrew, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[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
Yes systemd is now at 245.4-4ubuntu3.1 and the interface does come up
at boot.
Note my config is also now using the macaddress parameter as mentioned
by another commenter above, which may have effected the result.
Thank you very much!
--
You received this bug notification because you are a
This bug was fixed in the package systemd - 245.4-4ubuntu3.1
---
systemd (245.4-4ubuntu3.1) focal; urgency=medium
*
d/p/lp1867375/0001-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,
d/p/lp1867375/0002-test-network-add-a-test-case-for-DHCPv4.UseGateway-n.patch,
This bug was fixed in the package systemd - 242-7ubuntu3.9
---
systemd (242-7ubuntu3.9) eoan; urgency=medium
* d/p/lp1867375/0001-network-Allow-to-configure-GW-even-UseRoutes-false.patch,
d/p/lp1867375/0002-network-add-a-flag-to-ignore-gateway-provided-by-DHC.patch,
On Focal, I can confirm the bug and the fix from 245.4-4ubuntu3.1
(focal-proposed). Thanks for working on this!
--
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
Same here:
/etc/netplan/01-netcfg.yaml
network:
version: 2
renderer: networkd
ethernets:
eno1:
dhcp4: no
bridges:
br0:
dhcp4: yes
interfaces:
- eno1
addresses:
- 192.168.xx.xx/24
- 2a02:...::xx/64
gateway4:
autopkgtest remaining failing tests:
systemd (ppc64el): this has always failed, ignore.
snapd (ii386): this has failed in i386 for a long time due to missing i386
deps/snaps, ignore
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
autopkgtest analysis for eoan above in comment 43, analysis for focal
above in comment 37
--
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
eoan:
root@lp1860926-e:~# cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
#
I applied the fix from proposed and I can confirm that it fixed the
issue for me too. thank you!
--
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
Just a quick note to say that I removed the PPA enabled -proposed in my
apt sources and rebooted, and networking is all working fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Using ubuntu-20.04-live-server-amd64.iso I created an USB and did fresh
install, after fresh install I ran apt get update followed by apt get
upgrade, I then removed the existing yaml in /etc/netplan and added
99_config.yaml:
labuser@lab:~$ sudo nano /etc/netplan/99_config.yaml
labuser@lab:~$
autopkgtest analysis for focal:
prometheus fails in all archs due to bug 1878709 (ignore)
gvfs (arm64) is flaky, test retried (ignore if it fails again)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Andrew, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.9
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package systemd - 245.5-2ubuntu2
---
systemd (245.5-2ubuntu2) groovy; urgency=medium
[ Dan Streetman ]
* network: Change IgnoreCarrierLoss default to value of
ConfigureWithoutCarrier.
This fixes bridges with static IP configuration. (LP: #1860926)
** Description changed:
[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
** Tags removed: verification-needed
** Tags added: verification-done
--
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
systemd-245.4-4ubuntu3.1 fixes the problem for me as well
--
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
Verification successful.
Package version: systemd-245.4-4ubuntu3.1 from -proposed repository.
Upgraded and rebooted. The network came up normally.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member
Hello Andrew, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@american your issue has nothing to do with this bug; this applies only
to bridges with static configuration. You are not using a bridge and
you are not using static configuration.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I changed the f/g status back; also I set groovy to fit committed.
** Changed in: systemd (Ubuntu Focal)
Status: Fix Released => In Progress
** Changed in: systemd (Ubuntu Groovy)
Status: Fix Released => In Progress
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress
Sorry am new here and pressed wrongly on the status. i don't know how to
revert it back to `In Progress`
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug
@ddstreet please have a look on my previous post. thanks in advance.
--
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
```
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
Thanks! upstream still hasn't decided on the patch, but I'll upload to
focal anyway since this has a serious impact on users. Hopefully
upstream will accept the patch later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@ddstreet the previous upload finally landed in groovy, now I'm testing
the next upload with this fix in in
https://bileto.ubuntu.com/#/ticket/3801 .
** Changed in: systemd (Ubuntu Groovy)
Assignee: (unassigned) => Balint Reczey (rbalint)
** Changed in: systemd (Ubuntu Groovy)
@rbalint sounds good to me, thanks!
--
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
@ddstreet Regarding the fix IMO the proposed fix makes sense and makes
systemd more robust. I'd like to add it in Ubuntu even if upstream would
like to stick to a more fragile default to notice bugs earlier.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Forwarded to upstream via https://github.com/systemd/systemd/pull/15619
. (Thanks @ddstreet!)
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
[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
Also working for me.
Also of note, configuring the bridge via DHCP worked prior to the patch,
regardless of assigning a dynamic or static IP via the DHCP server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Also working here.
'networkctl status' shows:
● State: routable
Address: 192.168.1.65 on br0
192.168.122.1 on virbr0
fe80::3a2c:4aff:febd:306a on br0
Gateway: 192.168.1.1 (PC Engines GmbH) on br0
DNS:
That works for me too :-)
Apr 27 18:43:50 mephi-server systemd-networkd[799]: br107: netdev ready
Apr 27 18:43:50 mephi-server systemd-networkd[799]: br1: netdev ready
Apr 27 18:43:50 mephi-server systemd-networkd[799]: br0: netdev ready
Apr 27 18:43:50 mephi-server systemd-networkd[799]:
It work ! Thank-you so much :-)
● State: routable
Address: 192.168.2.1 on enp2s0
192.168.1.166 on br1
192.168.122.1 on virbr0
Here is the output from networkctl
root@leblancs-Z170X-UD3:~# networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 enp14s0f0etherenslavedconfigured
3 enp14s0f1etheroff unmanaged
4 enp0s31f6ether
Doing the test now, will report back in 5 minutes.
--
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
Can anyone affected by this please test with the systemd packages from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1860926
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This happens because the bridge interface comes up with carrier
(specifically, with +LOWER_UP interface flag) and begins setting its
addresses/routes, but then briefly loses carrier. I'm not sure why the
bridge comes up with +LOWER_UP when ens3 appears to *not* be up:
Apr 27 10:46:56 lp1860926-f
** Tags added: seg
--
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
If that help here is my netplan setup that was working perfect in 18.04,
19.04, 19.10
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
dhcp4: false
dhcp6: false
match:
macaddress: 1c:1b:0d:61:85:40
mtu: 9000
enp12s0f0:
dhcp4: false
Cloundinit is not install neither networkmanager !!! :-(
--
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
Jane, Thanks, that interesting mine were from the use of KVM, although i
don't think i had it installed at the time (initially at least), as i
building the system. Although i can't be totally sure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Sylvain, I also have mounts and had to do the same thing. I did notice
that the coundinit was getting in the way , so removed it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The following has me wondering if this has partly to do with the
presence of containers, VMs and similar items.
I upgraded my router to 20.04 a few days before release. (Plain Ubuntu
command-line OS on a PC Engines APU1 board) That machine has a bridge
network comprising two ethernets and one
I have this exact bug after upgrading from 19.10 workstation to 20.04,
please notice I use the workstation has a LXD container server, all my
nfs mount point failed to mount, and I also never get an Ip address on
my bridge interface, to fix this manually I have todo netplan apply and
mount -a !
Just a note to confirm that this bug still exists in the public release
downloaded from the Ubuntu website today.
The crontab workaround has saved me a bit of angst.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
This may be the same bug as
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1872185
--
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
Same problem for me on Raspi 4 (bridged networking)
I have found a quick and dirty workaround:
In crontab:
@reboot root netplan apply
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Just a note to say that I found I had the same problem.
I documented it in the linked question:
https://answers.launchpad.net/ubuntu/+question/689859
I'm happy to help gather more debug information if there's a problem
reproducing it.
--
You received this bug notification because you are a
** Description changed:
[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 configuration and
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Critical
** Description changed:
- Freshly installed Ubuntu 20.04 fully patched to days date with static IP
- address works fine and
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags added: systemd-networkd
--
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
61 matches
Mail list logo
