From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: The MTU definition part of dhcpcd has been rewritten in version 10.0.10
Date: Mon, 02 Sep 2024 18:29:02 +0200 [thread overview]
Message-ID: <452a98a2-d939-4180-be81-e84244409d41@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Dear All,
dhcpcd-10.0.10 is available but I noticed that a change has been made in the mtu definition section that means that the patch we have had to allow free selection of the MTU by the user will not apply.
I have had a look through the changes but I can not determine if what they have done will give us the equivalent of the patched result we used to have or if a totally new patch needs to be created to deal with the changed coding.
The commit with the change is
https://github.com/NetworkConfiguration/dhcpcd/commit/5ac1235b99d33085d0574ef81b95ceafcf79db34
The issue that triggered the change
https://github.com/NetworkConfiguration/dhcpcd/pull/346
is labelled "No longer set interface mtu" which would suggest that it might be in line with what we want to have but I have no idea of how to test this and I don't understand the changes well enough to know if give us the result of users having free selection of the mtu.
Can someone more experienced look through the changes to see if they are okay, before I look at doing a package update build for the updated version.
Regards,
Adolf.
next reply other threads:[~2024-09-02 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 16:29 Adolf Belka [this message]
2024-09-03 7:45 ` Michael Tremer
2024-09-03 8:22 ` Nick Howitt
2024-09-03 8:24 ` Michael Tremer
2024-09-04 7:54 ` Adolf Belka
2024-09-04 9:25 ` Adolf Belka
2024-09-04 9:33 ` Michael Tremer
2024-09-04 9:46 ` Adolf Belka
2024-09-04 19:39 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452a98a2-d939-4180-be81-e84244409d41@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox