- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 changed: rpsl-admin(a)nzix.net 20040810 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

paypal phishing site
by Ian Batterbee 11 Nov '05

11 Nov '05

Have seen a few spams that has all the paypal images (even gets the images from the real paypal site) and lists a bunch of dummy IP addresses that my paypal (I don't have one) account was apparently used from recently, and encourages me to click on the given URL, which goes to [http://www.paypal.update-user-form.com/] Any request to *.update-user-form.com gets redirected to [http://www.paypal.update-user-form.com/webscr.php?cmd=LogIn] and the domain resolves to the following six IP addresses: 68.142.234.[52..57], which all seem to belong to Yahoo. God knows how people get away with registering DNS entries for sites that couldn't be used for anything other than phishing attempts.. I guess someone thought update-user-form.com looked innocent enough.

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 09 Nov '05

09 Nov '05

At 10:31 10/11/2005, Mark Foster wrote: > > "Your server is not an open relay, but you have a user that is > > infected with a mass-mailer trojan/malware" > > > > (and finally a copy of some message headers that prove it) > > >Was this the honest-to-god reason? Yes, that was a verbatim quote from the message. >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? I thought so too, but obviously some don't. >Given the sheer volume of smtp-crud that a lot of people see, it wouldnt >suprise me that large blocks get put in sooner rather than later. > >In some respects though, SORBS's policy is actually reasonably well >thought out. Entries get a TTL of 2 days and if now further 'hits' on the >IP are received, the TTL auto-expires and the block comes off. TTL gets >renewed each time a further report is received. The spamcop list auto-removes you after sometime between 12 and 24 hours too, but the problem as I see it is that they rely on unverified user entered "reports" so potentially you could keep getting unfairly listed over and over without any real comeback... Regards, Simon

2 1

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 09 Nov '05

09 Nov '05

At 16:45 10/11/2005, Andrew Stephen wrote: >On 11/10/05, Lesley Walker <lrw(a)clear.net.nz> wrote: > > Simon Byrnand wrote: > > > Not only that, but the sample message header they provided > > > had many of the message fields obfuscated, including the > > > message id tag and the time, making it extremely > > > > The reason they obfuscate some of the fields is that in some > > cases the report could be going to the spammers themselves, > > and the concern is that spammer will be able to identify the > > user who reported them and exact some kind of revenge. > >Ah, yeah. That happens. I received several death threats after >reporting some spam a year or so ago. Nothing happened (and I didn't >really expect it to) but it does make one wary. In my case however it wasn't a person(s) reporting the message, it was one of their honeypot addresses that the spam was sent to, and they claimed in a later email that the obfuscation was to protect the honeypot address. Fair enough, except it didnt seem to dawn on the guy that if I couldn't work it out from my mailserver logs thanks to their obfuscation then I couldn't find the customer with the trojan to do anything about it, and on the other hand that if I could figure it out by deduction (which I did) that the honey pot address would be in my log files anyway and thus compromised if I were a spammer :) Security by obscurity ? :) Regards, Simon

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Lesley Walker 09 Nov '05

09 Nov '05

Simon Byrnand wrote: > Not only that, but the sample message header they provided > had many of the message fields obfuscated, including the > message id tag and the time, making it extremely The reason they obfuscate some of the fields is that in some cases the report could be going to the spammers themselves, and the concern is that spammer will be able to identify the user who reported them and exact some kind of revenge. IIRC, the munging is set on a per-user basis by the users reporting spam. Some Spamcop users will argue that the spammer could be using a database to key the message id and timestamp to the recipient address. (I tend to think this is excessively paranoid, but some vigilante anti-spammers probably have good reason to exhibit this level of paranoia.) The other thing to bear in mind is that they have no way of knowing which ISPs are "spam-friendly" (ie very happy to recieve payment for the bandwidth used by spammers), which many Spamcop users regard as being just as evil as the spammers themselves and completely worthy of blocking. > I strongly suggest that people DONT do SMTP level blocks > using spamcop lists, as they are simply not trustworthy > enough, I only use spamcop as a points scoring mechanism > in spamassassin, I've never trusted it for outright > blocking... Indeed, Spamcop's own advice to users of the list includes the comments: "SpamCop encourages SCBL users to tag and divert email, rather than block it outright" and "The SCBL is aggressive and often errs on the side of blocking mail." (Quoting http://www.spamcop.net/bl.shtml) If anyone wants to get into a discussion with Spamcop about the issues, you could try their news server at news.spamcop.net. If you have time to spare, that is. Lesley W

2 1

Apology - Rod Donald Funeral
by Richard Naylor 09 Nov '05

09 Nov '05

A BIG sorry to Operators who may have been affected by higher than usual traffic this morning. As you know we like to issue pre-event warnings of potential traffic or support issues. Today we supported the streaming of the Rod Donald Funeral Webcast, picking up the load mid-event and using anycast routing to distribute the load. So we didn't get much warning either. The decision was made on the phone as we worked setting things up. While not a huge event, it did produce a higher than normal load. There was a steady 45Mbps coming out of our USA server, peaking to 85Mbps. ISPs *really, really* should peer to avoid this cost and also help us service the international viewers. It reflects badly on them internationally. There are at least 4 more significant events before the end of the year, so Operators are strongly urged to peer. Once again - sorry if your traffic graph got a nasty kink in it today. Rich

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Ewen McNeill 09 Nov '05

09 Nov '05

In message <40972.203.97.112.6.1131571888.squirrel(a)webmail.blakjak.net>, "Mark Foster" writes: >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? There's at least one common variant around now which seems to relay via the ISP mail servers. I notice it mainly through the reflections, including some where that ISP's mail server apparently tried to deliver to some nonexistant user at my domain, got rejected, and so instead delivers a bounce message to the (forged) from address at the same domain (which happens to exist; if that one didn't exist either I'd never see it). I'm not sure how much longer relaying mail without scanning it first (and rejecting anything that doesn't pass at SMTP time) is going to be a viaable strategy for both incoming and outgoing mail relays. Either that or dynamic IP addresses going away, so it's possible to assign reputation right back to the originating machine. Ewen

1 0

Paradise.Net SMTP server blocked.
by Steve Biddle 09 Nov '05

09 Nov '05

After experiencing email problems I've noticed Paradise's SMTP server is currently being blocked by SpamCop. http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 Anybody got any comments? These email problems have been ongoing over the last few weeks so I suspect the server (smtp1.paradise.net.nz) has been on the list for some time.

6 5

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 09 Nov '05

09 Nov '05

> Warning, rant ahead. :) I see your rant, and raise you a rant and a beer (just to keep it ontopic) At my previous job, we moved from a single IP connection to a block of 8. Problem was, one of the addresses in the "new" block of 8 was black listed - and guess which one we put the mail server on <sigh> Got it cleaned up, but no outgoing (without a work around) for 48 hours. That said, on the RBL list on my server, I removed SpamCop. Why? Too many false positives, and WAY too many false negatives (letting spam in). It's close to useless.... (and there are other, GOOD ones, out there) Cheers Nic

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 09 Nov '05

09 Nov '05

Paradise gets blocked about once a month (or more, some times). I've had to put a rule in, allowing *(a)paradise.net.nz :) (there again, my server is not huge - 2 users - so not really an issue for me :) ) I assume their admins are aware, as they appear to normally be on the ball..... I'm guessing they are now, anyway! Cheers Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited > -----Original Message----- > From: Steve Biddle [mailto:sjbiddle(a)paradise.net.nz] > Sent: Wednesday, 9 November 2005 6:07 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Paradise.Net SMTP server blocked. > > > > > After experiencing email problems I've noticed Paradise's > SMTP server is currently being blocked by SpamCop. > > http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 > > Anybody got any comments? These email problems have been > ongoing over the last few weeks so I suspect the server > (smtp1.paradise.net.nz) has been on the list for some time. > > > > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Nov '05

08 Nov '05

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: AS24183 as-name: NZRR-AS24183 descr: DTS1 descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3580 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24183 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051109 source: NZRR

1 0

Update: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 07 Nov '05

07 Nov '05

An update and 2nd Call for papers. The Systems Administration Miniconf will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 . We have had a good response to our first call for papers and have accepted several great presentations. In addition we have several others submitted after the early deadline or which didn't quite make the first cut. Please see http://sysadmin.miniconf.org/program.html for our draft programme or http://sysadmin.miniconf.org/presentations.html for more details on the accepted presentations. A reminder that we are still accepting proposals for presentations until at least the 18th of November. Presentations can be lightning talks or full presentations between 30 and 120 minutes. See: http://sysadmin.miniconf.org/cfp.html for details. Topics for presentations could include (but are not limited to) Samba, Databases, Backups, Firewalls, AAA, Troubleshooting, Buying Decisions, VPN, Virtual machines (Xen, UML, VMware), Monitoring Software, Web/Mail/LDAP/etc Server software, Wikis, PHP, Spam and Virus Filtering, VOIP, Trouble Ticket System, Best Practices, New Developments, Clustering/High Availability , Automated Installs, Automated configuration, Packaging Local Software. Speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ----------------------- Presentations of between 30 and 120 minutes (including questions) or Lightning Talks of 5-10 minutes. Submitting talks ---------------- Please note that in order to give a presentation you must be signed up for the main linux.conf.au conference. In order to submit a talk please see our Call for Presentations web page at: http://sysadmin.miniconf.org/cfp.html Submissions (or any questions) should be sent to: contact @ sysadmin.miniconf.org. Dates and Deadlines ------------------- 18 Nov 2005 - Deadline for Submissions Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Spammers Again (pricecutter.co.nz/brands4less.co.nz)
by Craig Whitmore 07 Nov '05

07 Nov '05

People have been talking about this company lately... pricecutter.co.nz/brands4less.co.nz strike again and sends out their new batch of blatent spams today Recieved a load of spam this afternoon to email addresses which have not been used for over 7 years old. (The info on their website says they've only been running since 2005) pricecutter/brands4less registered to John Kyle (Cannot find any company owned by him) Calypso Records (cannot find any company called that) Address: 68 Lincoln Road, Henderson (This is The Lincoln Road Bible Chapel ) (I live 2 mins away and I checked !) Phone Number: 09 828 7890 (invalid number) (invalid exchange) Email: zxd(a)xtra.co.nz (when you email it you get back saying "Your email gas been removed. This is an automated message please do not reply." (same with Looks like same people as fitnessgear.co.nz with very similar style ads and invalid domain contacts and same hosting/ip address!! Be aware of this company.. (Search for brands4less.co.nz on google) I've also emailed their kliksend.com about this spam (or are they the same people and ignore me) Also.. can Domainz contact this customer of theirs and get some valid details for their domain as they are breaking Domainz's T&C and also I believe the DNC's for having false details. Thanks Craig Talking for Myself

1 0

Short notice of webcast
by Richard Naylor 05 Nov '05

05 Nov '05

Evening All, The following webcasts will take place this week at rather short notice (friday night). I doubt there will be huge traffic, but better warned...... On Monday and Tuesday, we will be streaming the 2 Opening ceremonies of Parliament, live from the grounds. (There will be cameras inside as well, just we'll be outside) The links for the streams are on http://www.r2.co.nz/20051107 Rich

1 0

Re: [nznog] DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

That'll teach me for being naive. I take it you meant that they are unrelated. R. >>> Joe Abley <jabley(a)isc.org> 11/05/05 4:10 PM >>> > Apologies if I appear pedagogical :-) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

A naive question: With the limiting of recursion (which appears to be a Good Thing) does it make it more (or less) important to have good network diversity (hint:peering) ? Or does it not matter? Richard >>> "Simon Allard" <simon.allard(a)staff.ihug.co.nz> 11/04/05 8:00 PM >>> Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > 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

4 4

Google Oddness
by Mark Foster 04 Nov '05

04 Nov '05

; <<>> DiG 9.2.1 <<>> www.google.com A ;; global options: printcmd ;; connection timed out; no servers could be reached ns1.google.com through ns4.google.com are as follows: ns1.google.com. IN A 216.239.32.10 ns2.google.com. IN A 216.239.34.10 ns3.google.com. IN A 216.239.36.10 ns4.google.com. IN A 216.239.38.10 I can't get to any of those. Wonder if 216.239/16 has dissapeared off the net? traceroute to 216.239.32.10 (216.239.32.10), 30 hops max, 38 byte packets 1 akl-colo1.helix.net.nz (202.50.176.78) 42.880 ms 0.222 ms 0.171 ms 2 202-49-59-254.level48.net (202.49.59.254) 0.450 ms 0.354 ms 0.324 ms 3 qsi2.ape.net.nz (192.203.154.29) 2.005 ms 0.662 ms 0.853 ms 4 gateway3-acc-skyt.qsi.net.nz (202.89.128.91) 26.475 ms * 4.674 ms 5 Mercury-Quicksilver-FE-1-0-0-402-ar1.akl1.gblx.net (203.192.179.9) 4.059 ms 3.245 ms 3.954 ms 6 po0-0.gw2.sjc1.asianetcom.net (202.147.50.130) 156.300 ms 155.490 ms 158.930 ms 7 72.14.197.37 (72.14.197.37) 156.797 ms 159.034 ms 158.760 ms 8 * * * Problem exists from both QSI and GGI... Mark.

4 3

Inspire Net name servers
by Mark Seward 03 Nov '05

03 Nov '05

ns1.inspire.net.nz (203.114.128.1), and ns2.inspire.net.nz (203.114.128.2) now accept recursive and cached queries from Inspire Net customers only. Queries for domains that ns1 and ns2 are authoritative for are unaffected. Mark Seward Inspire Net Ltd.

7 9

Re: [nznog] Inspire Net name servers
by Simon Allard 03 Nov '05

03 Nov '05

Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

> Google Groups has fallen over now. And it's back. LW.

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

Google Groups has fallen over now. ----- Original Message Follows ----- > On 03/11/05, Mark Foster <blakjak(a)blakjak.net> wrote: > > > > I can't get to any of those. Wonder if 216.239/16 has > > dissapeared off the net? > > > Seems to be a widespread problem at google - gmail was > down as well but coming up now.... > -- > Ian McDonald > http://wand.net.nz/~iam4 > WAND Network Research Group > University of Waikato > New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Update to Telecom Xtra DNS servers
by Ted Grenfell 02 Nov '05

02 Nov '05

As part of our ongoing DNS service improvements, Telecom is making some changes to it's DNS servers which will affect some non-Telecom customers. The following Xtra name servers will in future only accept queries from Non-Telecom customers for domains that the name servers are authoritative for. Recursive queries for other domains (e.g. www.google.com) will no longer work. * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz We will be phasing in these changes from November 15th over a period of several weeks and you may wish to alert your help desks to check the DNS settings of users having problems after that. Currently Xtra operates the following recursive DNS services: * dnsc1.xtra.co.nz ( 202.27.158.40 ) * dnsc2.xtra.co.nz ( 202.27.156.72 ) We are happy for external people to query those IP's for DNS troubleshooting and similar purposes but they should not be directly configured into machines. Please note these IP's may change from time to time and external access may be limited or withdrawn without prior warning (especially in cases of abuse). Regards, -- Ted Grenfell, ISP Performance Manager, IS Online Services, Telecom NZ Ltd Mob: +64 274 435 455; DDI: +64 9359 5854; Fax: +64 9377 0781; Pager: +64 2611 1445 ICQ: 191891; MSN Messenger: cameleon @ xtra.co.nz Level 11, 8 Hereford St, Private Bag 92028, Auckland CBD, New Zealand "today was so quiet, you could hear a packet drop" - Tom Liston, ISC Handler's Diary 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.

9 11

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

There are stats but we do not have a view on the exact numbers of people who have configured alien and terminator as their DNS. There will be some and they will be impacted in some way from recursion being disabled. Hence the heads up. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, 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: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 1:46 p.m. To: Joe Abley Cc: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Joe Abley" <jabley(a)isc.org> > Unless Xtra's planned configuration is particularly unusual, >I would imagine they would return answers from the cache >where they exist, return authoritative answers in the case of >queries that they have authoritative data for, and otherwise >return a referral to the root. "no answers" is the usual "not here" reply (like ns1.ihug.co.nz) And therein lies the problem. For a non Xtra user, that has Xtra DNS servers hard coded, 90% of DNS requests will probably work because Xtra's servers have much of the nz internet namespace in their cache, (or the servers are authorititive) The IP address 202.27.184.3 is a virus, it seems have spread into the configurations of many NZ computers, I think it is one of those "it just works" scenarios and computer technicians have used it as a default fix for many "wierd" DNS issues. Once Xtra disable recursion for non Xtra customers, those same techncians will be challenged with trying to diagnose a very intermittent "page can not be displayed" fault. Ted, if we assume this change is being made because there are a significant number of requests (relative to the size of your user base) coming from non Xtra IP addresses, then we would have to assume that a significant number of users (that have dumb client resolvers) are going to be affected. Are there any statistics available from your name servers on the scale of this issue (Like is it 10% non Xtra requests?) Cheers BG

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

All IP's mentioned in my previous email are still accepting queries. Nothing has yet been implemented as we wanted to ensure advance notice was given so I'm not sure why you were getting 440's sorry. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, 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: Regan Murphy [mailto:regan.murphy(a)oasystems.co.nz] Sent: Wednesday, 2 November 2005 10:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Update to Telecom Xtra DNS servers >>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] Update to Telecom Xtra DNS servers
by Regan Murphy 01 Nov '05

01 Nov '05

>>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

Most likely your option 3 Brian. There can be expected that there will be some customers who'se interweb thingy appears to die on them. Hence our advance notice. -----Original Message----- From: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 9:19 a.m. To: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Ted Grenfell" <Ted.Grenfell(a)telecom.co.nz> > The following Xtra name servers will in future only accept queries >from Non-Telecom customers for domains that the name servers are > authoritative for. > * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz > * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz What action will those servers take when they receive a request from a non Xtra IP? Will they : 1. Quietly discard the request (as in, blocked by a front end firewall) 2. Return a referal to another DNS server e.g. .co.nz etc. 3. Return "invalid domain name" Cheers BG Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, 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."

1 0

Re: [nznog] Melbourne Cup Streaming
by Webmaster 31 Oct '05

31 Oct '05

We are carrying audio on National Radio at 5pm: www.radionz.co.nz regards, Richard Hulse >>> "Regan Murphy" <regan.murphy(a)oasystems.co.nz> 1/11/2005 15:06 >>> Are there any localised streams for the Melbourne Cup race? -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Melbourne Cup Streaming
by Regan Murphy 31 Oct '05

31 Oct '05

Are there any localised streams for the Melbourne Cup race? -- Regan

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Oct '05

31 Oct '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information. The call for presentations officially closes today, so please contact me off list if you'd like to present and haven't already indicated your interest. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins 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.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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: 202.154.128.0/19 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.154.128.0/19 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.16.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.16.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.48.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.48.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

MX2 with SPF
by Joel van Velden 29 Oct '05

29 Oct '05

Hi all I've been having a problem lately of getting far too much spoofed email being sent with my email address directly to our secondary mx which tries delivering it to our primary which 550's it (unknown user) and thus I get the bounce. To solve this I thought about doing the SPF thing for our domains, but this wouldn't solve the above problem unless the secondary mx does SPF as well. Because of various reasons we are using an ISPs seconday mx server for our domains, and thus have no control of that servers configuation. What i'm really asking is, does anybody know of someone selling a secondary mx service with SPF enabled? Cheers Joel van Velden

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-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.27.204.0/24^24-29, 202.36.70.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, 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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

NZNOG 2006 - October Update.
by Simon Lyall 26 Oct '05

26 Oct '05

1. Dates. The conference is now less than 5 months away, from 22 March to 24 March, just before the Wellington ICANN meeting Call for Papers close next week, if you wish to have your talk given full consideration then please send us something before then. Squeezing in after that date will be much harder. http://www.nznog.org/cfp.html Even if you only send us a brief description then your presentation will still be considered. 2. Sponsorship. We wish to apologise to those people who have emailed us and not heard back. Due to various factors we have not got back to you yet, this is being worked on and should hopefully be sorted out soon. :( 3. General. We are in the process of finalizing venues for the main conference, dinners and the like. Most of it is looking fairly promising if not always as cheap as we would hope. We have had several good talk proposals, however there is still some room in the programme especially for lightning talks. Wednesday is looking more and more like becoming a full or half day of normal conference. Finally if you have any general, off the wall or other ideas please email us now as things will start being settled soon. We have had a couple of good suggestions already. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Re: [nznog] Voip response
by chris＠archnetnz.com 26 Oct '05

26 Oct '05

Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Both of you misread what I said - I said Sipserve. Barry said Sipserve used the same PRI's as slingshot/italk/callplus, which, I apologize if I'm wrong, but I'm pretty sure that that is not the case. And as I said, they said 2 or 3 months, so give them that at least :) Will -----Original Message----- From: chris(a)archnetnz.com [mailto:chris(a)archnetnz.com] Sent: Thursday, 27 October 2005 5:00 p.m. To: Will Steele Subject: Re: [nznog] Voip response Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Sipserve doesn't use the same PRI's, they have their own, provided by callplus (afaik). The standard italk prefix of 974 is assigned to callplus in all area codes except 06, where it is taken by TelstraClear. iTalk told everyone in September that it would be ready in 2 or 3 months, yet people are still sending typical "where the hell is it" emails/forum posts, and also have the nerve to go "oh btw, we want to pay less." People are assholes. ________________________________________ From: Barry Murphy Sent: Thursday, 27 October 2005 4:20 p.m. To: will(a)excom.net.nz Subject: [nznog] Voip response Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Voip response
by barry＠unix.co.nz 26 Oct '05

26 Oct '05

Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '05

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:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.36.205.128/27^27-29, 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.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: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '05

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: AS24181 as-name: NZRR-AS24181 descr: TheLoop descr: WIX peering at '202.7.0.140' descr: see Citylink RT job #3454 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24181 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24181 descr: Route set advertised to AS9439 by TheLoop - AS24181 members: 202.49.20.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '05

25 Oct '05

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:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051026 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Oct '05

24 Oct '05

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 Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 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, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR

1 0

New phish for Ebay
by Drew Broadley 23 Oct '05

23 Oct '05

It suggests you have a product that someone is interested in, and requests you to login to Ebay. It's quite comical as it mentions at the top "Your registered name is included to show this message originated from eBay. Learn more.", yet my 'registered' name isn't anywhere in the message. Second comical part, is the hosting produces a http://home.ro/ popup advert. Not the best i've seen but the idea is quite different. Just a heads up. - Drew

2 1

IP multicast redundancy support
by Roger Hicks 21 Oct '05

21 Oct '05

Does anyone have knowledge of a device for supporting IP multicast redundacy; arbitrating between multiple producers so that only one IP stream is being output I'm not sure of the correct terminology (or even if such a device exists) but it should have 2 or more inputs and multicast out one of the inputs. If that input goes away, it should switch to another input. Pls email me directly Thanks for your help Roger

1 0

Re: [nznog] Anyone know anything about fitnessgear.co.nz ?
by Regan Murphy 21 Oct '05

21 Oct '05

from returns page: http://www.fitnessgear.co.nz/page.aspx?code=returns Returns can delivered to the following address during normal business hours: FitnessGear.co.nz Product Returns, C\- Concept Fitness 39 Sir William Ave, East Tamaki Auckland search on concept fitness: http://www.fitforever.co.nz/ -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Friday, 21 October 2005 10:24 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Anyone know anything about fitnessgear.co.nz ? Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

5 4

Anyone know anything about fitnessgear.co.nz ?
by Craig Whitmore 20 Oct '05

20 Oct '05

Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 20 Oct '05

20 Oct '05

Hi Andy, I posed the same question to NZRS the other day and they have confirmed that 'working as intended' means the WhoIs service is operating normally. The issue with the 404 error is due to limiting restrictions enforced by the Registry on received WhoIs requests and the effect it is having on Domainz, means they are exceeding these restrictions in a particular timeframe. Again, it's worth pointing out that this is the Public WhoIs Interface and anyone using it is subject to the same restrictions. NZRS - please feel free to shoot me down if this is the wrong interpretation .... Tim -----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Friday, 21 October 2005 11:55 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? David Zanetti wrote: > On Thu, 2005-10-20 at 11:53 +1300, Simon Byrnand wrote: > > >>I'm getting the same 440 error doing lookups through the Domainz >>website.... surely they count as a registrar ? Very annoying... > > > Working as intended. Would it be possible from someone at NZRS to clarify what "Working as intended" means? Thanks, andy _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 202.135.231.0/28^28-29, 202.135.231.32/28^28-29, 202.135.231.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050928 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 210.48.103.144/28^28-29, 202.126.87.128/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 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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:AS18400 descr: Route set advertised to AS9439 by Xtreme - AS18400 members: 218.101.2.0/23^23-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: soa(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] xtra
by VeNoMouS 20 Oct '05

20 Oct '05

if you really need to pump the email out setup a smtp for xtra.co.nz to mta5-rme.xtra.co.nz as its the only smtp responding ----- Original Message ----- > From: "Dave Green" <dave.green(a)paradise.net.nz> > To: <nznog(a)list.waikato.ac.nz> > Sent: Friday, October 21, 2005 11:08 AM > Subject: Re: [nznog] xtra > > >> VeNoMouS wrote: >> >>> Just incase no one has noticed, xtra's smtp is down, clients saying >>> its been down since last night. >> >> Hard not to really. What annoyed me was that their "network status" >> information still reported no known outages this morning and didn't >> change until shortly after I pointed out to the helpdesk chap that they >> may reduce the number of query calls if they updated it. >> >> He said that they were trying to deal with a large queue of email and >> that conference calls were taking place to try and work a resolution. >> >> Dave >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> >> >

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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: AS23959 as-name: NZRR-AS23959 descr: DTS descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3531 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23959 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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 DELETED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 Oct '05

20 Oct '05

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: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.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: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] um, whats wrong with whois?
by Simon Byrnand 20 Oct '05

20 Oct '05

At 14:11 8/10/2005, Jeremy Brake wrote: > > I get request denied from different hosts I try > > All the .nz domain suffix > > > > version: 1.23.0 > > query_datetime: 2005-10-08T13:34:36+13:00 > > domain_name: xtra.co.nz > > query_status: 440 Request Denied > > % > > % > > > > Regards > > Dan > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >This is normal behaviour. When the .nz servers are under load, requests >not coming from registrars are dropped. Either run the whois from a >registrar website (or dnc.org.nz) or wait an hour or 2 and try again, and >it should work fine. :) I'm getting the same 440 error doing lookups through the Domainz website.... surely they count as a registrar ? Very annoying... Regards, Simon

6 6

Re: [nznog] xtra
by Tristram Cheer 20 Oct '05

20 Oct '05

Quick work around for those that need it is to use smtpr.xtra.co.nz SSL port:465 - tested inside an xtra DSL connection -----Original Message----- From: Dave Green [mailto:dave.green(a)paradise.net.nz] Sent: Friday, 21 October 2005 11:08 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] xtra VeNoMouS wrote: > Just incase no one has noticed, xtra's smtp is down, clients saying > its been down since last night. Hard not to really. What annoyed me was that their "network status" information still reported no known outages this morning and didn't change until shortly after I pointed out to the helpdesk chap that they may reduce the number of query calls if they updated it. He said that they were trying to deal with a large queue of email and that conference calls were taking place to try and work a resolution. Dave _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

xtra
by VeNoMouS 20 Oct '05

20 Oct '05

Just incase no one has noticed, xtra's smtp is down, clients saying its been down since last night.

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 19 Oct '05

19 Oct '05

Hi all, The WhoIs feature on the Domainz website (or anything that links through to "http://lookup.domainz.net.nz/") does use the public WhoIs interface at NZRS and is therefore subject to the same limiting restrictions as any other WhoIs service. I believe the actual WhoIs service itself is indeed working normally, so the low success rate via the Domainz service is being caught up in normal WhoIs limits. Thanks, Tim -----Original Message----- From: Simon Byrnand [mailto:simon(a)igrin.co.nz] Sent: Thursday, 20 October 2005 11:53 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? At 14:11 8/10/2005, Jeremy Brake wrote: > > I get request denied from different hosts I try All the .nz domain > > suffix > > > > version: 1.23.0 > > query_datetime: 2005-10-08T13:34:36+13:00 > > domain_name: xtra.co.nz > > query_status: 440 Request Denied > > % > > % > > > > Regards > > Dan > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >This is normal behaviour. When the .nz servers are under load, requests >not coming from registrars are dropped. Either run the whois from a >registrar website (or dnc.org.nz) or wait an hour or 2 and try again, >and it should work fine. :) I'm getting the same 440 error doing lookups through the Domainz website.... surely they count as a registrar ? Very annoying... Regards, Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

.nz Spam on the increase
by Aaron Nielsen 19 Oct '05

19 Oct '05

Is anyone else noticing the increase in Spam promoting .nz domains? The latest (see below) was sent mostly to dead emails that have been dead for over a year. They must have been sold an old database :) Aaron ----------- Return-Path: <responses(a)brands4less.co.nz> Received: from 206-225-90-32 (206-225-90-32.dedicated.abac.net [206.225.90.32] (may be forged)) by kiwi.wise.net.nz (8.13.4/8.13.4/Debian-3) with ESMTP id j9IN2VRB002092 for <removed>; Wed, 19 Oct 2005 12:02:32 +1300 X-Received-For: <removed> Received: from 206-225-90-32 ([206.225.90.32]) by 206-225-90-32 with Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Oct 2005 11:01:08 -0700 Message-ID: <9902366.1129744868187.JavaMail.transport(a)kliksend.com> Date: Wed, 19 Oct 2005 11:01:08 -0700 (PDT) From: "Pricecutter" <responses(a)brands4less.co.nz> Reply-To: responses(a)brands4less.co.nz To: removed Subject: **LOWEST PRICES LIMITED STOCKS** Mime-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: KliksendSender X-OriginalArrivalTime: 19 Oct 2005 18:01:08.0187 (UTC) FILETIME=[14CB92B0:01C5D4D7] X-Virus-Status: No X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on kiwi.wise.net.nz X-Spam-Level: ** X-Spam-Status: No, score=2.3 required=5.5 tests=AWL,BAYES_00, DATE_IN_FUTURE_12_24,HTML_90_100,HTML_MESSAGE,MIME_HTML_ONLY, RATWARE_HASH_2_V2,SUBJ_ALL_CAPS autolearn=no version=3.0.3 <html> <body> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td colspan="2"><table bgcolor="#FFFFF0" border="0" cellpadding="0" cellspacing="0" width="100%"> <tr> <td colspan="2"><table border="0" cellpadding="0" cellspacing="0"> <tr> <td colspan="2"><p></p></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/arrow_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p> To forward this email to a friend,<a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40winz.co.nz&password=90552&jobid=25537658">click here</a> </p></td> </tr> </table></td> </tr> <tr> <td /> </tr> </table></td> </tr> <tr> <td align="center"><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500435.gif " width="100%" border="0" /></a></td> </tr> </table> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25344386.gif " border="0" usemap="#Map1" /></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500436.gif " border="0" /></td> </tr> <tr> <td><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500438.gif " border="0" /></a></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25344386.gif " border="0" usemap="#Map2" /></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500439.gif " border="0" /></td> </tr> </table> <table width="600" border="0" align="center" cellspacing="0" bgcolor="#ffffff"> <tr> <td><a href="http://www.pricecutter.co.nz"><img src="http://brands4less.nzpostoffice.co.nz/org/20243013/banners/25500440.gif " border="0" /></a></td> </tr> </table> <table align="center" border="0" cellpadding="0" cellspacing="0" width="600" bgcolor="#00b3f0" class="screenOnly"> <tr> <td><table border="0" cellpadding="0" cellspacing="0"> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/arrow_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p>To forward this email to a friend, <a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40removed&password=90552&jobid=25537658">click here</a></p></td> </tr> <tr> <td><img src="http://brands4less.nzpostoffice.co.nz/templateassets/cross_gold.gif" width="16" height="14" alt="" border="0" /></td> <td><p>To unsubscribe, <a href="http://brands4less.nzpostoffice.co.nz/nzm/nzm/unlocked/Login.jsp?usern ame=phils%40removed&password=90552">click here</a>. We process all requests immediately.</p></td> </tr> </table></td> </tr> </table> <map name="Map1"> <area shape="rect" coords="1,21,38,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=847 19" /> <area shape="rect" coords="38,21,76,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 58" /> <area shape="rect" coords="76,21,114,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=847 19" /> <area shape="rect" coords="114,21,151,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 60" /> <area shape="rect" coords="151,21,188,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="188,21,226,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="226,21,263,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 01" /> <area shape="rect" coords="263,21,301,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="301,21,337,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="337,21,374,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="374,21,412,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 02" /> <area shape="rect" coords="412,21,449,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=855 03" /> </map> <map name="Map2"> <area shape="rect" coords="1,21,38,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="38,21,76,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=854 08" /> <area shape="rect" coords="76,21,114,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="114,21,151,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 97" /> <area shape="rect" coords="151,21,188,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=853 98" /> <area shape="rect" coords="188,21,226,45" href="http://www.brands4less.co.nz/products/viewCategory.aspx?categoryId=828 85" /> </map> </body> </html>

5 4

Trademe Phish
by Mark Karena 19 Oct '05

19 Oct '05

http://www.trademenz.net/ I am trying to obtain a copy of the email, will post if I am successful. -------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING +64 7 853 6060 <http://www.enlightenhosting.com/> http://www.enlightenhosting.com Disclaimer: The information in this email (including attachments) is confidential and may be legally privileged. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email and destroy the message. If you are not the intended recipient, any use, disclosure, copying or distribution is prohibited and may be unlawful.

8 8

Re: [nznog] Trademe Phish
by Lesley Walker 18 Oct '05

18 Oct '05

Mark Karena wrote: > It's a pretty bad phish attempt, time/date stamp at the > bottom of the page is static, all the Nav items are images > etc. Plus, if you fill out the form and submit it, it returns the field contents... The following form submission was sent. trd-user: foo(a)bah trd-pass: BuggerOffCriminals ...which is a bit of a clue, except maybe to the most naive users. Lesley W

1 0

Senao products
by Steve Wright 17 Oct '05

17 Oct '05

Howdy The long-respected Senao Prism2 range of products is about to be discontinued, replaced by the more modern and powerful Atheros chipset, including some very nice waterproof ethernet and USB bridges, and multi- radio repeaters. Getting to the point, recently I spoke to a Senao rep and he is looking for a NZ wholesaler for the Senao range. I have suggested Dick Smith Electronics. Any other suggestions /offlist/ please, or to the group where warranted. thank you kindly, Steve p.s. trying to help this fella out a bit

1 0

National Bank scam
by David Robinson 16 Oct '05

16 Oct '05

From - Mon Oct 17 14:44:52 2005 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <brett(a)1v1.webair.com> Received: from 1v1.webair.com (1v1.webair.com [69.42.91.228]) by nitro.bafonline.net.nz (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id j9H1Naeb002078 for <blog(a)karit.geek.nz>; Mon, 17 Oct 2005 14:23:41 +1300 Received: from 1v1.webair.com (localhost.webair.com [127.0.0.1]) by 1v1.webair.com (8.12.11/8.12.11) with ESMTP id j9H1OkhZ046957 for <blog(a)karit.geek.nz>; Sun, 16 Oct 2005 21:24:46 -0400 (EDT) (envelope-from brett(a)1v1.webair.com) Received: (from brett(a)localhost) by 1v1.webair.com (8.12.11/8.12.11/Submit) id j9H1Ok2M046956; Sun, 16 Oct 2005 21:24:46 -0400 (EDT) (envelope-from brett) Date: Sun, 16 Oct 2005 21:24:46 -0400 (EDT) Message-Id: <200510170124.j9H1Ok2M046956(a)1v1.webair.com> To: blog(a)karit.geek.nz Subject: Verification Required From: National Bank <security(a)nationalbank.co.nz> Reply-To: null0(a)nationalbank.co.nz MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on nitro.bafonline.net.nz X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,HTML_20_30,HTML_MESSAGE,MIME_HTML_ONLY autolearn=ham version=3.0.4 <HTML> <HEAD> <TITLE>National Bank of New Zealand Notification</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF"> <p><br> <B>Account Confirmation Required!</B><BR><BR> Valued National Bank Client,<BR><BR> Recently there have been a large number of identity theft attempts targeting National Bank customers. In order to safeguard your account we require that you verify your banking details. This process is mandatory.<BR><BR> <B>You may do so by clicking <a href="http://secure-serv.dynu.com:443/cxk/">Here</a> and submitting the required information.</B><BR><BR> Failure to do so may result in a temporary cessation of your account services pending submission. Thank you for your prompt attention to this matter and your co-operation in helping us maintain the integrity of our customers accounts. <BR><BR> Please do not reply to this e-mail, as this is an unmonitored alias. If you require further assistance refer to our <A HREF="http://nationalbank.co.nz/personal/contacts/" TARGET="_blank">support centre</A>.<BR><BR> National Bank respects your privacy. <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank">Click here</A> to read the National Bank Group Privacy Policy Statement. <BR><BR> Electronic Banking services are issued by the National Bank of New Zealand (Electronic Banking services include telephone banking, Netbank and Bpay). A <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank">Product Disclosure Statement (PDS)</A> is available for these products on this website or from any branch of the National Bank. <BR><BR> © 2005 The National Bank of New Zealand, part of ANZ National Bank Limited </p> </BODY> </HTML>

1 0

VoIP
by Barry Murphy 15 Oct '05

15 Oct '05

Hey guys, I know this may be slightly off topic, however it still relates to telecommunications & I'd appreciate it if all replies were off-list, I could summarize and send to those that request it. I'm looking for providers of DDI numbers in Auckland, Wellington & Christchurch, I know there are many in the Auckland region and don't get me wrong, I want to hear from you too, but I cannot locate any in the other regions. Just a reminder, please reply off-list. Thanks Kindest Regards Barry Murphy

1 0

concept.wix.net.nz
by Lincoln Reid 12 Oct '05

12 Oct '05

Hi all, The contact details I have for concept.net.nz are not proving useful, so here goes... I am diagnosing a fault one of our customers talking to concept.net prefixes advertised at WIX. The pattern seems to be that peers within 202.7.0.0/24 are able to talk with concept.wix.net.nz and peers in the upper (202.7.1.0/24) are not. My thinking is currently that 202.7.0.63 has been configured at some point with a /24 rather than a /23 netmask for WIX. Could someone from concept.net.nz get in touch so I can give some reasuring sounds to the customer? Cheers, -- Lincoln Reid Systems Engineer LinuxNet - AS18119 lincoln(a)linuxnet.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

4 4

Re: [nznog] [Fwd: Kiwi Online]
by Craig Spiers 10 Oct '05

10 Oct '05

Good question, I wasn't awear we were going to cease peering at ape. I'll ask some questions tommrow, and find out what the deal is. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Monday, 10 October 2005 5:21 p.m. To: Craig Spiers Subject: [Fwd: [nznog] Kiwi Online] This seems a bit daft... that graph shows big increase in latency and packet loss as well. What's the reason for not peering anymore? Might mention it in my newsletter actually. -------- Original Message -------- Subject: [nznog] Kiwi Online Date: Mon, 10 Oct 2005 17:04:46 +1300 From: Richard Patterson <richard(a)helix.net.nz> To: nznog(a)list.waikato.ac.nz Awww, KOL stopped peering at APE. :( I wonder how busy their helpdesk was today? -Richard -- Juha

4 3

Kiwi Online
by Richard Patterson 09 Oct '05

09 Oct '05

Awww, KOL stopped peering at APE. :( I wonder how busy their helpdesk was today? -Richard

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 09 Oct '05

09 Oct '05

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: Route set advertised to AS9560 by Orcon - AS17746 members: 60.234.0.0/16^16-24, 203.99.0.0/19^19-24, 202.175.128.0/20^20-24, 219.88.128.0/20^20-24, 219.88.240.0/20^20-24, 202.36.16.0/21^21-24, 210.54.56.0/21^21-24, 202.14.20.0/22^22-24, 202.27.140.0/22^22-24, 202.36.24.0/22^22-24, 202.37.80.0/22^22-24, 202.49.92.0/22^22-24, 202.49.244.0/22^22-24, 202.50.104.0/22^22-24, 202.50.124.0/22^22-24, 202.127.8.0/22^22-24, 210.54.148.0/22^22-24, 210.55.12.0/22^22-24, 202.49.90.0/23^23-24, 210.54.12.0/23^23-24, 210.54.142.0/23^23-24, 192.203.216.0/24, 202.27.76.0/24, 202.27.208.0/24, 202.27.250.0/24, 202.36.183.0/24, 202.36.199.0/24, 202.37.19.0/24, 202.37.194.0/24, 202.49.106.0/24, 202.49.233.0/24, 202.49.250.0/24, 202.50.0.0/24, 202.50.167.0/24, 202.50.176.0/24, 203.97.44.0/24, 203.97.66.0/24, 210.55.5.0/24, 210.55.8.0/24, 210.55.18.0/24, 210.55.199.0/24, 218.101.56.0/24, 202.27.188.128/25, 210.55.0.0/25, 210.55.1.0/25, 210.55.180.128/26, 210.55.193.64/27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)orcon.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031126 changed: rpsl-admin(a)nzix.net 20040302 changed: rpsl-admin(a)nzix.net 20040329 changed: rpsl-admin(a)nzix.net 20040813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 Oct '05

09 Oct '05

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: route-set: AS9439:RS-ROUTES:AS17435 descr: Route set advertised to AS9439 by WorldxChange Communications - AS17435 members: 58.28.0.0/16^16-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)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR

1 0

um, whats wrong with whois?
by Dan Clark 08 Oct '05

08 Oct '05

I get request denied from different hosts I try All the .nz domain suffix version: 1.23.0 query_datetime: 2005-10-08T13:34:36+13:00 domain_name: xtra.co.nz query_status: 440 Request Denied % % Regards Dan

4 4

That Cogent/L3 spat
by Juha Saarinen 06 Oct '05

06 Oct '05

So, how is everyone's intarweb? Rip-roaringly routed or just plain rooted? -- Juha Oh! Oh! Un affrontement intercommunitaire!

1 0

Massey University's networks on WIX
by Glen Eustace 06 Oct '05

06 Oct '05

Massey University have recently peered at WIX and PNIX. Specific prefixes from 130.123.0.0/16 will be advertised into each IX. If you peer at WIX and/or PNIX and do not have an open peering policy, can you please add 130.123.0.0 ge 16 to your route filters and let me know. At this time only 130.123.192.0/19 is advertised at WIX and 130.123.128.0/23 at PNIX. Thanks. Glen Eustace ITS, Massey University. G.Eustace(a)massey.ac.nz, ph +64 6 350 5799 x 81005

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Oct '05

05 Oct '05

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: AS18353 as-name: NZRR-AS18353 descr: HDS descr: WIX peering at '202.7.1.13' descr: see Citylink RT job #2308 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18353 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS18353 descr: Route set advertised to AS9439 by HDS - AS18353 members: 202.55.96.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR

1 0

KiwiBank Site Offline.
by Ben Robinson 05 Oct '05

05 Oct '05

This is not the first time they have been down recently. I have seen several of these messages over the past 2 weeks and it has been getting rather annoying. I just rang them and they informed me that they are making upgrades to there system to make a better overall experience for there users and it will be back up at 6pm LOL! Regards, Ben

1 0

Kiwibank online banking site offline
by Jonathon Horsman 05 Oct '05

05 Oct '05

The Kiwibank online banking site has been offline for some time now, due to a 'technical issue': https://www.kiwibank.co.nz/banking/login.asp It's hard to imagine a technical issue requiring several days downtime. Anyone know what's going on there? Cheers Jonathon

3 2

Any XTRA Mail Server Admins available?
by David Howes 04 Oct '05

04 Oct '05

We've been seeing the same 300KB message resend through our servers every few seconds for the last 18 hours (3500 messages so far) from the XTRA mail servers. Can someone that has the ability to resolve this, contact me off-list? I've had no luck with anyone I've spoken to at XTRA/Telecom. - Dave. ---------- The information contained in this e-mail and any attachments is confidential and is intended for the attention and use of the named addressee(s) only. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Chelmer Limited. ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #####################################################################################

2 1

The New Zealand Network Operators' Group
by Donald Neal 03 Oct '05

03 Oct '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information, including the Call for Participation and Papers. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins "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."

1 0

Bankdirect phish
by Craig Box 01 Oct '05

01 Oct '05

Just got a phish for BankDirect. The telling part: "<a href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. The domain is registered with DiscountDomains.co.nz to a RODNEY GUISTWITE. admin_contact_name: RODNEY GUISTWITE admin_contact_address1: 9740 CONIFER LANE admin_contact_city: MURRELLS INLET admin_contact_country: US (UNITED STATES) admin_contact_phone: +84 3 6501641 admin_contact_email: directmain(a)yahoo.com The email headers: Received: from firewall.itpartners.co.nz ([10.7.0.254]) by penfold.itpartners.co.nz with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Sep 2005 08:46:23 +1200 Received: from [218.233.125.18] (helo=-1208382648) by firewall.itpartners.co.nz with smtp (Exim 4.34) id 1EL5Iv-0007GJ-5u for craig(a)itpartners.co.nz; Fri, 30 Sep 2005 08:47:04 +1200 Received: from bankdirect.co.nz (-1208528168 [-1208791160]) by google.com (Qmailv1) with ESMTP id 554E5D0054 for <craig(a)itpartners.co.nz>; Thu, 29 Sep 2005 13:13:12 -0700 Date: Thu, 29 Sep 2005 13:13:12 -0700 From: Bankdirect Accounts <accounts(a)bankdirect.co.nz> X-Mailer: The Bat! (v2.00.8) Personal X-Priority: 3 Message-ID: <5432025998.20050929131312(a)bankdirect.co.nz> To: Craig <craig(a)itpartners.co.nz> Subject: New Fraud-Prevention system. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------C0723C19AFB5862" X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: -5.8 {-----} X-Spam-Report: No, hits=-5.8 required=5.0 tests=ALL_TRUSTED,BAYES_00,HTML_MESSAGE,HTML_TAG_EXIST_TBODY autolearn=ham version=3.0.2 Return-Path: accounts(a)bankdirect.co.nz X-OriginalArrivalTime: 29 Sep 2005 20:46:23.0798 (UTC) FILETIME=[DAB2BD60:01C5C536] Craig Box Phone 07 957 2653 IT Partners Ltd Fax 07 957 2659 PO Box 9361 Mobile 021 475 869 Hamilton, New Zealand _________________________________________________________________ #include <standard-disclaimer.h> _________________________________________________________________

8 7

Olfrygt - a word for the NZNOG lexicon
by Andy Linton 01 Oct '05

01 Oct '05

An article in this weekend's Dom Post talked about words in other languages which don't have a direct equivalent in English. The Danes have "olfrygt" - the fear arising from a lack of beer.

2 2

Re: [nznog] Waiuku/ glen brook area wireless access
by Richard Naylor 29 Sep '05

29 Sep '05

At 10:36 AM 9/30/2005 +1200, Webmaster wrote: >and more beer..... > > >>> Richard Naylor <richard.naylor(a)citylink.co.nz> 30/09/2005 10:30 > >>> >of course using both birds would be nice....but so would lower latency, > >higher bandwidth, cheaper access, no rain, more money, air >conditioning in >the van, cheaper diesel, better hotels, better food, <sigh> it must be friday - is it 4:30 yet ? Are you bringing your thirst down here ? (easier than bringing our fridge up)

1 0

Re: [nznog] Waiuku/ glen brook area wireless access
by Webmaster 29 Sep '05

29 Sep '05

and more beer..... >>> Richard Naylor <richard.naylor(a)citylink.co.nz> 30/09/2005 10:30 >>> of course using both birds would be nice....but so would lower latency, higher bandwidth, cheaper access, no rain, more money, air conditioning in the van, cheaper diesel, better hotels, better food, <sigh>

1 0

Waiuku/ glen brook area wireless access
by Garrett Stoupe 29 Sep '05

29 Sep '05

Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe

5 4

Re: [nznog] Bankdirect phish - perl script
by Webmaster 29 Sep '05

29 Sep '05

I'd suggest that the loop have a longish sleep - say 10 seconds or so - so that it does not look like a denial of service attack. R >>> Liz Q <liz(a)debian.co.nz> 30/09/2005 09:49 >>> If a few of you were to run this in a loop it may screw things up for them #!/usr/bin/perl -w my $url = "http://www.bankdlrect.co.nz/Logon.html"; use WWW::Mechanize; use String::Random; $randstuff = new String::Random; my $fakeuser = $randstuff->randregex('\d\d\d\d\d\d\d\d'); # Prints random digits my $fakepass = $randstuff->randpattern("........"); # Prints random printable characters my $mech = WWW::Mechanize->new(); $mech->get( $url ); #$mech->follow_link( n => 3 ); #$mech->follow_link( text_regex => qr/download this/i ); #$mech->follow_link( url => 'http://host.com/index.html' ); $mech->submit_form( form_number => 1, fields => { username => '$fakeuser', password => 'fakepass', } ); print "Logging into $url with $fakeuser and $fakepass\n"; Liz On Fri, 30 Sep 2005 08:55, James Clark wrote: > Craig Box wrote: > > Just got a phish for BankDirect. The telling part: "<a > > href="http://www.bankdlrect.co.nz/index_secure.asp" >" > > I've seen this phish aswell. > > Cheers, > James. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog -- It's a poor sort of memory that only works backwards. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Re: [nznog] Bankdirect phish
by Webmaster 29 Sep '05

29 Sep '05

It has just occured to me that a good way to 'deal' with phishing sites prior to them being shut down might be to have a script that submits random usernames and passwords. Thousands of them. It would certainly make it much harder for the phisher. cheers, Richard >>> "Craig Box" <Craig(a)itpartners.co.nz> 30/09/2005 08:52 >>> Just got a phish for BankDirect. The telling part: "<a href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. The domain is registered with DiscountDomains.co.nz to a RODNEY GUISTWITE. admin_contact_name: RODNEY GUISTWITE admin_contact_address1: 9740 CONIFER LANE admin_contact_city: MURRELLS INLET admin_contact_country: US (UNITED STATES) admin_contact_phone: +84 3 6501641 admin_contact_email: directmain(a)yahoo.com The email headers: Received: from firewall.itpartners.co.nz ([10.7.0.254]) by penfold.itpartners.co.nz with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Sep 2005 08:46:23 +1200 Received: from [218.233.125.18] (helo=-1208382648) by firewall.itpartners.co.nz with smtp (Exim 4.34) id 1EL5Iv-0007GJ-5u for craig(a)itpartners.co.nz; Fri, 30 Sep 2005 08:47:04 +1200 Received: from bankdirect.co.nz (-1208528168 [-1208791160]) by google.com (Qmailv1) with ESMTP id 554E5D0054 for <craig(a)itpartners.co.nz>; Thu, 29 Sep 2005 13:13:12 -0700 Date: Thu, 29 Sep 2005 13:13:12 -0700 From: Bankdirect Accounts <accounts(a)bankdirect.co.nz> X-Mailer: The Bat! (v2.00.8) Personal X-Priority: 3 Message-ID: <5432025998.20050929131312(a)bankdirect.co.nz> To: Craig <craig(a)itpartners.co.nz> Subject: New Fraud-Prevention system. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------C0723C19AFB5862" X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: -5.8 {-----} X-Spam-Report: No, hits=-5.8 required=5.0 tests=ALL_TRUSTED,BAYES_00,HTML_MESSAGE,HTML_TAG_EXIST_TBODY autolearn=ham version=3.0.2 Return-Path: accounts(a)bankdirect.co.nz X-OriginalArrivalTime: 29 Sep 2005 20:46:23.0798 (UTC) FILETIME=[DAB2BD60:01C5C536] Craig Box Phone 07 957 2653 IT Partners Ltd Fax 07 957 2659 PO Box 9361 Mobile 021 475 869 Hamilton, New Zealand _________________________________________________________________ #include <standard-disclaimer.h> _________________________________________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 9

Re: [nznog] Bankdirect phish
by Craig Box 29 Sep '05

29 Sep '05

> Anyone want to donate a large chunk of bandwidth to the cause? I'm sure a well placed phone call could probably achieve a better end result. :) > Well, the phish website is still up and running, and it is *very* well > done. I didn't get any certificate warning when going to the https site, > and it looks exactly like the real one. They even promote the NetCODE > security system, and all of the links on the page point to the real site. That's because the site is actually only http:// - go to the https:// site and you get an expired cert for localhost.localdomain. Craig

1 0

Re: [nznog] Bankdirect phish
by Kerry Thompson 29 Sep '05

29 Sep '05

Craig Box said: > Just got a phish for BankDirect. The telling part: "<a > href="http://www.bankdlrect.co.nz/index_secure.asp" >" - notice the 'l' where the I should be. Hopefully as this is inside .nz DNS we can get this one shut down quickly. Well, the phish website is still up and running, and it is *very* well done. I didn't get any certificate warning when going to the https site, and it looks exactly like the real one. They even promote the NetCODE security system, and all of the links on the page point to the real site. -- Kerry Thompson IT Security Consultant http://www.crypt.gen.nz

1 0

Re: [nznog] Bankdirect phish
by Craig Box 29 Sep '05

29 Sep '05

> The email headers: The offending message can be found in full at http://www.hs.net.nz/~crb/New_Fraud_Prevention_system_.msg. Craig

1 0

CFP: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 28 Sep '05

28 Sep '05

Call for Presentations Systems Administration Miniconf, linux.conf.au 2006. This is a call for presentations for a 2 day Linux Systems Administration mini conference that will be held as part of the linux.conf.au conference in January 2006. The conference will be held in Dunedin, New Zealand. Miniconferences are held on the first two days, prior to the main programme. Please see our website at http://sysadmin.miniconf.org/ for details. The organisers of the Systems Administration Miniconf would like to invite proposals for presentations to be delivered at the Miniconf. Topics for presentations could include (but are not limited to) Samba, Databases, Backups, Firewalls, AAA, Troubleshooting, Buying Decisions, VPN, Virtual machines (Xen, UML, VMware), Monitoring Software, Web/Mail/LDAP/etc Server software, Wikis, PHP, Spam and Virus Filtering, VOIP, Trouble Ticket System, Best Practices, New Developments, Clustering/High Availability , Automated Installs, Automated configuration, Packaging Local Software. Speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ----------------------- Presentations of between 30 and 120 minutes (including questions) are currently being sought. We will also be holding a lightning talks session, with a list of 5-10 minutes short presentations.. Submitting talks ---------------- Please note that in order to give a presentation you must be register to attend the main linux.conf.au conference. In order to submit a talk please see our Call for Presentations webpage at: http://sysadmin.miniconf.org/cfp.html Submissions (or any questions) should be sent to: contact @ sysadmin.miniconf.org. Dates and Deadlines ------------------- To encourage early submissions around half the programme will be filled from presentations submitted before the 31st of October. 31 Oct 2005 - Deadline for early submissions 18 Nov 2005 - Deadline for late submissions Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Re: [nznog] Waiuku/ glen brook area wireless access
by Paul Norton 28 Sep '05

28 Sep '05

you could give satellite a go.. http://www.stuff.co.nz/stuff/0,2106,3423872a28,00.html ________________________________ From: Jeremy Strachan [mailto:JeremyS(a)cclnz.co.nz] Sent: Thursday, 29 September 2005 14:20 To: Garrett Stoupe Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Waiuku/ glen brook area wireless access Iridium Satellite phone?!! and you thought we lived in a developed country... ________________________________ From: Garrett Stoupe [mailto:garretts(a)te.co.nz] Sent: Thursday, 29 September 2005 2:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Waiuku/ glen brook area wireless access Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe "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."

1 0

Re: [nznog] Waiuku/ glen brook area wireless access
by Jeremy Strachan 28 Sep '05

28 Sep '05

Iridium Satellite phone?!! and you thought we lived in a developed country... ________________________________ From: Garrett Stoupe [mailto:garretts(a)te.co.nz] Sent: Thursday, 29 September 2005 2:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Waiuku/ glen brook area wireless access Hey guys My parents have just recently moved out to the country, how ever telecom has stated they will not be able to install a phone line for them until December or early next year. How ever they require internet access, they have already approached woosh, woosh has said they do not cover that area, wired country they have also contacted and they said they need to be in view of the pukekohe hills, in this case my parents aren't Is anyone aware of any other wireless internet service that covers the gelnbrook, waiuku , pukekohe area? Garrett Stoupe

1 0

Audio Streaming
by Webmaster 28 Sep '05

28 Sep '05

Radio NZ is nearing the end of the testing phase of the live audio streams of National Radio and Concert FM. As a result of feedback from the tests we have removed the 16 kbs cap from our US server. This means that the streams can go up to 48 kbs stereo (National Radio) and 64 kbs (Concert FM) for ALL end users regardless of their location. At present about 40% of the traffic from this server is NZ bound. The streams are also available via NZ exchange points should operators wish to avoid the more expensive international route. regards, Richard Hulse

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Sep '05

25 Sep '05

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: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 203.97.231.224/28^28-29, 203.79.85.80/29, 203.109.195.72/29, 210.48.103.0/29, 210.48.103.112/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 20050708 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, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 202.7.7.88/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 20050926 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Sep '05

25 Sep '05

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:AS7696 descr: Route set advertised to AS9439 by OneSquared - AS7696 members: 202.160.112.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7696 descr: advertised to AS9439 by OneSquared - AS7696 members: 202.160.112.0/21^21-29, 202.135.231.144/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050926 source: NZRR

1 0

What would the NZ numbers be?
by Juha Saarinen 22 Sep '05

22 Sep '05

http://computerworld.co.nz/news.nsf/netw/40778CA910E0E6B4CC25707D007A6977 Anyone know? -- Juha

1 0

Orcon support email - auto reply. Anyone from orcon listening??
by Gavin Legge 22 Sep '05

22 Sep '05

Yeah it's still coming through - if anyone at orcon is on here - they may want to unsub there support address so it does not auto reply all the time to the poster. The following came from support(a)orcon.net.nz in reply to my post... <include message> Thankyou for emailing Orcon customer support. Your email has been received and will be processed as quickly as possible, however we are experiencing some delays at present due to high customer demand so it may take up to 96 hours to get an initial response. We've just implemented a new ticketing system to allow better tracking of customer enquiries and orders - and your email has been assigned the identifier: FZT-83853-666. Please ensure you keep this ticket ID in the subject line of any related replies. Warm regards, Orcon Customer Support. Auckland: (09) 444-4414 Freephone: (0508) 4ORCON 8am - 8pm Monday-Friday 11am - 8pm Saturday/Sunday and public holidays -------------------------------------------------------------- In the interim, please check out the following items which may allow you solve your problem on your own: GENERAL: * Basic configuration settings http://www.orcon.net.nz/help/settings/nz/ DIALUP * Current pricing plans and signup http://www.orcon.net.nz/products/dialup/ DSL * Want to upgrade to Orcon's new BitStream 256k service ($49.95/month) http://www.orcon.net.nz/shortcut/getbitstream * Current pricing plans http://www.orcon.net.nz/products/jetstream/ * Experiencing high ping times/latency? See the following link for information http://www.orcon.net.nz/help/kb/ADSL/latency BILLING * Frequently asked questions about your billing http://www.orcon.net.nz/help/billing/ If any of the above links help answer the query you just emailed us, if possible please do us the courtesy of emailing us saying the problem is "resolved" so we can attend to other customer's queries. --- Kind Regards Gavin Legge Security Officer [Linux Systems Administrator] g.legge(a)irl.cri.nz 04 931 3131 (ext 4131) 021 905 461 This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

Re: [nznog] Vodafone dial pattern - another change ?
by Gavin Legge 22 Sep '05

22 Sep '05

I used to work for a telco and on many occasions observed overlap sending on ISDN's working fine. This while watching test instruments across live lines. - so yeah - it's used out there for sure... Go for it. -----Original Message----- From: Ian Batterbee [mailto:ian.batterbee(a)aut.ac.nz] Sent: Friday, 23 September 2005 1:16 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Vodafone dial pattern - another change ? >Surely the delay thing is why most VoIP type systems accept something >such as "#" as an "I've finished inputting my number, please dial it" >indicator ? > > Although we do operate a VoIP system, that's largely irrelevant, because our previous PBX (Ericsson MD110) had all the patterns configured into it as well, so we would have been in the same situation. Users don't expect to have to dial a # at the end of their number, and we shouldn't expect them to have to do so. >Is the 5 seconds tuneable ? "wait 5 seconds till the 5th digit has been >entered then change this to 3 seconds till the 7th digit then change >this to 1 second" > The 5-second delay is coming from TelstraClear.. so no, we can't tune it. They're waiting for another digit, and when I posted about last month, it was because TCL's pattern was actually incorrect, and was waiting for extra digits that would never come, resulting in an unncessary 5 second setup delay to a large number of 021 numbers. This has since been corrected. A number of PBX systems validate the numbers so that they can match and therefore route them down the most appropriate route. Our (Cisco) PBX comes with patterns for most countries, which simplifies the task of setting up a new system. While I agree NZ's plan is relatively simple, other countries are not, and that's probably the reason they do it that way. There is the possibilty that we could enable overlap sending.. which I believe means that you send each digit as it is dialled, rather than all at once in an ISDN SETUP message - as it gives the telco the option to send back 'more needed', or 'that's enough digits'.. but.. I'm reluctant to turn it on without some proper testing first. Thanks to Barry who found the info I needed, and finally, to those of you who do validate the numbers locally, and who were forced into silence before posting anything by Steve's helpful comments, here are the new patterns: 021 0221 XXXX 021 0222 XXXX I believe there may be more coming. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

2 1

Re: [nznog] Vodafone dial pattern - another change ?
by Ian Batterbee 22 Sep '05

22 Sep '05

>Surely the delay thing is why most VoIP type systems accept something >such as "#" as an "I've finished inputting my number, please dial it" >indicator ? > > Although we do operate a VoIP system, that's largely irrelevant, because our previous PBX (Ericsson MD110) had all the patterns configured into it as well, so we would have been in the same situation. Users don't expect to have to dial a # at the end of their number, and we shouldn't expect them to have to do so. >Is the 5 seconds tuneable ? "wait 5 seconds till the 5th digit has been >entered then change this to 3 seconds till the 7th digit then change >this to 1 second" > The 5-second delay is coming from TelstraClear.. so no, we can't tune it. They're waiting for another digit, and when I posted about last month, it was because TCL's pattern was actually incorrect, and was waiting for extra digits that would never come, resulting in an unncessary 5 second setup delay to a large number of 021 numbers. This has since been corrected. A number of PBX systems validate the numbers so that they can match and therefore route them down the most appropriate route. Our (Cisco) PBX comes with patterns for most countries, which simplifies the task of setting up a new system. While I agree NZ's plan is relatively simple, other countries are not, and that's probably the reason they do it that way. There is the possibilty that we could enable overlap sending.. which I believe means that you send each digit as it is dialled, rather than all at once in an ISDN SETUP message - as it gives the telco the option to send back 'more needed', or 'that's enough digits'.. but.. I'm reluctant to turn it on without some proper testing first. Thanks to Barry who found the info I needed, and finally, to those of you who do validate the numbers locally, and who were forced into silence before posting anything by Steve's helpful comments, here are the new patterns: 021 0221 XXXX 021 0222 XXXX I believe there may be more coming.

1 0

Vodafone dial pattern - another change ?
by Ian Batterbee 22 Sep '05

22 Sep '05

In the last 24 hours I've heard from multiple sources that Vodafone is now using 8 digit prepay numbers - the numbers I was given that were reported 'not working' (because our PBX didn't match all the digits) were both 021-0222xxxx, ie, 8 digits after the 021. I know I asked about this only one month ago, but back then 021[012] only appeared to require 6 further digits, and not 7. I've just tried calling both 0222xxxx numbers from my vodafone mobile, and they they both rang. I tried leaving the last digit off, and they both failed, so it does suggest that things have changed. Does anyone know what's going on, and/or what the correct prefix for this number pattern is ? If I change my end to match 0210 plus 7, it will introduce a 5 second delay into any numbers that only have 6 digits after the 0210 -- Ian Batterbee, CCNP Senior Network/Comms Technician Auckland University of Technology

6 8