- NZNOG - lists.nznog.org

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 31 Dec '06

31 Dec '06

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