Clarify MAC and MTU setting requirements
Bug #1800668 reported by
Mathieu Trudel-Lapierre
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
High
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Documentation for netplan.
[Test case]
Run 'man netplan'; validate that the documentation clearly states that setting MTU requires matching by MAC address; under the 'mtu' section.
[Regression potential]
None; this is limited to documentation.
---
We already document that you should match by MAC when setting MTU.
Because MAC addresses are set in the link file as well, they should
also specify a MAC.
Also point out that the restriction only applies to networkd.
Changed in netplan: | |
status: | New → Fix Committed |
importance: | Undecided → High |
Changed in netplan: | |
status: | Fix Committed → Fix Released |
description: | updated |
To post a comment you must log in.
This bug was fixed in the package netplan.io - 0.90
---------------
netplan.io (0.90) disco; urgency=medium
* New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection (LP: #1770082)
- Add support for IPv6 Privacy Extensions (LP: #1750392)
- Add dhcp{4,6}-overrides to control DNS, NTP, hostname updates via DHCP
(LP: #1759014)
- Clarify MAC and MTU setting requirements (LP: #1800668)
- Various documentation fixes (LP: #1800669)
- Improve error reporting to give clearer messages and context
(LP: #1800670)
- Skip non-physical/bond interfaces when applying renames (LP: #1802322)
-- Mathieu Trudel-Lapierre <email address hidden> Wed, 21 Nov 2018 14:06:13 -0500