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/1745597
Title:
mii-monitor-interval unit is undocumented, and may be wrong
Status in netplan:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in nplan source package in Xenial:
Fix Released
Status in nplan source package in Artful:
Fix Released
Bug description:
[Impact]
Users of bond and bridges devices requiring tuning of the default device
parameters.
[Test case]
== Configure MII monitor interval ==
1) Configure a bond device
2) Add parameters:
bonds:
mybond0:
parameters:
mii-monitor-interval: 1
3) Verify that the applied MII monitor interval is of 1ms, as opposed
to 1 second (1000ms), by verifying the contents of
/sys/class/net/mybond0/bonding/miimon
== Validate default behavior ==
1) Configure a bond device without parameters.
2) Verify that no special MII monitor interval is applied, the default value
should be 0:
$ cat /sys/class/net/mybond0/bonding/miimon
0
[Regression potential]
MII monitor behavior is changing with this SRU. Default behavior for an
unqualified value (ie. a number alone), which was also the only way to specify
parameters, was to interpret the values as *seconds*. This leads to relatively
slow checking of the device link status (for MII monitor), much slower than
generally expected. The same applies to other time-based values such as up
delay, down delay, arp interval. The interpretation for these values changes to
reading them as *milliseconds* when unqualified, and a new way of qualifying
the values (adding a modifier) was added. This was, people who do require
"slow" checking of the MII link status will be migrated to "fast" checking
right now, moving from an interval of 1 second to 1 millisecond (more checking
means less false-negatives for packet passing through an interface, should
reduce packet loss, at the cost of potentially flapping the interfaces
(bringing down a path often if MII status is bad or slow to be returned)).
Users who require the old behavior may add "s" at the end of the value to make
it read as "1 second" again, or modify the value to be "1000", which will be
1000ms (1 second). We estimate the impact of this change to users to be
minimal, actually requiring a 1 second interval for MII monitoring / up/down
delay, and ARP interval is very uncommon and counter-intuitive as all other
systems work on a millisecond basis.
---
The manpage for netplan doesn't indicate what the unit for mii-
monitor-interval is on bond devices. It appears to be in whole
seconds, but at the kernel level, the unit is milliseconds.
From my testing, it appears to be impossible to set a value for mii-
monitor-interval with netplan that is <1s (e.g. I got a syntax error
with a value of 0.1 for 100ms)
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1745597/+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
