# Privex IP Allocation Policy # Sweden ## IPv4 Addresses Swedish **Virtual Servers** (VPS's) usually receive ONE individual IPv4 address, with the exception of IPv6-only packages such as our Micro VPS™ and some of our WebBox™ (below $5/mo) packages Customers may purchase up to 32 additional IP addresses for VPS's which may be shared between other Swedish VPS's that they own - however the price per IP increases depending on how many IP addresses you're purchasing: - $1.00 USD / mo per IPv4 address for the first 8 IP addresses - $2.50 USD / mo per IPv4 address for the 9th to 16th IP addresses they purchase - $5.00 USD / mo per IPv4 address for the 17th to 24th IP addresses they purchase - $8.00 USD / mo per IPv4 address for the 25th to 32nd IP addresses they purchase **Examples** If you purchased just 4 IPv4 addresses, you would pay $4/mo total for the 4 IP addresses. If you purchased 12 IPv4 addresses, you would pay $8/mo total for the first 8 IP addresses, and $10/mo for the 4 following IP addresses ($2.50/mo x 4 IPs) If you purchased 28 IPv4 addresses, you would pay $8/mo total for the first 8 IP addresses, $20/mo for the 8 following IP addresses ($2.50/mo x 8 IPs), $40/mo for the 8 IP addresses after those ($5.00/mo x 8 IPs), and finally $32/mo for the 4 final IP addresses of the 24 IPs that you purchase. ### Sharing IPv4 addresses with other Dedicated / Virtual Servers When you purchase additional IPv4 addresses within our Swedish region, it's possible to share them with other servers of the same type in Privex's Sweden region, however, if a server has it's existing primary IPv4 address in a different subnet to the additional IP addresses that you own, they may not work, or may require complex networking configuration such as **source routing** for them to be fully usable. For example, assuming you have the 10 additional IPs 1.2.3.10 to 1.2.3.19 - which are contained within the VPS subnet 1.2.3.0/27 (0 to 32) - then you would be able to use them easily with any other VPS which has an IP in the 1.2.3.0/27 subnet. #### Notify Privex before attempting to share individual IPs with other servers While it's possible to share your additional IP addresses with other servers, we have firewalling in place (commonly referred to as IP locking) which prevents dedicated/virtual servers using IP addresses which do not belong to them. Thus, to be able to share additional IPs between other servers, you must notify our support team, and tell us which servers you're planning on sharing your additional IPs with. This will allow us to whitelist the additional IPs on the network/hypervisor firewall for each machine. #### Potential issues with IP sharing However, if you had a VPS with the primary IP address `1.2.3.45/27` - then that VPS would be using a gateway in a different subnet (`1.2.3.33`), and thus attaching the IP address `1.2.3.15` for example, would require **source routing**, so that traffic to/from `1.2.3.15` goes via the gateway `1.2.3.1` instead of the gateway `1.2.3.33`. If you simply needed another IP address, and didn't care whether or not it was in `1.2.3.0/27` - then depending on how many unused IPs that we have available in `1.2.3.32/27` - we may allow you to trade an IP address from your 10 IP block within the `1.2.3.0/27` subnet, for an IP address within `1.2.3.32/27`. Alternatively, if you purchased an entire subnet, such as a /27 (32 IPs), then we can offer you an isolated VLAN - this is a separated network from the shared networks that are used to allocate singular IPs to customers. See the following section. ### Isolated Customer VLANs (Virtual Local Area Networks) In Sweden, we can offer customers a dedicated VLAN which can hold IPv4 + IPv6 subnets, along with custom network configuration such as IPv6 SLAAC for automatic IPv6 addressing. A VLAN can be shared between both virtual AND dedicated servers, either via the primary interface, or attached as a secondary virtual VLAN interface. To be eligible for a VLAN, you must have, or be willing to purchase an IPv4 subnet. The minimum size for a subnet is a `/30`, which contains 4 IP addresses (and will be billed as such), however the first and last IP address are not usable, as they are the gateway and broadcast address respectively. We can however, offer VLANs for free - for IPv6-only networks. #### VLAN Setup #### Using a VLAN for new or existing dedicated/virtual servers Once you've obtained an IPv4/v6 subnet to use, and requested a VLAN - then we'll send you some information that you should keep for future reference, which will look like this: ``` interface Vlan123 description John Doe Private Customer VLAN 123 ip address 12.34.5.65 255.255.255.224 ipv6 address 2a07:e01:123::1/48 ipv6 address FE80::1 link-local ``` This snippet contains several important pieces of information which tell you how you can use your VLAN, as well as information needed for Privex staff to easily lookup your VLAN and attach it to your servers when requested. - `interface Vlan123` - This identifies the unique VLAN number, which is `123` - you'll need to reference `VLAN 123` when contacting support in regards to your VLAN. - `description John Doe Private Customer VLAN 123` - This is a human readable description that we've set on the VLAN, helping us clearly identify that VLAN 123 belongs to you when checking our network configuration. It may help staff locate your VLAN if you include the description in your ticket. - `ip address 12.34.5.65 255.255.255.224` - This identifies your IPv4 gateway - `12.34.5.65` - and the subnet mask `255.255.255.224` - this subnet mask in particular means the subnet is a `/27`, with 32 IP addresses (30 usable) from `12.34.5.64` to `12.34.5.95` - `ipv6 address 2a07:e01:123::1/48` - This identifies your IPv6 subnet, and subnet-level gateway. - `ipv6 address FE80::1 link-local` - This means that the global IPv6 gateway `FE80::1` has been enabled on your VLAN - which allows you for example to use arbitrary subnets within your `/48` such as `2a07:e01:123:99::1/64`, as long as you use `fe80::1` as your IPv6 gateway.