This bug was fixed in the package nplan - 0.32~17.10.4
---------------
nplan (0.32~17.10.4) artful; urgency=medium
* bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
* debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
denote the migration to using netplan. (LP: #1756742)
* DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
with Windows Server-based DHCP servers which don't support RFC 4361.
(LP: #1738998)
* IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
* doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
* critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
* networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)
-- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Tue, 08 May 2018
11:04:30 -0400
** Changed in: nplan (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756587
Title:
mii-mon should have a consistent unit schema
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Invalid
Status in netplan.io source package in Xenial:
Invalid
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Artful:
Invalid
Status in nplan source package in Artful:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Status in nplan source package in Bionic:
Invalid
Bug description:
[Impact]
Documentation is confusing to users wishing to tune bond and bridge
parameters. This potentially affects all users of netplan.
[Test case]
1) Update the netplan.io package.
2) Run 'man netplan'
3) Verify that the documentation under "parameters" for bridges and bonds is
clear that time-based parameters are in milliseconds unless otherwise specified
by the individual parameter:
For example, in the bonds section:
- learn-packet-interval is in seconds
- mii-monitor-interval, up-delay, down-delay, arp-interval are in
milliseconds
[Regression potential]
Change is limited to the manpage; there is no risk of regression there,
except for a garbled manpage or missing file. Any new bugs in netplan behavior
found after this SRU that can't be reproduced with the immediately previous
version should be investigated as potential toolchain / build issues introduced
by the new build required for the SRU.
---
The docs say "Using the NetworkManager renderer, parameter values for
intervals should be expressed in milliseconds; for the systemd
renderer, they should be in seconds unless otherwise specified."
This however fails to encapsulate the description of the network in a
form abstracted from the renderer. We should have a scheme which is
clear, has one and only one explicit form, and works with all
renderers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1756587/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
