Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Fix Released
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
DHCP configurations where custom settings (MTU) need to be applied. This is a subset of the changes presented in bug 1759014.
[Test case]
1) Configure netplan for the particulars of the network by configuring an appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-
use-mtu: false
Additionally, if so required, add a custom MTU to the configuration. e.g.
mtu: 1700
(See https:/
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or NetworkManager. Existing configurations will remain unchanged, but new configurations using the dhcp{4,6}-overrides fields will benefit from additional flexibility.
---
This is very similar to https:/
I'm trying to set the MTU to 1500 and using a match on mac address, but after a netplan apply or reboot, it does not change or stick. This is on a EC2 T2.Medium instance. Actual configuration from a dev server:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 12:0f:ae:49:5d:06
mtu: 1500
dhcp4: true
nameservers:
search: [ devbuilds.vpc, ec2.internal ]
$> cat /var/run/
[Match]
MACAddress=
[Link]
WakeOnLan=off
MTUBytes=1500
$> cat /var/run/
[Match]
MACAddress=
[Network]
DHCP=ipv4
Domains=
[DHCP]
UseMTU=true
RouteMetric=100
$> ip link show eth0
2: eth0: <BROADCAST,
link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
# manually set MTU
$> sudo ip link set dev eth0 mtu 1500
$> ip link show eth0
2: eth0: <BROADCAST,
link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
$> sudo netplan generate
$> sudo netplan apply
$> ip link show eth0
2: eth0: <BROADCAST,
link/ether 12:0f:ae:49:5d:06 brd ff:ff:ff:ff:ff:ff
The last netplan commands could be replaced with a reboot with the same result. This configuration seemed to help others, so hopefully i'm simply missing something or perhaps this is related to EC2?
Attaching output of cloud-init
jd (jeff-dyke) wrote : | #1 |
Ryan Harper (raharper) wrote : Re: [Bug 1807273] [NEW] netplan not respecting mtu | #2 |
jd (jeff-dyke) wrote : | #4 |
- Files from previous post Edit (1021 bytes, text/plain)
That was my thinking as well and your correct. Attached are the data you asked for. And tested a couple different things, what i found is that this does not survive a reboot, but i'm guessing that netplay apply may get called?
I remove the mtu value from the yaml file as well, but it would seem that some sort of netplan apply gets called on reboot.
Thanks for the tips.
Ryan Harper (raharper) wrote : Re: [Bug 1807273] Re: netplan not respecting mtu | #5 |
On Thu, Dec 6, 2018 at 5:00 PM jd <email address hidden> wrote:
> That was my thinking as well and your correct. Attached are the data
> you asked for. And tested a couple different things, what i found is
> that this does not survive a reboot, but i'm guessing that netplay apply
> may get called?
>
> I remove the mtu value from the yaml file as well, but it would seem
> that some sort of netplan apply gets called on reboot.
>
Yes, it will get re-applied from the source netplan yaml
(etc/netplan/
There is upstream work to allow this to be toggled[1]. And the solution
there will
likely be storing that use-mtu: False snippet in an
/etc/systemd/
file.
It's somewhat unlikely that folks want to drop MTU when the underlying
device
can support larger ones.
1. https:/
> Thanks for the tips.
> ** Attachment added: "Files from previous post"
>
> https:/
>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https:/
>
> Title:
> netplan not respecting mtu
>
> To manage notifications about this bug go to:
> https:/
>
jd (jeff-dyke) wrote : | #6 |
I completely understand people not wanting to drop the larger MTU, but i
have a similar issue with my galera cluster that is documented with
Redshift Clusters, Since these don't reboot much i'm just going to change
them manually and see nodes dropping from the cluster stops.
It looks like a good change, but i'm a bit biased b/c of my cluster issue.
Appreciate it, i'll write back if this does indeed fix the problem.
On Thu, Dec 6, 2018 at 6:20 PM Ryan Harper <email address hidden>
wrote:
> On Thu, Dec 6, 2018 at 5:00 PM jd <email address hidden> wrote:
>
> > That was my thinking as well and your correct. Attached are the data
> > you asked for. And tested a couple different things, what i found is
> > that this does not survive a reboot, but i'm guessing that netplay apply
> > may get called?
> >
> > I remove the mtu value from the yaml file as well, but it would seem
> > that some sort of netplan apply gets called on reboot.
> >
>
> Yes, it will get re-applied from the source netplan yaml
> (etc/netplan/
>
> There is upstream work to allow this to be toggled[1]. And the solution
> there will
> likely be storing that use-mtu: False snippet in an
> /etc/systemd/
> file.
>
> It's somewhat unlikely that folks want to drop MTU when the underlying
> device
> can support larger ones.
>
> 1. https:/
>
>
> > Thanks for the tips.
>
>
> > ** Attachment added: "Files from previous post"
> >
> >
> https:/
> >
> > --
> > You received this bug notification because you are subscribed to
> > netplan.
> > Matching subscriptions: netplan
> > https:/
> >
> > Title:
> > netplan not respecting mtu
> >
> > To manage notifications about this bug go to:
> > https:/
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> netplan not respecting mtu
>
> Status in netplan:
> New
>
> Bug description:
> This is very similar to https:/
> decided to open this as i have tried what has succeeded for others.
> Thanks for any assistance.
>
> I'm trying to set the MTU to 1500 and using a match on mac address,
> but after a netplan apply or reboot, it does not change or stick. This
> is on a EC2 T2.Medium instance. Actual configuration from a dev
> server:
>
> network:
> version: 2
> ethernets:
> eth0:
> match:
> macaddress: 12:0f:ae:49:5d:06
> mtu: 1500
> dhcp4: true
> nameservers:
> search: [ devbuilds.vpc, ec2.internal ]
>
> $> cat /var/run/
> [Match]
> MACAddress=
>
> [Link]
> WakeOnLan=off
> MTUBytes=1500
>
> $> cat /var/run/
> [Match]
> MACAddress=
>
> [Network]
> DHCP=ipv4
> Domains=
>
> [DHCP]
> UseMTU=true
> RouteMetric=1...
jd (jeff-dyke) wrote : | #7 |
Looks like the PR was merged a couple hours ago, hopefully it will be
released soon. Thanks.
On Fri, Dec 7, 2018 at 11:19 AM Jeff Dyke <email address hidden> wrote:
> I completely understand people not wanting to drop the larger MTU, but i
> have a similar issue with my galera cluster that is documented with
> Redshift Clusters, Since these don't reboot much i'm just going to change
> them manually and see nodes dropping from the cluster stops.
>
> It looks like a good change, but i'm a bit biased b/c of my cluster issue.
>
> Appreciate it, i'll write back if this does indeed fix the problem.
>
>
>
> On Thu, Dec 6, 2018 at 6:20 PM Ryan Harper <email address hidden>
> wrote:
>
>> On Thu, Dec 6, 2018 at 5:00 PM jd <email address hidden> wrote:
>>
>> > That was my thinking as well and your correct. Attached are the data
>> > you asked for. And tested a couple different things, what i found is
>> > that this does not survive a reboot, but i'm guessing that netplay apply
>> > may get called?
>> >
>> > I remove the mtu value from the yaml file as well, but it would seem
>> > that some sort of netplan apply gets called on reboot.
>> >
>>
>> Yes, it will get re-applied from the source netplan yaml
>> (etc/netplan/
>>
>> There is upstream work to allow this to be toggled[1]. And the solution
>> there will
>> likely be storing that use-mtu: False snippet in an
>> /etc/systemd/
>> file.
>>
>> It's somewhat unlikely that folks want to drop MTU when the underlying
>> device
>> can support larger ones.
>>
>> 1. https:/
>>
>>
>> > Thanks for the tips.
>>
>>
>> > ** Attachment added: "Files from previous post"
>> >
>> >
>> https:/
>> >
>> > --
>> > You received this bug notification because you are subscribed to
>> > netplan.
>> > Matching subscriptions: netplan
>> > https:/
>> >
>> > Title:
>> > netplan not respecting mtu
>> >
>> > To manage notifications about this bug go to:
>> > https:/
>> >
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> netplan not respecting mtu
>>
>> Status in netplan:
>> New
>>
>> Bug description:
>> This is very similar to https:/
>> decided to open this as i have tried what has succeeded for others.
>> Thanks for any assistance.
>>
>> I'm trying to set the MTU to 1500 and using a match on mac address,
>> but after a netplan apply or reboot, it does not change or stick. This
>> is on a EC2 T2.Medium instance. Actual configuration from a dev
>> server:
>>
>> network:
>> version: 2
>> ethernets:
>> eth0:
>> match:
>> macaddress: 12:0f:ae:49:5d:06
>> mtu: 1500
>> dhcp4: true
>> nameservers:
>> search: [ devbuilds.vpc, ec2.internal ]
>>
>> $> cat /var/run/
>> [Match]
>> MACAddress=
jd (jeff-dyke) wrote : | #8 |
Just wanted to respond that after about 2 days, i've only had one drop,
which is better than what i was seeing. I know its not reboot proof, bu i
have the change in a salt state, so anytime its required to change back, i
can do so. I look forward to the release of that patch.
Thanks, please close at will.
On Fri, Dec 7, 2018 at 2:35 PM Jeff Dyke <email address hidden> wrote:
> Looks like the PR was merged a couple hours ago, hopefully it will be
> released soon. Thanks.
>
> On Fri, Dec 7, 2018 at 11:19 AM Jeff Dyke <email address hidden> wrote:
>
>> I completely understand people not wanting to drop the larger MTU, but i
>> have a similar issue with my galera cluster that is documented with
>> Redshift Clusters, Since these don't reboot much i'm just going to change
>> them manually and see nodes dropping from the cluster stops.
>>
>> It looks like a good change, but i'm a bit biased b/c of my cluster
>> issue.
>>
>> Appreciate it, i'll write back if this does indeed fix the problem.
>>
>>
>>
>> On Thu, Dec 6, 2018 at 6:20 PM Ryan Harper <email address hidden>
>> wrote:
>>
>>> On Thu, Dec 6, 2018 at 5:00 PM jd <email address hidden> wrote:
>>>
>>> > That was my thinking as well and your correct. Attached are the data
>>> > you asked for. And tested a couple different things, what i found is
>>> > that this does not survive a reboot, but i'm guessing that netplay
>>> apply
>>> > may get called?
>>> >
>>> > I remove the mtu value from the yaml file as well, but it would seem
>>> > that some sort of netplan apply gets called on reboot.
>>> >
>>>
>>> Yes, it will get re-applied from the source netplan yaml
>>> (etc/netplan/
>>>
>>> There is upstream work to allow this to be toggled[1]. And the solution
>>> there will
>>> likely be storing that use-mtu: False snippet in an
>>> /etc/systemd/
>>> file.
>>>
>>> It's somewhat unlikely that folks want to drop MTU when the underlying
>>> device
>>> can support larger ones.
>>>
>>> 1. https:/
>>>
>>>
>>> > Thanks for the tips.
>>>
>>>
>>> > ** Attachment added: "Files from previous post"
>>> >
>>> >
>>> https:/
>>> >
>>> > --
>>> > You received this bug notification because you are subscribed to
>>> > netplan.
>>> > Matching subscriptions: netplan
>>> > https:/
>>> >
>>> > Title:
>>> > netplan not respecting mtu
>>> >
>>> > To manage notifications about this bug go to:
>>> > https:/
>>> >
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https:/
>>>
>>> Title:
>>> netplan not respecting mtu
>>>
>>> Status in netplan:
>>> New
>>>
>>> Bug description:
>>> This is very similar to https:/
>>> decided to open this as i have tried what has succeeded for others.
>>> Thanks for any assistance.
>>>
>>> I'm trying to set the MTU to 1500 and using a match on mac address,
>>> but after a netplan apply or rebo...
Changed in netplan: | |
status: | New → Fix Committed |
Mathieu Trudel-Lapierre (cyphermox) wrote : | #9 |
Closing as Fix Released for upstream and for disco (netplan.io 0.95 contained the fix):
netplan.io (0.95) disco; urgency=medium
.
* New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
+ Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.
description: | updated |
Changed in netplan: | |
status: | Fix Committed → Fix Released |
Changed in netplan.io (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → In Progress |
status: | In Progress → Fix Released |
jd (jeff-dyke) wrote : | #10 |
Just wanted to say thank you!
Timo Aaltonen (tjaalton) wrote : Please test proposed package | #11 |
Hello jd, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in netplan.io (Ubuntu Cosmic): | |
status: | New → Fix Committed |
tags: | added: verification-needed verification-needed-cosmic |
Timo Aaltonen (tjaalton) wrote : | #12 |
Hello jd, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in netplan.io (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: | added: verification-needed-bionic |
Steve Langasek (vorlon) wrote : | #13 |
Hello jd, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Steve Langasek (vorlon) wrote : | #14 |
Hello jd, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Mathieu Trudel-Lapierre (cyphermox) wrote : | #15 |
Verification-done on bionic with netplan.io 0.96-0ubuntu0.
I set up a new AWS instance (t2.micro in this case); and applied a similar setup (attempting to just set mtu: 1500, that doesn't work, then using the new dhcp4-overrides feature). Forcing UseMTU=false makes the MTU apply to the interface.
ubuntu@
ii netplan.io 0.96-0ubuntu0.
ubuntu@
** (generate:2138): DEBUG: 16:30:02.609: Processing input file /etc/netplan/
** (generate:2138): DEBUG: 16:30:02.609: starting new processing pass
** (generate:2138): DEBUG: 16:30:02.609: Generating output files..
** (generate:2138): DEBUG: 16:30:02.609: NetworkManager: definition eth0 is not for us (backend 1)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eth0:
dhcp4: true
dhcp4-
use-mtu: false
match:
macaddress: 06:84:40:e0:fd:7c
mtu: 1500
set-name: eth0
vlans: {}
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:device eth0 operstate is up, not changing
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for eth0
ubuntu@
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,
link/ether 06:84:40:e0:fd:7c brd ff:ff:ff:ff:ff:ff
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Mathieu Trudel-Lapierre (cyphermox) wrote : | #16 |
Verification-done for cosmic, using netplan.io 0.96-0ubuntu0.
As for the above test, I set up a new AWS instance (t2.micro); and applied the configuration (first trying to just set mtu: 1500; then using dhcp4-overrides: { use-mtu: false }).
ubuntu@
ii netplan.io 0.96-0ubuntu0.
ubuntu@
** (generate:2737): DEBUG: 16:39:55.688: Processing input file /etc/netplan/
** (generate:2737): DEBUG: 16:39:55.689: starting new processing pass
** (generate:2737): DEBUG: 16:39:55.689: Generating output files..
** (generate:2737): DEBUG: 16:39:55.689: NetworkManager: definition eth0 is not for us (backend 1)
(generate:2737): GLib-DEBUG: 16:39:55.689: posix_spawn avoided (fd close requested)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eth0:
dhcp4: true
dhcp4-
use-mtu: false
match:
macaddress: 06:9d:85:76:e2:b2
mtu: 1500
set-name: eth0
vlans: {}
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:device eth0 operstate is up, not changing
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for eth0
ubuntu@
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,
link/ether 06:9d:85:76:e2:b2 brd ff:ff:ff:ff:ff:ff
tags: |
added: verification-done-cosmic removed: verification-needed verification-needed-cosmic |
Steve Langasek (vorlon) wrote : | #17 |
Hello jd, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
tags: |
added: verification-needed verification-needed-bionic removed: verification-done-bionic |
Mathieu Trudel-Lapierre (cyphermox) wrote : | #18 |
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior.
tags: |
added: verification-done-bionic removed: verification-needed verification-needed-bionic |
Launchpad Janitor (janitor) wrote : | #19 |
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.
---------------
netplan.io (0.96-0ubuntu0.
* d/p/0001-
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-
minimal setups there might be no job requiring network-
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)
netplan.io (0.96-0ubuntu0.
* Backport netplan.io 0.96 to 18.10.
* debian/
* debian/control: adjust Depends for cosmic / re-add nplan package.
netplan.io (0.96-0ubuntu1) disco; urgency=medium
* New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
* debian/control: Update Maintainer for ubuntu upload.
netplan.io (0.95-2) unstable; urgency=medium
* Set Priority to optional (Closes: #920327).
netplan.io (0.95-1) unstable; urgency=medium
* New upstream release.
* Update autopkgtests from the upstream.
* Add debian/watch following GitHub releases.
* Add Homepage (Closes: #917233).
netplan.io (0.95) disco; urgency=medium
* New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
+ Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.
netplan.io (0.90.1) disco; urgency=medium
* Do not assume /etc/network exists in postinst, as netbase 5.5 no longer
creates it.
* netplan/
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)
-...
Changed in netplan.io (Ubuntu Cosmic): | |
status: | Fix Committed → Fix Released |
Brian Murray (brian-murray) wrote : Update Released | #20 |
The verification of the Stable Release Update for netplan.io has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
Steve Langasek (vorlon) wrote : | #21 |
A possible SRU regression has been reported against netplan.io 0.96-0ubuntu0.
Changed in netplan.io (Ubuntu Cosmic): | |
status: | Fix Released → Fix Committed |
Brian Murray (brian-murray) wrote : Please test proposed package | #22 |
Hello jd, or anyone else affected,
Accepted netplan.io into cosmic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
tags: |
added: verification-needed verification-needed-cosmic removed: verification-done-cosmic |
Brian Murray (brian-murray) wrote : | #23 |
Hello jd, or anyone else affected,
Accepted netplan.io into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
tags: |
added: verification-needed-bionic removed: verification-done-bionic |
Mathieu Trudel-Lapierre (cyphermox) wrote : | #24 |
Verification-done for cosmic:
ubuntu@
cosmic
ubuntu@
netplan.io:
Installed: 0.96-0ubuntu0.
Candidate: 0.96-0ubuntu0.
Version table:
*** 0.96-0ubuntu0.
500 http://
100 /var/lib/
0.40.2.2 500
500 http://
0.40.2 500
500 http://
ubuntu@
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
mtu: 1700
match:
ubuntu@
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 06:24:03:7d:3e:ec brd ff:ff:ff:ff:ff:ff
inet 172.30.0.50/24 brd 172.30.0.255 scope global dynamic eth0
valid_lft 3593sec preferred_lft 3593sec
inet6 fe80::424:
valid_lft forever preferred_lft forever
Mathieu Trudel-Lapierre (cyphermox) wrote : | #25 |
Verification-done for bionic:
ubuntu@
bionic
ubuntu@
netplan.io:
Installed: 0.96-0ubuntu0.
Candidate: 0.96-0ubuntu0.
Version table:
*** 0.96-0ubuntu0.
500 http://
100 /var/lib/
0.40.1~18.04.4 500
500 http://
500 http://
0.36.1 500
500 http://
ubuntu@
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
mtu: 1789
match:
ubuntu@
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 06:12:92:f8:f9:c8 brd ff:ff:ff:ff:ff:ff
inet 172.30.0.32/24 brd 172.30.0.255 scope global dynamic eth0
valid_lft 3595sec preferred_lft 3595sec
inet6 fe80::412:
valid_lft forever preferred_lft forever
tags: |
added: verification-done-bionic verification-done-cosmic removed: verification-needed verification-needed-bionic verification-needed-cosmic |
Launchpad Janitor (janitor) wrote : | #26 |
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.
---------------
netplan.io (0.96-0ubuntu0.
* debian/
commit ebc212a: make renderer values explicit at the end of each parsing
pass; it breaks "default" renderer behavior when multiple files may set
a global renderer and expect the last to take effect globally.
(LP: #1825206)
* debian/
fallout from the above change: validate netdefs in a single pass at the
very end of parsing, once we know which is the applicable renderer. This
makes sure tunnels get validated correctly.
netplan.io (0.96-0ubuntu0.
* debian/
GRE tunnel tests; those appear to be broken because neither the kernel nor
networkd bring up the device automatically as in other releases.
netplan.io (0.96-0ubuntu0.
* d/p/0001-
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-
minimal setups there might be no job requiring network-
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)
netplan.io (0.96-0ubuntu0.
* Backport netplan.io 0.96 to 18.04.
* debian/
* debian/control: adjust Depends for bionic / re-add nplan package.
netplan.io (0.96-0ubuntu1) disco; urgency=medium
* New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
* debian/control: Update Maintainer for ubuntu upload.
netplan.io (0.95-2) unstable; urgency=medium
* Set Priority to optional (Closes: #920327).
netplan.io (0.95-1) unstable; urgency=medium
* New upstream release.
* Update autopkgtests from the upstream.
* Add debian/watch following GitHub releases.
* Add Homepage (Closes: #917233).
netplan.io (0.95) disco; urgency=medium
* New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
+ Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control ...
Changed in netplan.io (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #27 |
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.
---------------
netplan.io (0.96-0ubuntu0.
* debian/
commit ebc212a: make renderer values explicit at the end of each parsing
pass; it breaks "default" renderer behavior when multiple files may set
a global renderer and expect the last to take effect globally.
(LP: #1825206)
* debian/
fallout from the above change: validate netdefs in a single pass at the
very end of parsing, once we know which is the applicable renderer. This
makes sure tunnels get validated correctly.
netplan.io (0.96-0ubuntu0.
* d/p/0001-
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-
minimal setups there might be no job requiring network-
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)
netplan.io (0.96-0ubuntu0.
* Backport netplan.io 0.96 to 18.10.
* debian/
* debian/control: adjust Depends for cosmic / re-add nplan package.
netplan.io (0.96-0ubuntu1) disco; urgency=medium
* New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
* debian/control: Update Maintainer for ubuntu upload.
netplan.io (0.95-2) unstable; urgency=medium
* Set Priority to optional (Closes: #920327).
netplan.io (0.95-1) unstable; urgency=medium
* New upstream release.
* Update autopkgtests from the upstream.
* Add debian/watch following GitHub releases.
* Add Homepage (Closes: #917233).
netplan.io (0.95) disco; urgency=medium
* New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
+ Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.
netplan.io (0.90.1) disco; urgency=medium
* Do ...
Changed in netplan.io (Ubuntu Cosmic): | |
status: | Fix Committed → Fix Released |
Erwin Hager (errieman) wrote : | #28 |
This bug is still present in 0.98-0ubuntu1~
On Thu, Dec 6, 2018 at 3:40 PM jd <email address hidden> wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1724895, but I systemd/ network/ 10-netplan- eth0.link 12:0f:ae: 49:5d:06 systemd/ network/ 10-netplan- eth0.network 12:0f:ae: 49:5d:06 devbuilds. vpc ec2.internal
>
> This is very similar to https:/
> decided to open this as i have tried what has succeeded for others.
> Thanks for any assistance.
>
> I'm trying to set the MTU to 1500 and using a match on mac address, but
> after a netplan apply or reboot, it does not change or stick. This is on
> a EC2 T2.Medium instance. Actual configuration from a dev server:
>
> network:
> version: 2
> ethernets:
> eth0:
> match:
> macaddress: 12:0f:ae:49:5d:06
> mtu: 1500
> dhcp4: true
> nameservers:
> search: [ devbuilds.vpc, ec2.internal ]
>
> $> cat /var/run/
> [Match]
> MACAddress=
>
> [Link]
> WakeOnLan=off
> MTUBytes=1500
>
> $> cat /var/run/
> [Match]
> MACAddress=
>
> [Network]
> DHCP=ipv4
> Domains=
>
> [DHCP]
> UseMTU=true
> RouteMetric=100
>
>
I have a hunch that the ec2 DHCP response includes an MTU of 9001. You can
do two things:
Attach the contents of netif/*
1) /run/systemd/
Under /run/systemd/ netif/leases/ <number> , networkd stores the DHCP response
2) in /run/systemd/ networkd/ 10-netplan- eth0.network
a) Modify UseMTU=true, to UseMTU=False
b) ip link set dev eth0 mtu 1500
c) sudo systemctl restart systemd-networkd
Note, I don't think this will drop your connection, but it's possible.