From patchwork Thu Apr 11 15:01:05 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 7730 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 4VFjZt1KHfz3wwD for ; Thu, 11 Apr 2024 15:01:42 +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 4VFjZc6jkJz5XX; Thu, 11 Apr 2024 15:01:28 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4VFjZZ5FtYz32qT; Thu, 11 Apr 2024 15:01:26 +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 4VFjZQ1tJpz32qL 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 4VFjZQ0Tw6z1Gx; Thu, 11 Apr 2024 15:01:18 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1712847678; 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=GHsaisqKV4CphJXmEJ3ohbNa2MiiewSeq5Ip3qOoN4s=; b=/8MP1OyFrZ94o1RM+a9ozBtpBh4uiKcxk3tt1sLa8LuSkQTon99cBS6MC9COrOWkMB9hso scH6m1F3sUbLtrDA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1712847678; 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=GHsaisqKV4CphJXmEJ3ohbNa2MiiewSeq5Ip3qOoN4s=; b=thZk7Rg+nbVnz3gzm1pVEHY+o00mn9kPCtafKozj4wNwIw/NIoc21rOAUIgRybI4lH+E37 9d7XRyFGBfvSHPi6Gvjx70XMEhv6rSPwuN08y8ytA+hGVCvqOJZA0LlBSLa55fsOef2ec8 pFSyrnRpWjJ6Nii/ZWB6de2HNUSNNyTq2j79zqX8rpNeJff09U5oZ8bd/bRIcp2Ov40PFl PrNHhr3sdpRRaANkQnDAH9gAKuHtByhjMRhJ+HW7vTwU/drlgRHRXT/hSmf6nnq0H9y+89 QSLwcnkOYuMlp7cIV4KV4ZKPcHXfGwsK8vOQfTXH2zr9yZHghOKvELE+SvbRiw== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH 6/9] azure-setup: Fixes bug12763 Date: Thu, 11 Apr 2024 17:01:05 +0200 Message-ID: <20240411150108.21573-6-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: 5ZLA4T2667MEVVZ4U7A52NKKVZF7QL4P X-Message-ID-Hash: 5ZLA4T2667MEVVZ4U7A52NKKVZF7QL4P 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/azure-setup | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/initscripts/helper/azure-setup b/src/initscripts/helper/azure-setup index 7a4422a35..eff963a4b 100644 --- a/src/initscripts/helper/azure-setup +++ b/src/initscripts/helper/azure-setup @@ -298,7 +298,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