Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
kvm [2021/04/24 12:55]
canadianstormchaser [IPv6]
kvm [2022/02/09 19:54]
canadianstormchaser
Line 30: Line 30:
 For CentOS you will need to use a template. For CentOS you will need to use a template.
  
-Windows 2003 will work on a 128MB with about 30MB spare RAM. Windows 2008 R2 & 2012  +To run Windows Server 2012 or higher you need at least a **1GB Slice or higher**.
-both require a **minimum** of 512MB RAM.+
 ===== Networking ===== ===== Networking =====
  
Line 77: Line 76:
 === New York === === New York ===
  
-  * Gateway: 2605:6400:1:fed5::1+  * Gateway: 2605:6400:10::1
   * Netmask: /48   * Netmask: /48
  
Line 85: Line 84:
          address YOUR_IPV6_ADDRESS_HERE          address YOUR_IPV6_ADDRESS_HERE
          netmask 48          netmask 48
-         gateway 2605:6400:1:fed5::1+         gateway 2605:6400:10::1 
 + 
 +=== Luxembourg === 
 + 
 +  * Gateway: 2605:6400:30::
 +  * Netmask: /48 
 + 
 +== Example configuration for Debian using ifupdown2 in Luxembourg == 
 + 
 +    iface eth0 inet6 static 
 +         address YOUR_IPV6_ADDRESS_HERE 
 +         netmask 48 
 +         gateway 2605:6400:30::
 + 
 +=== Miami=== 
 + 
 +  * Gateway: 2605:6400:40::
 +  * Netmask: /48 
 + 
 +== Example configuration for Debian using ifupdown2 in Luxembourg == 
 + 
 +    iface eth0 inet6 static 
 +         address YOUR_IPV6_ADDRESS_HERE 
 +         netmask 48 
 +         gateway 2605:6400:40::1 
 ==== Windows ==== ==== Windows ====
  
Line 110: Line 134:
 ==== Poor Network Performance On Linux ==== ==== Poor Network Performance On Linux ====
  
-If your virtual server has 512MB RAM you'll likely suffer poor network performance due to strict default buffer sizes.+If your virtual server has 512MB RAM you'll likely suffer poor network performance due to strict default buffer sizes.
  
 To get around this please add the follow to your /etc/sysctl.conf To get around this please add the follow to your /etc/sysctl.conf