- NZNOG - lists.nznog.org

telecom peering
by Anton Smith 26 Jun '07

26 Jun '07

Hello all, Has anybody seen or heard of any further development of this: http://computerworld.co.nz/news.nsf/news/EA57668828E0FEEFCC2572AC0070D766 Basically Telecom saying they would establish 29 regional points of interconnection, where providers could interconnect with them. The article mentions paying for a circuit into Telecom's network, with them reciprocating a circuit back (in the case of an ethernet interconnect, does this mean paying half each?). I am also wondering if any of these "regional points of interconnection" will be at the existing IXs, and in which case it doesn't seem that either Telecom or the other provider should have to pay anything for interconnect. What's the current word on the street? Has anybody engaged Telecom over this, or know what stage they are at? On another note, it seems funny that I am almost scared to post to nznog these days given the recent 'moderation by the people' ;). Regards, Anton

6 5

Systems Administration and Monty Python
by Jamie Baddeley 24 Jun '07

24 Jun '07

Right. Now that the subject matter has got your attention.. FX Networks (http://www.fx.net.nz/) has a position available for a junior/medium level systems administrator with some experience in looking after Debian Linux systems. Ideally they should have experience with Asterisk (or an enthusiasm for it), and a willingness to learn Cisco Networking technology. Perl hacking is also good. This person should not be afraid of customer interaction and working in a small tight team that has fun. Natural talent in dealing with the killer white rabbit of Caerbannog and the knights who say neh! is also a plus. I should also mention beer to keep it OT. Oh, and Wellington as well. Now I shall don my flame proof suit to deal with the slings and arrows of those who've taken it upon themselves to become defacto moderators of this fine list. For those of you moderately interested, drop me a line. thanks! jamie

1 0

NZNOG 08 - Call for Participation and Papers
by Simon Lyall 23 Jun '07

23 Jun '07

NZNOG 08 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Dunedin, New Zealand between 23 January and 25 January 2008. Our host is WIC. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. Conference Overview ------------------- NZNOG 2008 will consist of one day workshop and tutorial day followed by two days of conference presentations. There will also be opportunity for more informal and small lightening talks. These are typically around five minutes long and are organised closer to the actual conference. Important Dates --------------- Call for Papers opens: 25 June 2007 Deadline for speaker submissions: 6 August 2007 Responses to speaker submissions: 24 August 2007 Draft program published: 3 September 2007 Final program published: 1 November 2007 NZNOG 2008 Conference: 23 - 25 January 2008 SIG / Miniconf / Tutorials -------------------------- The first day of the conference will again be a workshop and tutorial day. It is usually run as one or more parallel 'interest group' streams and practical or interactive workshops of interest to Network Operators. This is a call for papers and activities for the first day of conference. Examples of past activities workshops include 'MPLS and fixed access networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet Resource Management Essentials', and a System Administrators mini-conference which included talks on 'Using Debian packages for system administration' and '42 hosts in 1U: Using virtual machines'. Conference Presentations ------------------------ The main conference program for 2008 will be made up of two days with a single stream where possible. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. NZNOG conferences have traditionally spanned the entire operational spectrum, and then some. Proposals for conference presentations are invited for virtually any topic with a degree of relevance to the NZNOG community. Past years' talks have included the following: - Internet exchange operations - Global anycast networks and the building thereof - Peering, peering, and peering - Network security - 10GB ethernet operations - Advanced networks in NZ - Current Internet research in NZ - Wireless networking - QOS over carrier networks - Content distribution networks and media streaming - How we paid the construction guys 18 pints of beer and they gave us a free metro fibre network in Palmy North - Open Source VoIP Platform in Carrier Environments If you are interested in submitting a talk please fill out the questions at then end of this document and email them to prog08(a)nznog.org . Submission Guidelines --------------------- When considering a presentation or SIG, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but each will help us determine the quality of your proposal and increase the likelihood it will be accepted. Final slides are to be provided by 21 January 2008. Note: While the majority of speaking slots will be submitted by 6 August 2007, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. The NZNOG conference is a TECHNICAL conference so marketing and commercial content is NOT allowed within the program. The program committee is charged with maintaining the technical standard of NZNOG conferences, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and unforgiving, and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. Funding and Support ------------------- NZNOG conferences are community run and funded events that try to keep the cost to attendees as low as possible so generally we are unable to pay the travel costs of speakers. There is a limited amount of funding available to international speakers. Conference presenters will not have to pay any registration fee for the day they are presenting. Discounts for SIG and lightning talk presenters may be available but are not automatic. Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG 2008 it is planned that there will be at least one hour long lightning talk session. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information Contact ------- Website * http://2008.nznog.org General Enquiries * info(a)nznog.org Talks and Papers * prog08(a)nznog.org Talk Proposals -------------- Please send all talk proposals (including lightning talks) to prog08(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Author's short biography: Title of Talk: Abstract: Length of talk: Please provide details if a version of this talk has previously been given: Will travel and accommodation assistance be required:

1 0

Bytes, Gigabytes and "GB" on the bill
by Paul Adshead 23 Jun '07

23 Jun '07

Bearing in mind most switches/routers output traffic stats in Bytes and most bills go to customers in GigaBytes, which of the following options are being used by each of us to convert between the two when creating the bill? A, divide by 1024 * 1024 * 1024; B, divide by 1024 * 1024 * 1000; C, divide by 1024 * 1000 * 1000; D, divide by 1000 * 1000 * 1000. Option A gives what anyone associated with computers would expect. Whilst the later options give a larger GB figure (- that can appear on the bill and be charged more). What is in use out there by ISPs? According to Wikipedia (http://en.wikipedia.org/wiki/Gigabyte) "The usage of the word "gigabyte" is ambiguous, depending on the context. When referring to RAM sizes and file sizes, it traditionally has a binary definition, of 1024³ bytes (typically assimilated or approximated to 1000³, for convenience). For every other use, it means exactly 1000³ bytes. In order to address this confusion, currently all relevant standards bodies promote the use of the term "gibibyte" for the binary definition."

5 4

[Fwd: [SixXS] gblon02 PoP open for Australian and New Zealand]
by Andy Linton 19 Jun '07

19 Jun '07

This may be of interest to some readers. andy -------- Original Message -------- Subject: [SixXS] gblon02 PoP open for Australian and New Zealand Date: Tue, 19 Jun 2007 16:40:51 +0100 From: Jeroen Massar <jeroen(a)sixxs.net> Reply-To: info(a)sixxs.net Organization: SixXS To: info(a)sixxs.net Hi, We have been trying to get an ISP from Australian or New Zealand on board, unfortunately it seems that we have met little interest up to now. In case you do know an ISP who might be interested of course don't hesitate to let point us to them, or let the, contact us. From several people we understood that IPv6 connectivity that is provided in the AU/NZ region is quality wise not the best and that there is no real alternative. We recently opened a new PoP in London, UK. The owner of which (Goscomb Technologies) has permitted any and all endpoints to be connected to this PoP. As such, if you don't mind the latency, which will most likely be around the 300-350ms range at least, you can now request a tunnel to the gblon02 PoP and it will be approved. See below for an example traceroute, or test it yourself using http://www.sixxs.net/tools/traceroute/ This at least allows one to get connectivity and start using it. Spread the word and let your friends enjoy too. In case you don't have enough credits to request a tunnel&subnet, don't hesitate to give a shout and we'll make that in order. Greets, Jeroen -- traceroute to 60.241.43.12 (60.241.43.12), 30 hops max, 40 byte packets 1 ge-0-0-0-1235.rt0.lon4.goscomb.net (77.75.104.121) 6.347 ms 8.645 ms 0.457 ms 2 cr02.ldn01.pccwbtn.net (195.66.224.167) 0.958 ms 0.621 ms 0.748 ms 3 ge3-4.br01.lax04.pccwbtn.net (63.218.50.86) 145.981 ms 144.941 ms 145.831 ms 4 reach.ge2-16.br01.lax04.pccwbtn.net (63.218.51.82) 147.341 ms 145.926 ms 146.323 ms 5 i-1-2.wil-core02.net.reach.com (202.84.251.201) 148.638 ms 149.345 ms 148.358 ms 6 i-4-0.sydp-core02.net.reach.com (202.84.144.102) 308.198 ms 308.394 ms 308.181 ms 7 unknown.net.reach.com (134.159.126.134) 304.362 ms 303.994 ms 304.543 ms 8 202.92.64.140 (202.92.64.140) 304.016 ms 304.783 ms 304.452 ms 9 202.92.127.86 (202.92.127.86) 305.379 ms 305.236 ms 304.571 ms 10 bri-pow-ibo-zeu-1-pos-4-0.tpgi.com.au (202.7.162.241) 318.572 ms 316.667 ms 317.729 ms 11 bri-nxg-ibo-zeu-1-pos2-2.tpgi.com.au (202.7.162.178) 318.023 ms 318.791 ms 318.606 ms 12 bri-nxg-ibo-nik-1-ge-0-1.tpgi.com.au (220.245.180.205) 316.950 ms 317.960 ms 317.714 ms 13 60-241-43-12.static.tpgi.com.au (60.241.43.12) 334.618 ms 333.790 ms 334.346 ms -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Jeroen Massar / http://unfix.org/~jeroen/ iHUEARECADUFAkZ3+QMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I1TfAJ9grjh3/f2SA4RyEGim+xJboM4L tACgiA7ZDsod680zORKjd1W8QTpox48= =TohL -----END PGP SIGNATURE-----

1 0

ihug DNS problems?
by bigalownz 15 Jun '07

15 Jun '07

I think its now 203.109.129.67

1 0

Soekris ?
by Craig Spiers 13 Jun '07

13 Jun '07

Hi guys, Anyone out there got a soekris 4521 (with pcmcia slots) for sale? The 4801 model is commonly used by citylink for route servers - I have a couple of these I would be willing to swap for a 4521 with pcmcia if anyone is interested :) Cheers

1 0

(no subject)
by mark10＠compass.net.nz 13 Jun '07

13 Jun '07

Perfect. Thanks Jamie. -----Original Message----- From: Jamie Baddeley [mailto:jamie.baddeley(a)vpc.co.nz] Sent: Wednesday, 13 June 2007 9:33 p.m. To: Mark Frater Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Bill Nortons "Asia Pacific Peering Ecosystems" Hi Mark, It doesn't look like it's in the NZNOG archive, but I dug through mine. See attached. It looks like it's early draft but hopefully it should give you what you need. Cheers jamie On Wed, 2007-06-13 at 17:09 +1200, mark10(a)compass.net.nz wrote: > Does anyone have a copy of Bill Nortons presentation titled "Asia > Pacific Peering Ecosystems" from NZNOG 2005 in Hamilton? > > I had a look at http://2005.nznog.org/ but the cupboard was bare. > > Mark > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Bill Nortons "Asia Pacific Peering Ecosystems"
by mark10＠compass.net.nz 12 Jun '07

12 Jun '07

Does anyone have a copy of Bill Nortons presentation titled "Asia Pacific Peering Ecosystems" from NZNOG 2005 in Hamilton? I had a look at http://2005.nznog.org/ but the cupboard was bare. Mark

5 4

[Fwd: Re: Bill Norton’s "Asia Pacific Peering Ecosystems"]
by Gerard Creamer 12 Jun '07

12 Jun '07

2004 and 2005 are now up. http://2004.nznog.org/ http://2005.nznog.org/ Just the conference sites for now - we'll get the galleries etc up as time allows. If you find anything busted please email details to info at nznog.org Cheers, Gerard mark10(a)compass.net.nz wrote: > Does anyone have a copy of Bill Norton’s presentation titled "Asia Pacific > Peering Ecosystems" from NZNOG 2005 in Hamilton? > > I had a look at http://2005.nznog.org/ but the cupboard was bare. > > Mark > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

ihug DNS problems?
by Simon Lyall 12 Jun '07

12 Jun '07

I'm seeing problems with doing DNS lookups against 203.109.252.42 which I believe is still ihug's main recursive DNS server [1]. For at least the last week around 20% of DNS queries are not being replied to. Testing to other ihug DNS servers is not showing any problems. Not sure if this is a problem since I am testing from non-ihug IP space and possibly they have put in ACLs[2]. No luck contacting them via email or phone [3]. [1] It might not be, they don't list one on their webpage anywhere. [2] If someone is a customer of theres they could probably check themselves, something like this will work: while [ 1 ] do dig www.ihug.co.nz @203.109.252.42 +tries=1 | grep "msec\|timed" sleep 5 done [3] They might want to update their details at http://www.nznog.org/?page_id=6 -- 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

Dunedin 5.8
by Bill Walker 12 Jun '07

12 Jun '07

Anyone put up anything new last Saturday. Have spoken to the usual suspects and no luck. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited ------------------------------------------------------------------------------------------------ Tel: 03 348 8747 / 0800 500638 Email: bill.walker(a)team.snap.net.nz<mailto:bill.walker(a)team.snap.net.nz> Web: www.snap.net.nz<http://www.snap.net.nz/> ------------------------------------------------------------------------------------------------

1 0

IPv6 .nz name servers
by DNS 12 Jun '07

12 Jun '07

NZRS is today pleased to announce that the .nz name servers are now operating with IPv6 connectivity in what can be regarded as the first phase of the .nz IPv6 rollout. The name servers are named ns8.dns.net.nz and ns9.dns.net.nz, and are located in Wellington and Albany repsectively. Both are connected to the NZ IPv6 Internet Exchange and there is a .nz Whois server accessible at whois.ipv6.srs.net.nz. NZRS thanks Open Contributors Corporation for Advanced Internet Development (OCCAID) and US telco Sprint for providing the IPv6 tunnels, and thanks Citylink for help in connecting to the NZ IPv6 Internet Exchange. .nz Registry Services is responsible for the operation of the register of domain names and the Domain Name System (DNS) in the .nz domain name space. For further information contact: support<at>nzrs.net.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jun '07

11 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS24388:RS-ROUTES:AS17435 descr: Route set advertised to AS24388 by World Exchange - AS17435 members: 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR

1 0

CHIX opens, finally!
by Simon Blake 11 Jun '07

11 Jun '07

Hi all, apologies in advance, this isn't strictly operational, but is likely to be of interest to most ISP's. Feel free to flame me directly. A somewhat belated announcement, those of you with sharp eyes will have noticed the CHIX RPSL database changes cropping up in NZNOG over the last few days. Essentially, CHIX is up and running and ready to carry traffic. There's a short press release up on http://www.citylink.co.nz/, currently Snap, ServerWorks and Net24 are configured to peer, and we'll have FX, WorldxChange and StreamingNet peering shortly. For those interested in connecting, the exchange is available in several buildings around Christchurch, including TVNZ, PWC, State Insurance (Division St in Riccarton) and the Sir William Pickering Business Park. The exchange runs within a VLAN on the distributed ethernet that runs over the Canterbury Fibre Networks fibre infrastructure - there is a somewhat dated coverage map at http://www.cfnl.co.nz/index.php?option=com_content&task=view&id=13 If you're interested in peering, please get in touch. Cheers Si

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jun '07

11 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS18202 as-name: NZRR-AS18202 descr: Net24 descr: CHIX peering at '218.100.24.12' descr: see Citylink RT job #9729 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24388 accept ANY AND NOT fltr-bogons export: to AS24388 announce AS18202 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nikolai(a)net24.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR --- OBJECT BELOW CREATED: route-set: AS24388:RS-ROUTES:AS18202 descr: Route set advertised to AS24388 by Net24 - AS18202 members: 210.5.48.0/21^21-29, 210.55.30.0/23^23-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nikolai(a)net24.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR

1 0

www.nznog.org
by Gerard Creamer 10 Jun '07

10 Jun '07

Hi, A quick announcement to let everyone know that the site at http://www.nznog.org has been updated. It now has info on NZNOG, with links to conference sites and the NOC list. There is a NOC list as part of the site - please check your entries and if they are incorrect or incomplete please *follow the instructions on the page* to get them updated / adjusted. The NOC list is a fairly informal affair, but I have made a spur of the moment decision that we'll (there's three of us in the NZNOG08 conference web team who will be updating these) only update requests originating from a URL that matches the URL in the table or is so obviously related that we're willing to take the risk. In other words please don't ask for updates from some disposable email address as we will most likely ignore them. Most things on the historical conference sites work, but some things are broken. We're still working on getting them sorted out, but thought it better to get the NZNOG and the 2008.nznog.org sites out. Comments and feedback of a useful and constructive nature would be appreciated. Cheers, Gerard NZNOG08 Public Relations Team

1 0

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

10 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 116.93.128.0/20^20-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070611 source: NZRR

1 0

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

10 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 116.93.128.0/20^20-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070611 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 07 Jun '07

07 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.petrie(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070608 source: NZRR

1 0

[Fwd: Dear Sir/Madam Would You Want This Income?]
by Justin Cook 07 Jun '07

07 Jun '07

Although this isn't strictly a phish, it passed my spam filters and is obviously a scam. Worth blocking.

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '07

05 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23655 as-name: NZRR-AS23655 descr: Snap Internet descr: WIX peering at '202.7.1.240' descr: see Citylink RT job #2857 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23655 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: aut-num: AS23655 as-name: NZRR-AS23655 descr: Snap Internet Limited descr: CHIX peering at '218.100.24.10' descr: see Citylink RT job #9020 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24388 accept ANY export: to AS24388 announce AS23655 notify: rpsl-admin(a)nzix.net notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070606 source: NZRR

1 0

Re: [nznog] APE / WIX route list Quagga RAM
by Gerard Creamer 05 Jun '07

05 Jun '07

Stuff all. WIX + a 1 route from an upstream is using a total of ~7% of 64Mb on a Soekris here = ~4.5Mb (zebra and bgpd) A full route table an a different router is only using about 25Mb. Gerard On 6/06/2007 9:45 a.m., Michael Fincham wrote: > Hey All, > > Does anyone have some rough figures for how much RAM Quagga uses to keep > the routing tables for WIX or APE in memory? > > -- Netspace Services Limited http://www.netspace.net.nz Phone +64 4 917 8098 Mobile +64 21 246 2266 Level One, 220 Thorndon Quay, Thorndon PO Box 12-082, Thorndon, Wellington 6004, New Zealand

2 1

APE / WIX route list Quagga RAM
by Michael Fincham 05 Jun '07

05 Jun '07

Hey All, Does anyone have some rough figures for how much RAM Quagga uses to keep the routing tables for WIX or APE in memory? -- -Michael Fincham Unleash Technology Solutions

2 1

Code for IPv6 test for content providers
by Nathan Ward 01 Jun '07

01 Jun '07

During a discussion on the NANOG list this week, I came up with an idea that would allow content providers to test their IPv6-ability ie. what would happen if they turned on AAAA records for their websites, which is currently a big reason that content providers aren't "6-ing up". The general idea is to do GETs to several different URLs on different hostnames, and have the different hostnames have IPv4-only, IPv6-only and IPv4+IPv6, and then report the stats. After some playing+testing, I've come up with some code, and it's available here: http://www.braintrust.co.nz/ipv6wwwtest/ I'm not really a JavaScript hacker so it probably isn't terribly amazing quality, but it seems to work OK for me - I've been running it on several of my websites with a large range of user clue+access+OS +browser+ISP as visitors and I've had no complaints. The code is running on the page above, too. Also, the default timeout in the tarball is too high, 10000-20000 is probably adequate. Please let me know if you use it, or if you do something similar or use it for inspiration or whatever. In addition, I'm sure we'd all love to see any statistics you can share when using this. Enjoy! -- Nathan Ward

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24111 descr: advertised to AS9560 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061005 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24111 descr: advertised to AS9560 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: 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 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, 116.90.129.0/24^24-29, 116.90.130.0/24^24-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: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24111 descr: Route set advertised to AS9439 by NZwireless - AS24111 members: 203.110.28.0/23^23-29, 210.54.151.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: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040810 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24111 descr: advertised to AS9439 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

RIPE NCC DNS Monitoring Service (DNSMON) for .nz name servers
by DNS 30 May '07

30 May '07

The .nz secondary name servers have been added to the RIPE NCC DNS Monitoring Service (DNSMON). DNSMON provides a comprehensive, objective and up-to-date overview of the quality of the service provided by DNS servers. Graphs and further details about DNSMON can be found here: http://dnsmon.ripe.net/ -- Dave Baker .nz Registry Services

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 29 May '07

29 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070226 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 29 May '07

29 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070328 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR

1 0

Dunedin 5.8
by Bill Walker 29 May '07

29 May '07

Hi all, Anyone in Dunedin put up any new 5.8 gear around Monday lunchtime? Or changed channels on existing gear? We're seeing heaps of noise between 5808Mhz and 5824Mhz. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited ------------------------------------------------------------------------------------------------ Tel: 03 348 8747 / 0800 500638 Email: bill.walker(a)team.snap.net.nz<mailto:bill.walker(a)team.snap.net.nz> Web: www.snap.net.nz<http://www.snap.net.nz/> ------------------------------------------------------------------------------------------------

1 0

NZIX looking glasses
by Andy Linton 28 May '07

28 May '07

You may find this alternative Looking Glass view of the NZIX Route Servers useful. http://nzix.net/cgi-bin/lg.cgi At this stage this is in addition to the original interfaces.

3 2

Problems with WIX route servers late last week.
by Simon Blake 28 May '07

28 May '07

Hi folks This is a somewhat belated reply to those who might have noticed wiggyness with the WIX route servers late last week. Thanks to Lee from WorldExchange who first pointed out the problem. We eventually tracked it down fumble fingering at a local ISP, which caused a full route table to be sent to the route servers. As the route servers are RAM and CPU constrained, they didn't cope outstandingly well with this - while they didn't crash, they ran sufficiently slowly that other BGP sessions were getting randomly dropped. Once the offenders were tracked down and had their ways mended, it all came right. So we're currently thinking about ways to avoid this sort of DOS in future. Boxes with more headroom would be a start, so we're considering alternative hardware options at the moment. We're also considering the merits of running one RS with quagga, and one RS with OpenBGPD - that's a possibility into the future, but will require a certain amount of RPSL and looking glass rejigging before we could go live. Relatedly, Andy has been playing with alternate looking glass code, and has this under testing - the "looking glass for amiga users" (tm) http://nzix.net/cgi-bin/lg.cgi put your keyboard in the garage, click submit, and then keep clicking. Any feedback welcome. Cheers Simon

1 0

Network Engineer position available at Smartlinx 3 Ltd Upper Hutt
by Adrian Smith 27 May '07

27 May '07

we currently have a Network Engineer position available at Smartlinx 3 Ltd in Upper Hutt. http://smartlinx3.co.nz/ For further information on this position please contact David Haynes, Managing Director, Smartlinx 3 Ltd david.haynes (AT) smartlinx3.co.nz Phone/FAX +64 4 939 1444 Cheers Adrian Smith

10 10

Soliciting peers for the root servers located in NZ...
by Peter Losher 27 May '07

27 May '07

Hi, ISC is currently in the process of upgrading our routers in Auckland, and it behooves us to remind the local community that there is a local instance of f.root-servers.net here at the SkyTower, connected to APE. With the DDoS against several of the root servers back in February which proved our anycast model (most folks never noticed there was even a issue), we are once again soliciting peers across our 40+ nodes so we can "keep root server traffic local" wherever possible. So if you are not already peering with us and would wish to do so, please fill out our peering form here: http://www.isc.org/ops/peering/request/ For those of you that don't wish to peer with us over public IX's, we will consider private peering arrangements if you are already present (in the case of Auckland) at the SkyTower. For those of you only present at the WIX, might I suggest contacting Autonomica, who operate a instance of i.root-servers.net there. Hope to be peering with you soon (if we don't already). Best Wishes - Peter -- Peter_Losher(a)isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow"

1 0

Alert: Kiwibank scam
by Clark Mills 27 May '07

27 May '07

Hi all. Don't know if this is new/old but I got this an hour ago: Kiwibank wrote: > *Reminder:* Customers are reminded that User Maintenance personal > information requires update. At Kiwibank online banking, We are so > confident with our online security system that we guarantee your money. > This is provided you have complied with our Kiwibank Online Banking > Product Disclosure Statement. Please proceed to your Kiwibank online > banking personal internet banking below for more update on your account > maintenance : > > Proceed to Kiwibank Internet Banking Here > <http://www.zachcone.com/kiwibank/> It didn't trip Thunderbird's scam alert due to the way the link was constructed. I've the full message text and screenshot here if anyone's interested. http://c.mills.ctru.auckland.ac.nz/KiwibankScam/ Cheers... Clark

5 4

Notification of NZRR Database changes
by NZRR Database Notifications 23 May '07

23 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18353 descr: advertised to AS9439 by Revera - AS18353 members: 202.55.99.0/24^24-29, 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: Marc.Nienkemper(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060601 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18353 descr: advertised to AS9439 by Revera Limited - AS18353 members: 192.88.85.0/24^24-29, 202.55.99.0/24^24-29, 202.55.100.96/27^27-29, 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: networkteam(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070524 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 May '07

23 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070522 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, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070524 source: NZRR

1 0

Link-bonding scheduler on Allied Telesyn boxes
by Matthew Poole 23 May '07

23 May '07

Hi Does anyone happen to know the link-bonding scheduling method used by AT 9812T and Switchblade 2008 boxes? We've seen _reduced_ performance with link bonding on these systems when connecting them to Linux boxes, and were wondering if there's a particular scheduling method that should be enabled on the Linux end. -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '07

21 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070502 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, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070522 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 20 May '07

20 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS17649 descr: Route set advertised to AS9560 by DMZGlobal Ltd - AS17649 members: 203.144.40.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: john.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070521 source: NZRR

1 0

.co.uk zone changes.
by Andy Davidson 17 May '07

17 May '07

Hi, How long does it take for changes to the .co.nz domains take to be reflected in whois and dns ? I am not native to the region, so don't have existing experience with this. A client of mine registered a .nz domain for a project of theirs through melbourneit. I changed the dns servers on their site, and it said that the change has been submitted, but 'dig ns theirdomain @202.46.190.130' still shows the original nameservers, as does whois. Any clues ? cheers -a

7 7

Notification of NZRR Database changes
by NZRR Database Notifications 16 May '07

16 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom Systems Auckland - AS10022 members: 202.36.8.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060807 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom Systems - AS10022 members: 202.36.8.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.188.185.0/24^24-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 210.55.5.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: nigelm(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070517 source: NZRR

1 0

[Fwd: Security Survey]
by Philip Smith 14 May '07

14 May '07

Forwarded on behalf of Danny McPherson. (And apologies for any duplicates!) -------- Original Message -------- Subject: Security Survey Date: Mon, 14 May 2007 15:55:00 -0600 From: Danny McPherson <danny(a)tcb.net> Folks, It's time for the Infrastructure Security Survey again! If you're willing to complete the survey please go here to receive a token (which will be mailed to you with a URL for response input): https://sec-survey.tcb.net/index.php?sid=1 You can find the previous editions of the survey report here: http://www.tcb.net/ISP_Security_Report-2H2005.pdf http://www.tcb.net/2006-WISR.pdf If you have any questions, comments or concerns please let me know. Thanks in advance! -danny danny(a)tcb.net

1 0

TelstraClear DSL AKL-CHC
by Russell Tester 13 May '07

13 May '07

We have a customer experiencing problems since around mid-day Friday with their Auckland site talking to their Christchurch site via TCL on net DSL. The problem appears to be with the AKL site that can also not reach a number of our other DSL fed TCL customers in CHC, yet all other internet access appears to be fine. Whilst we have a TCL tech visiting the ALK site (some time), I'm interested if anyone else has encountered similar issues? Also if someone in ALK on TCL on net DSL could reply with a trace to 203.97.49.85 id appreciate this. Cheers, Russell Tester ServerWorks Ltd

2 3

Re: [nznog] Whois Server
by Ewen McNeill 13 May '07

13 May '07

In message <007701c795ac$c9249580$966e000a(a)craigcdaacab45>, "Craig Spiers" write s: >I've been doing whois lookups against whois.srs.net.nz for a few domains we >host at work, mainly to look at the billed until date. However, small >problem.. query 10 domains and suddenly they block you. There is an automatic blacklist which is triggered by a rate of recent requests from the same IP address (and/or netblock). Querying, eg, 10 domains a day isn't a problem (I regularly do this by hand in the course of my work), but querying 10 domains one after another, with no delay, from a script is likely to trigger the blacklist. After a quiet period (some hours?) the IP will fall back out of the automatic blacklist. (I believe there's also a manual blacklist for particularly troublesome offenders.) If your queries are not time critical (and it sounds like from later posts to NZNOG they're not), I'd suggest slowing your queries down so that you're only doing, eg a dozen queries an hour. (I'm assuming given the choice of forum that you have a legitimate reason for doing this. Illegitimate purposes are likely to get you permanently blacklisted anyway.) It may also be helpful to know that at least some registrars provide a customer-usable interface to the whois XML interface bulk query for the domains belonging to you that are registered through them. Which may be an easier way to get the information that you want. Ewen

1 0

Whois Server
by Craig Spiers 13 May '07

13 May '07

Hi All, I've been doing whois lookups against whois.srs.net.nz for a few domains we host at work, mainly to look at the billed until date. However, small problem.. query 10 domains and suddenly they block you. Has anyone else come across this? if so who do you talk to to get the limit increased? Cheers, Craig - Solarix

5 5

Re: [nznog] Whois Server
by Craig Spiers 13 May '07

13 May '07

yeah, i didnt think they would be.. any idea what the limit is set to? I dont mind say querying 1 domain every hour (extreme limit) but time is not critical with what im using it for. Just want to update billed until date in our database every month or so. I dont care if it takes all month to run over ~ 200 domains, as long as there's a date in there :) Cheers _____ From: Tim John - Domainz [mailto:tim.john(a)domainz.net.nz] Sent: Monday, May 14, 2007 10:26 AM To: Craig Spiers Subject: RE: [nznog] Whois Server Hi Craig, If you use the public whois or the lookup utility on the DNC site, there is a rate limit applied if a certain number of queries are attempted in a short space of time. If you happen to be an authorised Registrar, then you should connect via the XML gateway where rate limiting is not applied (or at least it's set a lot higher). I don't think the NZRS are interested in a conversation to increase this threshold on the public site. Been there, done it, got the T-shirt ! Tim From: Craig Spiers [mailto:craig(a)spiers.gen.nz] Sent: Monday, 14 May 2007 10:20 a.m. To: 'nznog' Subject: [nznog] Whois Server Hi All, I've been doing whois lookups against whois.srs.net.nz for a few domains we host at work, mainly to look at the billed until date. However, small problem.. query 10 domains and suddenly they block you. Has anyone else come across this? if so who do you talk to to get the limit increased? Cheers, Craig - Solarix

1 0

Re: [nznog] Whois Server
by Craig Spiers 13 May '07

13 May '07

Yeah, unfortunatly we arent a registrar. We just host a lot of domains, and use enlighten as our registrar. Just trying to query for the billeduntil date - it's a legitimate purpose - we are just trying to build ourselves a notification system to warn us when domains are due to expire etc. I'll try contact nzrs Cheers -----Original Message----- From: Sam Sargeant [mailto:sam.sargeant(a)gmail.com] Sent: Monday, May 14, 2007 10:25 AM To: Craig Spiers Subject: Re: [nznog] Whois Server On 5/14/07, Craig Spiers <craig(a)spiers.gen.nz> wrote: > I've been doing whois lookups against whois.srs.net.nz for a few > domains we host at work, mainly to look at the billed until date. > However, small problem.. query 10 domains and suddenly they block you. If you're a registrar it's recommended you use the XML api to the SRS for queries like this. The folks at NZRS (www.nzrs.net.nz) might be able to tweak their whois blacklisting if that's not an option for you. Sam.

1 0

New Zealand IP Range
by bigalownz 13 May '07

13 May '07

does any one have a list of New Zealand IP Range ??

5 8

Re: [nznog] New Zealand IP Range
by Ian Henderson 12 May '07

12 May '07

Drew Broadley <mailto:drew(a)broadley.org.nz> wrote on Sunday, 13 May 2007 12:03 PM: > Maxnet Nationalroute list > BGP feed on APE > BGP feed on WIX > Global Gateway NZ routing list 'wget ftp://ftp.apnic.net/pub/stats/apnic/delegated-apnic-latest; grep NZ delegated-apnic-latest' may also be useful. -- Ian Henderson, CCIE #14721 Senior Network Engineer, iiNet Limited

1 0

Geoff Huston and Tony Hain align - This is bad.
by Nathan Ward 12 May '07

12 May '07

http://www.potaroo.net/tools/ipv4/ Those of you who are giving out or selling CPEs (or is the plural CPE?), would be wise to ensure that they currently, or with a software upgrade can, support IPv6. http://search.dse.co.nz/search.php? site=&w=IPv6&submit.x=0&submit.y=0&submit=Go -- Nathan Ward

1 0

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

10 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070410 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 202.6.116.0/23^23-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.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070511 source: NZRR

1 0

Re: [nznog] Xtra
by Craig Whitmore 09 May '07

09 May '07

----- Original Message ----- From: "Geraint Jones" <g.jones(a)fmf.net.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Tuesday, May 08, 2007 12:04 PM Subject: [nznog] Xtra > Can someone from xtra please contact me offlist > Someone I know has a Dialup Xtra Account, so they are from Xtra. Good enough? Xtra is a large place..different people look after different things who may or may not be on this list. Dialup problem? Mail Problem? DNS Problem? Something else problem... too many to name. Being Serious now.. This mailing lists isn't for "please can someone contact me". There are other more official and better ways of contacting people who can help you. You could try: http://xtra.co.nz/help/0,,14395,00.html which seems to be the official ways of contacting them. Craig..

7 7

Telstra Cable contact
by Nick Larsen 09 May '07

09 May '07

Hi, Could a Telstra Cable (or DSL) network engineer please contact me off-list (if emailing, use the email address in my signature). It's with regards to Telstra Cable and DSL customers experiencing issues with HTTP on the IP range: 202.174.6.0/23 Cheers, -- Nick Larsen ZeroOne Operations 04 471 4447 nick(a)zeroone.co.nz

3 2

451 error from Freeparking mail server
by Michael Fincham 07 May '07

07 May '07

Hi everyone, Is anyone else experiencing this error delivering mail to freeparking hosting customers: <address removed>: host mta.hosts.net.nz[210.48.108.65] said: 451-Unable to validate michael(a)unleash.co.nz with the MX mailserver for 451 unleash.co.nz (in reply to RCPT TO command) We've been getting this message for several weeks when we attempt to deliver mail to Freeparking hosted customers. It doesn't seem like postmaster@ is being monitored, certainly I haven't received a reply from the several e-mails I've sent, and Freeparking's phone support people weren't any help. Any suggestions? -- -Michael Fincham <michael(a)unleash.co.nz> Unleash Technology Solutions

6 8

Re: [nznog] Xtra
by Nathan Ward 07 May '07

07 May '07

Additionally, can Steve Phillips <steve(a)focb.co.nz> please contact me offlist. On 8/05/2007, at 12:04 PM, Geraint Jones wrote: > Can someone from xtra please contact me offlist > > Ta > > Geraint Jones > Systems Administrator > French Maid Foods > Tel + 64 4 568 2687 > Fax + 64 4 568 2345 > Mob + 64 21 739 240 > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > !DSPAM:22,463fbf378171548713350! > >

2 1

Xtra
by Geraint Jones 07 May '07

07 May '07

Can someone from xtra please contact me offlist Ta Geraint Jones Systems Administrator French Maid Foods Tel + 64 4 568 2687 Fax + 64 4 568 2345 Mob + 64 21 739 240

1 0

NZNOG 08 - Call for SIG / Miniconf / Tutorials
by Simon Lyall 03 May '07

03 May '07

The NZNOG 08 conference will be held on 23-25 January 2008 in Dunedin. The first day of the conference will again be a workshop and tutorial day. It is usually run as one or more parallel 'interest group' streams and practical or interactive workshops of interest to Network Operators. This is a call for papers and activities for the first day of conference. Examples of past activities workshops include 'MPLS and fixed access networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet Resource Management Essentials', and a System Administrators mini-conference which included talks on 'Using Debian packages for system administration' and '42 hosts in 1U: Using virtual machines'. A further call for presenters for the remainder of the conference (a single stream of general networking topics) will be made in due course. Please contact prog08 @ nznog.org if you are interested in organising an event on this day or if you have a suggestion about an event that could be included.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 May '07

02 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9733 descr: advertised to AS9439 by Netspace Services Limited - AS9733 members: 210.4.208.0/21^21-29, 203.118.134.64/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: operations(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070116 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9733 descr: advertised to AS9439 by Netspace Services Limited - AS9733 members: 210.4.208.0/21^21-29, 203.118.134.64/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: gerard(a)netspace.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070503 source: NZRR

1 0

InternetNZ Governance Positions
by Keith Davidson 01 May '07

01 May '07

Please pardon the intrusion of this somewhat off-topic post to this list, and I promise to buy beer for anyone who takes offence, at next years NOG meeting... InternetNZ is recruiting directors to sit on the Board of its subsidiary company, New Zealand Domain Name Registry Ltd (trading as .nz Registry Services or "NZRS"); and members to sit on the .nz Oversight Committee ("NZOC"), which has stewardship of the .nz domain name space. These positions provide an exciting opportunity to contribute to the good governance of the .nz domain name space. Company directors and those with general governance skills are encouraged to apply for the appropriate positions. The retiring incumbents are eligible for reappointment. More information on the Domain Name Commission can be found at www.dnc.org.nz and about NZRS at www.nzrs.net.nz and a summary of the vacancies is available at <www.internetnz.net.nz/vacancy/index.html> Please send applications to vacancy(a)internetnz.net.nz by 5pm on Wednesday 9 May. Regards Keith Davidson Executive Director - InternetNZ

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 May '07

01 May '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: thomas.salmen(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070111 source: NZRR 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, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070502 source: NZRR

1 0

IPv6 WIX Route Server being upgraded
by Dylan Hall 26 Apr '07

26 Apr '07

The IPv6 WIX route server will be disappearing for a short time this afternoon while it is upgraded. The upgrade fixes a couple of quagga bugs, gives us a newer OS/Kernel, and adds support for MD5 auth (passwords) and 4-byte ASN's. If anyone is interested in testing the new features please drop an email to: tech <at> citylink.co.nz. If anyone has any issues with the route server after the upgrade, please drop an email to: faults <at> citylink.co.nz. or call the usual fault numbers. Thanks, Dylan

1 0

Notice of maintenance work on ns1.dns.net.nz
by DNS 25 Apr '07

25 Apr '07

Please note we will be doing some maintenance work on the machine that serves ns1.dns.net.nz between 06:00 and 10:00 on Sunday 29th of April. During this time ns1.dns.net.nz may not be available. Throughout this period the other six .nz zone servers (ns2 - ns7) will be available. Please contact me if you have any questions. Dave Baker .nz Registry Services support(a)nzrs.net.nz

1 0

Reminder for 2.3Ghz BWA comments
by Paul Horak 25 Apr '07

25 Apr '07

Just a reminder for anyone with an interest in using 2.3Ghz for Broadand Wireless Access - comments on the proposed Auction/Managed Park have to be in by 5pm tommorrow (27th April). Full details are on the MED site here: http://www.rsm.govt.nz/auctions/auction09/index.html Cheers, Paul NetSmart Ltd http://www.netsmart.co.nz/, Level 2, Regency House, 1 Elizabeth Street, P O Box 15020, Tauranga, New Zealand Tel: 07 5711367 Fax: 07 5711372

1 0

Re: [nznog] Traffic shaping
by Jonathon Exley 25 Apr '07

25 Apr '07

Try mastershaper (www.mastershaper.org) I haven't used it but it looks pretty Jonathon Exley ------------- Date: Tue, 24 Apr 2007 23:54:30 +1200 (NZST) From: "Michael Fincham" <michael(a)unleash.co.nz> Subject: [nznog] Traffic shaping To: nznog(a)list.waikato.ac.nz Hello Everyone, What're people using for traffic shaping and prioritisation these days? I'm trying to find if there is a viable alternative to the old standard of tc and qdiscs like htb and cbq which are a pain (and a half) to maintain. -- -Michael Fincham Unleash Technology Solutions

2 1

Traffic shaping
by Michael Fincham 25 Apr '07

25 Apr '07

Hello Everyone, What're people using for traffic shaping and prioritisation these days? I'm trying to find if there is a viable alternative to the old standard of tc and qdiscs like htb and cbq which are a pain (and a half) to maintain. -- -Michael Fincham Unleash Technology Solutions

3 3

Hotmail
by Simon Garner 24 Apr '07

24 Apr '07

Has anyone else here encountered issues where email to Hotmail is just silently discarded? Hotmail's servers accept the email for delivery, but then it never appears in the inbox, nor the Junk folder. I have been trying to work through this problem with a customer for the last couple of weeks and it's got me stumped. The domain (simpleas.co.nz) of the server the customer is sending from has SPF and SenderID records, and mail to other sites works fine (Gmail for example shows "PASS" for the SPF records). I am offering free beer for the first person with a working solution. PS: I'd ask Hotmail, but it seems like it's not worth the effort: http://davesource.com/Bugs/hotmail.1.html Cheers, -- Simon Garner Technical Director <sgarner(a)expio.co.nz> EXPIO Communications Ltd <http://www.expio.co.nz>

4 4

Network changes at Xtra ...
by Tim John - Domainz 23 Apr '07

23 Apr '07

Hi, We're having a number of customers complain about email not being delivered over the Xtra network. Error messages being submitted to us are similar to: Apr 24 00:00:37 web1 postfix/smtp[14312]: 999977E99E: to=<xx(a)xtra.co.nz>, orig_to=<les(a)xx.co.nz>, relay=mta.xtra.co.nz[210.54.141.1], delay=7174, status=deferred (host mta.xtra.co.nz[210.54.141.1] said: 421 Message rejected (in reply to end of DATA command)) We know Xtra have recently being changing setting on firewall/router combination as we had a similar issue last week .... It looks like they are doing it again ! What really takes the biscuit is that customers who call Xtra are told that it's a fault of someone else i.e ours !! We're happy to take calls from these customers, but we would like to give them the right information, unlike Xtra is doing ! Could someone Xtra contact me off list, please. Sorry if this is off topic, but it's mighty frustrating as this is a continuous battle .. Thanks, Tim

2 1

[Fwd: IPv6 Type 0 Route Header Design Flaw]
by Juha Saarinen 23 Apr '07

23 Apr '07

Apropos the recent discussions about IPv6: -------- Original Message -------- Subject: IPv6 Type 0 Route Header Design Flaw Date: Mon, 23 Apr 2007 20:09:19 +0200 From: Marc Balmer <mbalmer(a)openbsd.org> Organization: The OpenBSD Project To: security-announce(a)openbsd.org IPv6 type 0 route headers can be used to mount a DoS attack against hosts and networks. This is a design flaw in IPv6 and not a bug in OpenBSD. This problem has been fixed in the OpenBSD CVS repository in the -current and -stable branches. The -current snapshots of OpenBSD contain these fixes as well. It is recommended that users of OpenBSD update their kernel asap using cvs or manually apply the source code patches listed below. A source code patch for OpenBSD 4.0-stable can be downloaded from ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.0/common/012_route6.patch. A source code patch for OpenBSD 3.9-stable can be downloaded from ftp://ftp.openbsd.org/pub/OpenBSD/patches/3.9/common/022_route6.patch. -- Juha Saarinen * Quidquid latine dictum sit, altum videtur * www.geekzone.co.nz/juha

2 1

NZNOG 2008 - Where, When, WIC
by Donald Neal 22 Apr '07

22 Apr '07

WIC New Zealand Ltd ( http://www.wic.co.nz/ ) have stepped forward to host next year's NZNOG conference on 23-25 January 2008 in Dunedin. "I've consulted a map, and while Dunedin isn't in Auckland or Wellington, it does appear to be part of New Zealand", said Jonny Martin, chair of the organising committee. "This announcement represents an opportunity for those intending to come to next year's conference to think about arranging travel more than two or three days before the event." Look out for more information, including a Call For Presentations, by mid-May. - Donald Neal For the Organising Committee Donald Neal | Joe Abley Rules! Alcatel-Lucent | http://www.iab.org/ Support Engineer | Technology Operations | HTC, Caro Street, Hamilton +--------------------------------- 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 22 Apr '07

22 Apr '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: Route set advertised to AS9439 by Cafenet CHC - AS23754 members: 198.48.3.64/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: simon(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070402 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by Citylink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 97.64.46.0/24^24-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: simon(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070423 source: NZRR

1 0

Jabley selected as Executive Director for Internet Architecture Board.
by jamie baddeley 22 Apr '07

22 Apr '07

http://www.iab.org/ I for one, welcome our new Internet overlord. Congrats Joe. Jamie

2 1

Backlog of email to Xtra
by Glen Eustace 19 Apr '07

19 Apr '07

We currently have a growing queue of email to xtra.co.nz on all of our mail servers. According to Xtra's website, there are no issues. Is this just our problem or is this a little more of a generic problem ? We are just getting lost of "421 Message rejected (in reply to end of DATA command)" errors. Glen.

5 5

TCL -> Callplus/Slingshot issues
by Steve Biddle 18 Apr '07

18 Apr '07

All day yesterday I was unable to see any of the Callplus/Slingshot network from my TCL cable connection (obviously due to the Telecom problems). This issue was resolved last night but is now occuring again. I've given up trying to ring the TCL helpdesk (wait times listed as 90 mins despite no known network issues) so am at least hoping somebody reading this may be able to look into the issue if they're not already. All other internet sites from TCL are working fine so it appears to be some sort of routing issue somewhere..

5 4

List archives somewhere peered?
by Jonathan Brewer 17 Apr '07

17 Apr '07

Hi Folks, Does anyone keep a list archive somewhere not affected by the current outage? Cheers, Jon

2 1

Re: [nznog] Temporary IP tunnel to Digiweb
by Stephen Sheehan 17 Apr '07

17 Apr '07

Yup It all back up now, have a vodafone card in laptop as back up :-) --- Criggie <criggie(a)criggie.dyndns.org> wrote: > Try again now - should be all fixed for you. > > > > Stephen Sheehan wrote: > > The tunnel through Jasper fell through, can anyone > > else help? > > > > Thanks > > > > Stephen > > Chillisoft ltd > > > > --- Stephen Sheehan <axpunix(a)yahoo.com> wrote: > > > >> Date: Tue, 17 Apr 2007 15:03:57 -0700 (PDT) > >> From: Stephen Sheehan <axpunix(a)yahoo.com> > >> To: nznog(a)list.waikato.ac.nz > >> Subject: [nznog] Temporary IP tunnel to Digiweb > >> > >> Hi, > >> > >> Is anyone able to provide an IP tunnel to bypass > the > >> telstra clear outage, 128k will be fine. We need > >> access to our extranet based at digiweb in > >> christchurch. > >> > >> Thanks > >> > >> Stephen > >> Chillisoft Ltd > >> > >> > __________________________________________________ > >> Do You Yahoo!? > >> Tired of spam? Yahoo! Mail has the best spam > >> protection around > >> http://mail.yahoo.com > >> > >> _______________________________________________ > >> NZNOG mailing list > >> NZNOG(a)list.waikato.ac.nz > >> http://list.waikato.ac.nz/mailman/listinfo/nznog > >> > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > > -- > Criggie > > http://criggie.dyndns.org/ > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [nznog] Temporary IP tunnel to Digiweb
by Stephen Sheehan 17 Apr '07

17 Apr '07

The tunnel through Jasper fell through, can anyone else help? Thanks Stephen Chillisoft ltd --- Stephen Sheehan <axpunix(a)yahoo.com> wrote: > Date: Tue, 17 Apr 2007 15:03:57 -0700 (PDT) > From: Stephen Sheehan <axpunix(a)yahoo.com> > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Temporary IP tunnel to Digiweb > > Hi, > > Is anyone able to provide an IP tunnel to bypass the > telstra clear outage, 128k will be fine. We need > access to our extranet based at digiweb in > christchurch. > > Thanks > > Stephen > Chillisoft Ltd > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Temporary IP tunnel to Digiweb
by Stephen Sheehan 17 Apr '07

17 Apr '07

Hi, Is anyone able to provide an IP tunnel to bypass the telstra clear outage, 128k will be fine. We need access to our extranet based at digiweb in christchurch. Thanks Stephen Chillisoft Ltd __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Email to SMS gateway
by Clark Mills 16 Apr '07

16 Apr '07

Hi all. I read this on one of our internal mailing lists, thought it might be of interest / use. We use something like this for server monitoring but it's not so good if your email server / network is down, aside from the potential lagginess [SP?] that sometimes occurs with the SMS service. Still, it may have some value to you. Of course if any information below is wrong, please let me know. Cheers... Clark ================================================================================= [forwarded & edited] If you are on Vodafone, you can 'register' you phone by texting the letter R to the number 901. You should then get back a 'you are registered etc' welcome message. Once your phone is registered anyone/thing can send you a txt by using an email address such as: 6421123456(a)sms.vodafone.net.nz Where your mobile number is presumed to be 021-123456. As far as I know, there is no charge for this service.

14 17

Re: [nznog] Email to SMS gateway
by Stewart Fleming 16 Apr '07

16 Apr '07

We use the Psychic Hotline. When anything is about to go down, they give us a call and we can get it fixed before it causes a problem. -- -- Tel: 03 474 2100 Cell: 021 993 125 Web: www.wic.co.nz Co-location and Web hosting. Dunedin-wide wireless. Independent Internet Service Provider.

3 2

Re: [nznog] Email to SMS gateway
by Phill Mckenna 16 Apr '07

16 Apr '07

We use a combination of SMS messages sent via a Wavecom GSM Modem for server and network link and services monitoring, and our main alarm system connects via xml to a "datashed" gateway which gives us handset availability notification, automatic escalation and fallback to a Telecom CDMA modem for backup. In addition we send a test message once an hour to a remote site, if the message isn't heard, it triggers a timer that eventually triggers a voice dialer. Telecom paging was our previous provider, however as they keep continuing to threaten to phase this out, we moved over to SMS some time ago. Phill Mckenna Operations Technology Manager Kapiti Coast District Council Operations Centre DDI: +64 4 296 4753 Fax: +64 4 296 4733 Mobile: +64 027 555 5753 E mail: phill.mckenna(a)kapiticoast.govt.nz -----Original Message----- From: Alastair Johnson [mailto:aj(a)sneep.net] Sent: Tuesday, 17 April 2007 11:30 a.m. To: NZ Network Operators Group Subject: Re: [nznog] Email to SMS gateway Erin Salmon - Unleash wrote: > We actually use a Nokia cellphone and a data cable. I'm not aware of a > method which guarantees delivery. We are in the CBD and I note sometimes > when all those nightclubbers are frantically messaging each other messages > occasionally don't make it to the recipient. Best solution to my mind is > just to send a message periodically until a reply is sent to the system to > dismiss the notification. That is a reasonably practical solution. It has the nice side effect of ensuring that even if the message does get delivered, whoever is on call isn't ignoring it. I looked at this a while ago, and used an external mail-to-SMS provider (Bulletin Wireless) which worked fine. Obviously having an out-of-band path to them is also handy. As someone else mentioned, Telecom's analog paging service is also reliable and easy to automate. Pagers tend to work when out of cell coverage or in deep dark basements. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog ##################################################################################### This e-mail message and any attached files may contain confidential information, and may be subject to legal professional privilege. If you are not the intended recipient, please delete. Unless formally stated, this e-mail and any attachments do not necessarily reflect the views of the Kapiti Coast District Council. The Council takes extensive precautions with the aim of detecting and removing any virus or defects from its e-mail system but accepts no liability for loss or damage should this e-mail not be virus or defect free or should there be any errors in transmission. #####################################################################################

1 0

Vodafone Peering
by Philip D'Ath 16 Apr '07

16 Apr '07

Does Vodafone peer with anybody in NZ? I've been playing with an HSPDA card, and every traceroute (even to IHUG!) always go directly to the US. I would thought they would at least peer with the other two major Telco's in NZ.

4 3

Re: [nznog] Save your money and hassle
by John ＠ netTRUST 16 Apr '07

16 Apr '07

> [Reply] > > John, > > What do you use to drive it? I see the ActiveXperts software is another > US$395 .... > > Must be a simpler way. SMS link http://smslink.sourceforge.net/ Pro's works well once setup and tuned. Has support for MySQL Supports all major SMS modems though I'm unsure of the support for Nokia or any cellphone. Con's - slow to process send / receive (as is most software because the msgs get stored on the SIM card first) Good for low traffic, unsuited to bulk send/receive. Note to the person suggesting using a cellphone. SMS modems use a pretty standardised AT command set and you talk to them just like you would to a modem. Cellphones AFAIK usually have proprietory interfaces.

2 1

Save your money and hassle
by John ＠ netTRUST 16 Apr '07

16 Apr '07

We exclusively use SMS modems here. The Wavecom is the best you can buy and only slightly dearer then the cheaper models. http://www.itx.co.nz/index.php?cPath=29 is a company I've dealt with before and they are allright.

4 4

Re: [nznog] Email to SMS gateway
by Philip D'Ath 16 Apr '07

16 Apr '07

Actually, SMS does offer "guaranteed" delivery. It doesn't matter if the phone is off, an error occurs in communication, a data circuit goes down ... However there are limits. If the message cannot be delivered (such as end device failure) then you can request a receipt to get notification of this. I don't recall ever noticing a lag of hours for SMS delivery (I don't ever recall a TXT taking more than 60s to be delivered) but I guess different TXT processing systems use different methods for getting the TXT into the network for delivery. -----Original Message----- From: Jasper Bryant-Greene [mailto:j(a)digiweb.net.nz] Sent: Tuesday, 17 April 2007 11:15 a.m. To: Philip D'Ath Cc: Samuel Collinson; Dan Clark; NZ Network Operators Group Subject: Re: [nznog] Email to SMS gateway On this - we have found SMS to be a bit unreliable lately, with messages being delivered hours late or not at all. I am aware that SMS does not provide "guaranteed delivery" - what methods are others on this list using to send alerts reliably? Cheers Jasper

4 3

Affordable Voltage Monitoring over Ethernet?
by Dan Clark 16 Apr '07

16 Apr '07

Gidday, Just wondering if any network operators etc here are using or have seen any kind of device that can measure voltage/current out there somewhere on a network and we can interrogate it remotely and may even send alerts etc if drops below threshold etc? Would have to be resonably affordable, and in simple kit form or off the shelf. If nothing available that anyone can think of I may develop something along these lines, cheap, simple, ethernet, and probably 12V Open for discussion if anyone remotely interested. Regards Dan

5 4

MP3 streaming data usage
by John ＠ netTRUST 15 Apr '07

15 Apr '07

Anyone have any idea how much data would be consumed each day streaming MP3 at 128kbps audio stream rate? Thanks.

11 14

Re: [nznog] MP3 streaming data usage
by Richard Naylor 15 Apr '07

15 Apr '07

At 03:38 p.m. 16/04/2007 +1200, Neil Gardner wrote: >Ergh... Hate to say this, but don't you have that 10 bits to the byte >thing approximately ass-backwards? No. As I said, I come from an Ancient World (TM), where we debugged protocols like DDCMP with a Tek Logic Analayser, scope or logic probe. None of this Ethereal stuff, ethernet hadn't escaped from PARC and Vint was still drawing on envelopes. RS-232 was modern, current loop was till very active (sorry, no pun intended). (Probably Michael Newberry is the only one who will get it anyway, Andy and Sid say they're too young, and the others are looking blank) Each Byte is (or was) a START bit, 8 data bits, PARITY and a STOP or IDLE bit. So we always approximated it to 10 bits. (different devices handle parity bits different ways, it used to be that if there was no parity, no bit was used. LSI USARTS started the trend towards always having a bit used. This is a world where a serial port took up a whole UNIBUS slot (ie a card 400mm by 200mm). As I said, its an approximation for budgeting purposes and comes from an ancient era. Have you found the beer yet ? R

2 1

Re: [nznog] Affordable Voltage Monitoring over Ethernet?
by Richard Naylor 15 Apr '07

15 Apr '07

At 04:10 p.m. 16/04/2007 +1200, Dan Clark wrote: >Gidday, > Just wondering if any network operators etc here are using or have seen > any kind of device that can measure voltage/current out there somewhere > on a network and we can interrogate it remotely and may even send alerts > etc if drops below threshold etc? >Would have to be resonably affordable, and in simple kit form or off the >shelf. > >If nothing available that anyone can think of I may develop something >along these lines, cheap, simple, ethernet, and probably 12V >Open for discussion if anyone remotely interested. google for a Link-10 or Link-20, I think they now do ethernet, it used to be serial, but you just chucked in a Lantronix thingy

1 0

Re: [nznog] MP3 streaming data usage
by Richard Naylor 15 Apr '07

15 Apr '07

At 02:49 p.m. 16/04/2007 +1200, Neil Gardner wrote: >Dammit - I know we've been asked to stop this, but now something >interesting has happened... you found the beer ? >Richard, you, who I know has great experience in this, have posted >figures that are UNDER my very basic but probably right theoretical >minimums > >How do you fit 3600 seconds at 128kbps into 46MB ? I get 56.25MB... I have this ancient spreadsheet with a few assumptions.... I basically round 10bits to the byte to cover overheads in the packet, etc. So a data rate of say 128kbps is 12.8KB per sec or 0.13Mbps 768KB per minute or 7.68Mbps 46080 KB per hour or 460.9 Mbps or 46.08 MBytes per hour Remembering that you will get silence and various other things (outages, etc) it will always be an approximation. It just gives you a feel for the order of magnitude of the bill :-) Most stations actually have a second stream in reserve for special "promotional" occassions and they kick them into life every now and then, just to muck up the stats. The biggest use of it has been to work out that a 10GB plan is OK for radio stations at 32Kbps streams. Now that 40+GB plans are out, folks are looking at webcams again and it looks like we can stream a camera and stay inside a 40GB plan at 128k video, which isn't too bad looking. I should probably rework the spreadsheet for HD streams at 10Mbps. It looks like 5TB a month. And yes, IPV6 and multicast will solve all our problems, including world hunger and the endless shortage of beer. But I'm showing my age......

2 1

Re: [nznog] IPv6 Incentive
by Scott Weeks 14 Apr '07

14 Apr '07

--- andy(a)nosignal.org wrote:---------------- ip is a means to an end, I don't craft packets for fun, I do work or have fun, and ip occurs as a way to send my messages from A to B. --------------------------------------------- ding, ding, ding! From the many lists discussing these issues recently, we finally have a winner! Most folk don't care about v4, v6, v8 or v<insert stuff here>. They want to do something and they 'just want it to work'. 99.999% couldn't give less than a crap how that happens. scott BTW 6,525,170,264 x .00001 = 65250 That's this: World — Population: 6,525,170,264 (July 2006 est.) https://www.cia.gov/cia/publications/factbook/print/xx.html times one minus five nines 65250 is about how many of there are who do give more than a crap about how that happens. Beer...MMMM... 8-)

12 14

[Fwd: Re: IPv6 Incentive]
by Gerard Creamer 12 Apr '07

12 Apr '07

On 13/04/2007 4:24 p.m., Craig Whitmore wrote: >> I'm not a porn fan myself, but from other types of media, 10G isn't that >> much. >> Maybe if they put 1TB of porn and 1TB of free tv content from a major >> studio, then we'd have an experiment. >> Would it be better to be Geek TV (Dr Who, Firefly, etc) or Jo Public TV (Lost, Grey's Anatomy, all 500 seasons of Coro St etc)? I think Geek TV would get more drive for it. Like it would happen though. >> > > There is some content at http://www.ipv6porn.co.nz. (If you have IPv6) Looking at http://www.v6.co.nz/ on the 'Who Provides IPv6' there's nothing - is there an NZ provider of IPv6? I know this topic has come up on the list before, and it usually degrades in circular discussions - it would be nice to hear 'Yes, ISP X offers IP6 within NZ'. Without anyone spieling on about the glories of their own wares, of course :^) Gerard

2 1

New Sepctrum Auction
by Paul Horak 12 Apr '07

12 Apr '07

Plans for auctioning the 2.3Ghz band for BWA/WiMAX have been published: http://www.rsm.govt.nz/auctions/auction09/index.html I think there is a real opportunity here for some of us to get access to spectrum. At present the lions share (or possibly all of it) will go to two or three companies to build a nationwide network. There is also a proposal to allocate some spectrum for regional operators under a "Managed Park". I suspect there are quite a few people interested in this who have not yet been in contact with RSM - it is essential that you let RSM know your interest and you respond to this consultation document. If the vast majority of comments come from the large providers wishing to deploy nationwide networks then I suspect there will be little or no regional spectrum available. I would also be grateful if you can contact me off list if you have an interest in obtaining spectrum for regional use. I have some ideas that might help our cause that I would like to share. Cheers, Paul NetSmart Ltd http://www.netsmart.co.nz/, Level 2, Regency House, 1 Elizabeth Street, P O Box 15020, Tauranga, New Zealand Tel: 07 5711367 Fax: 07 5711372

2 1

Re: [nznog] IPv6 Incentive
by Scott Weeks 11 Apr '07

11 Apr '07

--- steve(a)focb.co.nz wrote: Scott Weeks wrote: > > --- andy(a)nosignal.org wrote:---------------- > ip is a means to an end, I don't craft packets for fun, I do work or > have fun, and ip occurs as a way to send my messages from A to B. > --------------------------------------------- > > ding, ding, ding! From the many lists discussing these issues > recently, we finally have a winner! Most folk don't care about > v4, v6, v8 or v<insert stuff here>. They want to do something > and they 'just want it to work'. 99.999% couldn't give less > than a crap how that happens. : or are you saying that there are only 65,250 clueful IP/IT : engineers in the world or people working in related fields ? This one. Clueful IP engineers in the world that also care about the version of IP used more than leaving a crap. :-) : Feel like citing references for your 99.999% figure ? It was just for fun and to make the point that most people in the world just don't care how stuff moves around the internet. They just want it to get to where they tell it to go. The five nines comes from many marketing-speak droids when telling everyone that their network has 5-nines of uptime. Of course with no more details than just that... <8-0 <== that's a crazy-eyed marketing droid babbling marketing-speak. scott

1 0

Some graphs of .nz domain statistics
by Blair Harrison 10 Apr '07

10 Apr '07

Hi Guys, I took some of the data provided from the DNC website here: http://dnc.org.nz/story/30221-51-1.html and turned it into some graphs. You can check this out in either HTML or XLS format at my website: http://jedi.school.nz/nzdg.html Hope this is interesting viewing for someone :) Cheers, Blair

1 0

IPv6 Incentive
by Andrew Ruthven 10 Apr '07

10 Apr '07

Hey, During the NZNOG conference it was joked that if the next WoW pack required IPv6 then IPv6 would be rolled out by the ISPs (and transit providers) for the next morning. See the attached mail for an experiment that might be cause it to be rolled out for that evening... Cheers! -- Andrew Ruthven, Wellington, New Zealand At home: andrew(a)etc.gen.nz | This space intentionally | left blank.

15 20