From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka 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 Message-ID: <452a98a2-d939-4180-be81-e84244409d41@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1865141901051530881==" List-Id: --===============1865141901051530881== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 se= lection 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 ha= ve 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/5ac1235b99d33085d0574ef= 81b95ceafcf79db34 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 b= e in line with what we want to have but I have no idea of how to test this an= d 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. --===============1865141901051530881==--