- NZNOG - lists.nznog.org

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