jezahost
  • bgp
  • network
  • ripe

Your own ASN in Baku: how to get a BGP session

If you have your own ASN and IP block, you can announce them from Baku over a BGP session on a VPS. Every step from the request to your prefixes being visible worldwide, from the customer's side.

If you have your own ASN and IP block, there are not many ways to announce them from Baku. At JezaHost we offer a BGP session on a VPS: your prefixes reach the world through our network (AS218452), and you run the routing on your own server, with BIRD, FRR or whatever software you prefer. This post walks through the process step by step, from the customer's side.

What you need

  • Your own ASN.
  • An IP block registered with RIPE: at least a /24 for IPv4, at least a /48 for IPv6.
  • A route (IPv4) or route6 (IPv6) object in RIPE for each prefix, with your ASN as origin.
  • RPKI (ROA): recommended; an invalid prefix is not accepted.
  • Any of our Linux VPS plans. The smallest one is enough.

Step 1: request and automatic checks

Once you have the VPS, you send a BGP request from its page in the portal: your ASN and prefixes. The form checks the RIPE data right away: the ASN's status, the aut-num object, the route/route6 objects, the RPKI state and whether someone else is announcing the prefix right now. You see the result on the spot: wherever there is a problem, it tells you what to fix.

Step 2: LOA

The portal prepares an LOA (letter of authorisation) with your details. You download it, sign it and upload it back. The LOA is proof for the upstream providers that you have authorised us to announce the prefixes.

Step 3: the aut-num object

In RIPE, add lines for two networks to your aut-num object: for us (AS218452) and for our upstream (AS200154). The second is often forgotten, but without it some backbones will not accept the prefix:

import:     from AS218452 accept ANY
export:     to AS218452 announce AS<sizin ASN>
import:     from AS200154 accept ANY
export:     to AS200154 announce AS<sizin ASN>

Replace AS<sizin ASN> with your own AS number. For IPv6, the same lines with mp-import and mp-export.

Step 4: approval and payment

We review the request within one business day. Payment opens only after approval, so you pay nothing for a request we do not approve. The BGP service is 15 AZN a month.

Step 5: the session

After payment, a separate network interface for BGP is attached to your VPS, with no reboot. In the portal you see:

  • your link addresses (IPv4 and IPv6),
  • our two neighbours: two separate switches, and you set up a session with both for redundancy,
  • the MD5 password.

From us you receive only a default route. From you we accept only the approved prefixes, at their exact length. The session usually comes up as soon as you put the configuration in place.

Step 6: reaching the world

Once the session is up, your prefixes reach us, and then the upstream providers' filters are updated. This usually takes 1–2 business days. Some local backbones may accept a new prefix a little later; in the meantime, traffic from within the country may take a longer path. You can follow the state yourself in tools like bgp.tools: AS218452 should appear in your prefix's path.

A real example

A customer recently sent the request in the evening; the same night all four sessions (IPv4 and IPv6, to both switches) came up, and the next day the prefixes were visible worldwide.

Questions?

If you are new to BGP and have a question about the configuration, we will point you in the right direction by ticket, e-mail ([email protected]) or WhatsApp. We do not log in to your server remotely; the configuration stays under your control.

To get started, see the VPS plans or open the BGP request in the portal.