There is an error in the bridging section. The config file needs to
include a definition for the adapter. Formatting may not look great in
email but the config file should look like this:
Also the usage of true/false and yes/no should probably stay consistent in
the documentation. The default config file has "dhcp4: yes" so my vote
would be stick with "yes" and "no" in the documentation. However the
documentation mostly uses "true" or "false" but has "dhcp4: yes" in the
bridging section. I think should either change that to "dhcp4: true" to
keep the documentation consistent, or switch all the documentation to using
"yes" and "no" to stay consistent with the default config file.
On Tue, Jun 5, 2018 at 9:09 AM, Doug Smythies <email address hidden>
wrote:
There is an error in the bridging section. The config file needs to
include a definition for the adapter. Formatting may not look great in
email but the config file should look like this:
network:
version: 2
renderer: networkd
ethernets:
enp3s0:
dhcp4: no
bridges:
br0:
dhcp4: yes
interfaces:
- enp3s0
Also the usage of true/false and yes/no should probably stay consistent in
the documentation. The default config file has "dhcp4: yes" so my vote
would be stick with "yes" and "no" in the documentation. However the
documentation mostly uses "true" or "false" but has "dhcp4: yes" in the
bridging section. I think should either change that to "dhcp4: true" to
keep the documentation consistent, or switch all the documentation to using
"yes" and "no" to stay consistent with the default config file.
On Tue, Jun 5, 2018 at 9:09 AM, Doug Smythies <email address hidden>
wrote:
> ** Changed in: serverguide /bugs.launchpad .net/bugs/ 1769007 /bugs.launchpad .net/serverguid e/+bug/ 1769007/ +subscriptions
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Server networking should be updated for systemd-networkd
>
> To manage notifications about this bug go to:
> https:/
>