-
Release Notes
- June 13, 2022
- May 31, 2022
- May 16, 2022
- April 28, 2022
- March 24, 2022
- February 8, 2022
-
2021 Releases
- December 20, 2021
- December 1, 2021
- November 22, 2021
- November 4, 2021
- October 26, 2021
- September 30, 2021
- September 22, 2021
- September 2, 2021
- August 16, 2021
- August 2, 2021
- July 19, 2021
- July 1, 2021
- June 17, 2021
- June 1, 2021
- April 30, 2021
- April 8, 2021
- March 25, 2021
- March 15, 2021
- February 25, 2021
- February 8, 2021
- January 28, 2021
- January 21, 2021
- January 13, 2021
- 2020 Releases
- Getting Started
- Ports
- Cross Connects
- Point-to-Point
- Virtual Circuits
- Cloud Connectivity
- Cloud Router
- Marketplace & IX
- Storage
- Administration
- Billing
- Troubleshooting & FAQ
- Technical Reference
- Reseller Admin Portal
- API
Configure BGP for VPN Connections
Before you begin, ensure you have completed the steps outlined in Add a VPN Connection to the Cloud Router.
Add BGP information to the Cloud Router connection
-
After completing the steps above, return to the Cloud Routers page in the PacketFabric portal.
-
Click the connection to open its side panel.
-
Under BGP Sessions, click Create New Session.
Complete the following fields and then click Submit.
BGP Settings
-
Header row
- Field
- Description
-
Row 1
- PacketFabric ASN
- This is the ASN you specified when creating your PacketFabric Cloud Router. You cannot edit this field.
-
Row 1
- ASN
- This is the ASN for your on-premises environment. If you have one, you can use your public ASN. Otherwise, you can select a private ASN from 64512 to 65534.
-
Row 1
- PacketFabric Router Peer IP + Mask (CIDR notation)
- Enter a private IP prefix of your choice.
-
Row 1
- Router Peer IP + Mask (CIDR notation)
- Assign a private IP address to the PacketFabric router.
-
Row 1
-
Allow longer prefixes
-
This applies to the allowed incoming and outgoing prefixes that you list below.
For example, say you list
172.16.2.0/24
as an allowed incoming prefix. You have three other cloud connections with the following outgoing prefixes:Connection A:
172.16.2.0/24
Connection B:172.16.0.0/16
Connection C:172.16.2.128/25
If you do not select this option, only routes from Connection A are allowed.
If you select this option, routes from Connection A and Connection C are allowed.
-
Allowed prefixes to cloud
This is a list of addresses that you want to allow into your on-premises router. These can be addresses from other cloud environments or from a different router.
- Row
- Field
- Description
- Row
-
ASN prepend
-
Number of additional times to add the ASN to the BGP path, resulting in a higher path length.
Routes with higher path length (a higher ASN prepend value) have a lower priority.
-
- Row
-
MED
-
The multi-exit discriminator (MED) value.
When the same route is advertised in multiple locations, those with a lower MED are preferred by the peer AS.
-
- Row
- Prefix/Mask
- Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.
Allowed prefixes from cloud
This is a list of addresses from within the on-premises environment that you want to advertise to other connections.
- Row
- Field
- Description
- Row
- Local preference
- When the same route is received in multiple locations, those with a higher local preference value are preferred by the PacketFabric Cloud Router.
- Row
- Prefix/Mask
- Enter an allowed IP address range in CIDR format. You can add up to 1000 prefixes.
Updated on 17 May 2022