Afternoon, It would be worth summarising some of the recent changes to NZNOG: There have been changes to the configuration of the route servers at APE, WIX, CHIX and HIX over the last couple of weeks. PNIX will be upgraded shortly, many thanks to Inspire for facilitating the PNIX upgrade. The significant changes are: 1) Route servers are now dual stacked for IPv4 and IPv6. This means that the v6 route servers no longer run on separate hardware to the v4 route servers and there are now two dual stacked route servers available in all locations (i.e. v6 is now rolled out at the CHIX/HIX as well as the APE/WIX). Please contact us if you would like a v6 peering session to match your existing v4 peering at any of these locations. IXP ASnum IPv4 servers IPv6 servers APE 9560 192.203.154.1 2001:7fa:4:c0cb::9a01 APE 9560 192.203.154.2 2001:7fa:4:c0cb::9a02 WIX 9439 202.7.0.2 2001:7fa:3:ca07::2 WIX 9439 202.7.0.3 2001:7fa:3:ca07::3 CHIX 24388 218.100.24.1 2001:7fa:3:5f44::1 CHIX 24388 218.100.24.2 2001:7fa:3:5f44::2 HIX 45279 218.100.56.1 2001:7fa:3:b0df::1 HIX 45279 218.100.56.2 2001:7fa:3:b0df::2 PNIX 9821 218.100.21.1 2001:7fa:3:265d::1 PNIX 9821 218.100.21.2 2001:7fa:3:265d::2 You can check your details using the Looking Glasses at http://nzix.net/cgi-bin/lg.cgi 2) Filtering has changed. The following filters are applied to inbound and outbound sessions. The only exception is in Wellington where prefixes up to /29 are still accepted. Our intention is to phase that out and standardise on /24 across all the exchanges as soon as possible. !++++++++++++++++++++++++++++++++++++++++++++++++++++++ ! ! IPv4 prefix list ! ! Bogon filters made from Team Cymru data ! Retrieved 'http://www.team-cymru.org/Services/Bogons/bogon-bn-agg.txt' (13 prefixes) ip prefix-list filteredIPv4-routes seq 5 deny 0.0.0.0/8 le 32 ip prefix-list filteredIPv4-routes seq 10 deny 10.0.0.0/8 le 32 ip prefix-list filteredIPv4-routes seq 15 deny 100.64.0.0/10 le 32 ip prefix-list filteredIPv4-routes seq 20 deny 127.0.0.0/8 le 32 ip prefix-list filteredIPv4-routes seq 25 deny 169.254.0.0/16 le 32 ip prefix-list filteredIPv4-routes seq 30 deny 172.16.0.0/12 le 32 ip prefix-list filteredIPv4-routes seq 35 deny 192.0.0.0/24 le 32 ip prefix-list filteredIPv4-routes seq 40 deny 192.0.2.0/24 le 32 ip prefix-list filteredIPv4-routes seq 45 deny 192.168.0.0/16 le 32 ip prefix-list filteredIPv4-routes seq 50 deny 198.18.0.0/15 le 32 ip prefix-list filteredIPv4-routes seq 55 deny 198.51.100.0/24 le 32 ip prefix-list filteredIPv4-routes seq 60 deny 203.0.113.0/24 le 32 ip prefix-list filteredIPv4-routes seq 65 deny 224.0.0.0/3 le 32 ! ! Don't allow default or prefixes over /24 ! ip prefix-list filteredIPv4-routes seq 70 deny 0.0.0.0/0 ip prefix-list filteredIPv4-routes seq 75 permit 0.0.0.0/0 le 24 ! !++++++++++++++++++++++++++++++++++++++++++++++++++++++ ! ! IPv6 prefix list ! ipv6 prefix-list filteredIPv6-routes seq 5 deny ::/0 ipv6 prefix-list filteredIPv6-routes seq 10 permit ::/0 le 48 ! !++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3) ICMP responses from the route servers. The route servers still respond to ICMP but only from the IX subnet. The servers no longer load the routes they learn via BGP into their own routing tables. If you are relying on a ping from some other network for alerts you'll need to do something else. We will be in touch in the next while as we sort out the PNIX. Cheers, Tim