BGP Sessions

A BGP session (or peering) is a persistent TCP connection (port 179) established between your router—typically software-based like BIRD or FRRouting—and Melbicom’s routers. It dynamically exchanges routing information, optimizing your network’s traffic flow for improved redundancy, reduced latency, and enhanced performance. You directly announce your IP prefixes to the Internet, giving you fine-grained control over your traffic routing.

Yes, we support both our predefined communities and passthrough communities towards upstream providers. A complete community list is available on request.

Yes. We offer BGP at every datacenter, globally, with full IRR integration across all major regional registries—RIPE, ARIN, APNIC, and more.

You will find below the steps required to set up your BGP session using the BIRD daemon:

1. Install BIRD for IPv4 & IPv6

For Ubuntu 20.04 / 22.04 / 24.04 and Debian 11 / 12

sudo apt update && sudo apt install bird bird6

For CentOS 9 Stream / AlmaLinux 8 & 9 / Rocky Linux 8.6 & 9.x

sudo dnf install bird bird6

2. Create Config Files

/etc/bird/bird.conf     # IPv4
/etc/bird/bird6.conf    # IPv6

IPv4 Configuration Example

router id X.X.X.X;                    # VPS IPv4
protocol static { route YOUR.PREFIX.IP/MASK via "eth0"; }
protocol bgp provider {
    local as YOUR_ASN;
    neighbor x.x.x.x as MELBICOM_ASN;
    import all; export where net ~ [ YOUR.PREFIX.IP/MASK ];
    next hop self;
}

IPv6 Configuration Example

router id X.X.X.X;                    # still IPv4
protocol static { route YOUR:V6::/MASK via "eth0"; }
protocol bgp provider {
    local as YOUR_ASN;
    neighbor xxxx:xxxx::1 as MELBICOM_ASN;
    import all; export where net ~ [ YOUR:V6::/MASK ];
    next hop self;
}

3. Enable & Start Services

sudo systemctl enable --now bird
sudo systemctl enable --now bird6

Tip: Ensure TCP port 179 is open on your firewall.

Yes, our infrastructure fully supports the announcement of IPv6 prefixes alongside IPv4.

Yes. We reject invalid ROAs via RPKI and only accept prefixes with valid IRR entries. This guarantees route legitimacy and protects against hijacks.

We validate against RIPE, ARIN, APNIC, AFRINIC, LACNIC, RADB, and IDNIC—ensuring global compatibility.

Only if the specific /24 is individually registered in the IRR. We follow strict filtering rules to maintain routing integrity.