From patchwork Thu Apr 11 15:01:04 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 7729 Return-Path: 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 ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4VFjZc6t8rz3wwD for ; Thu, 11 Apr 2024 15:01:28 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) client-signature ECDSA (secp384r1)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4VFjZY4fJWz5VN; Thu, 11 Apr 2024 15:01:25 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4VFjZY40yWz32qT; Thu, 11 Apr 2024 15:01:25 +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 ECDSA (secp384r1)) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4VFjZQ0Tr8z32qL for ; Thu, 11 Apr 2024 15:01:18 +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 ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4VFjZP6CJqzGf; Thu, 11 Apr 2024 15:01:17 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1712847677; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uFRFoQJrXtur6OfMURUPITgYQ7mh3ZyExIUnSk7t9xs=; b=n2N2GvGsiWRYJ42iquYvF4iJ9DI7DQl12tq4cVhWRkGWSPgHqoppLIgua/TrLEstCEWcAg VzAqW9MbhOT2lJCQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1712847677; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uFRFoQJrXtur6OfMURUPITgYQ7mh3ZyExIUnSk7t9xs=; b=qWEI1DlwPx9fRTNxTfNbucQ77KrOsOE0Q4ziPEYp1Pm4xfhLmgARY5E9RE2DQ3fv6ODBl3 OLTltA/WAVxQojCO6iBD/XY588QY0jxRILggWcE3ZMEP3QVEHW//i79IaEHaEpZvcb52PI cTOIZ9dLWrDLMSxT0wrzZmd7Q1LMTM6zhdTRyg7NBtP2rUK+ndnMy4hoYnoHK5Oi5d/Rr6 P8PkLmDaMxw+GTf7vCGY0xk2q6aHGEG1bOwX5T7mIfONjs8OAfAskmuOTUBZ1LgKGH66re 4j3lynHky750GahM5a6pjTP7VsMTmi/lMMLFIIcl5m+KBT4bXzRDlK7ulQCPMA== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH 5/9] aws-setup: Fixes bug12763 Date: Thu, 11 Apr 2024 17:01:04 +0200 Message-ID: <20240411150108.21573-5-adolf.belka@ipfire.org> In-Reply-To: <20240411150108.21573-1-adolf.belka@ipfire.org> References: <20240411150108.21573-1-adolf.belka@ipfire.org> MIME-Version: 1.0 Message-ID-Hash: 4LC33CURD7M2JSRGIK56TEZQMZUP5K5J X-Message-ID-Hash: 4LC33CURD7M2JSRGIK56TEZQMZUP5K5J X-MailFrom: adolf.belka@ipfire.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: IPFire development talk Archived-At: <> List-Archive: <> List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: - This ensures that all ip route and ip rule commands are redirected to null if the output is not used to feed into a variable. - This will prevent any error messages related to empty iproute tables being displayed during boot if an empty table is accessed. Fixes: Bug#12763 Tested-by: Adolf Belka Signed-off-by: Adolf Belka --- src/initscripts/helper/aws-setup | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/initscripts/helper/aws-setup b/src/initscripts/helper/aws-setup index f14f4eb57..0bcf75572 100644 --- a/src/initscripts/helper/aws-setup +++ b/src/initscripts/helper/aws-setup @@ -278,7 +278,7 @@ case "${reason}" in ip addr add "${new_ip_address}/${new_subnet_mask}" dev "${interface}" # Add the default route - ip route add default via "${new_routers}" + ip route add default via "${new_routers}" >/dev/null 2>&1 # Setup DNS for domain_name_server in ${new_domain_name_servers}; do