BGP/Quick Start: Difference between revisions

Latest revision as of 22:28, 28 September 2026

Use this guide to arrange a BGP announcement for a 44Net subnet.

Exact router configuration depends on your provider and equipment. Sort out the details with your provider before activation.

Before you begin

Create a Portal account and review the verification requirements. For BGP-announced subnets, you will need to verify your physical address.

See the BGP overview for brief background on BGP and 44Net.

1. Coordinate with a provider

Consider sending the provider the Guide for ISPs, which answers common questions about 44Net and BGP. Confirm the following with your provider:

Who will announce the prefix and which public origin autonomous system number (ASN) will appear on the Internet.
How traffic will reach your network, including the type of handoff and equipment requirements.
Whether the provider accepts the authorization and routing records ARDC can supply, particularly considering current RPKI limitations.

If you will run a BGP session yourself, also agree on neighbor addresses, ASNs, and route policies. If the provider announces for you, confirm any configuration requirements between your systems and theirs.

2. Request the subnet

In the Portal, request address space for direct BGP announcement. Include your intended use, requested size, provider details, and the agreed public origin ASN. Supply any further information requested in the review ticket.

3. Check the authorization

After approval, download the Letter of Authorization (LOA) from the Portal. Check the prefix, origin ASN, and validity dates, then give it to your provider.

Resolve discrepancies before activation. For authorization or ARDC-maintained routing-record questions, contact noc@ardc.net.

4. Configure and activate

With your provider:

Configure the circuit, tunnel, or hosted network that will carry the traffic.
Configure the BGP session if your arrangement requires one. Limit exported routes to the authorized prefixes.
Set up local addressing, forwarding, return routes, and firewall rules.
Agree on how to withdraw the announcement if activation fails, then enable it.

5. Verify the result

Check an external BGP looking glass like bgp.tools or a route collector for the exact prefix and expected public origin ASN.
Test an intended service from outside your network, and test outbound traffic using a 44Net source address.
If the route is visible but traffic fails, check the provider's delivery path, local routes, and firewall rules. For connections that stall or fail with larger packets, see MTU and MSS.

Keep your Portal records and provider contacts current. Renew the LOA before it expires, and update the authorization before changing the public origin ASN. Do so as soon as possible, since the review and approval process can take several days.

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:BGP Quick Start (Stub)}}
+{{DISPLAYTITLE:BGP Quick Start}}
-== What this page is ==
+Use this guide to arrange a BGP announcement for a 44Net subnet.
-This is an orientation stub for BGP-based 44Net participation.
-A full end-to-end quick start procedure is not published yet.
-== What you can do today ==
+Exact router configuration depends on your provider and equipment. Sort out the details with your provider before activation.
-* Use [[Provisioning Methods|Provisioning Methods]] to confirm BGP is the right operating model.
-* Make sure your network already operates BGP-capable edge routing and has a stable tunnel or transit plan.
-* Start account and eligibility prerequisites in [[GetStarted|Getting started]] and [[Portal/Sign Up|Portal Sign Up]].
-* Review [[Routing|Routing and connectivity]] for routing concepts and decision points.
-* Ask implementation questions in [[Community|Community and mailing lists]].
-== What this page will cover ==
+== Before you begin ==
-* Prerequisites: ASN, policy ownership, and upstream coordination.
-* Address assignment scope and route advertisement boundaries.
-* Session design, failover patterns, and filtering expectations.
-* Validation and troubleshooting checklist.
-* Operational hygiene for changes and incident response.
-== Related pages ==
+Create a [[Portal/Sign Up|Portal account]] and review the [[Verification|verification requirements]]. For BGP-announced subnets, you will need to verify your physical address.
-* [[Provisioning Methods|Provisioning Methods]]
-* [[GetStarted|Getting started]]
+See the [[BGP|BGP overview]] for brief background on BGP and 44Net.
-* [[Routing|Routing and connectivity]]
-* [[Portal/Request Address Space|Request Address Space]]
+== 1. Coordinate with a provider ==
-* [[Governance|Governance]]
-* [[Policies|Policies]]
+Consider sending the provider the [[Guide for ISPs]], which answers common questions about 44Net and BGP. Confirm the following with your provider:
-* [[Community|Community and mailing lists]]
-* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]
+* Who will announce the prefix and which public origin autonomous system number (ASN) will appear on the Internet.
+* How traffic will reach your network, including the type of handoff and equipment requirements.
+* Whether the provider accepts the authorization and routing records ARDC can supply, particularly considering [[RPKI and ROAs on 44Net|current RPKI limitations]].
+If you will run a BGP session yourself, also agree on neighbor addresses, ASNs, and route policies. If the provider announces for you, confirm any configuration requirements between your systems and theirs.
+== 2. Request the subnet ==
+In the [https://portal.ampr.org Portal], request address space for direct BGP announcement. Include your intended use, requested size, provider details, and the agreed public origin ASN. Supply any further information requested in the review ticket.
+== 3. Check the authorization ==
+After approval, download the Letter of Authorization (LOA) from the Portal. Check the prefix, origin ASN, and validity dates, then give it to your provider.
+Resolve discrepancies before activation. For authorization or ARDC-maintained routing-record questions, contact [mailto:noc@ardc.net noc@ardc.net].
+== 4. Configure and activate ==
+With your provider:
+# Configure the circuit, tunnel, or hosted network that will carry the traffic.
+# Configure the BGP session if your arrangement requires one. Limit exported routes to the authorized prefixes.
+# Set up local addressing, forwarding, return routes, and [[Firewalling Basics|firewall rules]].
+# Agree on how to withdraw the announcement if activation fails, then enable it.
+== 5. Verify the result ==
+* Check an external BGP looking glass like [https://bgp.tools bgp.tools] or a route collector for the exact prefix and expected public origin ASN.
+* Test an intended service from outside your network, and test outbound traffic using a 44Net source address.
+* If the route is visible but traffic fails, check the provider's delivery path, local routes, and firewall rules. For connections that stall or fail with larger packets, see [[MTU and MSS]].
+Keep your Portal records and provider contacts current. Renew the LOA before it expires, and update the authorization before changing the public origin ASN. Do so as soon as possible, since the review and approval process can take several days.
-== Contribute / next steps ==
-If you can share a proven deployment path, capture topology, BGP edge role, filtering assumptions, and rollback strategy. Add that material through [[Contributing]] so this stub can be upgraded to a real Quick Start.
-== Older docs and notes ==
-Earlier pages that may still be useful:
-* [[Routing your allocation via BGP]]
-* [[Announcing your allocation directly]]
-* [[FAQ|Why can’t I announce my allocation directly?]]
-* [[SWIP]]
-* [[NSP Details]]
-* See [[Archive]] for more.
-[[Category:Tutorial]]
 [[Category:How-To]]
 [[Category:Participation Methods]]