From d630415261213025c14d6d3c1267c971dc9fae0e Mon Sep 17 00:00:00 2001 From: Ornela Maric Date: Wed, 12 Nov 2025 17:16:51 +0100 Subject: [PATCH] Cont. --- CHANGELOG.md | 2 ++ .../pages/network-requirements.adoc | 7 +++++++ 2 files changed, 9 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8ffd9f872cb..9672348f782 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,5 @@ +- Added non-SUSE URLs to requirements in installation and Upgrade + Guide (bsc#1252665) - Fixed wrong --ssl-db-server-{cert|key} parameters in Specialized Guides (bsc#1249462) - Added additional step for client deletion in Client Configuration diff --git a/modules/installation-and-upgrade/pages/network-requirements.adoc b/modules/installation-and-upgrade/pages/network-requirements.adoc index e74d5310771..c4e22ac67c2 100644 --- a/modules/installation-and-upgrade/pages/network-requirements.adoc +++ b/modules/installation-and-upgrade/pages/network-requirements.adoc @@ -314,6 +314,13 @@ In most cases, allowing access to these URLs is sufficient: * [literal]``installer-updates.suse.com`` * [literal]``registry.suse.com`` * [literal]``registry-storage.suse.com`` +* [literal]``opensuse.org`` + +Additionally, you may need access to these URLs for non-SUSE products: + +* [literal]``download.nvidia.com`` +* [literal]``public.dhe.ibm.com`` +* [literal]``nu.novell.com`` You can find additional details on whitelisting the specified URLs and their associated IP addresses in this article: https://www.suse.com/support/kb/doc/?id=000021034[Accessing {scclongform} and SUSE registry behind a firewall and/or through a proxy].