Network requirements

What we need from your network

We want to run our dedicated servers with you as one network, not a set of separate ports. These are the features we need.

1

Shared IPs across all our servers

Any of our addresses usable from any of our ports.

2

Our own IPv4 ranges

You announce ranges we send you and route them to us.

3

Dedicated lines for NAT gateways

A NAT gateway can leave on its own line with its own capacity.

The network we want

Internet Dedistart network Router AAS209625 Router BAS209625 Your IPv4 blocks Our own IPv4 ranges, announced by you Native IPv6 prefix Dedicated linesown port or VLAN, stated capacity Our side, on your servers Gateway 1shares all addresseswith Gateway 2 Gateway 2takes over whenGateway 1 is lost NAT gatewaycustomer Aown IP, own line NAT gatewaycustomer Bown IP, own line One address, any portAn address moves between gateways and serverswithout a ticket or a change of filter BGP: we announce prefixes one line each Private network across every server, isolated, 10G or better, large framesbetween every server, on every switch Dedicated server Dedicated server Dedicated server More serverson the same network Remote console and power control on every server, through an API
The dashed area is what you run. Cyan lines are the private network and the dedicated lines.

Shared IPs across all our servers

Every address we hold with you must work from any of our ports, so we can move it in seconds without a ticket. Keep anti-spoofing, applied to all our prefixes together instead of per port.

Today: one address, one port Your switch Port S08only its own addresses Port S10only its own addresses Port S02only its own addresses ServerServer lostServer Its addresses stay dark until that server returns.Sending one from another port gets it dropped. Wanted: one set of addresses, every port Your routers All our prefixes allowed from all our ports Gateway 1lost Gateway 2carries everything Any servercan hold an address Addresses keep working when a server is lost.Addresses move in seconds, with no ticket.

Any of these gets us there. We prefer the first.

OptionWhat it isWhat we need from you
Preferred
BGP		Two of our servers run BGP with your routers and announce our addresses, including single addresses.BGP sessions on two ports, a route filter for our prefixes, and acceptance of more specifics up to /32.
Good
Routed block		You route a block to one next hop, shared by two of our servers.A static route to that next hop, and a shared VLAN across our ports.
Minimum
One filter for all ports		Addresses stay on-link, and every one of our ports may use all of them.One allow list for our whole account. Inbound must reach whichever port answers.

ARP and MAC addresses

We'd rather ARP can be shared, so any of our servers can answer for any of our addresses. If you need a MAC address, we'll run a VM dedicated to routing and networking. Either we update the registered MAC ourselves, or you give us a dynamic one that we set on the VM. It must be allowed on all our ports. This is probably the most secure way.

Dedistart network Our addresses are allowed only from one MAC, on our ports Allowed MAC, updated by us or dynamic from youfor example by API or a ticket Dedicated server 1 Routing VMcarries the allowed MAC Other serversreached through it Dedicated server 2 Routing VM, standbystarts here if server 1 is lost Other serversreached through it same MAC moves with it

Our own IPv4 ranges

We'll want to send you IPv4 ranges we hold ourselves. You announce them and route them to us the same way as your own blocks, usable from all our ports. We provide the letter of authority, ROA and route object for your AS. We need reverse DNS delegated to us.

Dedicated lines for NAT gateways

We want to offer NAT gateways with the option of their own dedicated line, beside the shared uplink.

Shared NAT gateway Customer ACustomer BCustomer C GatewaysNAT with HA Yournetwork Everyone shares capacity and the uplink.Good default, simple, lower price. Dedicated NAT gateway Customer ACustomer B NAT gateway Aown address NAT gateway Bown address Yournetwork line Aline B Own capacity, own stable address, own usage figures.

Everything we need

FeatureRequirementPriority
FiltersStay off until shared IPs are in place, with notice before they return.Now
Shared IPsBGP, a routed block, or one filter for all our ports.Now
ARP or MACShared ARP, or a MAC we update or a dynamic one from you, allowed on all our ports.Now
Private networkIsolated from other customers, across every server and switch, 10G or better, large frames.Next
UplinkStated, committed rates per port in both directions.Next
Native IPv6A routed prefix, /48 or larger.Next
Remote managementRemote console and power control on every server, through an API.Next
Own IPv4 rangesAnnounce and route ranges we send you.Plan
Dedicated NAT linesDedicated lines as described above.Plan

Please tell us which of these you can offer, and when.