From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4b5Wq023pQz32wX for ; Mon, 26 May 2025 10:15:08 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4b5Wpw5XMnz2xng for ; Mon, 26 May 2025 10:15:04 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4b5Wpt4cmtz26T; Mon, 26 May 2025 10:15:02 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1748254504; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BkQJoaZ4pFe/PySLA5QN5OPvKXu+HHDjiP9ELSDg4TY=; b=NfCZZ5CCVB1+6wK3jzRM2JdVjmvV++VZU/yolSd1tj2pw6QMUOmrfwUJ1rEtdItlM322Kx OxNCbyY8I7+/QGAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1748254504; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BkQJoaZ4pFe/PySLA5QN5OPvKXu+HHDjiP9ELSDg4TY=; b=XIdW/8vCkKGQlFyQ6SeSWrA+w01vDv8cxB2BAoXHx/bZCD1oQFpQ8AonmkVMKhkYZ+48ll vLttrtCBXUw50RXijCFKGJNU25jRwG30fh+sOQeY9MLw+qgZw880idoT/tyS2HSDpALuy7 UYR8g8IFxEcDHERzL6h6kFzbboAGzVMxW8wNxNf/V9ZVzg2MXH8p7wgSR5PFvwGUlonEZp kun9nCEgUdaxYIcXvTaqBCRNtPDeguyGEJth43ZK5wsY2hVRhmW6wXz6wTBli8VA/Em+Rm fHYqKvO1KioAi44eh9vQiAS4BGjkbtV9gSQVCnh8XlzeG6044BdJL6jugoJ96Q== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: dhcpcd has removed the rapid_commit option From: Michael Tremer In-Reply-To: <2034be1a-fd2d-41c6-9be1-b9bf6900cbeb@ipfire.org> Date: Mon, 26 May 2025 11:14:54 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2034be1a-fd2d-41c6-9be1-b9bf6900cbeb@ipfire.org> To: Adolf Belka Hello Adolf, That is not surprising at all then. I was wondering how the default = would work in other places when it could not have. I suppose all the downsides are still there, so making it configurable = is not a bad idea. This would reflect our current implementation. Best, -Michael > On 19 May 2025, at 13:47, Adolf Belka wrote: >=20 > Hi All, >=20 > In the latest dhcpcd-10.2.3 release they have removed the rapid_commit = option from their standard dhcpcd.conf file. >=20 > Their commit message for the change is >=20 > "dhcpcd: Remove option rapid_commit from dhcpcd.conf > Apparently some ISPs report they support it by sending the option > back, but the reality is they don't." >=20 > The option will still work with ISP's that properly support it so I = don't believe that we need to change anything as we can either run with = the option or without via the setup program. >=20 > So we weren't the only ones having problems. >=20 > Regards, >=20 > Adolf. >=20