- NZNOG - lists.nznog.org

nzwireless (ISP, ASN 24111) requesting peering with any interested parties on WIX and APE
by Anton Smith 23 Jul '07

23 Jul '07

Hi, As in the subject line, we would like to establish direct peering sessions with any interested parties at WIX and/or APE. Anyone interested please reply off-list to me to arrange peering :). Regards, Anton

1 0

Re: [nznog] History of the Internet in New Zealand
by Ian Batterbee 23 Jul '07

23 Jul '07

You reckon Mikey Havoc could turn that into a documentary ? I'm sure it would be just the sort of thing he'd love to do. > Note: About 3/4s of the above occurred at companies I was not working > for at the time or have never worked for and at least 2 have happened in > the last 12 months. My knowledge of most is 3rd hand ( except the "hacker > in the Star Wars tie" ). Some of them have appeared in the press though.

2 1

CFP: Systems Administration Mini-Conference at NZNOG 08
by Simon Lyall 23 Jul '07

23 Jul '07

Call for Presentations for NZNOG 2008: Systems Administration Mini-Conference http://nznog.miniconf.org We will be holding a network systems administration mini-conference in Dunedin, New Zealand on Wednesday 2008-01-23, as part of the New Zealand Network Operators' Group 2008 conference (http://2008.nznog.org/) The NZNOG 2008 conference will be held between 2008-01-23 and 2008-01-25. Registration at the NZNOG 2008 conference is a mandatory prerequisite for attendance at the mini-conference; we expect there will be no additional charge. Note: A similar Mini-conference is also intended to be held in Melbourne, Australia, a week later as part of linux.conf.au 2008. The mini-conference's focus is on "Layer 7" issues to do with network and ISP operations, including providing customer services (email, DNS, etc) and provisioning and management topics. We are now seeking proposals for presentations at the mini-conference. We have openings for: - 50-60 minute full presentations - 25-30 minute half presentations - 5-10 minute "lightning talks" - 5-10 minute "How we do things" presentations Presentations are expected to be directed at a technical audience, and focused on a system administration area related to network or ISP operations. Some possible topics: - Email servers and spam filtering techniques - DNS servers, registry systems - server security and best sysadmin practices in an Internet provider environment - VoIP servers - network management / monitoring tools - RADIUS/TACACS/LDAP - Netflow, routing, and traffic analysis tools - server tuning for high performance networking - provisioning tools - honeypots and other security techniques - network based storage - high availability and disaster recovery for network services - virtual machine technology for network services - *nix based routing and fire-walling - tools you need that you may not know about We are happy to discuss the suitability of other topics with intending presenters. The 10 minute "How we do things" presentations are intended for people to talk about their sites. Information could include: Servers, talks, tools, people and roles, experiences, software, operating systems, monitoring, alerting, provisioning etc. The intent is to give other attendees a picture of what is happening in the "real world" and some understanding of how other sites work and how to interact with them. Timeline: - Proposals due by 2007-11-19 - Selection advised by 2007-11-27 - Draft program published by 2007-11-30 - Presentations 2008-01-23 Please send all proposals and questions to <talks08(a)nznog.miniconf.org> Andrew McMillan, Ewen McNeill and Simon Lyall (Conveners)

1 0

peering mailing lists for NZIXs?
by Anton Smith 23 Jul '07

23 Jul '07

Hi all, I have a question for you all that has come up for me after spending most of my recent time up here in good old Iceland. The company I work for are connected to both LINX and AMSIX, and as some of you may know both of these exchanges have mailing lists that are used for such things as.. well, asking everybody else if they would like to peer. As part of the process of a new member coming onto the exchange, it is sent to the mailing list and all existing members can say 'yes, that organisation is perfectly fine to come on board, and yes, we will peer with them'.. or something along those lines (they might say, yes we don't mind them connecting but we won't peer with them). Where would be an appropriate place here in NZ to broadcast a desire to peer with anyone present at WIX and APE? How many organisations 'trust' the route servers? Is there a significant amount of missed peering traffic because some organisations have an open peering policy, but don't trust the route servers, and don't know where to broadcast a 'we would like to peer' message? The large carriers aside, are entities on WIX, APE, etc, missing out on some free peering simply because they don't know who else has an open peering policy? I notice that up here on AMSIX and LINX, it's very no nonsense and organisations often have a 'peering(a)xyz.com' mailbox, and anyone who is a member of the exchange can feel free to send mail to it (or just to the mailing list as happens reasonably frequently). In fact, it is built into the rules (at least on LINX), that you must monitor the mailbox and must respond within some time limit. Perhaps we don't need anything so formal, but maybe a peering mailing list for our IXs would be a good start. Or should we just use NZNOG? Regards, Anton

2 1

IPv6 Workshop
by Keith Davidson 22 Jul '07

22 Jul '07

All, What: IPv6 Technical Workshop, 6 - 10 August 2007 Where: InternetNZ, 10th Floor, Exchange Place, 5 - 7 Willeston St, Wellington When: 6 - 10 August 2007 What: Five day, hands-on workshop - IPv6 lab equipment, for up to 28 participants Who: Any technical people wanting to gain in depth knowledge of IPv6 Faraz Shamim (Cisco) and Gaurab Upadaya (Packet Clearing House) have kindly agreed to deliver their five day IPv6 Workshop in NZ. This workshop has been delivered at several APRICOT / APNIC / SANOG meetings in recent years. Faraz and Gaurab are experienced, world-class instructors on IPv6. The lab equipment consists of at least 14 Cisco routers and switches, a minimum of 1 set per 2 attendees. Nathan Ward will also be helping out with some of the sessions, particularly those relating to IPv6 transition strategies, and providing NZ specific insights. More details on this workshop at <www.internetnz.net.nz/events/ipv6workshop/ipv6workshop> The workshop is strictly limited to 28 attendees, on a first come, first served basis. Please confirm your attendance by emailing Susi Fookes, susi at internetnz.net.nz. Please include your daytime telephone contact number, and advise if you are able to supply your own laptop computer and advise if you are an InternetNZ member. For any details on the course contents contact Jonny Martin at internetnz.net.nz or by phone on 021 2304323. Regards Keith Davidson Executive Director - InternetNZ

1 0

Cisco 5500 bits
by Nathan Ward 21 Jul '07

21 Jul '07

I now work for WIC in Dunedin. We've got some Cisco 5500s, as we're keepin' it real, old-school style. Your Internet will likely traverse one (or more) of these 5500s when you attend NZNOG in January, so pay attention if you want reliable access to IRC. I'm interested in hearing from people who have spare parts for these that they'd be keen to move (for $, of course). It's better for the environment than throwing them out or dumping them in a store room, as they're not (AFAIK) RoHS compliant! Particular interest in: - GE modules - FE modules - Rack mount hardware (for 5513 - the one with 5 screws on to the chassis) - PSUs Additionally, if anyone has info RE the internal LEDs on a 5500 RSM (seemingly named CRXX, where X is a number), please let me know - we've got what appears to be a faulty one, and I'd like to figure out why. (Yes I know they're EOL) (Replies RE parts offlist please) (Also, any other unwanted router or switch hardware, I'd be interested to hear about too. If other people are after parts, I'll circulate some offlist summaries of what's out there to those who register interest with me.) -- Nathan Ward

1 0

Kiwicon 2k7 - Call For Presenters
by Simon Howard 20 Jul '07

20 Jul '07

[-----------------------------------------------------------------------] __ _ __ _ _ / ('>- / /__ (_) __(_)______ ___ '07 \__/ / '_// / |/|/ / / __/ _ \/ _ \ L\_ /_/\_\/_/|__,__/_/\__/\___/_//_/ [-----------------------------------------------------------------------] After travelling the world to attend many excellent security conferences with our compatriots, we decided it was time to pull finger and organise one in Aotearoa, New Zealand. This is the call for presenters for the inaugural Kiwicon. [WTF?] Kiwicon '07 will be a largely informal conference, organised by the security community for the security community. It will be held in Wellington, New Zealand, on the weekend of the 17th and 18th of November, 2007. It will focus on sharing information; ideas, code, and catching up with other like-minded people from around New Zealand (and further abroad). [Venue] Our hosts for the weekend will be Victoria University of Wellington. This location has the advantage of being close to cheap accommodation and, more importantly, several good pubs. Details will be provided closer to the conference date. [Costs] Kiwicon '07 is a non-profit event. Attendance for the entire weekend will cost $50 for employed individuals (self-employed and salaried). There is a discounted rate of $30 for students and the unemployed. Please do note that there are several good pubs in close proximity. We anticipate the total cost of the weekend in money and dignity may be higher. [Topics] Suggested topics include but are not limited to: - Information Warfare / Industrial Espionage - Satellite Hacking - Echelon - Waihopai & Tangimoana - Lockpicking / Wiretapping / Bugs - Biometrics - Cellular Networks (GSM,GPRS,CDMA,3G,4G) - Phreaking / VoIP - Web Security - Wireless / Bluetooth / Infrared / Fibre - Exploitation Techniques - Access Control and Authentication - Reverse Engineering - Application Security, Testing, Fuzzing - Code Auditing - Virtualization - Malware (Viruses, Spam, Phishing, Botnets) - Banking / ATMs / Carding - Crypto - Forensics / Antiforensics - 0dayz!!! We do not plan on having pre-determined time slots for presentations. If your talk is only 20 minutes long, then you will only be talking for 20 minutes. The goal of the weekend is to share useful information - this means flexible time limits. We already have a number of excellent speakers confirmed, to get a slot for a talk send an email to cfp(a)kiwicon.org with the following information: Name: Handle: Country of Residence: Employer (if applicable): Brief Bio: Presentation Title: Presentation Length: Presentation Synopsis: [The Team] Kiwicon is being duct taped together by the following people: pipes - Doing it all wrong since 1973 bogan - Proprietor of fine minced emails since 1822 antic0de - What is Freelist[] anyways? shammah - I know i left a rootkit around here somewhere hntr - Will you post my bail? metlstorm - True Norwegian back bacon Joshua - Defcon 3: I lost my password [Contacts & Further Information] Email us: kiwicon(a)kiwicon.org Check the site: http://www.kiwicon.org Drop by silc: silc.isig.org.nz:2706/kiwicon Join the list: kiwicon-subscribe(a)lists.isig.org.nz :wq

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jul '07

19 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by Inspire Net Ltd - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: james(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jul '07

19 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by Inspire.Net Ltd. - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: mds(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

TelstraClear RPF and caching
by David Robb 19 Jul '07

19 Jul '07

Hi all, Given the thread over the last couple of days asking how TCL is implementing RPF and transparent caching I thought a semi-official reponse might be useful. We have RPF (the ERXs call it SA Validate) enabled on DSL connections, and the filters applied to the cable modems implement the same functionality there. RPF is not enabled on non-residential services, nor it is configured within the core of the network. Regarding transparent caching, all international traffic passes through the caching infrastructure, although only certain IP ranges are matched for redirection to the caches. There's nothing in there which takes into consideration whether you have a mixed international/domestic link (sorry Philip :). Wholesale customers are very much in the "do not redirect" category, as most are multi-homed and the probability of encountering problems due to asymmetric routing are high. Residentially allocated IP Hi all, The caches themselves spoof the source IP of the client when making an outbound connection to the greater internet, because we've found that although there are occasionally issues caused by asymmetry the problems of cache IPs being blacklisted or DoSd are much fewer. Probably the most commonly observed scenario is where more specific routes are advertised by someone to their upstream (and thus internationally) than domestically (either directly to TCL or via Telecom or whatever) - a number of the routers on the TCL network carry a full routing table, and will prefer the more specific route out via the international path, thus feeding packets to the caches. The return path's then via the path one would normally expect, with the ensuing breakage of port 80 traffic. While this obviously isn't ideal, we do our best to work with the other ISPs to resolve this as fast as possible. --David Robb Network Design Engineer TelstraClear

1 1

History of the Internet in New Zealand
by Susi Fookes 19 Jul '07

19 Jul '07

Hi all, InternetNZ has commissioned Keith Newman to write a history of the Internet in New Zealand. The book will go to the publishers later this year. I have read the first few chapters and it is a fantastic read (I look forward to reading it all). He is near the final stages of writing and is now in search of photographs to help document the history. Can you help? If you have a photo(s) that could be of use – please contact Keith (wordman(a)wordworx.co.nz) or myself. And of course we will give you credit in the publication for allowing us to use the image. We are very eager to hear from you! Susi Fookes -- Project Administrator InternetNZ w +64 4 495 2117 | f +64 4 495 2115 | m +64 21 119 7539 susi(a)internetnz.net.nz | http://internetnz.net.nz PO Box 11-881, Manners Street, Wellington 6142, NEW ZEALAND

7 6

Re: [nznog] Telstra contact - BGP advertisements
by Anton Smith 18 Jul '07

18 Jul '07

> Message: 1 > Date: Wed, 18 Jul 2007 10:17:27 +1200 > From: "Nick Larsen (ZeroOne Operations)" <nick(a)zeroone.co.nz> > Subject: [nznog] > To: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> > Message-ID: > <E50D0676A6F98941BC86ED082F8F2AA407F9286275(a)e12be1.anywhereexchange.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > > Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). > It's regarding our prefix advertisements / asymmetric routing. > > Kind regards, > > Nick Larsen Hi.. sorry but I'm going to hijack this a bit. How many operators out there are using strict RPF? With a lot of interconnection points around the place to me it seems a bit harsh to use strict RPF. And in fact, I wonder if Telstra Clear are using it, since a lot of times I notice broken connectivity due to what appears to be asymmetric routing, and I then have to work around it. It seems to me that the internet is inherently asymmetrical, particularly between ISPs and their carriers. So, can someone please give me the low-down on what the most commonly thing done is w.r.t. asymmetry? Cheers :) Anton

7 8

Telstra contact - BGP advertisements
by Nick Larsen (ZeroOne Operations) 17 Jul '07

17 Jul '07

Hi, Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). It's regarding our prefix advertisements / asymmetric routing. Kind regards, Nick Larsen Network Technician ZeroOne (NZ) Limited 0800 ZEROONE www.zeroone.co.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jul '07

15 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: { 1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+ } remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes fltr-bogons - fltr-unallocated + fltr-martian http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 changed: rpsl-admin(a)nzix.net 20060914 changed: rpsl-admin(a)nzix.net 20070716 source: NZRR

1 0

Decent bandwidth required - Invercargill and AKL
by Richard Naylor 14 Jul '07

14 Jul '07

Hi there, I'm looking for some decent bandwidth in Invercargill for an event in August. 2 Mbps symmetric is all I need at the Ascot Park Hotel. Of course we'll always use more than 2Mbps if its available. The main thing is symmetric. Traffic will all be national, with the other end points at AKL and WLG and I'll probably hub out of WLG, so thats where most of the traffic will come from/to. Also looking for the same at ASB Arena (is this the showgrounds ?). It will also hub out of WLG and needs to be around 2Mbps. The event is one day, so we would be looking for (and pay for) connectivity on the Saturday, testing, rehearsals on the Sunday and Live on the Monday. Pack out Tuesday. Please save me the trouble of driving everywhere installing satellite dishes......then pulling them out..... Contact me off list of you can help. Thanks - Rich

1 0

gmail blacklisted at ahbl
by Blair Harrison 12 Jul '07

12 Jul '07

Hey folks, I've just discovered[1] that gmail appears to have been listed on the ahbl blacklist, which it appears at least one NZ ISP is using. If you're using the ahbl blacklist then I'd suggest either whitelisting gmail, or dropping this blacklist from your filters, I'd imagine there are quite a lot of legitimate messages getting blocked by this. [1] http://oldwww.temp.ahbl.org/tools/lookup.php?ip=gmail.com Cheers, Blair

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070608 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070606 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.37.114.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Jul '07

12 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jul '07

10 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jul '07

10 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070330 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR

1 0

New daylight savings setting for cisco...
by Barry Murphy 10 Jul '07

10 Jul '07

Hi, Can anyone confirm these daylight saving changes for cisco are correct? Solaris and a few other O/S's have already released their patches. Current: clock summer-time nzdt recurring 1 Sun Oct 3:00 3 Sun Mar 2:00 New: clock summer-time nzdt recurring last sun sep 3:00 first sun apr 2:00 Ref: http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Index Can't find anything else on the net where people have discussed this. Cheers Barry

4 3

Various email issues, including domains without MX records
by Martin Kealey 09 Jul '07

09 Jul '07

Hi all I've been paying attention to our mail logs lately and seeing some "interesting" stuff. So I was wondering... Does anyone run a serious (commercial) email operation in New Zealand without having appropriate MX records these days? (i.e. relying on the legacy behaviour of using A records in the absence of MX records.) What about web forms? What about embedded devices? What proportion of valid mail in NZ is sent from an address that doesn't have an MX record? Do you check? What do you do if it's not? If one were to block email from addresses without MX records, how much would break? How many complaints would one get? -Martin -- Martin D Kealey, ihüg engineering

9 9

Notification of NZRR Database changes
by NZRR Database Notifications 08 Jul '07

08 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS38602 as-name: NZRR-AS38602 descr: Pronet descr: APE peering at '192.203.154.38' descr: see Citylink RT job #9881 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38602 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS38602 descr: Route set advertised to AS9560 by Pronet - AS38602 members: 117.53.144.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS17484 as-name: NZRR-AS17484 descr: The Wellington Schools Loop Network descr: WIX peering at '202.7.0.40' descr: see Citylink RT job #9974 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17484 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17484 descr: Route set advertised to AS9439 by The Wellington Schools Loop Network - AS17484 members: 117.18.80.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR

1 0