- NZNOG - lists.nznog.org

pdf presentations from conference
by Mark Smith 28 Jan '08

28 Jan '08

are the presentations from the conference up on the web page yet? -- Mark Smith E mark.smith(a)endace.com P +64 7 957 0540 W http://www.endace.com Endace Technologies, Limited 85 Alexandra Street Hamilton Endace delivers absolute performance for monitoring and intervention over the widest range of network types and software applications.

5 6

Mac bits left behind at NZNOG08
by Jonny Martin 28 Jan '08

28 Jan '08

A Mac mini-DIV to DVI and 3-pin to cloverleaf mains lead where behind at NZNOG last week. Let me know if they belong to you, and I'll send them off. Cheers, Jonny.

2 1

Updated .nz Domain Growth Statistics
by Blair Harrison 25 Jan '08

25 Jan '08

Hello List, I've updated my graphs once again and they are available to view at http://jedi.school.nz/nzdg.html Please let me know if you have any comments or ideas for other ways to display this information. Cheers, Blair

1 0

Perry's NZNOG'08 IP-over-something challenge!
by Nathan Ward 23 Jan '08

23 Jan '08

I hereby issue the challenge to get IP running over the dishes photographed at: http://unobtainium.braintrust.co.nz/~nward/dishes/ Normally, you'd stand at one and talk, and someone standing at the other would hear you.. you've all played with these before. Perry's challenge is to make two laptops talk to each other, using sound. Note: These photos were taken in winter, which is why those girls have lots of warm stuff on. I have a tshirt on today, but it's raining a little. -- Nathan Ward

15 20

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by yuri 23 Jan '08

23 Jan '08

On 24/01/2008, Bruce Kingsbury wrote: > > > Does one person standing at one dish speaking IP and the person at the > > other end reconstituting packets count as a solution? > > What, an IPoV solution? Hmmm.. You mean like this http://xkcd.com/257/ ? Yuri

1 0

Re: [nznog] NZNOG Digest, Vol 61, Issue 14
by Stu Fleming 23 Jan '08

23 Jan '08

> > From: Matthew Poole <matt(a)p00le.net> > Subject: Re: [nznog] Perry's NZNOG'08 IP-over-something challenge! > > > For those who don't understand the terminology, Ed's talking about pouring > roughly 15L/sec of cold, high-pressure water on said drunk students. Who, > presumably, won't stay drunk for long :P You obviously haven't been to Dunedin lately... Does one person standing at one dish speaking IP and the person at the other end reconstituting packets count as a solution?

2 1

NZNOG 2008 live stream
by Jonny Martin 22 Jan '08

22 Jan '08

Hi All. The live stream is available at http://www.r2.co.nz/20080124/ Recordings of all the sessions will also be available online after the conference, thanks to Richard Naylor and co. at R2. Cheers, Jonny.

1 0

Could someone from Compass, Orcon, DTS, Xtreme, Actrix, etc. please contact me off-list?
by Jonathan Brewer 22 Jan '08

22 Jan '08

Preferably in Dunedin. There's this conference going on, with at least 130 network admins present, and there are a couple of companies conspicuously absent. Regards...

1 1

NZNOG'08 session recording
by Cameron Kerr 22 Jan '08

22 Jan '08

Hello, due to an itinerary clash, I'll be on a bus all day Friday travelling to another conference. I understand the conference will be streamed. Will it also be available post-conference? Any details so far (perhaps this should go onto the Wiki? Many thanks. -- Cameron Kerr <ckerr(a)cs.otago.ac.nz> Telecommunications Teaching Fellow & SysAdmin Cell: 027 7175 244

1 0

Re: [nznog] Perry's NZNOG'08 IP-over-something challenge!
by Jonathan Woolley 22 Jan '08

22 Jan '08

>The main point is that soaking the aforementioned hackers (yes I >know!) with a high pressure hose won't really make them sober up in >a >pharmacological sense, but it would be great fun. > >Cheers - N Pharmocologically sober them up: no, psychologically sober them up: yes. And I think it's the behaviour of said student hackers we care about, so aside from the enjoyment factor it may prove effective as well!

1 0

Sir Ed's Live feed
by Ian Batterbee 22 Jan '08

22 Jan '08

Just out of interest, was anyone able to watch the funeral on tvnz's website ? I tried it on a host of different browsers and settings and the best I got was an "error in page" in IE, and a flash app in firefox etc that wouldn't display any video at all (but I could change the bitrate settings) Just wondering if it was just me / my connection ?

6 6

NZNOG 2008 - Call for Lightning Talks
by Jonny Martin 22 Jan '08

22 Jan '08

NZNOG 2008 - Call for Lightning Talks ===================================== The NZNOG 2008 call for lightning talks is now open! Lightning talks are scheduled for 9am sharp, this Friday 25 January. Lightning talks are short talks/presentations on relevant topics that last no more than 10 minutes. They may be as quick as one minute. This time limit is strictly enforced. Talks on topics that are timely, interesting, or a little crazy, are invited. If you've thought about presenting at a future NZNOG, a lightning talk this year is a great place to start! The use of slides is not required although most people choose to use them. Speakers typically prepare three or four slides. Ideally you will provide final slides in PDF format so we can present of a common laptop. If you have other applications or anything special you wish to use in your presentation, you are welcome to use your own laptop, but please be ready for a speedy setup. To submit a proposal for a Lightning Talk, send an email to nznog08(a)jonnynet.net *** Proposals are due by 3pm Thursday 24 January, so hurry *** You can find some useful advice on giving Lightning Talks at: http://www.justanotherperlhacker.org/lightning/ http://perl.plover.com/lt/lightning-talks.html http://www.metaart.org/maca/perl/lightning/lightning_what.html Thanks! The NZNOG 2008 team.

1 0

Re: [nznog] Sir Ed's Live feed
by Richard Hulse 22 Jan '08

22 Jan '08

>>> Ian Batterbee <ibatterb(a)gmail.com> 22/01/2008 19:42 >>> > Just wondering if it was just me / my connection ? Based on the numbers in this press release: http://www.scoop.co.nz/stories/CU0801/S00171.htm and combined with our own figures and info from the non publically owned stations, I'd estimate that NZ broadcasters were doing in excess of 1 gigabit/s. There might have been a few bottlenecks around the place.

1 0

Re: [nznog] Perry's NZNOG'08 IP-over-something challenge!
by elroy 22 Jan '08

22 Jan '08

1) Connect Laptop1 sound-card audio-in and audio-out to appropriate small speaker(s)/mic (1) ; add your favourite *nix; 'cat <pre-made signal file> > /dev/dsp' 2) Same setup Laptop2 is listening for xxx signal level on mic input - writes a 1 to a file in RAM tempfile when above predefined level, then a 0 when below - insert appropriate programming magic to monitor tempfile and interface to something useable... 3) Profit!!! (Or IP-over-Audio) Elroy. (1) Would the laptop built-in ones be sensitive/powerful enough?!? NOTES: 1) Maybe different frequencies for each units send/receive so Duplex can be achieved?!? 2) Sorry Michael! Michael Fincham wrote: > How about a couple of old analog modems with 9v batteries to simulate being connected to a line, along with a little audio amplifier / receiver? I see duplex being a problem in that situation, but it's a start... > > As an aside, we had briefly discussed the possibility of establishing an RFC 1149 IPoAC link for VPN back to the office for our man on the ground at NZNOG but the link quality was deemed unsuitable.

2 1

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 20 Jan '08

20 Jan '08

> >From TVNZ's press release: >"In addition to TVNZ's own live broadcast on TV ONE, live streaming >on tvnz.co.nz and replay on TVNZ ondemand, TVNZ has offered the >broadcast free of charge to domestic and international radio and >television broadcasters and agencies. > >"So far the following news organisations have requested access to >the TVNZ feed: >ABC Australia, Al Jazeera, APTN, BBC, Channel 9 Australia, Channel 10 >Australia, CNN, EBU (European Broadcasting Union), Reuters Australia, >SBS Australia, Sky News Australia, Prime/Sky, Radio Works, TV Works, >and Newstalk ZB." > >One would assume that this is a clean feed, since it will be used >(domestically) by the competing networks too. in theory. Practise is different. Often we have to switch out the ad breaks, so we mix our cameras, with the feed. It doesn't matter now. The plan was that we would have started at 9am this morning and gone on non-stop "as required". We were to cover inside the Cathedral where Sir Ed is lying in state. Its a good application of robotic cameras and webcasting - sort of fly on the wall stuff. I don't think TVNZ are covering that and DIA didn't want cameras in there. I suspect DIA's decision was based on respecting people's privacy when paying their respects. No one wants a camera in their face or a close up shot, when they're grieving. As robot operator, theres no way I'd have gone close up, but you'd have to trust my judgement. It was probably just all too new for DIA. Our client was TV3 and it may have been seen as a competitve move. The word I got was that clean feed or iso feeds off host broadcaster cameras were not available and we had to do it ourselves. That would have been easy in the Catherdral and then when the casket moved to the funeral we would have just switched to the host feed. The OB is probably rigging today so no feeds would be available until tomorrow. Its all too late now...... Rich

1 0

Sysadmin Miniconf programme online
by Ewen McNeill 20 Jan '08

20 Jan '08

For those that are interested, the programme for the Sysadmin Miniconf at NZNOG 2008 (in Dunedin, this Wedesday -- 23 January 2008) is now online: http://nznog.miniconf.org/programme08.html Ewen

1 0

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 19 Jan '08

19 Jan '08

At 09:09 a.m. 20/01/2008, David Robb wrote: >On Sat, 19 Jan 2008, Richard Naylor wrote: > >>Sadly DIA has advised our client (a broadcaster) that we're not >>allowed to place our cameras on site and so the job has been canned. >>Its really sad as it was a great application for webcasting. But the >>powers that be have decided "no cameras". <sigh> > >"No Cameras", yet they're having cameras to feed out to TV screens >in the neighbouring cathedral and in the Domain..? > >You can't just get a feed from those perhaps? No - the plan was for us to webcast a different part of the 2 days, not the "main event", so it would have been our cameras. Often we take an "international" or "clean" feed and mix that with our cameras. There is some discussion as to whether an international grade clean feed is available. RNZ are unable to make a clean feed available. There have been some space issues. The bottom line is we were turned down. DIA don't want cameras in the bit we were asked to cover. Sorry I'll explain later over beer - a bit of broadcaster competition was occuring. On the bright side - its 20hours driving less to do, and Jeremy doesn't have to fly to NZNOG in/out of AKL. He gets to fly out of DNN to WLG - then drive to AKL. Rich

2 1

Re: [nznog] URGENT - broadband connex in AKL
by Richard Naylor 19 Jan '08

19 Jan '08

Evening All, Further to my request for urgent help - I received a heap of really great offers and with some help with a Microwave link from Parnell to SKY, we had it all sorted. Sadly DIA has advised our client (a broadcaster) that we're not allowed to place our cameras on site and so the job has been canned. Its really sad as it was a great application for webcasting. But the powers that be have decided "no cameras". <sigh> So a big THANKS to everyone. There was terrific generosity - everyone really pulled in and it would have been a great project. (with lousy hours though). Next time.... Rich

2 1

URGENT - broadband connex in AKL
by Richard Naylor 16 Jan '08

16 Jan '08

Hi folks, I have an urgent need for 1-2Mbps of IP capacity from AKL to WIX for Monday-tuesday next week for the Ed Hillary funeral. I ay use satelite, but if a wireless operator can do a link to the Sky Tower for good money, I'd love to hear from them. And yes we will drive the 1-2Mbps fairly hard Cheers Richard

1 0

Spam statistics for AA
by Thomas Layzell 16 Jan '08

16 Jan '08

Here's our statistic for the last year: Total Spam Messages Dropped 9,490,810 Total Virus Messages Dropped 1,300 Total Clean Messages Processed 1,787,289 THOMAS LAYZELL | NETWORK MANAGER | INFORMATION & COMMUNICATIONS TECHNOLOGY The New Zealand Automobile Association Incorporated

1 0

ICANN: JPA midterm review - have your say
by Save Vocea 15 Jan '08

15 Jan '08

(apology for any duplicate - slightly less tech in nature but worth sharing as its about DNS admin) Dear colleagues, My first mail in 2008 - so very warm greetings all. First up I'd like to highlight this very important information from ICANN. ccTLD managers in each economy have received this as well. ICANN in the past have had its fair share of critics "for/against" the current model or it's relationship with the US Govt and transition to independence. (just have to Goggle to read this) May I request those that particularly follow ICANN work (and those new to this space) to spare some time to read through the latest announcement from ICANN website particularly the "Joint Project Agreement - ICANN response" about the Notice of Inquiry put out by the USG regarding ICANN and the USG Joint Partnership Agreement. The documents referenced will clarify why ICANN was formed and delegated the role to perform the technical coordination and management of the Internet’s domain name and addressing system (DNS). ICANN's role is now in midterm review with this Notice of Inquiry requested for by the USG. http://www.icann.org/ As you will see from ICANN's submission, among other things, it is the view of the ICANN Board that: ~ The JPA like the memorandums of understanding before it has helped ICANN to become a stable organization; ~ ICANN has executed the terms of the JPA commenced in September 2006; ~ ICANN is meeting its responsibilities under the JPA; ~ The JPA is no longer necessary. Concluding it is the next step in transition of the coordination of the Domain Name System (DNS) to the private sector; ~ This step will provide continuing confidence that the original vision laid out in the White Paper is being delivered; ~ Concluding the JPA will not affect existing accountabilities expressed in the IANA contract and the United States Government¹s participation through the Governmental Advisory Committee. I am sure that both ICANN and the US Department of Commerce would appreciate hearing the views of the Internet community on this important review. As there's a very narrow window in which to tailor and submit responses/comments I hope I can again contact some of you to discuss or please feel free to contact me at any time to clarify. It will be useful under this review term that as many responses are received from those parties interested to have a say. I encourage those interested in this list to also contribute to this process and to add to a truly global response. Now is the chance to get your voices heard. Comments close on 15 February. regards, -- Save Vocea Global Partnerships Manager, Regional Relations - Australasia/Pacific Islands http://www.icann.org ICANN is about coordination, not control

1 0

iperf/AS7108
by jamie baddeley 14 Jan '08

14 Jan '08

Hi There, Does anyone have ssh access to a well connected host that can run iperf that is either directly connected or very near AS7018 in the US? If so, can you please contact me offlist thanks? Cheers Jamie

1 0

OT - Martin Hunt
by Richard Naylor 14 Jan '08

14 Jan '08

Some of the list members who were around in the early 90's may have known Martin Hunt, a Sysadmin based in Wellington. He passed away suddenly at home last week aged 46. There was a death notice in Saturday's Dominion Post. He was a really nice guy. Martin worked at Govt Print (with Don Stokes, Larry Hall and Ian Calhaem, etc), then WCC IT Dept and latterly at Fairfax Media. While at WCC he was one of the Sysadmins who looked after WCC CityNet. He was active in DECUS in the early 90's. A service for Martin will be held in St Lukes, cnr Pitt St and Wadestown Rd, Wednesday 16 January at 1100 (sadly I have to be working elsewhere). Messages to Martin's family c/o P O Box 50-347 Porirua, or I can pass on emails via his brother. A really nice guy. He will be missed. Richard

2 1

NZRR Route Registry Update
by NZRR Database Notifications 14 Jan '08

14 Jan '08

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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 210.54.142.0/23^23-29, 117.53.150.0/24^24-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080115 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64533 descr: advertised to AS9439 by ERMA - AS64533 members: 202.68.89.96/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Mark.Harris(a)ermanz.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64533 descr: advertised to AS9439 by ERMA - AS64533 members: 202.68.89.96/28^28-29, 202.68.89.120/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Mark.Harris(a)ermanz.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080115 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Using nolisting to reduce spam
by Glen Eustace 14 Jan '08

14 Jan '08

> The primary downside initially is that any legitimate server is doing > two transactions for every email. This would delay mail slightly and > increase queue lengths and CPU usage of every legitimate mail server > sending to you. If everybody implemented this it would load mail > servers up a bit. My observation would be that a TCP reject doesn't result in a requeuing of the email. With postix, it would appear that the smtp sending process immediately tries the MX in the chain upto a max of 5 ( but this is configurable ). There is a SYN packet, an RST and then a SYN to the secondary, not IMHO a significant overhead or delay. NB: The first MX must reject the connection not just drop it, otherwise the behaviour you describe does occur. > Again it is a temporary workaround but it might be worthwhile for > knowledgable system administrators. Over time the issues of spam still > need to be sorted out but that is a longer term project and is both > technical and political. It would seem that all spam solutions are just sticking plasters but a 'defense-in-depth' approach using multiple techniques does seem to be viable for the time being. Glen.

1 0

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

10 Jan '08

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:AS10022 descr: Route set for AS10022 members: 202.27.77.0/24, 202.175.136.0/21^+ admin-c: RPA1-NZRR tech-c: RPA1-NZRR mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS10022 descr: advertised to AS9439 by Datacom Systems Wellington Limited - AS10022 members: 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.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: matthewda(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080111 source: NZRR ------------------------------------------------------------

1 0

Sysadmin Miniconf: Lightning talks
by Ewen McNeill 09 Jan '08

09 Jan '08

I would like to hold a lightning talk session during the Sysadmin Miniconf stream at NZNOG 2008 (in Dunedin very soon; register now!). If you would be willing to talk for 5-15 minutes about either: - a tool, or technique that you find useful and think others should know about; or - how your AS looks after servers, users, etc (eg, what you use for deploying servers, how you manage trouble tickets, how you handle mail, etc) I'd like to hear from you soon. Email nznog08 @ nznog.miniconf.org to register your interest in speaking with an indication of how much time you need to cover your topic (eg 5 minutes, or 15 minutes). Also if anyone is willing to talk about: - Deploying IPv6 aware applications[0]; or - A comparision of trouble ticket/helpdesk systems (RT versus OTRS versus...) I'd love to hear from you ASAP. Email nznog08 @ nznog.miniconf.org with offers to speak. Other topics are of course welcome too, but I'd need to know this week. Ewen McNeill For the Sysadmin Miniconf [0] Yes, I know there's an entire IPv6 stream on at the same time. But a shorter overview of the application aspects would still be very useful especially from a sysadmin who has "been there, done that" without necessarily having got involved in IPv6 routing.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Jan '08

08 Jan '08

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: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 08 Jan '08

08 Jan '08

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:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 202.175.142.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.77.0/24^24-29, 202.27.160.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.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: brian.gould(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080109 source: NZRR ------------------------------------------------------------

1 0

NZNOG 2008 - reminder!
by Jonny Martin 07 Jan '08

07 Jan '08

[Apologies for any duplicates...] A quick reminder that the NZNOG 2008 conference is only two weeks away now. http://conference.nznog.org We need to finalise numbers very shortly now, so go ahead and register NOW if you intend to come and haven't already. The largely-finalised programme is up on the website, there's been some great new additions over the past month so do check it out at: http://conference.nznog.org/conferenceprogramme.html Thanks, and looking forward to seeing you in Dunedin! Jonny.

2 1

Call for nominations to APNIC Executive Council
by Srinivas Chendi 03 Jan '08

03 Jan '08

_______________________________________________ CALL FOR NOMINATIONS TO APNIC EXECUTIVE COUNCIL _______________________________________________ Three positions on the APNIC Executive Council will be opened for election at the APNIC Member Meeting in Taipei on Friday, 29 February 2008. The members whose positions are up for re-election are Akinori Maemura, Che-Hoo Cheng, and Vinh Ngo, who were elected at the APNIC Member Meeting in Perth on 3 March 2006. Nominations are due by the close of business on Tuesday, 12 February 2008 at the latest (5:30pm UTC+10 Brisbane time). Only APNIC members may nominate and vote for candidates, but nominees do not have to be representatives of members. Nominations must be made using the online nomination form available at: http://www.apnic.net/meetings/25/elections/ec.html For more information on nominations received, proxy registration, current EC members, and the role of the EC, please refer to: http://www.apnic.net/meetings/25/elections/ Online voting will be available for this election via the MyAPNIC web site and will open soon after the nomination period closes. If you are not able to vote online or attend the AMM, you can still make your vote count by appointing a proxy to represent you at the meeting. Proxy forms are available at: http://www.apnic.net/meetings/proxy.html Nominees should note that positions on the APNIC Executive Council are currently voluntary and that APNIC may not be able to reimburse EC members all expenses associated with EC duties. Where possible, however, APNIC will reimburse actual expenses for attendance at APNIC meetings, providing that these fall within budget and cash flow constraints. If you have any questions, please contact the APNIC Secretariat at secretariat(a)apnic.net. Regards, ________________________________________________________________________ APNIC Secretariat 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 ------------------------------------------------------------------------ See you at APNIC 25 Taipei, Taiwan, 25-29 February 2008 http://www.apnic.net/meetings/25 ------------------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 01 Jan '08

01 Jan '08

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 changed: rpsl-admin(a)nzix.net 20080102 source: NZRR ------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Dec '07

31 Dec '07

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Meetings Our next annual conference is to be hosted by the WAND group in Hamilton on February 2nd to 4th, 2005. See http://www.nznog.org/ for more information, including the Call For Presentations. Offers to present are due in by 22nd October, and all presenters should have had their acceptance confirmed by 31st October. Also see http://auckland.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. See http://www.wix.net.nz/ for the Wellington Internet Exchange. About This Mailing List This list has slightly over 700 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins Donald Neal |Palmersdale: Are you in charge here? Technical Specialist |The Doctor: No, but I'm full of Operations Engineering | ideas. Integration & Services Division +----------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

3 16

Seasons greetings message
by Elly Tawhai 20 Dec '07

20 Dec '07

Hi, Thank you for supporting APNIC this year. The APNIC Secretariat has created a short movie greeting for your enjoyment: http://www.apnic.net/flash/new-year-2008.swf We would like to wish you a safe and happy festive season and a prosperous new year. We look forward to working with you in 2008. Kind regards The staff of the APNIC Secretariat ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

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: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by KOrdia Ltd. - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-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, 202.174.190.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, 203.171.4.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 20071211 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-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, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 116.90.132.0/24^24-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, 203.171.4.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 20071221 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071128 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 20 Dec '07

20 Dec '07

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: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071128 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 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.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.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.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071221 source: NZRR ------------------------------------------------------------

1 0

Get your own strawberries email
by Dean Pemberton 19 Dec '07

19 Dec '07

Hi all. You no doubt will have all seen/heard about the latest viral (in the spreading, not the harming sense) email doing the rounds. http://www.stuff.co.nz/4330204a11.html I'm interested in what the breadth and depth of this email is, what the average branch size was etc. Could any of you who received the email (and if you got multiple copies that would be cool) forward me a copy with all the cascade still intact. I'm going to anonymise all the results, so don't worry about being identified. Dean

4 5

Updated domain stats
by Blair Harrison 19 Dec '07

19 Dec '07

Hi folks, I've re-done my domain stats spreadsheet / graphs to include the last three months. http://jedi.school.nz/nzdg.html I know the html version is ugly, Openoffice just doesn't seem to deal with it very well. Interesting to note that the net increase in domains last month was 5752, taking to a total of 311,198. Biggest jump yet, and crossed the 300,000 mark since I last looked at it all a few months ago :) Cheers, Blair

1 0

Flights to NZNOG...
by Jonny Martin 18 Dec '07

18 Dec '07

For all of you who have the impression that Dunedin is an expensive place to fly to... AirNZ currently have on offer, for 48hrs, discount flights to and from Dunedin ex Napier, Wellington, and Christchurch for $99, $89, and $59 respectively, one way. Travel valid for period 26 Dec through 31 Jan. Sounds good to me. http://airnz.co.nz/airfares_offers/hotdeals/hot_deals_fares/ new_zealand_summer_sale_19dec07.htm Oh, and did anyone remind you all to register for the conference? ;) Cheers, Jonny.

3 4

[Fwd: Re: Flights to NZNOG...]
by Dean Pemberton 17 Dec '07

17 Dec '07

Heh - nope - I can't get a refund on the $300 I paid for "Getting in Early" either =) Those prices are almost less than I paid in petrol to get to the last one in Palmie. Dean -------- Original Message -------- any way to get the refund on the USD 400 plus i have already spent to get there from AKL? :) --bill On Tue, Dec 18, 2007 at 03:07:03PM +1300, Jonny Martin wrote: > For all of you who have the impression that Dunedin is an expensive > place to fly to... > > AirNZ currently have on offer, for 48hrs, discount flights to and > from Dunedin ex Napier, Wellington, and Christchurch for $99, $89, > and $59 respectively, one way. Travel valid for period 26 Dec > through 31 Jan. Sounds good to me. > > http://airnz.co.nz/airfares_offers/hotdeals/hot_deals_fares/ > new_zealand_summer_sale_19dec07.htm > > Oh, and did anyone remind you all to register for the conference? ;) > > Cheers, > Jonny. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

NZNOG 2008 - Fellowship Program
by Jonny Martin 17 Dec '07

17 Dec '07

Hi All, The NZNOG Organising committee is trying something a little different this year and offering a small number of Fellowships to the conference. The aim of this is to provide assistance to those people that mightn't otherwise be able to come - but have a lot to offer to, or gain from, the NZNOG community. The fellowships will cover up to four nights accommodation at the NZNOG hostel and the conference registration fee. Five fellowship packages are being made available. Criteria for applicants: - They write a few paragraphs explaining why they need a fellowship to NZNOG08 and what they hope to get out of it, and otherwise convince us that they're not after a freebie for the sake of it being free. - Their employer can't or won't cover them and they're having to cover costs personally or they're a student / unemployed. - They have a history of involvement in the NZNOG community, or can demonstrate an intent to do so, or how attending an NZNOG community will benefit them. - It will help greatly if they are presenting a talk (or intend to) and wouldn't be able to without some form of fellowship assistance - They actually have to attend the NZNOG sessions, and not run off sightseeing or touring the local breweries! Submissions will be evaluated by the NZNOG 2008 organising committee. Email your submissions to prog08(a)nznog.org Closing date for applications 23:59hrs Wednesday 19th December (that's soon!) Successful applicants notified on Friday 21st December. For those of you who like something a little more than plaintext, all these details are at: http://conference.nznog.org/fellowships.html Cheers, Jonny.

2 1

<OT> Araneo is Hiring
by Jonathan Brewer 16 Dec '07

16 Dec '07

Hi Folks, We have a mid-level position at Araneo open in provisioning. Details on our website. http://www.araneo.net.nz/jobposting1207 Cheers, Jonathan Brewer -------------------------------- Araneo Limited 232A Left Bank 116 Cuba Street Wellington 6011 ph: 04 978 7350 fx: 04 978 7355 mb: 021 345 054 <http://www.araneo.net.nz/> www.araneo.net.nz --------------------------------

1 0

Re: [nznog] Xtra Mail Admin Contact Off List re White List - Reporting back
by Don Gould 16 Dec '07

16 Dec '07

This is a quick round up of my earlier post for those who are interested in these issues. It is provided for information, not to troll for a flame :) I got hold of Ted. Following a half dozen pointless emails, he confirmed today that the shared server I'm using is in the Yahoo! block list. Yahoo! run a 'voting' system that counts messages users put in to their spam folder from different locations and blocks those sites. HOW TO FIX THE PROBLEM Ted expressed that I needed to ensure that our shared service is filtering for spam, before auto forwarding, then apply to have the server block removed. http://help.yahoo.com/l/us/yahoo/mail/yahoomail/postmaster/defer.html MY CONSIDERED ISSUES Frankly I suspect that this may be pointless. I know that the shared server is used to host a number of applications that can be hacked (eg poorly written Joomla components) and used to leverage the sending of spam. I suspect that if I get it removed from the Yahoo! block list this week then I'll have to start over again next week as I do not have control over the rest of the server. I'd like to thank the person who suggested I contact Ted. I got the clear impression (and I mean 'impression') that he's as frustrated with the whole email thing as the rest of us. He referred me to many pages on the Yahoo! web site that were incomplete and did little to explain clearly how to fix these sort of problems. Frankly by the end of the week I felt very stone walled. FINAL OUTCOME / RECOMMENDATIONS You may recall the purpose of the 'auto forwarding' was to save the 27 users from having to reconfigure their client software. I have now told them that they do not have this option. They have to set up their mail client to read from the server and/or pay someone else to do it or use our web mail interface. So much for trying to same someone some hassle. We are also having ongoing problems with email messages taking time to exit Xtra's/Yahoo!'s mail system and getting delivered. I've expressed that they should change providers to a smaller firm who have a more reliable system that is not quite so subject to the load issues that a mail provider such as Yahoo! has. I'm sure it will come as no surprise that despite explaining this to the users, only 2 of the 30 users have change provider. I should have thought that 2 months free service, your own account manager and email delivered in seconds, would have been enough to entice the users to change - I was wrong. Cheers and thanks to everyone for their help, especially Ted! Merry Christmas, Don Blair Robson wrote: > I don't have a clue about whether this is true or not, but it was my > understanding that Xtra had some sort of deal with 3rd party mail > services such as http://www.smartmail.co.nz/ that exempted them from > the standard mail policies for a regular user.. (thereforn avoiding > problems like this... > > On 28/11/2007, *Brian Gibbons* <brian(a)outersite.co.nz > <mailto:brian(a)outersite.co.nz>> wrote: > > > >From: "Steve Phillips" <steve(a)focb.co.nz <mailto:steve(a)focb.co.nz>> > > I guess people have short attention spans here ;-) > > > > (Don, if you search the archives for posts from Ted Grenfell - > last one > > dated 7-12-2006, you should find his contact details) > > I think we all tried that.... > > Xtra no longer exist, they are a brand of Telecom and if you contact > Xtra(Ted) about this problem they/he will "refer" you to Yahoo who > are now > the provider of the service > > This is a bit like taking a product back to The Warehouse and being > told to > send it back to China yourself. A service company would take > ownership of > the problem. Xtra has not. > > By now I would expect an "Xtra" procedure for whitelisting a .nz server > (sorry Ted but this is a big time waster). > > Cheers > > BG > > > > ---------------------------------------------------------------------- > This e-mail message has passed virus scanning by Outersite Technology. > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz <mailto:NZNOG(a)list.waikato.ac.nz> > http://list.waikato.ac.nz/mailman/listinfo/nznog > > -- Don Gould 2/59 Peverel Street, Riccarton, Christchurch, New Zealand Phone: +64 3 348 7235 - Mobile: +64 21 114 0699 www.thinkdesignprint.co.nz

2 1

RT users in NZ
by Nathan Ward 13 Dec '07

13 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, I'm trying to convince a customer of mine that RT (Request Tracker, the ticketing system) is the way to go for ticketing for their organisation. The question has come up (as it always does for open source applications) of what the installed base in NZ is. Obviously this is hard to gauge, as there's no licensing etc. as there is for commercial solutions. So, are you using RT, or are you aware of people using RT, in anger in NZ today? (Private reply is fine) (Yep, I realise it's not hugely on topic, but an ISP list seems like it's have lots of RT users on it) - -- Nathan Ward -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.7.0 (Build 867) Charset: US-ASCII wsBVAwUBR2DSmqhXB4ariYS3AQgTPwf/QjGiQJWytZRDiN2dbVkjRn6Is9V0WMNE IpOXwnfu+1FxoFjyUIpzQKsWeALZBWbhoNBJEJgR7VNyBrmUjAdDvgW7svGFDkaI TaYm3cy4rufgxInjZpbh2Hn3nGWNzyXWtSoXA7DGaT2Xk0K3H4tqyhS6H0a+HL+T L3dfgPErxZmeoXd5vnO4rsRN61n8g0wKW24AgZYD09C8vfSM3tcSxpdRdY6KJ0dK m5vwHFXNcX3wo40r33/dYW4jwzN2ZOzOYS2qvfJuJ4Cs8tB+DePMUb//V1LyOSyV PkOKyXo5Cf9w7sVX7hd5aI8xKDoe7aqW5+vgfqkC45PkyzS2s8L5Hw== =IPrU -----END PGP SIGNATURE-----

4 3

Re: [nznog] RT users in NZ
by Ewen McNeill 12 Dec '07

12 Dec '07

In message <CE64FCF2-B49B-4A44-98B1-1DD4B81AB3BD(a)daork.net>, Nathan Ward writes: >So, are you using RT, or are you aware of people using RT, in anger in >NZ today? (Private reply is fine) I'm aware of three NZ ISPs (or ISP-like) organisations using RT for their ticketing system, at least one with moderately extensive customisations. As well as at least two other NZ organisations using RT for their internal task management.[0] My impression is that it's one of the most widely deployed open source task tracking systems outside development projects.[1] <subliminal>I'd be keen for someone to talk about ticketing systems and ticket triage/management at the Sysadmin Miniconf</subliminal> Ewen [0] I support some of these RT installs, but by no means all of them. [1] Developers tend to use Bugzilla or DebBugs or similar. Bugzilla in particular doesn't seem as nice to interact with as RT.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 12 Dec '07

12 Dec '07

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: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071029 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071213 source: NZRR ------------------------------------------------------------

1 0

NZNOG 2008 - Don't forget to register!
by Jonny Martin 11 Dec '07

11 Dec '07

Hi All, The NZNOG 2008 program has been largely finalised. The PC have done a great job providing a topical program with a great line up of both international and local speakers. Highlights are our keynote speakers, Geoff Huston, Philip Smith, and Bill Manning, alongside many fresh local presenters and a number of NZNOG regulars. APNIC and Team Cymru are providing a hands-on security tutorial on the Wednesday, alongside BGP and IPv6 tutorials and the popular Sysadmin Miniconf. Some tutorials are space limited and will be filled on a first-in basis. Full program details are available at: http://conference.nznog.org/conferenceprogramme.html In addition there are several co-located meetings taking place, with REANNZ, InternetNZ, and ISPANZ all holding meetings alongside NZNOG. There are now even more good reasons for you to come on down to Dunedin for NZNOG 2008. Numbers for the conference need to be finalised soon, so please register NOW! Cheers, Jonny.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Dec '07

10 Dec '07

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: 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, 116.89.224.0/20^20-29, 118.82.176.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-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, 202.174.190.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, 203.171.4.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 20070918 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by KOrdia Ltd. - AS24324 members: 118.148.0.0/15^15-29, 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-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, 202.174.190.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, 203.171.4.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 20071211 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] NZNOG Digest, Vol 60, Issue 6
by Tim Rowe 10 Dec '07

10 Dec '07

1 0