Skip to main content

Setting up BGP

Xenyth Cloud lets you bring your own ASN and run a BGP session directly on an Edge VM, peering with your region's route daemon over both IPv4 and IPv6.

Getting started takes two stages:

  1. Connect your ASN — verify ownership of your ASN against your Xenyth account. This is a one-time step per ASN.
  2. Deploy a BGP session — add BGP to an Edge VM and configure the peering on your side.

Prerequisites​

  • A Xenyth Cloud account.
  • An ASN you control, registered with an RIR (ARIN, RIPE, etc.) that publishes an abuse contact. Verification is performed by emailing that contact, so it must be reachable.
  • A PVE KVM Edge VM — its name carries the e2. tier prefix. BGP is only available on Edge VMs.
  • Published IRR / RPSL route objects for any prefixes you intend to announce. Import filters are built from your IRR data, so prefixes without a matching route object will be filtered.

Stage 1 — Connect and verify your ASN​

You can connect up to 3 ASNs per account. Only verified ASNs can be used to create a BGP session.

Step 1: Request verification​

  1. In the Xenyth Cloud dashboard, open Account → Connections.
  2. Add a new BGP connection and enter your ASN. The formats 835, AS835, and as835 are all accepted and normalized to AS835.

When you submit, Xenyth:

  1. Looks up the abuse contact for your ASN via RIPEstat.
  2. Generates a 16-character verification code, valid for 1 hour.
  3. Emails the code to your ASN's abuse contact, naming your account so the contact knows the request came from you.
note

If no abuse contact is published for the ASN, verification cannot proceed. Publish an abuse contact with your RIR first, then request verification again.

Step 2: Submit the code​

  1. Retrieve the verification code from your ASN's abuse mailbox.
  2. Back in Account → Connections, enter the code for the same ASN and submit.

If the code matches and hasn't expired, the ASN is marked verified. If the hour lapses before you submit, simply request a new code (Step 1) and try again.

Step 3: Confirm​

Your connections list will now show the ASN as verified. It's ready to use when you deploy a BGP session.

Stage 2 — Deploy a BGP session on an Edge VM​

Step 1: Add BGP to your Edge VM​

  1. Open your PVE KVM Edge VM service page. The BGP panel appears once you have at least one verified ASN.
  2. Order a BGP session and choose one of your verified ASNs.

Requirements enforced when you create a session:

  • The service must be a PVE KVM Edge VM (e2. tier).
  • The VM must not already have a BGP session — one session per VM.
  • The chosen ASN must be verified on your account (Stage 1).

The BGP add-on is free. Once created, Xenyth registers your VM as a BGP peer with the region's route daemon using the VM's provided IPv4 and IPv6 addresses.

Step 2: Note your peering details​

Open the BGP panel's Details view. It shows your side and our side of the session.

Your side is your VM's own IPv4 / IPv6 addresses and your ASN. Xenyth's side depends on your region. The Xenyth side details will be provided to you on the BGP Settings page once provisioned.

Step 3: Configure BGP inside your VM​

Install a BGP daemon in the VM (BIRD, FRR, or similar) and configure a session toward the Xenyth IP for your region.

The session comes up over both IPv4 and IPv6. The Details view reports a separate status for each protocol, so you can confirm each one reaches the established state.

Step 4: Announce your prefixes​

Announce your prefixes over the session, keeping the following in mind:

  • Route filtering is driven by your published IRR / RPKI objects. If a route appears as filtered in the Details view, it failed validation — check that the prefix is covered by a route object originating from your ASN.
  • Filters refresh automatically every 24 hours. After publishing new route objects, you can rebuild your filters immediately with the Refresh Filters action rather than waiting for the next cycle.

Step 5: Choose what Xenyth sends you (export mode)​

Use the Export Mode action to control which routes Xenyth advertises into your session:

ModeWhat Xenyth announces to you
noneNothing.
defaultA default route only.
fullA full table.

Managing your session​

From the BGP panel you can:

  • Details — view received routes (including filter reasons), the neighbor ASN, per-protocol session status, and both sides' peering addresses.
  • Refresh Filters — rebuild your import filters from current IRR data after publishing new route objects.
  • Set Export Mode — switch between none, default, and full.

Removing the BGP add-on, or terminating the VM, deletes the peer from the route daemon and tears the session down.

Troubleshooting​

SymptomLikely cause / fix
No abuse contact foundNo abuse contact is published for the ASN. Publish one with your RIR, then retry.
Invalid or expired codeThe code is wrong or older than 1 hour. Request a fresh code and try again.
You can connect at most 3 ASNsYour account's ASN limit has been reached.
BGP only available on Edge VMsThe service isn't a PVE KVM Edge VM (e2. tier).
ASN AS… is not verified on your accountComplete Stage 1 verification for that ASN first.
This service already has a BGP sessionOnly one session is allowed per VM. Remove the existing add-on first.
Routes show as filteredThe prefix isn't covered by a valid IRR object originating from your ASN. Publish or fix the route object, then use Refresh Filters.
Session won't establishCheck your VM's daemon config (neighbor IP and ASN), and confirm the VM's firewall permits TCP/179.