Ubiquiti - BGP

Page / - last modified by Jean Franco on 2022/06/20 23:37

BGP

last modified by Jean Franco

on 2022/06/20 23:37

Table of Contents

The Prefix Lists

Route Maps

The Prefix Lists

The prefix lists are used to control what routes you get from your ISP, as well as the ones you send (announce).

policy {
prefix-list BGP-ISP-From {
rule 10 {
action permit
le 24
prefix 0.0.0.0/0
}
}
prefix-list BGP-ISP-To {
rule 10 {
action permit
prefix 192.0.2.0/24
}
}
prefix-list6 BGP-ISPv6-From {
rule 10 {
action permit
le 64
prefix 0::/0
}
}
prefix-list6 BGP-ISPv6-To {
rule 10 {
action permit
le 48
prefix 2001:DB8::/32
}
}
}

The -From prefix lists are for routes you receive (imported) from your ISP, while the -To lists are for routes being exported (announced) to your provider. In the case of IPv4, the smallest globally accepted size most if not all providers announce is /24. For IPv6, the smallest globally accepted size is /48.

'le' means any prefix smaller (ie: 'le 48' won't allow a /64 IPv6 prefix from your ISP's routing table, but it will allow a /32). 'ge' means any prefix greater (ie: 'ge 56' won't allow a /48, but will allow a /56, /64, or even /128).

In the above examples, 192.0.2.0/24 is your IPv4 netblock, and 2001:DB8::/32 is your IPv6 one. 0.0.0.0/0 and 0::/0 means match all.

Route Maps

While you can just use prefix lists with BGP to control routes imported and exported, route maps give you much more flexibility and control, and can even include AS path matching.

policy {
route-map BGP-ISPv6-From {
rule 10 {
action permit
match {
ipv6 {
address {
prefix-list BGP-ISPv6-From
}
}
}
}
}
route-map BGP-ISPv6-To {
rule 10 {
action permit
match {
ipv6 {
address {
prefix-list BGP-ISPv6-To
}
}
}
}
}
route-map BGP-ISP-From {
rule 10 {
action permit
match {
ip {
address {
prefix-list BGP-ISP-From
}
}
}
}
}
route-map BGP-ISP-To {
rule 10 {
action permit
match {
ip {
address {
prefix-list BGP-ISP-To
}
}
}
}
}
}

Like the prefix lists, -To and -From are your specific directions in and out (import and export). They're pretty self explanatory and reference the prefix lists used before.

BGP Protocol Information

protocols {
bgp 65501 {
address-family {
ipv6-unicast {
network 2001:DB8::/32 {
}
}
}
neighbor 100.64.100.1 {
remote-as 65502
route-map {
export BGP-ISP-To
import BGP-ISP-From
}
soft-reconfiguration {
inbound
}
update-source 100.64.100.2
}
neighbor fd00::1 {
address-family {
ipv6-unicast {
route-map {
export BGP-ISPv6-To
import BGP-ISPv6-From
}
}
}
remote-as 65502
soft-reconfiguration {
inbound
}
update-source fd00::2
}
network 192.0.2.0/24 {
}
parameters {
router-id 100.64.100.2
}
redistribute {
connected {
}
kernel {
}
static {
}
}
}
}

In the above example, our local router has the IPv4 address of 100.64.100.2 and the IPv6 address of fd00::2 with an ASN of 65501. The BGP enabled router on our ISP side is 100.64.100.1 and fd00::1 with an ASN of 65502. We are assuming that our routers are connected over a non-shared link within one hop. If the BGP router is more than one hop away, you need to configure 'ebgp-multihop' with the appropriate amount of hops away your ISP's router is.

Show BGP information:

user@router1:~$ show ip bgp neighbor
BGP neighbor is 100.64.100.2, remote AS 65502, local AS 65501, external link
BGP version 4, remote router ID 100.64.100.2
BGP state = Established, up for 01w0d05h
Last read 01w0d05h, hold time is 90, keepalive interval is 30 seconds
Neighbor capabilities:
Route refresh: advertised and received (old and new)
4-Octet ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Address family IPv4 Multicast: received
Received 2838376 messages, 0 notifications, 0 in queue
Sent 20788 messages, 0 notifications, 0 in queue
Route refresh request: received 0, sent 0
Minimum time between advertisement runs is 30 seconds
Update source is 100.64.100.1
For address family: IPv4 Unicast
BGP table version 6603726, neighbor version 6603716
Index 2, Offset 0, Mask 0x4
Inbound soft reconfiguration allowed
Community attribute sent to this neighbor (both)
Inbound path policy configured
Outbound path policy configured
Route map for incoming advertisements is *BGP-ISP-From
Route map for outgoing advertisements is *BGP-ISP-To
688930 accepted prefixes
1 announced prefixes
Connections established 1; dropped 0
External BGP neighbor may be up to 1 hops away.
Local host: 100.64.100.2, Local port: 60803
Foreign host: 100.64.100.1, Foreign port: 179
Nexthop: 100.64.100.1
BGP connection: shared network
BGP neighbor is fd00::1, remote AS 65502, local AS 65501, external link
BGP version 4, remote router ID 100.64.100.1
BGP state = Established, up for 01w0d05h
Last read 01w0d05h, hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received (old and new)
4-Octet ASN Capability: advertised and received
Address family IPv4 Unicast: advertised
Address family IPv6 Unicast: advertised and received
Received 686685 messages, 0 notifications, 0 in queue
Sent 10394 messages, 0 notifications, 0 in queue
Route refresh request: received 0, sent 0
Minimum time between advertisement runs is 30 seconds
Update source is fd00::2
For address family: IPv4 Unicast
BGP table version 6603726, neighbor version 6603716
Index 1, Offset 0, Mask 0x2
Inbound soft reconfiguration allowed
Community attribute sent to this neighbor (both)
0 accepted prefixes
0 announced prefixes
For address family: IPv6 Unicast
BGP table version 858622, neighbor version 858620
Index 1, Offset 0, Mask 0x2
Community attribute sent to this neighbor (both)
Inbound path policy configured
Outbound path policy configured
Route map for incoming advertisements is *BGP-ISPv6-From
Route map for outgoing advertisements is *BGP-ISPv6-To
49892 accepted prefixes
1 announced prefixes
Connections established 1; dropped 0
Local host: fd00::2, Local port: 179
Foreign host: fd00::1, Foreign port: 8044
Nexthop: 100.64.100.1
Nexthop global: fd00::1
BGP connection: shared network