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."
------------------------------------------------------------------------------
The New Zealand Network Operators' Group
The New Zealand Network Operators' Group (NZNOG) has no king, president
or formal membership. It consists of the subscribers to this mailing
list. The group is intended to facilitate discussion among operators of
networks in New Zealand on matters relevant to network operators, as
described in the list's Acceptable Use Policy, which appears later in
this posting.
Conference
We are working towards our next annual conference, to be held early in
2007.
Other Meetings
See http://auckland.thursdaynightcurry.com/ or
http://wellington.thursdaynightcurry.com/ if you live in or near
Auckland or Wellington.
Operators' Contact List
See http://www.usenet.net.nz/noc/ for operational contact details
for most New Zealand ISP's. These are intended for use by other
network operators, not by most customers.
Internet Exchanges
See http://www.nzix.net/ for details of exchanges in operation, and some
information on others under construction.
About This Mailing List
This list has around 900 addresses subscribed. You may only post to the
list from a subscribed address. A number of people subscribe addresses
which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink
and Telecom. None of these organisations, nor any administrator, is
responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at
http://list.waikato.ac.nz/pipermail/nznog/
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
With site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
Dear Colleague,
This is to notify you that some object(s) in NZRR database
which you either maintain or are listed as to-be-notified have
been added, deleted or changed.
These objects are used to configure the various NZIX route
servers (http://nzix.net/) so you can expect the relevant
servers to be reloaded in the near future. The reloading
of the servers is staggered over a period of time so that
if you are peering with both servers at an exchange, you
can maintain at least one BGP session at all times and
consequently a full set of routes.
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9872
descr: advertised to AS9560 by Actrix Networks - AS9872
members: 202.154.128.0/19^19-29,
203.96.16.0/20^20-29,
203.96.48.0/20^20-29,
202.36.204.0/23^23-29,
192.100.53.0/24^24-29,
202.49.158.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)actrix.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20051114
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9872
descr: advertised to AS9560 by Actrix Networks - AS9872
members: 202.154.128.0/19^19-29,
203.96.16.0/20^20-29,
203.96.48.0/20^20-29,
203.96.128.0/20^20-29,
202.49.152.0/21^21-29,
202.36.204.0/23^23-29,
192.100.53.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)actrix.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060629
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: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
202.50.200.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.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.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.36.226.0/24^24-29,
202.46.190.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060525
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
202.46.176.0/21^21-29,
202.50.200.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.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.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.36.226.0/24^24-29,
202.46.190.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060629
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.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
202.50.200.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.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.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.36.226.0/24^24-29,
202.46.190.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060523
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
202.53.176.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
202.46.176.0/21^21-29,
202.50.200.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.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.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.36.226.0/24^24-29,
202.46.190.0/24^24-29,
202.50.247.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060629
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:AS9872
descr: advertised to AS9439 by Actrix Networks - AS9872
members: 202.154.128.0/19^19-29,
203.96.16.0/20^20-29,
203.96.48.0/20^20-29,
202.36.204.0/23^23-29,
192.100.53.0/24^24-29,
202.49.158.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)actrix.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20051031
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9872
descr: advertised to AS9439 by Actrix Networks - AS9872
members: 202.154.128.0/19^19-29,
203.96.16.0/20^20-29,
203.96.48.0/20^20-29,
203.96.128.0/20^20-29,
202.49.152.0/21^21-29,
202.36.204.0/23^23-29,
192.100.53.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)actrix.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060629
source: NZRR
---
PREVIOUS OBJECT:
route: 202.49.152.0/21
descr: Route for Actrix - AS9872
origin: AS9872
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: mikej(a)connections.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20040809
source: NZRR
REPLACED BY:
route: 202.49.152.0/21
descr: Route for Actrix Networks - AS9872
origin: AS9872
notify: rpsl-admin(a)nzix.net
notify: noc(a)actrix.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060629
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: 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.175.128.0/21^21-29,
202.14.20.0/22^22-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.14.82.0/23^23-29,
202.36.68.0/23^23-29,
202.36.198.0/23^23-29,
202.135.48.0/23^23-29,
203.163.70.0/23^23-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.84.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.76.0/24^24-29,
202.27.140.0/24^24-29,
202.27.160.0/24^24-29,
202.27.250.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.36.233.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,
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: david.lister(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060606
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,
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
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.175.128.0/21^21-29,
202.14.20.0/22^22-29,
202.36.192.0/22^22-29,
152.158.254.0/23^23-29,
202.14.82.0/23^23-29,
202.36.68.0/23^23-29,
202.36.198.0/23^23-29,
202.135.48.0/23^23-29,
203.163.70.0/23^23-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.84.0/24^24-29,
202.14.252.0/24^24-29,
202.21.128.0/24^24-29,
202.27.76.0/24^24-29,
202.27.140.0/24^24-29,
202.27.160.0/24^24-29,
202.27.250.0/24^24-29,
202.36.29.0/24^24-29,
202.36.80.0/24^24-29,
202.36.233.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,
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: david.lister(a)ap.att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060606
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,
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
Hi there - we've recentely put a fairly simple broadband speedtest
online at http://www.consumerspeedtest.org.nz
<http://www.consumerspeedtest.org.nz/> (hosted on a VPS on
www.openhost.co.nz <outbind://2/www.openhost.co.nz> which uses
www.maxnet.co.nz <outbind://2/www.maxnet.co.nz> as their ISP in case
you're interested)
Along with the the provider, plan, download and upload speeds we're also
recording the users IP address - I'm wondering if it's possible to work
out what city / region the user is from based on their IP?
Cheers
Steve
