The New Zealand Network Operators' Group
The New Zealand Network Operators' Group (NZNOG) has no king,
president or formal membership. At present it consists of the
subscribers to this mailing list, which anyone is free to join.
Meetings
Our next annual conference is to be hosted by the WAND group in Hamilton
on February 2nd to 4th, 2005. See http://www.nznog.org/ for more
information, including the Call For Presentations. Offers to present are
due in by 22nd October, and all presenters
should have had their acceptance confirmed by 31st October.
Also see http://auckland.thursdaynightcurry.com/ if you live in or near
Auckland or Wellington.
Operators' Contact List
See http://www.usenet.net.nz/noc/ for operational contact details
for most New Zealand ISP's. These are intended for use by other
network operators, not by most customers.
Internet Exchanges
See http://www.ape.net.nz/ for details of the Auckland Peering
Exchange and those connected there. See http://www.wix.net.nz/ for the
Wellington Internet Exchange.
About This Mailing List
This list has slightly over 700 addresses subscribed. You may only post
to the list from a subscribed address. A number of people subscribe
addresses which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink
and Telecom. None of these organisations, nor any administrator, is
responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at
http://list.waikato.ac.nz/pipermail/nznog/
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with
site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
Donald Neal |Palmersdale: Are you in charge here?
Technical Specialist |The Doctor: No, but I'm full of
Operations Engineering | ideas.
Integration & Services Division +-----------------------
Alcatel NZ Ltd - Telecom's network operations manager
------------------------------------------------------------------------------
"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."
------------------------------------------------------------------------------
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.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050830
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.59.4.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050901
source: NZRR
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050830
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.59.4.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050901
source: NZRR
In case some of you don't get this.
>From: "Colin Jackson" <president(a)internetnz.net.nz>
>To: "INZ Members Announce" <members-announce(a)internetnz.net.nz>
>Date: Tue, 30 Aug 2005 14:54:33 +1200
>
>InternetNZ ICT Leaders Election Forum 2005
>
>This Thursday evening InternetNZ is convening an Election Forum, for
>political parties to present and defend their policies relating to
>information and communications technology policy.
>
>David Cunliffe MP (Labour Party), Maurice Williamson MP (National Party)
>and Mikaere Curtis (Green Party) will face questions from a panel of
>journalists (Paul Brislen, IDG / Computerworld; and Kate McLaughlin,
>National Business Review) on where they see the future of this industry,
>where they want to take it, and why.
>
>Date: Thursday 1 September 2005
>
>Time: 7.00pm - 9.00pm
>
>Physical Venues: University of Auckland - Access Grid Suite (Main Venue)
>and Wellington - Media Lab Conference Room, L2, 205-207 Victoria St.
>
>Webcast/Chatlink : Link page will be available at 6pm this afternoon at
>www.internetnz.net.nz/forum, with links to actual webcast and chat posted
>on Thursday.
>
>Moderated by barrister Peter Dengate Thrush, the debate will commence with
>an hour-long session where the speakers respond to pre-prepared questions
>covering the wide range of issues relating to ICT and telecommunications
>policy.
>
>In the second hour with the politicians will take questions from the
>audience, channelled through the journalist panel, and live questions from
>the Wellington audience. Online participants will be able to participate
>in the debate through submitting questions via a web based chat channel.
>
>Communications between Auckland and Wellington will be by means of an
>Access Grid. The Access Grid technology provides realtime audio and video
>links between the two sites, making it an effective way to let audiences
>in different geographic locations interact in real time.
>
>The only attendees in the Auckland venue will be the Moderator, the
>journalists, and of course, the politicians. Outside the room will be the
>technical providers, the feedback co-ordinators and the politicians
>advisory teams. There will not be any general audience at this venue.
>
>There is a limited amount of space in the physical venue in Wellington for
>InternetNZ members to attend the event. Obviously we want to have a
>capacity audience at the venue. If you would like to attend, please advise
>office(a)Internetnz.net.nz as soon as possible. Physical attendance will be
>allocated on a first-come, first-served basis. For members outside of
>Wellington, we would value your on-line attendance and questions.
>
>This InternetNZ Election Forum provides a unique opportunity for you to
>put questions to the politicians who will be making critical decisions
>about the future regulatory environment for communications and information
>technology in New Zealand. We welcome your involvement. We feel that this
>"proof of concept" of the technologies may lead to a whole new method of
>engagement in political discussions for special interest groups wishing to
>engage in detailed debates in specialised areas of policy. Please help us
>make this event a success.
>
>Colin Jackson
>President - InternetNZ
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
These objects are used to configure the various NZIX route
servers (http://nzix.net/) so you can expect the relevant
servers to be reloaded in the near future. The reloading
of the servers is staggered over a period of time so that
if you are peering with both servers at an exchange, you
can maintain at least one BGP session at all times and
consequently a full set of routes.
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.0/23^23-29,
192.88.85.0/24^24-29,
192.133.31.0/24^24-29,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050526
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050830
source: NZRR
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.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.0/23^23-29,
192.88.85.0/24^24-29,
192.133.31.0/24^24-29,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050526
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.50.200.0/21^21-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.37.86.0/23^23-29,
202.49.80.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,
202.27.208.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.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 20050830
source: NZRR
Upcoming Webcast on www.R2.co.nz
This is a premature warning of what could be a webcast of interest to
Network Operators. The organiser will hopefully announce it very soon (was
due out by now <sigh>).
The event is 7pm to 9pm on Thursday 1 September 2005 and will be carried by
R2 using anycast routing. This means that ISPs not peering at APE, WIX or
PNIX will receive the traffic from our US server. If you require assistance
with peering, please contact Andy Linton at CityLink.
The event will be webcast in video at our usual bit rates of 56kbps,
128kbps and 384kbps, and audio at 28kbps and 56kbps. There will be a
separate stream at 2Mbps, for those who would like to experience near
standard definition video. A recent webcast had 25% of viewers watching the
2Mbps stream, so ISPs may experience an increase of traffic. (that was out
of 100 viewers)
Help Desks should also be advised that this event is happening, as there
may be an increase of requests for assistance.
This will be an interactive webcast, as will become apparent, when it
finally gets properly announced. As well as links to client mediaplayers,
the event will use a custom web page with embedded player and the
interactive stuff.
Thanks for your co-operation.
Rich
(wearing my R2 hat)
Has anyone else seen any other phishing attempts on Trade Me before? Are
there many of these coming through at the moment??
Cheers,
Paul.
----------
*From:* mailer@trademe.co.nz[SMTP:MAILER@TRADEME.CO.NZ]
*Sent:* Friday, August 26, 2005 11:24:06 AM
*To:* Help Desk
*Subject:* Your Trade Me Bid was Cancelled !!!
*Auto forwarded by a Rule*
**
**
* Dear Customer,*
**
*The bid that has been entered in error was cancelled, **Click Here
*<http://004c256.netsolhost.com/>
* to view the reason provided for the cancellation.*
**
*Happy Trading!
Trade Me Customer Support Team
**http://www.trademe.co.nz* <http://www.trademe.co.nz/>
To quickly answer all the replies I have gotten about summarizing the
replies. I'll post general colo costs in the same fashion paul vixie
has done his personal colo registry on www.vix.com
I will say right off the top, my requirements are much much more than
those of someone who is colocating 1 - 2 servers.
Also, I need a contact number for iconz, as the 0800 freefone doesn't
work internationally, reply off list would be great.
And just to stay on topic . beer