Be sure to check out the main Bogon Reference for more information on the project and terminology used, and why it is important to keep your bogon filters up-to-date.
​
​With regards to filtering 100.64.0.0/10, please consult RFC6598. Know your network, test your filters!
​
[ Bit Notation Non-aggregated ] [ Bit Notation Aggregated ] [ Juniper prefix-list Non-aggregated ] [ Juniper prefix-list Aggregated ]
​
CURRENT AS OF: AUGUST 2018
Bit Notation Non-Aggregated
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.2.0/24
192.168.0.0/16
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
224.0.0.0/4
240.0.0.0/4
Bit Notation Aggregated
If proper boundaries are not followed it is possible to further aggregate, though this likely won’t work on most gear.
​
0.0.0.0/8
10.0.0.0/8
100.64.0.0/10
127.0.0.0/8
169.254.0.0/16
172.16.0.0/12
192.0.0.0/24
192.0.2.0/24
192.168.0.0/16
198.18.0.0/15
198.51.100.0/24
203.0.113.0/24
224.0.0.0/3
Juniper Prefix-List Non-Aggregated
policy-options {
prefix-list bogons {
0.0.0.0/8;
10.0.0.0/8;
100.64.0.0/10;
127.0.0.0/8;
169.254.0.0/16;
172.16.0.0/12;
192.0.0.0/24;
192.0.2.0/24;
192.168.0.0/16;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/4;
240.0.0.0/4;
}
}
Juniper Prefix-List Aggregated
The following aggregations work with Cisco ACLs, and are aligned on proper boundaries.
​
policy-options {
prefix-list bogons {
0.0.0.0/8;
10.0.0.0/8;
100.64.0.0/10;
127.0.0.0/8;
169.254.0.0/16;
172.16.0.0/12;
192.0.0.0/24;
192.0.2.0/24;
192.168.0.0/16;
198.18.0.0/15;
198.51.100.0/24;
203.0.113.0/24;
224.0.0.0/3;
}
}