Cisco router traditional bogons

This page aggregates all of the examples referenced on the Bogon Route Server Project (Bogons via BGP) page. Please see that page for full details of the Bogon Route Server Project, system requirements, caveats, etc.

image 1.png

Cisco peer-groups traditional bogons

With the advent of multiple bogon route-servers, the use of BGP peer-groups on Cisco routers is very convenient. Thanks to John Brown for the original example.

image 3.png

Juniper router traditional bogons

image 2.png

Force10 router traditional bogons

image 4.png

OpenBSD bgpd traditional bogons

OpenBSD’s bgpd project can also be used to peer with the bogon route-servers. Our thanks to Pete Vickers for this example.

image 5.png

Mikrotik RouterOS traditional bogons

This example of how to configure a Mikrotik RouterOS box to use the Bogon Route Server Project is thanks to Ariel S. Weher.

image 6.png

Cisco fullbogons IPv4 and IPv6 (IPv4 transport)

image 7.png

Note: You can receive both IPv4 and IPv6 fullbogons over IPv4 transport. If you only requested one set of fullbogons, simply remove all references to the other set from the example above.

Cisco fullbogons IPv4 and IPv6 (IPv6 transport)

Thanks to Thomas Brandstetter for this example of configuring a Cisco router to receive the IPv4 and IPv6 fullbogons over IPv6 transit.

image 8.png

Note: You can receive both IPv4 and IPv6 fullbogons over IPv6 transport. If you only requested one set of fullbogons, simply remove all references to the other set from the example above.

Juniper JunOS Fullbogons IPv4 and IPv6

Thanks to David Hill at Hostcentral for the below example!

image 9.png

Quagga fullbogons IPv6

The following example will import and null-route the IPv6 fullbogons, peered over IPv4 transit, using the Quagga software router package.

image 10.png

If you wish to receive both IPv4 and IPv6 fullbogons over the same peering session, you will typically need to replicate the statements in the above example’s “address-family ipv6” section to an “address-family ipv4” section, with an appropriate change to the prefix-list applied to the peer-group.

Mikrotik RouterOS fullbogons

image 11.png

BIRD Internet Routing Daemon fullbogons

Courtesy of Miłosz Oller.

PLEASE NOTE: As of version 1.3.11 Bird does not allow you to run IPv4 and IPv6 simultaneously. Therefore you should use EITHER bgp_cymru_v4_1 and bgp_cymru_v4_2 OR bgp_cymru_v6_1 and bgp_cymru_v6_2 in your config. x For dual-stack systems can run two instances of Bird with one peering over IPv4 and the other over IPv6.

If you wish to receive both IPv4 and IPv6 fullbogons over the same peering session, you will typically need to replicate the statements in the above example’s “address-family ipv6” section to an “address-family ipv4” section, with an appropriate change to the prefix-list applied to the peer-group.

image 12.png

Cisco ASA Firewalls fullbogons

Courtesy of Abe Marji.

PLEASE NOTE: ASA Firewalls began supporting BGP as of version 9.2.

image 13.png

Nokia SR OS IPv4 and IPv6 Classic CLI

Courtesy of Greg Hankins

image 14.png

Nokia SR OS IPv4 and IPv6 MD-CLI

Courtesy of Greg Hankins

image 15.png

Cisco IOS-XR Fullbogons

Courtesy of Fulvio Picecchi

PLEASE NOTE: For traditional bogons you only need to update the remote-as directive.

image 16.png

Huawei NE20E

image 17.png