Guide: Network Configuration by Region - Revision history

Sia at 06:56, 26 March 2026

2026-03-26T06:56:11Z

← Older revision		Revision as of 06:56, 26 March 2026
Line 84:		Line 84:
	* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	Once assigned, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.		Once assigned to a project, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.

	=== Flat External Networks ===		=== Flat External Networks ===

Qw7402 at 19:04, 17 March 2026

2026-03-17T19:04:45Z

← Older revision		Revision as of 19:04, 17 March 2026
Line 41:		Line 41:
	* receive a separate public IPv6 Subnet		* receive a separate public IPv6 Subnet
	* have a separated Broadcast Domain only accessible by authorized projects		* have a separated Broadcast Domain only accessible by authorized projects
	* always use up at least one IPv4 used for the virtual Router		* always use up at least one public IPv4 used for the virtual Router

	=== Migration from Gen2 to Gen3 ===		=== Migration from Gen2 to Gen3 ===

Sia at 18:20, 17 March 2026

2026-03-17T18:20:29Z

← Older revision		Revision as of 18:20, 17 March 2026
Line 115:		Line 115:
	* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.		* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.

	📌 '''Note:''' We do not recommend allocating Floating IPs from the <code>provider_interim_net</code>, because they will be lost after the transition period. Instead, ~~Request~~ and associate them from <code>provider_default_net</code>.		📌 '''Note:''' We do not recommend allocating Floating IPs from the <code>provider_interim_net</code>, because they will be lost after the transition period. Instead, request and associate them from <code>provider_default_net</code>.

Sia at 18:17, 17 March 2026

2026-03-17T18:17:52Z

← Older revision		Revision as of 18:17, 17 March 2026
Line 63:		Line 63:
	== Mannheim ==		== Mannheim ==

	The Mannheim region provides a '''default routed network''', as well as additional networks that can be assigned to projects upon request. Both IPv6 and IPv4 connectivity options are available, depending on the selected network.		The Mannheim region provides a '''default routed network''', as well as '''additional networks''' that can be assigned to projects '''upon request'''. Both IPv6 and IPv4 connectivity options are available, depending on the selected network.

	=== Default Network ===		=== Default Network ===
Line 74:		Line 74:
	This is a '''routed network''' using an OpenStack router connected to an external provider network:		This is a '''routed network''' using an OpenStack router connected to an external provider network:

	* IPv6: Direct public connectivity		* '''IPv6''': Direct public connectivity
	* IPv4 (egress): Provided via '''SNAT''' through the router		* '''IPv4 (egress)''': Provided via '''SNAT''' through the router
	* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])		* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])
	📌 '''Note:''' This network extends the legacy IPv6-only network in the Mannheim region, which did not provide IPv4 connectivity. ''Before requesting an IPv4 address via a support ticket, please ensure that the combined connectivity is not already sufficient for your use case.''		📌 '''Note:''' This network extends the legacy IPv6-only network in the Mannheim region, which did not provide IPv4 connectivity. ''Before requesting an IPv4 address via a support ticket, please ensure that the combined connectivity is not already sufficient for your use case.''
Line 84:		Line 84:
	* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.		* They can be assigned to projects upon request via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	Once assigned, a Floating IP can be associated with an instance to provide IPv4 ingress connectivity.		Once assigned, a Floating IP can be associated with an instance to provide '''IPv4 ingress connectivity'''.

	=== Flat External Networks ===		=== Flat External Networks ===
Line 93:		Line 93:
	Instances connected directly to this type of network receive:		Instances connected directly to this type of network receive:

	* A public IPv4 address		* A '''public IPv4 address'''
	* A public IPv6 address		* A '''public IPv6 address'''

	This enables dual-stack public connectivity (IPv4 and IPv6) without the need for Floating IPs.		This enables dual-stack public connectivity (IPv4 and IPv6) without the need for Floating IPs.
Line 112:		Line 112:
	After the transition period:		After the transition period:

	* All IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>. This migration will be performed by administrators; no user action is required.		* All dual-stack IP addresses from <code>provider_interim_net</code> will be migrated to <code>provider_default_net</code>. This migration will be performed by administrators; no user action is required.
	* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.		* Projects requiring a flat external network will be assigned <code>provider_default_net</code>.

			📌 '''Note:''' We do not recommend allocating Floating IPs from the <code>provider_interim_net</code>, because they will be lost after the transition period. Instead, Request and associate them from <code>provider_default_net</code>.


	== Ulm ==		== Ulm ==

	Information for this region will be provided soon.		Information for this region will be provided soon.

Sia: /* Default Network */

2026-03-17T18:00:10Z

Default Network

← Older revision		Revision as of 18:00, 17 March 2026
Line 72:		Line 72:
	** A '''private IPv4 address'''		** A '''private IPv4 address'''

	This is a '''routed network''' using an OpenStack router connected to an external provider network.		This is a '''routed network''' using an OpenStack router connected to an external provider network:

	* IPv6: Direct public connectivity		* IPv6: Direct public connectivity

Qw7402 at 17:51, 17 March 2026

2026-03-17T17:51:26Z

← Older revision		Revision as of 17:51, 17 March 2026
Line 34:		Line 34:

	=== Seperated Networks ===		=== Seperated Networks ===
	If you require a seperated Broadcast Domain you can request one via a support ticket.		If you require a seperated Broadcast Domain you can request one via a '''[https://bw-support.scc.kit.edu/ support ticket]'''.

	The network will:		The network will:

Qw7402 at 17:49, 17 March 2026

2026-03-17T17:49:56Z

@@ Line 11: / Line 11: @@
 == Karlsruhe ==
-*Information for this region will be provided soon.*
+The Karlsruhe region provides a '''default routed network''', as well as additional networks that can be assigned to projects upon request.
 == Mannheim ==

Sia at 16:03, 17 March 2026

2026-03-17T16:03:25Z

← Older revision		Revision as of 16:03, 17 March 2026
Line 1:		Line 1:

	This guide provides details of the ~~networking setup~~ in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.		This guide provides details of the VM networks in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.

	While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.		While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.

Sia at 15:13, 17 March 2026

2026-03-17T15:13:08Z

← Older revision		Revision as of 15:13, 17 March 2026
Line 29:		Line 29:
	* IPv4 (egress): Provided via '''SNAT''' through the router		* IPv4 (egress): Provided via '''SNAT''' through the router
	* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])		* IPv4 (ingress): Not available by default (see [[Guide: Network Configuration by Region#IPv4 Ingress via Floating IPs\|'''IPv4 Ingress via Floating IPs''']])
			📌 '''Note:''' This network extends the legacy IPv6-only network in the Mannheim region, which did not provide IPv4 connectivity. ''Before requesting an IPv4 address via a support ticket, please ensure that the combined connectivity is not already sufficient for your use case.''

	=== IPv4 Ingress via Floating IPs ===		=== IPv4 Ingress via Floating IPs ===

Sia at 14:54, 17 March 2026

2026-03-17T14:54:09Z

← Older revision		Revision as of 14:54, 17 March 2026
Line 1:		Line 1:

	This guide provides ~~an overview~~ of the networking setup in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.		This guide provides details of the networking setup in each '''[[Registration#Regions\|bwCloud-OS region]]'''. It describes which networks are available by default, which can be requested, and how IPv4 and IPv6 connectivity is provided.

	While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.		While core networking concepts are consistent across regions, available networks, IP address ranges, and access methods may differ. Please refer to the section for your specific region.