rpsl and bird

Matthew Walster matthew at walster.org
Wed Apr 27 14:10:40 UTC 2011


On 27 April 2011 14:53, Herbert Faleiros <herbert at scw.net.br> wrote:
> $ rtconfig -cisco_use_prefix_lists -cisco_no_compress_acls -protocol ripe
> rtconfig> @RtConfig access_list filter afi ipv4,ipv6 AS-IXREACH
> !
> no ip prefix-list pl100
> ip prefix-list pl100 permit 46.18.168.0/21
> ip prefix-list pl100 permit 91.196.184.0/22
> ip prefix-list pl100 permit 91.196.184.0/22 ge 24 le 24
> ip prefix-list pl100 permit 109.246.32.0/20
> ip prefix-list pl100 permit 109.246.128.0/18
> ip prefix-list pl100 permit 109.246.192.0/20
> ip prefix-list pl100 permit 188.74.64.0/18
> ip prefix-list pl100 permit 212.9.96.0/19
> ip prefix-list pl100 permit 212.9.96.0/24
> ip prefix-list pl100 deny 0.0.0.0/0 le 32
> !
> no ipv6 prefix-list ipv6-pl100
> ipv6 prefix-list ipv6-pl100 permit 2A02:27F0::/32
> ipv6 prefix-list ipv6-pl100 permit 2A02:2B90::/32
> ipv6 prefix-list ipv6-pl100 deny ::/0 le 128

I wrote the script when I was at $job[-2] and was on Juniper. I had
assumed at that time that IRRToolset was only for Cisco. Things have
moved on since then...

For the most part, my script is deprecated. You should use peval etc
where possible as:

1) It supports IPv6
2) It's supported
3) It can actually parse RPSL ;)

M



More information about the irrtoolset mailing list