[Bug 1736975] Re: netplan does not bring up anonymous bridge on boot
Launchpad Bug Tracker
1736975 at bugs.launchpad.net
Wed Dec 5 18:47:48 UTC 2018
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---------------
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
* tests/integration.py: add test designed to catch the above regression.
netplan.io (0.40.1~18.04.2) bionic; urgency=medium
* Fix typo breaking rename on 'netplan apply'. (LP: #1770082)
netplan.io (0.40.1~18.04.1) bionic; urgency=medium
* Backport netplan 0.40.1 to 18.04. (LP: #1793309)
netplan.io (0.40.1) cosmic; urgency=medium
* tests/generate.py: use random.sample() instead of random.choices() to
better support older pythons.
* Deal gracefully with empty files on 'netplan apply' (LP: #1795343)
netplan.io (0.40) cosmic; urgency=medium
* New upstream release:
- networkd: route source is PreferredSource= not From=
- Improve NetworkManager error reporting on unrenderable routes.
- Don't render ipv4 dns-search unless we have an ipv4 address.
(LP: #1786726)
- Set permissive umask on networkd .network, .link and .netdev files
(LP: #1736965, LP: #1768560)
- Fix support for link-scope routes. (LP: #1747455)
- Update man pages for deletion of replug code.
- Spell Gratuitous ARP correctly and make it work. (LP: #1756701)
- Many typo fixes for documentation. (LP: #1783940)
- Various build system fixes.
- Fix integration tests:
- iproute2 output changes for link-scope routes
- fix stability of networkd igmp-resend test
- fix manual_addresses test now that networkd lists ~. domain
- Deduplicate code for parsing interface options
- Add support for optional-addresses.
netplan.io (0.39) cosmic; urgency=medium
* New upstream release:
- Allow link-local addresses to be configured. (LP: #1771704)
- Forces bridges with no addresses to be brought online. (LP: #1736975)
netplan.io (0.38) cosmic; urgency=medium
* New upstream release:
- Write udev .rules files to /run/udev/rules.d to enforce interface
renaming. (LP: #1770082)
- Don't traceback for 'netplan ip leases' when iface is not managed or
doesn't DHCP (LP: #1768823)
- Fix duplicate "/" path separator in error messages (LP: #1771440)
- Fix incorrect terminal reset in 'netplan try' on Ctrl-C. (LP: #1768798)
- Updated doc entries: mtu, fix fwmark->mark, cleanup optional.
(LP: #1768783)
- Added documentation validation at build.
- Added configuration example for multi-ip interfaces.
* tests/integration.py: fix test_eth_and_bridge autopkg test harder.
* debian/control:
- Add iproute2 to Depends.
- Add python3-netifaces to Depends, Build-Depends.
-- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com> Wed, 21 Nov 2018
14:42:59 -0500
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nplan in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1736975
Title:
netplan does not bring up anonymous bridge on boot
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Triaged
Status in netplan.io source package in Bionic:
Fix Released
Bug description:
[Impact]
Netplan users setting up bridges.
[Test cases]
1) Add a new bridge configuration in netplan yaml, without an IP address set:
[...]
bridges:
br0:
interfaces: [ interface ]
dhcp4: false
parameters:
stp: false
forward-delay: 0
[Regression potential]
Possible regression scenarios might be for a configured bridge not to come up / not be created or added by systemd-networkd when the network is configured; or for a bridge to be configured with addresses that should not be present (ie. dhcp when it is not enabled, or link-local address when not configured).
---
Configuring "/etc/netplan/01-netcfg.yaml" with an anonymous bridge
seems to require running "ip link set dev br0 up" to bring the bridge
up after boot. A bridge configured with an IP address is automatically
up after boot.
This is only a problem if you want an anonymous bridge which comes up
automatically after boot. For example, if you preferred to isolate
host traffic from your autostarting virtual machine traffic.
Configuration that results in the bridge being down after boot:
network:
version: 2
renderer: networkd
ethernets:
enp22s2:
dhcp4: yes
enp22s3:
dhcp4: no
bridges:
br0:
interfaces: [enp22s3]
dhcp4: false
parameters:
stp: false
forward-delay: 0
Enabling DHCP results in a bridge that is automatically up after boot:
network:
version: 2
renderer: networkd
ethernets:
enp22s2:
dhcp4: yes
enp22s3:
dhcp4: no
bridges:
br0:
interfaces: [enp22s3]
dhcp4: true
parameters:
stp: false
forward-delay: 0
Setting a static IP address results in a bridge that is automatically up after boot:
network:
version: 2
renderer: networkd
ethernets:
enp22s2:
dhcp4: yes
enp22s3:
dhcp4: no
bridges:
br0:
interfaces: [enp22s3]
dhcp4: false
addresses: [192.168.1.100/24]
parameters:
stp: false
forward-delay: 0
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nplan 0.30
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Thu Dec 7 11:06:25 2017
ProcEnviron:
LANGUAGE=en_CA:en
TERM=screen
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: nplan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1736975/+subscriptions
More information about the foundations-bugs
mailing list