From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4hKrgZ6RPpz36WP for ; Wed, 12 Aug 2026 14:37:46 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4hKrgW3VGVz2xHk for ; Wed, 12 Aug 2026 14:37:43 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4hKrgK55l8z16j; Wed, 12 Aug 2026 14:37:33 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1786545453; 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=9ET0D3WqmnghZKsiLAn1FICMqLB0qFZzRPy8T8+HMu4=; b=xIWlyH9nz/qnBBYpHfzBoQrUy7Imybgk7aHcNcZlbOtM9nfq9y8CqS6XOXJNvUKf1ceYfH BQ6+vKjOX4D2aFBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1786545453; 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=9ET0D3WqmnghZKsiLAn1FICMqLB0qFZzRPy8T8+HMu4=; b=tZxlX7FhSc6tLM9rlYGebxlKGCWkBp0uC3worRYETkInthqTmYl7lnaJ+rg5dQHHKsx9Gl 7G4neSPWMb2E7zq96+SO8ahNBudwL/uEBrEsGwfAbz1YsIuvK8DUQvuaFH0oZO7omJvEBe G/q9ROoO7s52AyP6JcafEuSqqE40+v0O1lyfY4TGNLniLwXSqB29CxA1/0wxS8V56jYGWF PkAAK+kwbsT6gYpzCyJUOYU3Haawu8W4gAx07Qu1Es2BjMexuBrRujrvqZfFfx4bGPI+NT HB9gwTBfKs3OiWTCebtUqZ2P+EaUleDFyigy6j5sqaMgZxeYKI6UX2RDtO3OUQ== Message-ID: <19524079-91de-4ff1-8c5d-b1556978e079@ipfire.org> Date: Wed, 12 Aug 2026 16:37:26 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Warning about dhcpcd-10.5.0 with arm Content-Language: en-US To: Adolf Belka References: Cc: "IPFire: Development-List" From: Matthias Fischer In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 12.08.2026 12:58, Adolf Belka wrote: > Hi All, Hi Adolf, see comments below... ;-) > Some information. I have a RPi with Arch Linux installed on it which I > use as my dhcp server on my orange network. > > The Arch Linux ARM group are separate from Arch Linux. They had not done > an update to 10.4.x so I was still on 10.3.2. > > I ran an update and they updated dhcpcd to 10.5.0 > > After the update dhcpcd failed to start and the logs showed it was > having a core dump when trying to start. > > I downgraded to 10.2.3 and everything worked fine, Upgraded to 10.5.0 > again and it had the core dump again and downgrading again made it work. > > So on my arm based rpi with arch linux I am staying with 10.3.2 for the > moment. > > It would probably be worth testing the 10.5.0 version on an arm IPFire > to see if it is a general issue or only for some hardware/os combinations. I compiled and pushed dhcpcd 10.5.0 a few days ago and got it running since then on Core 203 (x86_64). No seen problems so far - its running now for 5 days 17 hours 6 minutes (watched by 'monit'). ... root@ipfire: / # dhcpcd --version dhcpcd 10.5.0 Copyright (c) 2006-2025 Roy Marples Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP ... You can find it here: => https://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=c3df7efed69554c7f83e74c4d3a895cd77045dd4 HTH Matthias