- NZNOG - lists.nznog.org

Auckland Power Outage
by Jonathan Brewer 24 Jan '10

24 Jan '10

Hi Folks, We're experiencing another fun and exciting power outage in Auckland. Thus far I can confirm we have end users without power (and presumably without UPS protection) in the following neighborhoods: Albany CBD Eden Terrace Ellerslie Mt Eden Ponsonby St. Mary's Bay We're on generator and battery at a number of POPs. We'll start worrying tomorrow morning if power is still out. Regards, Jonathan Brewer www.araneo.net.nz Ph: +64 4 978 7350 jon.brewer(a)araneo.net.nz

11 16

FW: Auckland Power Outage
by Robert Cotter 24 Jan '10

24 Jan '10

The lack of beer in the super markets just makes you appreciate the Quay Street store even more..........45 different flavours of beer last time I look. Also still have power in Victoria Street West CBD Regards Robert Cotter -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Alastair Johnson Sent: Monday, 25 January 2010 6:02 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Auckland Power Outage Michael wrote: > What's not to like? Westies. Lincoln Rd. The North-Western motorway citybound in the mornings. Biggest problem: Inability to buy beer or wine in supermarkets. -aj (former Westie) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This email is for the intended recipient(s) only. Be advised that if you have received this email in error that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. The sender cannot guarantee that this email or any attachment to it is free of computer viruses or other conditions which may damage or interfere with data, hardware or software with which it might be used. If you have received this email in error, please notify Distribution Central on +61 2 8986 5000 or notify sender.

1 0

GeoIP reliability within NZ
by Russell Fulton 24 Jan '10

24 Jan '10

HI folks I am trying to spot compromised (or just 'shared') accounts by looking at where logins are coming from. I am doing this by using the free city data base from www.maxmind.com. If this works out we will probably pay for the full product. Anyway, my question for the list is "Just how reliable are these services for IPs within NZ?" Here is a sample from yesterday (with user names removed) -- each line represents source IPs for logins for an individual user: 219.89.198.13 (NZL - Auckland)121.72.9.137 (NZL - Hamilton) 121.90.27.131 (NZL - Wellington)121.90.122.37 (NZL - Auckland)121.90.74.159 (NZL - Auckland) 122.57.145.200 (NZL - Auckland)202.49.164.5 (NZL - Tauranga) 115.189.161.73 (NZL - Hamilton)115.189.179.137 (NZL - Waiuku)115.189.145.152 (NZL - Thames) 121.90.0.218 (NZL - Auckland)121.90.111.192 (NZL - Dunedin) 79.149.142.140 (ESP - Madrid)121.98.170.93 (NZL - Auckland)95.124.89.94 (ESP - Madrid)95.124.67.187 (ESP - Madrid) 121.72.217.194 (NZL - Manukau City)121.72.180.138 (NZL - Auckland)210.246.2.132 (NZL - Auckland) 129.132.128.136 (CHE - Zürich)130.132.123.28 (USA - New Haven) 203.82.92.164 (MYS - Johor Bahru)203.82.80.55 (MYS - Kuala Lumpur)203.82.80.49 (MYS - Kuala Lumpur) 118.93.234.249 (NZL - Auckland)118.92.201.194 (NZL - Whangarei) 118.90.64.249 (NZL - Hamilton)118.90.103.244 (NZL - Auckland)118.90.108.245 (NZL - Auckland) 222.154.97.215 (NZL - Whangarei)121.98.180.58 (NZL - Auckland) 121.72.9.243 (NZL - Hamilton)121.72.24.158 (NZL - Auckland) 202.27.76.119 (NZL - Auckland)222.154.97.134 (NZL - Whangarei) 139.80.123.38 (NZL - Dunedin)132.239.1.230 (USA - La Jolla)139.80.123.34 (NZL - Dunedin)118.17.75.101 (JPN - Osaka) Some of these are clearly suspicious -- Auckland and Madrid ? Dunedin, US, JP ? but what about the ones within NZ? Yes, some of these locations may well be correct and the usage legit (people do travel) but the number seems high. Russell

1 0

1/8 and 27/8 allocated to APNIC
by Leo Vegoda 21 Jan '10

21 Jan '10

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in January 2010: 1/8 and 27/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. The IANA free pool contains 24 unallocated unicast IPv4 /8s. Regards, Leo Vegoda Number Resources Manager, IANA ICANN

6 9

Conference stuff
by Dave Mill 21 Jan '10

21 Jan '10

Hi all A few conference bits and bobs. The NZNOG 2010 conference runs from Wed 27 to Fri 29 Jan, 2010 in the friendly city of Hamiltr0n. Registrations are open so please register ASAP. This year we're doing something slightly different - our 3 day routing workshop from Monday to Wednesday. Until today we didn't have Monday night accomodation available - that is now fixed and available on the conference registration system. http://2010.nznog.org/register Accomodation on campus, especially Monday night, is limited in terms of numbers. So if you want to be staying on campus please register soon. We now have a programme online - http://2010.nznog.org/full-program . This should be a close to final programme, I wouldn't expect too many changes from here. This should help convince employers that NZNOG is a worthwhile conference for you to attend. I'd also like to thank all of our sponsors. In particular Vocus who have come aboard as a Platinum sponsor this year plus WAND and Rural Link who are hosting this years' conference. Without our sponsors the current style (and price) of the NZNOG conferences would just not be possible. NZNOG 2010 Sponsors - http://2010.nznog.org/cms_display.php?sn=11 Did I mention to register soon? Hope to see you there! Cheers Dave

1 1

Two /8s allocated to APNIC from IANA (1/8 and 27/8)
by Elly Tawhai 20 Jan '10

20 Jan '10

_______________________________________________________________________ Two /8s allocated to APNIC from IANA (1/8 and 27/8) _______________________________________________________________________ Hi NZNOG Community, The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in January 2010 and will be making allocations from these ranges in the near future: 001/8 027/8 Reachability and routability testing of the new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Please be aware, there are now just twenty-four /8s remaining in IANA's unallocated IPv4 address pool. Thank you for your cooperation. If you have any questions, please contact the APNIC helpdesk helpdesk(a)apnic.net Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

NZ NOG Entertainment
by Corinne Cowlishaw 20 Jan '10

20 Jan '10

Hi everyone, I would just like to thank you all for your help and suggestions for the entertainment for next Thursday night, it was really helpful! Taking all offers into consideration we have come to a decision. After the dinner, Vocus' buses will take us all to the casino where we'll have gambling (with fake money ;) and drinks. Looking forward to seeing you all there. Kind Regards, Corinne Cowlishaw Administration Assistant Level 1, 189 Miller St North Sydney, NSW 2060 T: +61 2 8999 8999 E: corinne(a)vocus.com.au W: www.vocus.com.au

1 0

Less than 10% of IPv4 Addresses Remain Unallocated
by Elly Tawhai 19 Jan '10

19 Jan '10

_______________________________________________________________________ Less than 10% of IPv4 Addresses Remain Unallocated, says Number Resource Organization _______________________________________________________________________ Hi NZNOG Community, Deploying IPv6 - the next generation of the Internet Protocol - is vital to the continued development of the Internet AMSTERDAM - The Number Resource Organization (NRO), the official representative of the five Regional Internet Registries (RIRs) that oversee the allocation of all Internet number resources, announced today that less than 10 percent of available IPv4 addresses remain unallocated. This small pool of existing IP addresses marks a critical moment in IPv4 address exhaustion, ultimately impacting the future network operations of all businesses and organizations around the globe. "This is a key milestone in the growth and development of the global Internet," noted Axel Pawlik, Chairman of the NRO. "With less than 10 percent of the entire IPv4 address range still available for allocation to RIRs, it is vital that the Internet community take considered and determined action to ensure the global adoption of IPv6. The limited IPv4 addresses will not allow us enough resources to achieve the ambitions we all hold for global Internet access. The deployment of IPv6 is a key infrastructure development that will enable the network to support the billions of people and devices that will connect in the coming years," added Pawlik. Internet Protocol is a set of technical rules that defines how devices communicate over a network. There are currently two versions of IP, IPv4 and IPv6. IPv6 includes a modern numbering system that provides a much larger address pool than IPv4. With so few IPv4 addresses remaining, the NRO is urging all Internet stakeholders to take immediate action by planning for the necessary investments required to deploy IPv6. The NRO, alongside each individual RIR, has actively promoted IPv6 deployment for several years through grassroots outreach, speaking engagements, conferences and media outreach. To date, their combined efforts have yielded positive results in the call to action for the adoption of IPv6. Given the less than 10 percent milestone, the NRO is continuing its call for Internet stakeholders, including governments, vendors, enterprises, telecoms operators, and end users, to fulfill their roles in IPv6 adoption, specifically encouraging the following actions: The business sector should provide IPv6-capable services and platforms, including web hosting and equipment, ensuring accessibility for IPv6 users. Software and hardware vendors should implement IPv6 support in their products to guarantee they are available at production standard when needed. Governments should lead the way by making their own content and services available over IPv6 and encouraging IPv6 deployment efforts in their countries. IPv6 requirements in government procurement policies are critical at this time. Civil society, including organizations and end users, should request that all services they receive from their ISPs and vendors are IPv6-ready, to build demand and ensure competitive availability of IPv6 services in coming years. The NRO's campaign to promote the next generation of Internet Protocol continues to positively impact the Internet community. IPv6 allocations increased by nearly 30% in 2009, as community members continued to recognize the benefits of IPv6. "Many decision makers don't realize how many devices require IP addresses - mobile phones, laptops, servers, routers, the list goes on," said Raul Echeberria, Secretary of the NRO. "The number of available IPv4 addresses is shrinking rapidly, and if the global Internet community fails to recognize this, it will face grave consequences in the very near future. As such, the NRO is working to educate everyone, from network operators to top executives and government representatives, about the importance of IPv6 adoption," added Echeberria. IP addresses are allocated by the Internet Assigned Numbers Authority (IANA), a contract operated by the Internet Corporation for Assigned Names and Numbers (ICANN). IANA distributes IP addresses to RIRs, who in turn issue them to users in their respective regions. "This is the time for the Internet community to act," said Rod Beckstrom, ICANN's President and Chief Executive Officer. "For the global Internet to grow and prosper without limitation, we need to encourage the rapid widespread adoption of the IPv6 protocol." ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: 61 7 3858 3100 PO Box 2131 Milton, QLD 4064 Australia Fax: 61 7 3858 3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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:AS9503 descr: Route set advertised to AS24388 by FX Networks - AS9503 members: 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: service(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Jan '10

19 Jan '10

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091208 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.160.48.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.50.247.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 202.89.43.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR ------------------------------------------------------------

1 0