BGP Example Configuration

The following example configures a BGP adjacency to a neighbor using the settings from Example BGP Configuration.

Assumptions

This example makes a few assumptions for brevity and to keep the example simple, including:

  • The remote peer is already configured for BGP with equivalent settings.

  • Transit to the peer across a directly attached shared network is already configured, for example over a VPN, shared network segment, or peer-to-peer link.

  • Firewall rules pass BGP traffic on TCP port 179 between the peers.

Example Configuration

Route Map for Peer Filtering

Before configuring BGP, add a route map to match any routes so it can be used by FRR to allow exchanging all routes with the peer.

Warning

This basic example replicates previous FRR behavior which allowed any routes to be exchanged with a peer. This is convenient, but not secure. For increased security, create a set of route map entries which ensure that only expected routes are sent and received where possible.

  • Navigate to Services > FRR Global/Zebra, Route Maps tab

  • Click fa-plus Add

  • Set the following options:

    Name:

    ALLOW-ALL

    Description:

    Match any route

    Action:

    Permit

    Sequence:

    100

FRR BGP Configuration

  • Navigate to Services > FRR BGP

  • Set the following options:

    Enable:

    Checked

    Local AS:

    65014

    Router ID:

    10.14.0.1

    Networks to Distribute:

    10.14.0.0/16

  • Click Save

  • Navigate to the Neighbors tab

  • Click fa-plus Add

  • Set the following options:

    Name/Address:

    203.0.113.2

    Remote AS:

    65002

    Route Map Filters:

    Set both Inbound and Outbound to ALLOW-ALL

FRR Global Configuration

  • Navigate to the [Global Settings] tab

  • Set the following options:

    Enable:

    Checked

    Master Password:

    Create a random string to use

  • Click Save

  • Navigate to the Status tab

  • Confirm that the BGP neighbor is present and its routes are in the table