Cloud Router Frequently Asked Questions
PacketFabric Cloud Routers
Do I need to set up a cross connect to PacketFabric?
No. You do not need a physical port or a data center presence to use Cloud Router services.
We can transfer data between your cloud environments, but then you would be responsible for reaching the cloud via another route (such as over the open internet or a VPN connection).
Can I connect my on-premises network to the cloud router?
Yes. If you aren’t already connected, you will need to provision an access port in one of our locations and set up a cross connect to our network.
If you already have an access port, you can use that to connect your on-premises network to the Cloud Router.
Is Q-in-Q supported?
Q-in-Q tunneling is fully supported. Q-in-Q S-tag/S-VLAN is supported for Azure connections. If you require S-tag/S-VLAN for another cloud, contact your Customer Service Manager to discuss options.
Do you provide public IPs?
Can I use my own public IPs for the router peering? What about my own public ASN?
At this time, you cannot use your own public ASN.
For an AWS public virtual interface, you can use your own public IPs. When you provision your connection, we send AWS an automated email to confirm that you are authorized to use our public ASN with your public IPs. All public virtual interfaces require up to 72 hours approval by AWS.
You cannot use your own IPs for Google or IBM.
At this time, we do not support Microsoft public peering.
Can I use my own private IPs?
This depends on the cloud service provider.
For router peer IPs:
- AWS allows you to input your own IP addresses or have them generated on your behalf.
- Microsoft Azure requires you to provide your own subnet ranges. The peer IPs are auto-allocated from this range.
- For Google Cloud and IBM Cloud, the IP addresses are generated on your behalf and cannot be edited.
When advertising VPC subnets, you can set your own prefixes (up to 1000 in and 1000 out).
Is IPv6 supported?
How long does provisioning take?
Provisioning can take up to 10 minutes, depending on the cloud.
Additional configuration takes a few more minutes depending on how many prefixes you need to add.
How many connections can I have per Cloud Router?
Can a virtual circuit be ordered from a Cloud Router to anywhere in the PacketFabric network?
Will my data traverse the public internet?
How do you choose the best path for data to take?
What do you mean when you say it’s a “distributed” service?
Rather than creating one centralized router to handle inter-cloud, we create routing instances at each location you provision a connection.
This allows us to avoid hairpinning traffic and provides far more scalability.