- NZNOG - lists.nznog.org

Old Newby
by Allister Clarke 11 Jan '07

11 Jan '07

Hello. I am back. Last posted while at Waikato uni in 2002. Hello Lindsay if you are still around? Al.

1 0

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

10 Jan '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:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.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.164.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 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, 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, 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.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: thomas.salmen(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070111 source: NZRR

1 0

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

10 Jan '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:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 123.100.64.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, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.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: simon.allard(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061011 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, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.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.54.142.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 20070111 source: NZRR

1 0

Greylisting New Zealand whitelist
by Simon Lyall 08 Jan '07

08 Jan '07

Andy wrote: > You can see the routes advertised at the APE and WIX on the pages: > but it does provide a couple of lists that by some definition are in NZ. I don't know what "some definition" is but by most definitions there are quite a few non-NZ IPs there ( Specificly things like 203.59.0.0/17 that ihug advertising on behalf of iinet). Anyway, you don't want random IPs home luser IPs for greylisting, you want IPs that are sending you non-spam email. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

9 13

[NZNOG 07 Conference] Registrations over the Holiday Period
by Mark Foster 08 Jan '07

08 Jan '07

Folks, Unfortunately it seems there was a glitch in the backend of nznog.org during the Christmas period. Anyone who registered for NZNOG during the holiday period _and did not receive an emailed confirmation__ - could you please re-register via http://www.nznog.org. If you are in any way in doubt, could you register again anyway. We'll be watching for duplicates. Sorry for the trouble. Regards Mark

2 1

Greylisting New Zealand whitelist
by Gerard Creamer 08 Jan '07

08 Jan '07

Hi there, Is there a list of NZ networks or mail hosts that are considered OK for whitelisting in an email greylisting implementation? I realise that there are trust issues etc etc but what I want to do is have domestic mail from known providers (ie ISPs and hosting providers) essentially unhindered by the usual time delay of greylisting. We're using qmail, and the greylisting options are a bit basic. If there isn't a list would I be correct in assuming that moving to postfix and using postgrey with its database learning / remembering option would be a smart move? I realise that this is verging on off topic, but my googling has netted ziltch. Regards, Gerard

4 3

[NZNOG 07 Conference] Registration Reminder
by Mark Foster 07 Jan '07

07 Jan '07

Good morning all, I imagine many of you are back at work now, so it seems timely... *** NZNOG Accommodation *** If at all possible, would people intending to attend NZNOG 07 who are looking to take advantage of the Hostel Accommodation please book _this week_. If you are unable to book this week for some reason but would still like to make use of the Hostel facility, could you please fillin the contact-us form ( http://www.nznog.org/contact.html ) and let us know what your requirements are likely to be, in order that we can plan around it. I would encourage people to make their bookings sooner rather than later, as this will greatly assist us in the planning of this event. The timing is unfortunate, and for this we apologise, but remember that conference is not far away... ! For further info check out http://www.nznog.org Cheers all, Mark For the Org Committee...

1 0

Network Systems Miniconference
by Nigel Roberts 03 Jan '07

03 Jan '07

The link for this is broken on nznog.org: http://www.nznog.org/networksystemsminiconference.html So those in the know, what's this all about then? Happy new year, Nigel

4 3

Re: [nznog] Bus/Train to NZNOG
by Martin Kealey 03 Jan '07

03 Jan '07

Darn, I'm going to have to get to Curry more often... this is much the same idea I had. Count me in, plus 2 others from Ihug. How many people have you heard from so far? I ask because we're hoping we can get Ihug to pay for a bus, which means it'll be very cheap for the individuals travelling. If we get enough we'll get a coach (in which case it WILL be cheap, because I'll be driving). As I see it, the only snag is agreeing on dates & times; my preference would be for a longer period -- go for the first tutorial, back after taking a weekend tour of the town (and visiting friends) -- but it's not essential. -Martin > -----Original Message----- > From: Joel van Velden [mailto:joel(a)tpnz.co.nz] > Sent: Tuesday, 19 December 2006 12:01 > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Bus/Train to NZNOG > > Hi all > > The idea was floated at last weeks Curry in Auckland about > hiring a bus > to travel to NZNOG, as there would possibly be quite a number > of people > between Auckland and Palmerston North interested in a less > stressful and > cheaper means of getting there. > > I have no idea of what numbers would be required at this stage or what > the cost would be. Obviously it would be cheaper than flying, but take > longer to get there. > > The other alternative might be to group-book the train, which has > tables, not sure about AC power, you can walk around, is apparently > newly-refurbished, but probably takes a little longer than a bus, and > possibly more expensive. > > Is anyone is interested? > Contacting me off-list would be best. > > Regards, > Joel van Velden > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Re: [nznog] Telstra's Outage
by jdmwoolley＠ihug.co.nz 01 Jan '07

01 Jan '07

Steve Wray wrote: > Redundancy isn't really what I mean; more > forward-thinking. So if a TelstraClear engineer thought about it really hard the truck would have missed the fibre? Personally, I don't think the power of prayer is a valid network protection scheme. Though when I used to work there, it was useful on occassion ;) > From what I've heard out of Telstra people -- and > thats just the faults and 'helpdesk' people, the > attitude seems to be that a 'truck hitting a > pole' is not something that could have been > foreseen and that therefore there was no point in > having a contingency plan to deal with it. > > To me, this just seems wrong-headed. > > My question for Telstra is, was there a plan? How > well did it work out? > If they didn't have a plan or if it didn't work out > well, how are they going to address this in future? > And the answers I've been getting back from Telstra > people are rather disconcerting. A quick talk about how things are done in a Telco may be in order. 1. You need money to do everything. This includes laying fibre, writing plans and taking a toilet break. 2. There are two types of money to be spent - OPEX and CAPEX (OPerational expenditure and CAPital expenditure). 3. OPEX is evil. Accountants see it as a black hole that money is thrown down. It is not an investment. It is paying some guy for something you already own. OPEX is constantly cut. Many things that should be done as OPEX are classed as CAPEX by squinting your eyes and with the aid of smoke and mirrors. 4. CAPEX is ok - it is investing money in something with the expectation of a return at some point in time. Dig a hole, lay a cable, charge people to use it, eventually they've paid you more than it cost you to lay - this is CAPEX. You need a business case to spend CAPEX. This will consist of all likely and unlikely costs and revenues; and consequently a best, worst and expected-case return on investment. If the company thinks this is the best way to spend it's money it will do it. If it thinks it can make a larger profit or the same profit in a shorter time frame elsewhere it will do that. This is The Way It Works(tm) for a Telco and most businesses. If you can write a business case showing that getting 1000 monks in Tibet to pray for the safety of TelstrClear's network will turn a profit then they will do it. If prayer wasn't what you meant by "forward-thinking", and redundancy wasn't it then I'm at a loss. What else could they do? Not lay the fibre there? That location was probably the place that brought the best return on investment to justify the CAPEX. Could there have been a better place to put it - probably. Do companies have the time to second guess every decision made? Or will someone else beat you to the punch if you do that? Sorry for the massive rant, but berating a company, any company, for doing their best to fix a fault caused by some truck driver who was likely high on P at the time just seems like cynical people trying to complain about nothing to me. Sure, if you were one of the people affected it must've really sucked. In the end them's the breaks. On a lighter note, Merry Christmas to everyone - try to shake off the cynicism and anger that accumulated through the year at the beach this summer! Jonathan

5 5

Virus alert
by Lesley Walker 28 Dec '06

28 Dec '06

Looks like there's a new email worm/virus epidemic on the go. We've quarantined over 1100 incoming emails since 2pm, and we normally only get a trickle. ClamAV reports "postcard.exe contains Trojan.Downloader-388", and the subject line is "Happy New Year". Just what we all need. :-( Lesley W (Happy to be running Ubuntu)

3 2

Re: [nznog] Telstra's Outage
by Steve Wray 28 Dec '06

28 Dec '06

(sorry about lack of threading etc, I clipped the text out of the web-based archive) Jonathan wrote: > David Robinson wrote: >> >> "For a start, it takes more than two fibre cuts in the > North Island to >> disrupt us" >> >> And also remember back early in the year when one slip on the Hutt >> motorway took out all services in Wellington. >> >> What is so wrong with Telstra's network that single events can affect >> so many people, when supposable it takes more than two fibre cuts to >> disrupt them? > > This post you've quoted was related to the core network - > i.e. the bits that connect Wellington to Auckland etc. This > is a fault in the access network i.e. the bit that connects > Mary and Bob (or in this case Kandallah) to the core > network. NO operator has full redundancy in the access > network for residential services. What amazes me is that Telstra maintain that a truck hitting a pole was a *completely* unforseeable event and that even in retrospect they could not have been expected to have forseen that *one* *day* a truck would hit a 'single-point-of-failure pole' and that they could not have been expected to have planned for it. I ask you, is that really reasonable? I thought that engineers were the types of folk would look at diagrams of such a network and say: "well this pole is a single point of failure and its right by a road. Sooner or later its going to get hit by something, we'd better plan for that". I don't get the feeling that TC *had* planned for it... though maybe they did and if they hadn't planned for it we'd be disconnected till the new year... Insights anyone? Also, is there anywhere which keeps a log of outages experienced by NZ ISP's, how long they last etc? Thanks

4 4

Connection reliability (was Re: Telstra's Outage)
by Matthew Poole 21 Dec '06

21 Dec '06

On Thu, 21 Dec 2006, David Robb wrote: > On Thu, 21 Dec 2006, Simon Allard wrote: > >> You can't expect good uptimes and run your business which requires high >> availability internet on a $39.95 DSL account. > > Good, Fast, Cheap. Pick any two. > Where Good==Reliable, I assume? Since the relative goodness of broadband products for most consumers is often associated with their fastness and cheapness, with reliability (provided one can actually pass packets, of course) being an unconsidered factor. I do agree with Dean that we know you can't reasonably expect multiple nines of reliability from a residential service, but we, as geeks, have far different expectations from the average consumer. Plus, with NZ's high incidence of home-based businesses, how many users have actually had ANY choice of carrier until quite recently? I can probably get Woosh at home, and we have a Telecom landline. What are my other choices? TCL is still delivering over TCNZ's cable, so that's a non-starter. I could maybe get hooked into Vector's fibre, though I don't think it comes quite far enough down Great South Rd. And I'm in a better position than a lot of residential users, who can't get Woosh and aren't even close to someone's fibre network. When people have no choice, is it any wonder that they expect the earth for nothing? Nobody's telling them about the limitations of the one service they can afford, and nobody's offering them anything with better reliability for a reasonable price - what would one pay for a 2Mbps frame connection that, while unquestionably giving better upstream performance, comes in, at best, at half the downstream speed of a DSL connection? Many, many multiples of $40/month, that's for sure. Total no-brainer. We can sneer at the great unwashed, but the reality is that the marketroids aren't offering anything to fill the gaping void between DSL and frame/ISDN (does anyone even use ISDN for data anymore?). PS: Why pay metric boatloads for something like frame when Telecom won't give you credit if their network fails? Nobody got a cent out of them after the rat and the errant backhoe took out much of the country for several hours, so what's the point in handing them extra? Pardon the pun. -- Matthew Poole "Don't use force. Get a bigger hammer."

16 20

Re: [nznog] Telstra's Outage
by Simon Allard 20 Dec '06

20 Dec '06

Actually, I think it's the other way around. The reason NZ has 3rd rate broadband, is customers expect the world for free. You can't expect good uptimes and run your business which requires high availability internet on a $39.95 DSL account. I agree with everything Dean said, and I bet I am not the only one. -----Original Message----- From: John @ netTRUST [mailto:john(a)nettrust.net.nz] Sent: Thursday, 21 December 2006 11:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Telstra's Outage > Nothing used to piss me off more than the cable customer who used to > compain (without logging trouble tickets BTW) that thier home business > was losing money because their cable modem was down.... > > You buy a residential service - thats what you get. This type of arrogance from a NOC is why NZ has 3rd rate broadband. ADSL and cable are widely marketed to businesses and indeed business connections usually makes up the lions share of revenuw generated by these services. Let's hopen they keep you, and others with the same opinion, in the back room as far from customers as possible -or- put another way you should be using your l33t skills to substantally improve the reliability rather then having too much time on your hands digging for excuses. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

13 17

Re: [nznog] Telstra's Outage
by jdmwoolley＠ihug.co.nz 20 Dec '06

20 Dec '06

John @ netTRUST wrote: > antedotal evidence Erm, perhaps you meant anecdotal? http://www.m-w.com/dictionary/antedotal http://www.m-w.com/dictionary/anecdotal (sorry, couldn't resist - beer!)

1 0

Telstra's Outage
by David Robinson 20 Dec '06

20 Dec '06

Hi, With Telstra's outage taking out the Northern and Western suburbs of Wellington. For what I gather it was a single truck crash bringing down the overhead wires. A single truck crash is a single point of failure, but I remember this email http://list.waikato.ac.nz/pipermail/nznog/2005-June/010158.html which says: "For a start, it takes more than two fibre cuts in the North Island to disrupt us" And also remember back early in the year when one slip on the Hutt motorway took out all services in Wellington. What is so wrong with Telstra's network that single events can affect so many people, when supposable it takes more than two fibre cuts to disrupt them? David

6 5

Re: [nznog] Telstra's Outage
by jdmwoolley＠ihug.co.nz 20 Dec '06

20 Dec '06

David Robinson wrote: > > "For a start, it takes more than two fibre cuts in the North Island to > disrupt us" > > And also remember back early in the year when one slip on the Hutt > motorway took out all services in Wellington. > > What is so wrong with Telstra's network that single events can affect > so many people, when supposable it takes more than two fibre cuts to > disrupt them? This post you've quoted was related to the core network - i.e. the bits that connect Wellington to Auckland etc. This is a fault in the access network i.e. the bit that connects Mary and Bob (or in this case Kandallah) to the core network. NO operator has full redundancy in the access network for residential services. If you want that, you need to pay through the nose to get a business service, even then most services give you only a single copper pair/fibre/cable to your premises which is still a single point of failure. Jonathan

6 5

Re: [nznog] Telstra's Outage
by Scott Weeks 20 Dec '06

20 Dec '06

--- dave.robinson(a)gmail.com wrote: From: "David Robinson" <dave.robinson(a)gmail.com> With Telstra's outage taking out the Northern and Western suburbs of Wellington. For what I gather it was a single truck crash bringing down the overhead wires. A single truck crash is a single point of failure, but I remember this email http://list.waikato.ac.nz/pipermail/nznog/2005-June/010158.html which says: "For a start, it takes more than two fibre cuts in the North Island to disrupt us" And also remember back early in the year when one slip on the Hutt motorway took out all services in Wellington. What is so wrong with Telstra's network that single events can affect so many people, when supposable it takes more than two fibre cuts to disrupt them? ------------------------------------------------------------------- Both fibers are hanging on the same poles? ;-) scott ps. to be ontopic... beer :) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

NZNOG 2007 conference registrations are now open
by Jonny Martin 19 Dec '06

19 Dec '06

(Apologies for duplicates...) Hi All. The New Zealand Network Operators Group (NZNOG) is holding it's annual conference from January 31st to February 2nd 2007 in Palmerston North, New Zealand. Registrations are now open at http://www.nznog.org/registernow.html We encourage you to register early. NZNOG conferences are always lively, educational, and offer a great chance to network with peers from both within NZ and See you there! Jonny.

3 2

International problems via Global-Gateway
by robbie.gernandt＠apn.co.nz 19 Dec '06

19 Dec '06

Hi there Anyone experiencing problems with International connectivity via Global-Gateway? We can't get to www.google.co.nz and a few other sites at the moment I'm still waiting for a response from Global-gateway... PS! International traffic via TelsraClear is fine regards Robbie ******************************************************************************** NOTICE This email and any attachments are confidential. They may contain privileged information or copyright material. If you are not an intended recipient, you should not read, copy, use or disclose the contents without authorisation and we request you contact us at once by return email. Please then delete the email and any attachments from your system. We do not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company. ********************************************************************************

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 18 Dec '06

18 Dec '06

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: AS9733 as-name: NZRR-AS9733 descr: Netspace Services Limited descr: WIX peering at '202.7.0.242' descr: see Citylink RT job #7787 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9733 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: operations(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061219 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9733 descr: Route set advertised to AS9439 by Netspace Services Limited - AS9733 members: 203.118.134.64/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: operations(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061219 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Dec '06

17 Dec '06

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: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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.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 20061010 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.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 20061218 source: NZRR --- 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, 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 20061019 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 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: mark.petrie(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Dec '06

13 Dec '06

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 - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.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)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061018 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia (former BCL) - 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.106.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 20061214 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Dec '06

13 Dec '06

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: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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.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 20061010 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, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.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 20061214 source: NZRR

1 0

Outside broadcast of broadband march on Parliament
by Andy Linton 13 Dec '06

13 Dec '06

Richard has asked me to post this - mail him if you think it's off topic! http://www.r2.co.nz/meta/videonow.asx

3 2

APNIC fee structure
by Elly Tawhai 13 Dec '06

13 Dec '06

Hi, The APNIC fee structure is currently under review. As the fee structure is determined by the membership, we would like to encourage the NZNOG community to share their thoughts on our mailing list: wg-apnic-fees(a)apnic.net We would like to acknowledge the valuable contribution Andy has already made to the APNIC fee discussion mailing list. We are aware that the topic has recently been raised on the NZNOG mailing list, and we urge any interested parties to also provide input to the APNIC discussion. Contributing to the APNIC fees mailing list will enable you to participate in the official fee structure policy review process. We look forward to hearing from the NZNOG community. Regards, Elly APNIC

3 3

Notification of NZRR Database changes
by NZRR Database Notifications 13 Dec '06

13 Dec '06

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:AS23754 descr: Route set advertised to AS9439 by Cafenet-Free - AS23754 members: 198.48.3.192/26^26-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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061122 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 97.64.46.0/24^24-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.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: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061214 source: NZRR

1 0

Vodafone Issues
by Ernest Cunningham 13 Dec '06

13 Dec '06

Hi all, If somebody from Vodafones mac savy tech department could contact me off list I need some help with an issue I am having with my MacBook Pro + HSDPA Express Card (connections are fine, it is a more technical issue I have to do with unexplained network activity). Ernest Cunningham

2 1

XTRA mail servers
by Tom 13 Dec '06

13 Dec '06

on 7/12/2006 2:10 PM Simon wrote: > We are having some major issues over the past week when forwarding > mail to xtra. Mainly: > > - delivery temporarily suspended: connect to mta.xtra.co.nz > - connect to mta.xtra.co.nz[210.54.141.1]: server dropped connection > without sending the initial SMTP greeting > > Has anyone seen any of these issues and knows anything about them? I've been seeing similar issues, such as 2006-12-07 14:13:36 1Gs4Fp-0000gi-Vv SMTP error from remote mail server after initial connection: host mta.xtra.co.nz [210.54.141.1]: 421 Service not available 2006-12-07 14:13:36 1Gs4Fq-0000hO-Ut mta.xtra.co.nz [210.54.141.1] Connection refused 2006-12-07 12:03:52 1Gs4YH-0002YT-Qz mx1.xtra.co.nz [210.54.141.1] Connection reset by peer 2006-12-07 12:34:26 1Gs4Ll-00049D-Hg Remote host mx1.xtra.co.nz [210.54.141.1] closed connection in response to initial connection same issues, mail isn't getting delivered until a force mail queue run is done, clients are moaning...as usual :( tom

6 5

APNIC member survey: Still open for participation
by Elly Tawhai 12 Dec '06

12 Dec '06

Apologies for duplicate postings -------- Original Message -------- Subject: [apnic-talk] [Apnic-announce] APNIC Member Survey Date: Fri, 1 Dec 2006 12:00:02 +1000 From: dg(a)apnic.net Reply-To: apnic-talk(a)apnic.net To: apnic-announce(a)apnic.net Dear APNIC members and friends, As you may know, since 1999 the APNIC Executive Council has commissioned a regular survey of the APNIC community. Three surveys have been held so far, providing crucial input on APNIC's performance, development and future direction. Today we are pleased to announce the fourth survey of APNIC members and stakeholders. As in the past, this survey will be conducted independently from the APNIC secretariat, by the international firm KPMG. In this manner the process is assured to be neutral and objective, ensuring the highest quality result. Once again Dr John Earls of KPMG has developed the survey format and questions, with input from a large group of selected validators from the APNIC community. Dr Earls will receive and process all survey responses, and will guarantee the anonymity of all respondents. His report will be presented at the APNIC Annual Members Meeting in March 2007. We hope that you will participate in this important exercise, whether or not you are an APNIC member, or have participated in a previous APNIC survey. To express our appreciation for your time and effort, APNIC will provide a special reward to 3 randomly picked respondents. This reward, an APNIC meeting fellowship package, will include complimentary meeting registration plus USD $500.00 towards expenses, and can be used at either of the APNIC Open Policy Meetings in 2007. To participate in the survey, please visit the APNIC website and follow the instructions at: http://www.apnic.net/survey/2007 With sincere thanks in advance for your assistance, Paul Wilson Director General Akinori Maemura Chair, Executive Council. ________________________________________________________________________ Paul Wilson email: pwilson(a)apnic.net Director General, APNIC sip: apnic(a)voip.apnic.net http://www.apnic.net phone: +61 7 3858 3100 ________________________________________________________________________

1 0

IPv4 Exhaustion
by Philip D'Ath 11 Dec '06

11 Dec '06

I attended a very interesting presentation today by Tony Bain, one of the key IETF IPv6 chairs. He says that the rate of /8's being allocated is increasing exponentially at that moment (22 were allocated in 18 months [till July 2005], leaving just 64 available worldwide), and the prior estimate of when IPv4 address was going to be exhausted of 2020 has been revised to 2009 - as in three years away, and that IPv4 address space is likely to take on a much more commercially tradable value as it becomes very rare (like oil). For existing players in the market this doesn't mean much. However for expanding networks this is going to put a serious crimp in their plans. I polled a lot of players in the NZ market about 6 months ago and plans for IPv6 deployment were almost non-existent. There is an older article he wrote here: http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_8-3/ipv4. html We really need large commercial transit players like Global Gateway, TelstraClear, AT&T, UUNet, AsiaNetCom, and Sprint to start offering dual stack IPv6 connections to downstream ISPs, and for ISPs to start allowing clients to connection via IPv6, including via DSL. We really need to get critical infrastructure, like DNS, fully IPv6 enabled. The .nz domain isn't even reachable via IPv6 addresses yet. Now I know the shared registry system has IPv6 support now, but it is limiting in that you must still supply IPv4 addresses. You can't supply only IPv6 glue records. What happens when you can't get IPv4 addresses to use for glue? Also the majority of the registries out their offer very poor IPv6 support - as in no IPv6 connected DNS servers, and an inability to easily add IPv6 AAAA records.

14 23

Moving DNS providers - best practice.
by Simon Lyall 10 Dec '06

10 Dec '06

After a few recent instances I am getting sick of companies who transfer their DNS/Servers from one provider to another and then wonder why the old data is still cached by 3rd parties for 24 hours (or whatever). How do people feel about a "best practice" document on this that we could encourage people to follow ( perhaps the DNC could publish) for people moving their domain between providers. Just the basics like, dropping the TTLs, getting all the servers data in the right order etc? Similar to this: http://www.onr.com/services/data_center/colocation/transfer_tips.html Thoguhts? -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

14 21

NO contact list
by Gerard Creamer 10 Dec '06

10 Dec '06

There now appear to be two versions of this list. http://www.tcn.bowenvale.co.nz/content/view/49/40/ and http://www.usenet.net.nz/noc/index.html We have recently been assigned a public AS and I thought we should probably go on the list - as we're growing our things breaking will have a wider impact and other NOs might want to get hold of us. I have no issue with being woken up in the middle of the night when our things break. I have a strong objection to being woken up when someone elses things break. Personally I like the (mostly) unlinked anonymity of the list at usenet.net.nz, as it's less likely to be some kid who has no idea what an AS is calling at 2am because the gaming server they're using in suddenly unreachable (probably due to some reason other than our network being broken). Sure, the kid might ultimately pay my wages, but they're sure as hell not my customer... I emailed Simon Lyall yesterday to ask to go on the list at usenet.net.nz - is this still going to be considered the NO list? I know there's no king and all that jazz, but some direction for a newbie AS NO would be appreciated... For the record, here's our guff: Name Netspace Services Limited Domains netspace.net.nz ASN(s) 9733 Phone Number(s) +64 4 917 8098, 0800 NETSPACE (0800 638 772) Clueful People Gerard Creamer Direct Email noc(a)netspace.net.nz Hours Office Thanks, Gerard

5 5

XTRA mail servers
by Simon 07 Dec '06

07 Dec '06

Hi There :) We are having some major issues over the past week when forwarding mail to xtra. Mainly: - delivery temporarily suspended: connect to mta.xtra.co.nz - connect to mta.xtra.co.nz[210.54.141.1]: server dropped connection without sending the initial SMTP greeting Has anyone seen any of these issues and knows anything about them? I just trying to contact XTRA's administrators, but no response. I have had a good response back from the corporate side of XTRA, which is assuring. Regards and Thanks, Simon

11 12

Re: [nznog] NZNOG 2007: CFP: Network Systems Administration MiniConf
by Ewen McNeill 07 Dec '06

07 Dec '06

In message <20061122214213.8BB2A43E17(a)wat.la.naos.co.nz>, Ewen McNeill writes: > Call for Presentations for > NZNOG 2007: Network Systems Administration Mini-Conference >[....] >Some possible topics: >- Email servers and spam filtering techniques >[....] >Please send all proposals and questions to <talks(a)nznog.miniconf.org> At the risk of distracting everyone from arguing about responsible use of the list, I'd just like to point out that we still have room for a couple more talks at the Sysadmin Miniconf (on the first day of NZNOG 2007). And that we'd particularly welcome a proposal on, eg, best practices in running a mail server, or coping with the ever increasing volume of spam without rejecting all the legitimate mail. Proposals of other relevant talks (see the original CFP) are also welcomed, but be quick as we'd like to finalise the programme before Christmas so the speakers know what their summer homework is. Ewen

1 0

Re: [nznog] Xtra Email Administrators
by Martin Kealey 07 Dec '06

07 Dec '06

<metoo/> Given that (apparently) along with many other ISPs, Ihug also seem to have trouble with Xtra's inbound mailservers, perhaps I should say "could someone from Xtra please contact me ON list". (Yes we're all on fire trying to deal with Image Spam, but refusing valid mail just makes it worse...) -Martin -- Martin D Kealey, ihüg Systems Engineer

7 7

Xtra Email Administrators
by Simon 06 Dec '06

06 Dec '06

Would someone from the xtra email team please be able to contact me offlist? Much appreciated. Simon

20 35

INFO: Contact for xtra email admins
by Lin Nah 06 Dec '06

06 Dec '06

IN case this is lost amongst the flurry of flames, here's who to contact. It does appear lost as someone did ask again about 20 mins after Ted posted this (mind you I have only date stamps to go by). Lots of you are still flaming about it. May I also point out that Ted has in the past responded to this list stating he's happy to be contacted about this. eg http://list.waikato.ac.nz/pipermail/nznog/2005-August/010430.html http://list.waikato.ac.nz/pipermail/nznog/2005-January/009460.html regards lin ---------- Forwarded message ---------- Date: Thu, 7 Dec 2006 13:52:23 +1300 From: Ted Grenfell <Ted.Grenfell(a)telecom.co.nz> To: Simon <greminn(a)gmail.com>, nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Xtra Email Administrators So as always, you're all welcome to call me direct if you've an Xtra query that you don't want to send via postmaster etc. -- Kind Regards, Ted Grenfell Online Services Mgr (acting) T +64 9 359 5854 (extn 93254) F +64 9 377 0781 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford Street, Private Bag 92028, Auckland CBD, New Zealand ________________________________ "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." > -----Original Message----- > From: Simon [mailto:greminn(a)gmail.com] > Sent: Thursday, 7 December 2006 12:42 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Xtra Email Administrators > > Would someone from the xtra email team please be able to contact me > offlist? > > Much appreciated. > > Simon > > _______________________________________________ > 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

1 0

Re: [nznog] XTRA mail servers
by James Tolchard 06 Dec '06

06 Dec '06

On 07/12/2006, at 2:10 PM, Simon wrote: > We are having some major issues over the past week when forwarding > mail to xtra. Mainly: > > - delivery temporarily suspended: connect to mta.xtra.co.nz > - connect to mta.xtra.co.nz[210.54.141.1]: server dropped connection > without sending the initial SMTP greeting > > Has anyone seen any of these issues and knows anything about them? We are also seeing issues since late November. I emailed postmaster(a)xtra from elsewhere on 1 December, with no response so far. Typical log: Dec 7 14:19:26 skinner postfix/smtp[19226]: connect to mta.xtra.co.nz [210.54.141.1]: server dropped connection without sending the initial greeting (port 25) Typical telnet: $ telnet mta.xtra.co.nz 25 Trying 210.54.141.1... Connected to mta.xtra.co.nz. Escape character is '^]'. Connection closed by foreign host. $ The above is the most common behaviour, but apparently the connection does stay open properly from time to time (I had to send a bunch in a row to get this): Dec 7 14:28:34 skinner postfix/smtp[19322]: 187FFA9EF2B: to=<jkhhlkhkjh(a)xtra.co.nz>, relay=mta.xtra.co.nz[210.54.141.1], delay=27, status=bounced (host mta.xtra.co.nz[210.54.141.1] said: 550 Invalid recipient: <jkhhlkhkjh(a)xtra.co.nz> (in reply to RCPT TO command)) We also sometimes get "421 Service not available" before it drops the connection, and sometimes we even get connection refused. But when we're really lucky: 220 mta01.xtra.co.nz ESMTP server ready Thu, 7 Dec 2006 14:41:34 +1300 220 mta06.xtra.co.nz ESMTP server ready Thu, 7 Dec 2006 14:43:01 +1300 So, yeah, it looks like something might be up. Cheers -- James Tolchard System Administrator Christ's College Canterbury Phone: +64 3 364 6806

1 0

Null route on AT9812T router
by James Neil Tyson 06 Dec '06

06 Dec '06

If anyone knows how to add a null static route on an Allied Telesyn AT9812T router please email me offlist. I hate these damn things.

1 0

Re: [nznog] CHIX
by Stewart Fleming 05 Dec '06

05 Dec '06

DPE is also up and running in Dunedin and has first connections from January 2007. We requested a name change to DIX so that we could hook up CHIX with DIX, but the request was again denied.

2 1

Re: [nznog] Charging for IPv6
by Alex Hague 05 Dec '06

05 Dec '06

David Zanetti wrote: > I just don't see anything today I would bother demanding native v6 > transit for. So long as that't the case, I can live with tunnels for the > lab/play phase of things. How about an IPv6 wireless mesh as a reason to adopt... this is purely hypothetical, but say in the Auckland (/ Wellington / where ever) CBD there was an IPv6 wireless mesh, peered locally on the IPv6 peering exchange. New sources of local content may begin to appear such as bands providing live streams via the mesh of their gigs at the local bars / pubs / clubs etc. Current non-internet content providers such as radio stations might decide to provide their own streams. ISPs wishing to be WISPs would need to adopt v6. The benefits from what I know of IPv6 (which I'm still doing my homework on - so turn the flame jets down a notch) would be that all addresses on the mesh could be internet routable, and because of the local nature of the mesh most content would probably have local relevance rather than anything further a field, so with good local peering (which is relatively inexpensive) it would be completely feasible to deliver high speed local content. While I know that this is hypothetical, do you think it might provide an incentive for people to start using IPv6 to access the content? Furthermore, people might actually have a reason to request v6 from ISPs and ISPs wishing to provide services to mesh users would have a reason to go v6 ($$$)... Cheers, Alex -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.15.6/568 - Release Date: 4/12/2006

3 2

Any mail admins from sbc.sbcglobal.net on here?
by Paul Adshead 05 Dec '06

05 Dec '06

Please contact me off list.

1 0

CHIX
by Russell Tester 05 Dec '06

05 Dec '06

Does anyone know if CHIX is alive, was it ever alive or are there any plans to revive it in the future? Regards, Russell Tester Severworks Ltd

4 3

Re: [nznog] CHIX - who'd sign up tomorrow?
by Erin Salmon 04 Dec '06

04 Dec '06

Hi, Last I heard (about 2 years ago) it was to be hosted between Snap Internet and University of Canterbury. We have been eager to peer since before a chix was ruminated, and remain so. Unleash would be happy to put forth a small amount of rackspace for the purpose if others want to get some informal peering going. We also have tall buildings at our disposal for those out there who are wirelessly inclined. My motivation is to eliminate costly backhaul to other main centres and create a marketplace, if you will, for bandwidth down here. Christchurch could use some life breathed into its Internet. Expressions of interest? Erin -----Original Message----- From: "Nathan Ward" <nznog(a)daork.net> To: nznog(a)list.waikato.ac.nz Sent: 6/12/06 12:24 a.m. Subject: Re: [nznog] CHIX http://nzix.net/ The following exchanges are under construction: * Christchurch Internet Exchange * Southland Internet Exchange The "Who uses .." list shows nothing. Also, your sig is misspelt. On 6/12/2006, at 12:19 AM, Russell Tester wrote: > Does anyone know if CHIX is alive, was it ever alive or are there any > plans to revive it in the future? > > Regards, > > Russell Tester > Severworks Ltd > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > !DSPAM:22,457555d3143831749460768! > > > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

FW:Electricity Reforms Act and Diesel Generators
by Jeremy Simons 02 Dec '06

02 Dec '06

Statement from TeamTalk Kordia supplies services to TeamTalk and we have a longstanding relationship with Kordia. They are one of our preferred suppliers and we are happy with our commercial arrangements. TeamTalk did not authorise the release of any Kordia material. The statement in question was sent to a junior member of TeamTalk's staff who contrary to company policy copied it to Jonathan Brewer of Araneo. We are treating the matter very seriously and are taking steps to ensure that such a breach of policy does not occur again. It is important to note that the item quoted was one paragraph from a complex 25-page document and was taken out of context. We value our relationship with Kordia and regret that this incident has occurred Jeremy Simons General Manager - Operations TeamTalk Limited ____________________________________________ Jeremy Simons General Manager - Operations TeamTalk Limited How Work Gets Done Phone: ++64 4 802 1478 Mobile: ++64 21 715 390 Fax: ++64 4 802 1490 <mailto:jsimons(a)teamtalk.co.nz> Mail to: jsimons(a)teamtalk.co.nz Disclaimer: The information in this electronic mail message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Internet electronic mail message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. TeamTalk Limited accepts no responsibility for any effects this email message or attachments has on the recipient network or computer system.

7 7

Re: [nznog] FW: Electricity Reforms Act and Diesel Generators
by Dean Pemberton 30 Nov '06

30 Nov '06

> List moderator, is it possible to remove this list from the archives? I think we've been through this before, and the answer is no. There is all sorts of things in the archives that people would like to have removed. The answer has always been no. Infact way back in time there was a HUGE argument about it. Where people offered to just make alternative, REAL versions of the archives with the removed posts. It got really nasty. Dean (In his ad-hoc role as NZNOG historian)

5 4

FW: Electricity Reforms Act and Diesel Generators
by Jonathan Brewer 29 Nov '06

29 Nov '06

Hi Folks, I'm afraid my question may have breached a confidentiality agreement and we are getting angry phone calls from our supplier, so please disregard my email earlier today and delete any references to it from your inbox if that is possible. List moderator, is it possible to remove this list from the archives? Thanks, Jonathan Brewer > ______________________________________________ > From: Jonathan Brewer [mailto:jon.brewer(a)araneo.net.nz] > Sent: Thursday, 30 November 2006 9:42 a.m. > To: 'nznog(a)list.waikato.ac.nz' > Subject: Electricity Reforms Act and Diesel Generators > > Hi Folks, > > We telehouse at a number of facilities throughout New Zealand. We > typically provide our own batteries and contract for use of an on-site > diesel generator. At most sites we are not able to put in our own > generator. > > We were recently informed by Kordia (BCL) that they can no longer allow us > to use standby generator power at their sites due to the Electricity > Reforms Act. > > "BCL is deemed to be a Line Company under the Electricity Reforms Act and > therefore is unable to also be classified as a Generator. On that basis, > BCL is no longer able to provide you with Standby Generator Power for > upgrades to existing or new services." > > This effectively bars us from providing carrier grade telecommunications > services from BCL sites. > > One might say "use different sites" or "build your own towers", but these > are not options as these towers were built by the government before the > times of the Resource Management Act in unique locations where new towers > cannot be built. > > Can they do this? Are they doing this to everyone, or just us? > > Thanks, > > Jonathan Brewer

3 2

Re: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion)
by Scott Weeks 29 Nov '06

29 Nov '06

: The past 10+ years of work on IPv6 nee IPng have taught : many lessons about what will and will not work (and more : importantly what will be accepted or not). Exactly. I NEED to multihome. I won't accept not being able to do that. No provider is going to be good enough that I trust ALL of my connectivity with them and no one else. That settles it right there. A protocol should not dictate my business practice. : ps - the 100-million number likely came from Alain Durand's : presentation "Managing 100+ Million IP Addresses" WRT "Managing 100+ Million IP Addresses", I see the following chart. (apologies for the formatting. It's on page 6 at www.nanog.org/mtg-0606/pdf/alain-durand.pdf >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Triple Play Effect on the Use of IP Addresses 2005 2006+ HSD only Triple Play Cable Modem 1(private only) 1 Home Computer/Router 1 1 eMTA (Voice adaptor) 0 1 – 2 Set Top Box (STB) 0 2 Total number of IP addresses(assume 2.5 1 – 2 8 – 9 STB per household) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> What STB needs 2 IPs per box? The way we're doing it is one private IP per STB and one STB per television set, so that's 2-3 private IPs per household. One public IP per customer for Internet and we're not going for VoIP until later. Perhaps they have one STB per household no matter the number of television sets? Also, I see they have 20-30 ASNs. Are all 20M customers going to be in one AS? I wouldn't expect that. Finally, with VPRNs addresses could be reused. Just put the customers in different VPRNs and duplicate the address scheme. It's 'divide and conquer' methodology. I'm a noobie to VPRNs, so flame me if this isn't feasible. I have doused my flameproof underpants with beer, so I'm protected... :-) scott --- jejs+lists(a)sahala.org wrote: From: "joshua sahala" <jejs+lists(a)sahala.org> To: nznog(a)list.waikato.ac.nz Subject: [nznog] THE SKY IS FALLING ( was Re: IPv4 Exhaustion) Date: Wed, 29 Nov 2006 10:42:35 +1300 (NZDT) I find it slightly ironic that those screaming the loudest for IPv6 seem to have the most poorly researched assertions regarding the death of IPv4. (I am of course ignoring the obvious stupidity of things like IPv8/9/16) Who are the loudest proponents of IPv6? I tend to agree with the evaluation presented in Todd Underwood's blog: vendors, consultants, and the protocol designers themselves... (http://www.renesys.com/blog/2006/03/bashing_ipv6_at_telecomnext.shtml) If IPv6 is the answer, what was the question again? Perhaps it is time to accept that IPv6 is the wrong answer (or we need to start asking better questions), take the lessons learned from its failure, and start again. The past 10+ years of work on IPv6 nee IPng have taught many lessons about what will and will not work (and more importantly what will be accepted or not). There are many fundamental problems with the protocol that no amount of marketecture or hand-waving will fix; the least of which is a lack of end-users calling for a v6 address for their toaster/television/mechanical tie rack. These issue must be addressed, either in IPv6 (not likely), or in IPng-NG :) </soapbox> /joshua ps - the 100-million number likely came from Alain Durand's presentation "Managing 100+ Million IP Addresses" (it says ~20-million customers + kit == 100-million) -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. - Douglas Adams - _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 15

Electricity Reforms Act and Diesel Generators
by Jonathan Brewer 29 Nov '06

29 Nov '06

Hi Folks, We telehouse at a number of facilities throughout New Zealand. We typically provide our own batteries and contract for use of an on-site diesel generator. At most sites we are not able to put in our own generator. We were recently informed by Kordia (BCL) that they can no longer allow us to use standby generator power at their sites due to the Electricity Reforms Act. "BCL is deemed to be a Line Company under the Electricity Reforms Act and therefore is unable to also be classified as a Generator. On that basis, BCL is no longer able to provide you with Standby Generator Power for upgrades to existing or new services." This effectively bars us from providing carrier grade telecommunications services from BCL sites. One might say "use different sites" or "build your own towers", but these are not options as these towers were built by the government before the times of the Resource Management Act in unique locations where new towers cannot be built. Can they do this? Are they doing this to everyone, or just us? Thanks, Jonathan Brewer

3 2