This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
manuals:vps:ip_addresses [2016/12/11 14:39] – created toms | manuals:vps:ip_addresses [2016/12/11 19:55] – toms | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Public IP Addresses ===== | ===== Public IP Addresses ===== | ||
Every member has 1 public IPv4 address and 32 IPv6 addresses available. Additional | Every member has 1 public IPv4 address and 32 IPv6 addresses available. Additional | ||
- | public IPv4 addresses are subject to a [[informace:platby|fee]], IPv6 addresses are given upon request. | + | public IPv4 addresses are subject to a [[information: membership_fees |
- | Due to the type of [[informace: | + | Due to the type of [[information: |
or /32 IPv4 and /128 IPv6 addresses. This means that it is not possible to assign the whole | or /32 IPv4 and /128 IPv6 addresses. This means that it is not possible to assign the whole | ||
IPv6 subnet. | IPv6 subnet. | ||
Line 12: | Line 12: | ||
Private IP addresses access the internet using NAT and are therefore not accessible from | Private IP addresses access the internet using NAT and are therefore not accessible from | ||
the outside. Private addresses are useful if you divide the allocated | the outside. Private addresses are useful if you divide the allocated | ||
- | [[navody:vps:prostredi|resources]] between several VPSs. The public IPv4 address is | + | [[manuals:vps:environment|resources]] between several VPSs. The public IPv4 address is |
often unnecessary. However, functioning with only an IPv6 is problematic since | often unnecessary. However, functioning with only an IPv6 is problematic since | ||
some servers still don’t support it. | some servers still don’t support it. |