add product colocation
This commit is contained in:
		
					parent
					
						
							
								a6ef9f85fe
							
						
					
				
			
			
				commit
				
					
						61b886881c
					
				
			
		
					 1 changed files with 46 additions and 0 deletions
				
			
		
							
								
								
									
										46
									
								
								content/u/products/colocation/contents.lr
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										46
									
								
								content/u/products/colocation/contents.lr
									
										
									
									
									
										Normal file
									
								
							| 
						 | 
					@ -0,0 +1,46 @@
 | 
				
			||||||
 | 
					title: Colocation
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					link:
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					_discoverable: no
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					_hidden: yes
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					subtitle: Your space in Data Center Light
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature1_title: Necessary
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature1_text: We [ran out of IPv4
 | 
				
			||||||
 | 
					space](https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/the-ripe-ncc-has-run-out-of-ipv4-addresses)
 | 
				
			||||||
 | 
					by the end of 2019. While you can acquire IPv4 space on the market, it
 | 
				
			||||||
 | 
					is very expensive and effectively limiting new projects to come into
 | 
				
			||||||
 | 
					existence. IPv6 fixes all of this, today.
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature2_title: Sustainable & Simple
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature2_text: Compared to IPv4 only or Dual Stack VMs, IPv6 only VMs
 | 
				
			||||||
 | 
					are the only ones really ready for the future.
 | 
				
			||||||
 | 
					**IPv4** only VMs already face the problem that they cannot reach resources in the IPv6
 | 
				
			||||||
 | 
					Internet. Dual stack VMs are increasing complexity and difficulty,
 | 
				
			||||||
 | 
					especially when it comes to firewall rules and security.
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature3_title: Connected
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					feature3_text:
 | 
				
			||||||
 | 
					Even with IPv6 only VMs you are not isolated from the legacy (IPv4)
 | 
				
			||||||
 | 
					Internet. Our
 | 
				
			||||||
 | 
					[DNS64](https://redmine.ungleich.ch/projects/open-infrastructure/wiki/The_ungleich_DNS_infrastructure)
 | 
				
			||||||
 | 
					and
 | 
				
			||||||
 | 
					[NAT64](https://redmine.ungleich.ch/projects/open-infrastructure/wiki/The_ungleich_network_infrastructure#IPv6-NAT64)
 | 
				
			||||||
 | 
					services allow your VM to connect anywhere in the legacy
 | 
				
			||||||
 | 
					Internet. And even the legacy Internet can connect to you, using an
 | 
				
			||||||
 | 
					[IPv4-to-IPv6 proxy](https://redmine.ungleich.ch/projects/open-infrastructure/wiki/How_to_use_the_IPv4-to-IPv6-Proxy)!
 | 
				
			||||||
 | 
					---
 | 
				
			||||||
 | 
					description2:
 | 
				
			||||||
 | 
					IPv6 only hosting is giving you access to virtual machines that will
 | 
				
			||||||
 | 
					become the standard tomorrow, already today. Instead of managing
 | 
				
			||||||
 | 
					legacy IP VMs with NAT, creating floating IP addresses and complex
 | 
				
			||||||
 | 
					firewall setups, all this burden is lifted away with IPv6 only VMs.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Additionally you can request a /64 network to be routed to your VM,
 | 
				
			||||||
 | 
					for free!
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue