June 2012 - NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 24 Jun '12

24 Jun '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120502 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS38477 descr: advertised to AS24388 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120625 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 24 Jun '12

24 Jun '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS38477 descr: advertised to AS9439 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120502 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS38477 descr: advertised to AS9439 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 103.8.232.0/22^22-29, 103.11.124.0/22^22-29, 113.130.120.0/22^22-29, 114.23.96.0/22^22-29, 182.50.160.0/22^22-29, 202.44.60.0/22^22-29, 122.102.108.0/23^23-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 202.37.124.0/23^23-29, 103.246.250.0/24^24-29, 103.247.56.0/24^24-29, 131.203.133.0/24^24-29, 192.138.251.0/24^24-29, 202.50.102.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120625 source: NZRR ------------------------------------------------------------

1 0

New prefix at APE: 103.247.56.0/24
by Michael Fincham 24 Jun '12

24 Jun '12

Hi everyone, (cross-posted to NZNOG since nzix-route-announce still seems pretty much dead...) We intend to begin announcing the prefix 103.247.56.0/24 to the APE in approximately 2 weeks. This prefix will be originated from AS38477. This will bring our total set of (le 24) announced prefixes to: 114.23.96.0/22 originated from AS38477 113.130.120.0/22 originated from AS38294 path: 38477 38294 116.90.128.0/20 originated from AS38477 202.6.116.0/23 originated from AS38477 192.138.251.0/24 originated from AS38590 path: 38477 38590 182.50.160.0/22 originated from AS45641 path: 38477 45641 116.90.135.0/24 originated from AS45641 path: 38477 45641 202.37.124.0/23 originated from AS38477 131.203.133.0/24 originated from AS56102 path: 38477 56102 131.203.134.0/23 originated from AS56102 path: 38477 56102 202.44.60.0/22 originated from AS56214 path: 38477 56214 202.50.102.0/24 originated from AS38477 103.11.124.0/22 originated from AS38477 103.246.250.0/24 originated from AS38477 122.102.108.0/23 originated from AS38477 103.8.232.0/22 originated from AS132255 path: 38477 132255 103.247.56.0/24 originated from AS38477 -- -Michael Fincham System Administrator, Unleash www.unleash.co.nz Phone: 0800 750 250

1 0

Any spare Junipers?
by Nick Larsen 20 Jun '12

20 Jun '12

Hi all, Does anyone have any J2320's or SRX240h's for sale (in any condition, as just for a lab environment)? If so, please email nick(a)aptiv.co.nz Cheers, Nick Larsen

1 0

ARIN allows inter-RIR transfers.
by Dean Pemberton 19 Jun '12

19 Jun '12

Hi All, ARIN (the North American equivalent of APNIC) has just passed some new policy which has an impact for organisations in this region. There were three policies passed: ARIN-2011-1: ARIN Inter-RIR Transfers https://www.arin.net/policy/proposals/2011_1.html ARIN-2012-1: Clarifying requirements for IPv4 transfers https://www.arin.net/policy/proposals/2012_1.html ARIN-2012-3: ASN Transfers https://www.arin.net/policy/proposals/2012_3.html The impact for users in this regions is that APNIC members are now able to negotiate IPv4 Address Space transfers from organisations within the North American region. We have seen organisations in the ARIN region selling IP Address space in the past (Nortel selling 666k addresses to Microsoft for 7.5 million) , infact ARIN now has specific policy surrounding how to deal with a transfer in a bankruptcy scenario. The tricky part was that up until now they only allowed transfers to other members within the ARIN region. This meant that APNIC members were not able to get access to these resources and pull them into their APNIC account (and update the details around who currently holds them). This has now been changed so that as long as you can demonstrate to APNIC that you have a need for the addresses, and would have qualified for them under the old allocation scheme (ie when they still had addresses to give out), then you can transfer the numbers from the ARIN member into the APNIC region. This is generally considered a good thing. Having all users on an even footing is a step in the right direction. Anyone wanting some more clarification then feel free to post (if you think it's relevant to everyone) or mail me directly. Regards, Dean

5 5

InTAC invite
by Andy Linton 19 Jun '12

19 Jun '12

I forwarded something on this several days ago and I'm going to badger you once more about it. On Tuesday 10 July, InternetNZ is holding a one-day conference in Auckland to discuss issues related to the technical architecture and technical policy of ultra-fast broadband and fibre networks. See www.internetnz.net.nz/intac This is a chance for members of this group to meet with folks they often don't catch up with from the larger telcos and other industry players. We've got a couple of good speakers: Lev Gonick <http://www.case.edu/its/about/levgonick.html>, Chief Information Officer of Case Western Reserve University, Cleveland, USA Geoff Huston<http://www.apnic.net/publications/research-and-insights/geoff-huston>, Chief Scientist at APNIC and a chance to have some serious discussion about Technical Architecture Connectivity vs. Content UFB product specifications Technical Policy Keeping local traffic local - peering and interconnect Domestic and international IP transit

1 2

rs2.ape scheduled maintenence
by Tim Hoffman 17 Jun '12

17 Jun '12

Greetings, On Thursday 14 June Citylink will be taking rs2.ape (192.203.154.2) down for maintenance from 0800 till 0900. During this change window we will be observing a change freeze on the rest of the route servers nationwide. This is in preparation for upgrades which we are undertaking in the short to medium term. Cheers, Tim

1 1

ACL analyser
by Julian Maxwell 14 Jun '12

14 Jun '12

Hi All, I have a several-hundred-line extended ACL on a 6500, which is several years old and has had several admins over its time. As such, it is severaly (See what I did there?) ugly. I'm trying to find a tool that I can load this ACL into and it will tell me about redundant entries etc., as I have been given the envious task of moving the service it protects to a proper firewall. CiscoWorks ACL tool looks to be the business, but alas it's EOL and I can't find it anywhere. I don't want to pay hundreds/thousands for using something only once either. So what say you guys? Any suggestions on ACL managers? (Before you suggest, Gareth Evans ACL simulator won't work as you can't load ACL's into it). Cheers! Julian

3 2

RING Node in NZ
by Gaurab Raj Upadhaya 13 Jun '12

13 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Noggers, I'd think some of you may be interested in a project run by some friends of mine: the NLNOG RING. Project came out of the NLNOG (the Dutch NOG) discussions. It's based around the goals of making network debugging easier. When trying to debug complex problems and plan future upgrades, a point of view from outside your network is absolutely essential. Seeing what others see is incredibly useful when dealing with a variety of network problems. Well known examples are ‘it works for even numbered ip address, but not for odd numbered ip address via this and this route’. So tired of asking people to do traceroutes and wait for results, NLNOG RING was formed. In essence the project is very simple: you make a (virtual) machine available to the RING, and you gain access on all other servers which are part of the RING. The project currently has 108 nodes, located on 100 participant networks in 25 countries. Was just looking and see that NZ is missing on that list, the home of the rings, so thought I'd send this out. The RING provides tools to trivially launch a ping from all these nodes and summarize the results to, other examples are distributed tracerouting and MTU testing. The RING also maintains a record of latencies between nodes using smokeping to help identify historic problems. I say, have a look at https://ring.nlnog.net/ for more information. A map of current node locations is available here: https://ring.nlnog.net/map And email ring-admins(a)ring.nlnog.net directly with any questions you have. I am sure the they will send some good beer for the next NOG to make this on topic. - - gaurab -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/YkBwACgkQSo7fU26F3X2z9wCgo3bciqJuKD4TY48/TC9WEMH5 RPQAoO8o/lo4liNO1AjbVXAQpona6ETd =/AAz -----END PGP SIGNATURE-----

1 0

Reliability & performance of NZ carrier WAN/Internet services
by Josh Farrelly 13 Jun '12

13 Jun '12

Hi all One of our customers is looking at migrating away from their current WAN carrier and have nailed down their options to either FX Networks or Gen-i. This is a 3 office site (AKL/WGTN/CHCH) with relatively fat PIP pipes between all offices, and 20/30Mbps to the Internet from the AKL & WGTN locations using carrier managed BGP devices to allow for Internet failover. Obviously the overview of services according to the provider themselves are understandably at least somewhat bias, but I was wondering whether anybody from the NZNOG community has any objective views on each with regards to reliability and performance? For example FX seems to cost significantly less for relatively the same thing, however without personally having a lot of experience in provider topologies I can't justify being able to go back to the customer vouching for either provider either way. Any replies, either on or off-list are appreciated. Regards, Josh Farrelly

7 8