- NZNOG - lists.nznog.org

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

07 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050729 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.173.63.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050808 source: NZRR

1 0

Are Telecom Micro Outages still an issue?
by Gary T. Benner 07 Aug '05

07 Aug '05

HI all, Have been racking my brains trying to solve a problem, and I suddenly remembered an issue that Telecom had regarding "micro-outages". Does this problem still exist? Our problem comes up with a customer using chat rooms in the Moodle Learning Management System, for students in remote locations. The chat room relies upon a persistent socket connection for the duration of the "chat". Perhaps for 30+ mins or so at a time. However students and teachers are regularly dropped. The Chat daemon is basically a socket server, and the only way I can see this happening is if the socket connection is broken. We do not see this effect in LAN trials. kind regards Gary Benner Ref#: 41006

2 1

RE: [nznog] Are Telecom Micro Outages still an issue?
by Regan Murphy 07 Aug '05

07 Aug '05

I'd suggest looking at your firewall. Many firewalls have a configurable timeout for connections. The Sonicwall firewalls for example have a default "Inactivity Timeout in Minutes" of 5 minutes but it is configurable per port/protocol. -- Regan ________________________________ From: Gary T. Benner [mailto:gary(a)123.co.nz] Sent: Monday, 8 August 2005 12:19 p.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] Are Telecom Micro Outages still an issue? HI all, Have been racking my brains trying to solve a problem, and I suddenly remembered an issue that Telecom had regarding "micro-outages". Does this problem still exist? Our problem comes up with a customer using chat rooms in the Moodle Learning Management System, for students in remote locations. The chat room relies upon a persistent socket connection for the duration of the "chat". Perhaps for 30+ mins or so at a time. However students and teachers are regularly dropped. The Chat daemon is basically a socket server, and the only way I can see this happening is if the socket connection is broken. We do not see this effect in LAN trials. kind regards Gary Benner

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Aug '05

04 Aug '05

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Aug '05

02 Aug '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS18378 as-name: NZRR-AS18378 descr: NIWA descr: WIX peering at '202.7.0.135' descr: see Citylink RT job #2953 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS18378 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: c.edsall(a)niwa.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050803 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS18378 descr: Route set advertised to AS9439 by NIWA - AS18378 members: 202.36.29.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: c.edsall(a)niwa.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050803 source: NZRR

1 0

RIPE NCC to begin allocating from new IPv4 range
by leo vegoda 01 Aug '05

01 Aug '05

Dear Colleagues, This announcement is being sent to multiple lists. I apologise for duplicates. The RIPE NCC received the IPv4 address range 89.0.0.0 - 91.255.255.255 (89.0.0.0/8 and 90.0.0.0/7) from the IANA in June 2005. We expect to start making allocations from this range in the near future. We have started announcing two prefixes from each /8, which originate in AS12654. They are: 89.192.0.0/16 89.255.248.0/21 90.192.0.0/16 90.255.248.0/21 91.192.0.0/16 91.255.248.0/21 Details of target names and addresses, reachability tools and other information are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html You may want to update any filters you have in place. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

APNIC20 - IPv6 workshop and Pre-meeting routing workshop
by Miwa Fujii 01 Aug '05

01 Aug '05

Hi All, Apologies for duplicate copies. Dear APNIC members and friends, There are only six weeks to go before APNIC 20 commences in Hanoi, Vietnam. In this announcement: --------------------- 1. IPv6 workshop 2. Pre-conference routing workshop 3. Early bird registration extended 1. IPv6 workshop ---------------- Places are still available for the full day IPv6 workshop run by Jordi Palet (Consulintel). Date: Tuesday 6 September 2005 Participants will have hands-on experience of installing IPv6 on different platforms, basic stateless/statefull configuration, transition mechanisms, and more. More details are available at: http://www.apnic.net/meetings/20/programme/ipv6-ws.html 2. Pre-conference routing workshop ---------------------------------- We are pleased to announce the following pre-conference technical workshop, added to the programme since the last meeting announcement was sent: Six-day routing workshop run by Philip Smith (Cisco) and Amante Alvaran (APNIC) Date: Tuesday 30 August - Monday 5 September 2005 (no sessions on the national holiday, Friday 2 September) This workshop will cover basic aspects of OSPF and BGP and also provide hands-on router configuration workshop. More details are available at: http://www.apnic.net/meetings/20/programme/routing-ws.html 3. Early bird registration extended ----------------------------------- Early bird registration has been extended to Friday 5 August 2005. If you have not yet registered please do so quickly to take advantage of the significant saving. The online registration form is available at: http://www.apnic.net/cgi-bin/registration.pl?event_id=73 Terms and conditions of registration are available at: http://www.apnic.net/meetings/20/rego/conditions.html If you have any questions or suggestions about APNIC 20, please email us at <meetings(a)apnic.net> We look forward to seeing you in Hanoi. Best regards, ______________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 ---------------------------------------------------------------------- See you at APNIC 20! Hanoi, Vietnam, 6-9 September 2005 www.apnic.net/meetings ______________________________________________________________________

1 0

Congratulations
by Matthew Poole 31 Jul '05

31 Jul '05

to Mark, who's been a father for nearly 24 hours now. Which Mark? I'll leave that as an exercise for you, dear reader :P -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS7657 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink descr: SMARTLINX3 peering at '218.100.26.3' descr: see Citylink RT job #1927 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050331 source: NZRR REPLACED BY: aut-num: AS23754 as-name: NZRR-AS23754 descr: CityLink admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23754 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23754 import: from AS24385 accept ANY AND NOT fltr-bogons export: to AS24385 announce AS23754 import: from AS7657 accept {0.0.0.0/0} export: to AS24385 announce AS23754 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

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

31 Jul '05

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 Jul '05

31 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 198.32.71.0/24^24-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050801 source: NZRR

1 0

NASA TV Query...
by Clint Jeffrey 30 Jul '05

30 Jul '05

Thanks to all whom responded.Wally has been in contact.. Ta Thanks. Clint - VK3CSJ.

1 0

NASA TV Feed on OPTUS B1...query
by Clint Jeffrey 29 Jul '05

29 Jul '05

Hello to anyone that maybe still using this forum.I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

2 1

RE: [nznog] NASA TV Feed on OPTUS B1...query
by Jeremy Strachan 29 Jul '05

29 Jul '05

Done. ________________________________ From: Clint Jeffrey [mailto:vk3csj(a)netspace.net.au] Sent: Saturday, 30 July 2005 8:51 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NASA TV Feed on OPTUS B1...query Hello to anyone that maybe still using this forum...I'm trying to get in contact with Wally ZL1VWM about the question below:- Hi Wally I saw your call sign on the LygnSat site in regards to "NASA TV", for a long time now I have wished for the powers that be to place a feed on one of our Optus Satellites, in fact I'd even take a subscription to Foxtel if they'd organized a feed for NASA TV. So far nothing has come through, as member of "The Planetary Society" I have even emailed messages requesting someone to organize a NASA TV feed here in Australia. I've just discovered that Optus B1 has a feed albeit on New Zealand, I'm wondering if you would know if I can see this feed here in Melbourne? Currently I have a 90cm dish on a small motor control using a Humax 5400 receiver, I tried a quick look for Optus B1 the other night with out any luck though. Also I see the feed seems to be off the internet rather than any actual feed from a live NASA source so to speak, is that true? If so how good a quality are the images, at least what I'm try to say, it that I currently look at NASA TV off the internet, it's pretty horrible to say the least, picture keeps updating and then digitizes and then comes good for a few seconds and goes all horrible again, I have ADSL at 512 download, it's probably my computer that needs the upgrading, but if there is finally a feed off a Satellite visible in our own sky then bloody fantastic!....I'll go for that! Any thoughts on this Wally. Many Thanks Clint Jeffrey - VK3CSJ P.S I'm on my work computer at present, if you can, you can also reply to my home email address which is vk3csj(a)netspace.net.au

1 0

Anti Spam Legislation vs Spam realities and ISP staffing
by Mark Foster 29 Jul '05

29 Jul '05

http://www.nzherald.co.nz/index.cfm?c_id=5&ObjectID=10338203 My review of this article noted this paragraph: --8<-- Internet users will complain in the first instance to their internet provider about spam email, and the Department of Internal Affairs will act as an internet watchdog if the matter is taken further. --8<-- Now did I get the wrong end of the stick here, or is this saying that the onus of the ISP that provides connectivity to the Spam Receiver to act on complaints - or the DIA will be hounding them? Shouldn't the source ISP, and not the destination, be the people responsible for dealing with their own spam sources? I wrote a bit of a commentary of my own: http://www.blakjak.net/node/view/261 However wonder if this has come to the attention of anyone else yet... The first thing that jumps into my head is that ISPs are going to wind up having to do all the investigative legwork on the complaints they receive - and not many ISPS I know of are staffed to support this. Antispam costs for all providers going up - and probably going up in relation to the size of their customer base. Hmmm.... Mark.

3 3

RE: [nznog] Multi-point VPN around NZ to a central location ( Wellington)
by Kerry Milestone 28 Jul '05

28 Jul '05

Mmmmm....... Chrome bits...... Yes. Realistically though... Nissan350z. ________________________________ From: Drew Broadley [mailto:drew(a)corrupt.co.nz] Sent: Friday, 29 July 2005 2:19 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Multi-point VPN around NZ to a central location ( Wellington) Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

2 1

Multi-point VPN around NZ to a central location (Wellington)
by Drew Broadley 28 Jul '05

28 Jul '05

Hi all, I'm representing a company where the requirements are going to need a large amount of nodes around the country where they will all require (at least) a dedicated 128kbps connection to a central "nerve" located on WIX and additional redundancy on the central system at another location, ultimately somewhere on the APE. We would ideally not approach Telecom directly at the moment through a buzz-word junkie sales person at the moment as I want a realistic perspective on this, not someone who will just say yes so they can afford to chrome more parts on their Audi. If you have any available options, could you please contact me off list. Cheers, Drew

1 0

Reminder Notice: ENUM Consultation extended until 19th August
by Michael Sutton 28 Jul '05

28 Jul '05

ENUM ANNOUNCEMENT: Those interested are reminded, that InternetNZ is receiving feed back & submissions on the "New Zealand ENUM Trial Framework - Consultation Report" by M-co for InternetNZ: The Report is available on the web site at http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf (1.2MB) Originally we had advised 21 July, however there is now additional time available in our schedule. Best Regards Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chair - Enum Task Force InternetNZ Project Manager - UCI PUA Enum Prototype Member Audit & Technical Committee Telephone: +64 4 475 9235 Mobile: +64 21 305500 Facsimile: +64 21 305002 WWW: http://www.internetnz.net.nz/public/enum/ E-mail: mailto:michael.sutton(a)awacs.co.nz mailto:michael.sutton(a)internetnz.net.nz> ----------------------------------------------------------------------- CAUTION: This email and any attachments may contain information that is confidential and subject to legal privilege. If you are not the intended recipient, you must not read, use, disseminate,distribute or copy this email or any attachments. DISCLAIMER: To the maximum extent permitted by law, Michael Sutton is not liable (including in respect of negligence) for viruses or other defects or for the changes made to this email or to any attachments. Before opening or using attachments, check them for viruses and other defects. -----------------------------------------------------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Jul '05

28 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050729 source: NZRR

1 0

RE: [nznog] [FW] Re: Interesting articles from Beehive
by Jeremy Strachan 28 Jul '05

28 Jul '05

We'd like an increase from 128K to a whole 256K! Greedy I know ... But 128K is horribly limited for any remote users trying to access a site over a vpn, webmail, you name it. Things we do in the modern age. Jeremy -----Original Message----- From: Blair Harrison [mailto:nznog(a)jedi.school.nz] Sent: Thursday, 28 July 2005 9:09 p.m. To: Richard Dingwall Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] [FW] Re: Interesting articles from Beehive Richard Dingwall wrote: > > I would imagine that the low upstream limit could (partly) have been > an effort to curb NZ P2P network traffic. > > National P2P networks (DC, particularly) became very popular a few > years ago, when unlimited 128KBit/128KBit DSL was available (i.e, > download as fast as your connection goes - woohoo!). > > More recently, as the downstream rate has significantly exceeded the > upstream, your slow upload becomes someone else's slow download. > Imagine the thrill of leeching at 16KByte/s on a 2MBit connection..! > > - Richard > Quite a possibility. I did have one of our high speed customers leave Kazaa on over a few days.. managed to eat up about 75GB of traffic in those couple of days. They were uploading at a rate of about 1.8 gig an hour. I can see the merits of limiting upstream speed in the interests of conserving network capacity, but I don't see why regular non-p2p-using customers should be held back from experiencing true broadband speeds because of the actions of the leechers out there. There are methods available to limit the impact of such P2P applications and I believe at least one large ISP in NZ has implemented a layer 7 filtering system that can limit speeds at the application level. So the technology to limit the impact of P2P users to the network is available, should Telecom choose to use it. Why slow down the rest of the users who want to do really cool things like full screen multi-user videoconferencing and sending media files across town for processing because of the actions of the pesky leechers? Maybe because that would start to eat into their other more traditional 'higher value' revenue streams such as Frame Relay, Metro Ethernet and ATM? (which, incidentally, I can't even find on their website today) P2P may be a big reason and the most obvious, but I doubt it's the only reason. Cheers, Blair _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

NZ General Election - On The Night Results
by Andrew McMillan 28 Jul '05

28 Jul '05

Hi, As you will know by now this years general election will be on the 17th of September. The Chief Electoral Office have contracted Catalyst IT Ltd to host a public website with the election-night results, as we have done for the previous two elections. Counting of votes will begin when the polls close at 7:00pm, and will continue through to the small hours of the morning of the 18th. Historically, peak interest has been from around 8:30pm through to 10:30pm. If any ISPs or other websites would like to mirror this information for your own customers I will be happy to arrange rsync access to the changing website. In addition to the HTML formatted web pages there are a series of data files which are intended for post-processing and a specification of these data formats is available. Updates to the website are applied approximately every minute during the counting process. Please contact me off list if you are interested in any of this. Thanks, Andrew McMillan. ------------------------------------------------------------------------- Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Planning an election? Call us! -------------------------------------------------------------------------

1 0

Webcasting Heads up
by Richard Naylor 27 Jul '05

27 Jul '05

Tomorrow Internet NZ is having their AGM and using 2 Access Grid nodes to link participants in AKL and WLG. Its at 6pm from memory. I think I've managed enough parts to make another Access Grid node and so am going to attempt to webcast a grid session in action, using multiple simultaneous webcast streams . It may fail horribly. I will drink beer whatever happens (got back on topic). The link to the webcast is http://www.r2.co.nz/20050523 There is TV playing on the streams now if you want to see what it may look like, if it all works. Operators may get calls from clients requesting help. May see a bit of traffic (its about a meg per client) or may just like to watch and laugh as it all crashes. Drink beer, it all looks better then. Feedback will be appreciated. Anyone still got dial-up and willing to try it ? Rich

1 0

[FW] Re: Interesting articles from Beehive
by Juha Saarinen 27 Jul '05

27 Jul '05

---------------------------------------------------------------------------- Paul Brislen wrote: > I'm sorry but has the Minister read his own Commissioner's rulings? > > snip: > I am aware of an very strong opinion in the industry that 128k upstream is > a constraint. Like the Commissioner I do not regard the proposed regulated > 128k service as an upper limit. On the contrary, it should be seen as a > baseline and I expect commercial offerings in the market above that level. > snip I'm sorry but the regulation has 128 as the MAXIMUM upload speed, not some kind of regulated minimum. He can expect all he likes, without some new regulation that says otherwise, 128 is all the incumbent has to deliver and 128 is all it will deliver. I must now drink a lot of beer a: to stay on topic and b: to drown my narrowband sorrows. I bid you good day. - Paul ---------------------------------------------------------------------------

11 15

<<<Amendment>>> InternetNZ releases ENUM Personal User Agent Prot otype software under Open Source BSD Licence.
by Michael Sutton 27 Jul '05

27 Jul '05

============ July 28th 2005. Greetings: I am resending a modified version of this information bulletin highlighting the contribution of the European Telecommunications Standards Institute (ETSI) to this work: This PUA software was designed and developed in New Zealand by CatalystIT and utilised ETSI Guides available at http://www.etsi.org/services_products/freestandard/home.htm [1] ETSI EG 202 067: "Universal Communications Identifier (UCI); System framework". [2] ETSI EG 202 249: "Universal Communications Identifier (UCI); Guidelines on the usability of UCI based systems". We thank Mike Pluke and others at ETSI. Best Regards Michael Sutton Chair ENUM Task Force. ============ InternetNZ releases ENUM Personal User Agent Prototype software under Open Source BSD Licence. http://www.internetnz.net.nz/public/enum/pua/2005-07-pua-media-release.html InternetNZ announced today the release of its ENUM "Personal User Agent" prototype source code under an Open Source BSD Licence. The release hopes to encourage developer support of an ENUM initiative in New Zealand. The code is available from http://www.internetnz.net.nz/public/enum, as well as Reports prepared by the Task Force and a limited quantity of CDs. The PUA release does not include the "Universal Communications Identifier" Registry modules. Subscribe to a public information list at http://farsight.internetnz.net.nz/mailman/listinfo/enum. ENUM is a set of Internet protocols, mapping telephone numbers onto the Internet naming system. Existing email addresses, web sites and alternate telephone contact addresses can be attached to this ENUM record. This record can be used by suitable handsets or (pabx type) computer programs to contact the number holder. ENUM is in government approved trial or production in approximately 30 countries. "Personal User Agents" (PUA) are software programs which act like firewalls; automatically filtering requests for ENUM contact information and deciding what information to release and how incoming calls will be directed based on rules that look at the inbound identity of the caller. This protects the consumer from address harvesting or privacy breaches. In theory every existing and future telephone number in the world could be ENUM provisioned. This provides a massive legacy base on which commercial PUA software can be built. The ENUM PUA is based on our research and Guides by Europe's Telecommunications Standards Institute, ETSI (EG 202 067 & EG 202 249). http://www.etsi.org/services_products/freestandard/home.htm. In a complimentary note ETSI also referred InternetNZ's work to the European Commission. InternetNZ looks forward to continuing close and contructive dialogue with ETSI. Following completion of an ENUM PUA UCI Feasibility Study at the beginning of 2005 the prototype was developed by Catalyst IT (http://www.catalyst.net.nz) of Wellington, for InternetNZ. The PUA prototype was linked to another module known as the "Universal Communications Identifier" (UCI) which can bind an individual's name and service requirements to ENUM records and then be accessed by other PUAs. Future ENUM PUA software will enable users to opt-in to security services that will restrict publication of contact (email etc) information to anonymous callers and will permit intelligent routing of calls based on the relationship of the receiver to the caller and possible cost optimization of call termination and also increasing the rate of successful call completion for the networks. There are significant international opportunities for software developers to incorporate ENUM with PUA features into their existing communications software and directory services. InternetNZ anticipate that a number of software companies will work co-operatively to develop compatible systems that will compliment each other on different niche markets such as PUAs in the Telco-network, ISP, corporate business, SoHo and individual markets. Co-operating with the Government, Telecommunication Carriers Forum and applications developers, InternetNZ will participate and facilitate a New Zealand ENUM Trial over the next year that will provide a platform to test, demonstrate, commercialize applications and integrate ENUM to deliver economic advantage to the New Zealand community. InternetNZ welcomes enquiry from anyone interested in undertaking ENUM development work and participating in the Trial. "One Number To Hold Them All" Michael Sutton Chairman - InternetNZ ENUM Task Force Councillor InternetNZ Member Technical and Audit Committee Phone: +64 4 4721600 Ext 730 mailto:michael.sutton(a)internetnz.net.nz

1 0

Interesting articles from Beehive
by Ian McDonald 27 Jul '05

27 Jul '05

Folks, You might be interested in two postings today: http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=23810 which is the Anti Spam bill and includes a (badly) scanned version of the bill. Also: http://www.beehive.govt.nz/ViewDocument.aspx?DocumentID=23811 where the government seems to be rattling the sabres a little in broadband particularly around wholesale and the 128 k upload. Regards, Ian

1 0

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

27 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR

1 0

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

27 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17705 descr: Route set advertised to AS9560 by Inspire Net - AS17705 members: 203.114.128.0/19^19-24, 203.96.157.0/24, 203.79.88.0/23^23-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by Inspire Net Ltd - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: james(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR --- PREVIOUS OBJECT: route: 203.79.88.0/23 descr: Route for Inspire Net - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041126 source: NZRR REPLACED BY: route: 203.79.88.0/23 descr: Route for Inspire Net Ltd - AS17705 origin: AS17705 notify: rpsl-admin(a)nzix.net notify: james(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR

1 0

OT 1U or 2U servers
by Barry Murphy 26 Jul '05

26 Jul '05

Hey guys, Please reply offlist if you have some second hand 1U's or 2U's you're looking at getting rid of. Thanks Barry

1 0

Victoria SCS Mail Admin
by Jonathan Brewer 26 Jul '05

26 Jul '05

Hello, Looking for a mail admin at VUW to contact me off list fairly urgently re: an exploding mailing list running on terror.vuw.ac.nz. Quick response will save many headaches. Cheers, Jon

3 4

Iconz/esurf please contact
by Daniel Cross 25 Jul '05

25 Jul '05

Could somebody from esurf please contact me off-list. I've been trying to get hold of someone through the helpdesk (the only number I seem to be able to find), but am only getting an answering machine with no call backs thus far. This is in regards to one of our legacy customers with certain ports blocked. I can be reached on 021492917, or 5223680 Thanx, Daniel Cross Network Surveillance Engineer Woosh Wireless Limited Tel: +64 (9) 522 3680 Fax: +64 (9) 520 3447 0800 4 WOOSH www.woosh.com <http://www.woosh.com>

1 0

http://www.wlug.org.nz/NewZealandInternetHistory license details
by Matt Brown 25 Jul '05

25 Jul '05

Hi, Many of you will be familiar with the New Zealand Internet History page created on the WLUG Wiki after this years NZNOG conference. WLUG is currently in the process of clarifying the license situation for all of the wiki content, and we are endeavouring to bring all content under the a Creative Commons Wiki License (see http://www.wlug.org.nz/WlugWikiLicense for details). Due to the huge volume of edits and additions to this page we unfortunately don't have details of all of the original contributors and authors to it. My recollection is that this page was created by Ian McDonald based on notes from Joe's talk. Given that the content is all a historical record that has been collaboratively compiled, I don't imagine we're going to run into any copyright problems, but just to be sure, we would like to check. Does anyone on this list, who has contributed significantly to the page object to it being placed under the aforementioned license? If you do, please contact me so we can discuss it. Assuming we don't have problems I intend to relicense this page near the end of the week. Kind Regards PS. You're still welcome to add to/improve the page :) -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

5 4

OT: Jobs in Christchurch
by Bill Walker 20 Jul '05

20 Jul '05

Hi, Just a quick note to see if anyone knows of any jobs / job agencies in Christchurch? Please Reply off list. Thanks, Bill

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: 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 --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23655 descr: Route set advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/20^20-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.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.50.117.0/24^24-29, 202.50.169.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 20050721 source: NZRR

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050526 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050517 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR

1 0

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

20 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050517 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050526 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR

1 0

ICONZ prefix update 2005-07-20
by John Johnston 19 Jul '05

19 Jul '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer direct with ICONZ there is an update. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Jul '05

18 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.148.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug - AS7657 members: 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.118.128.0/18^18-29, 202.46.160.0/20^20-29, 210.55.248.0/21^21-29, 202.49.240.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 210.55.202.0/23^23-29, 202.21.130.0/24^24-29, 202.49.186.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR

3 3

Notification of NZRR Database changes
by NZRR Database Notifications 18 Jul '05

18 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route: 210.55.248.0/21 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.248.0/21 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 202.49.176.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 202.49.176.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 210.55.202.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.202.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR

1 0

Re: [nznog] DPE and 3CIX
by Webmaster 18 Jul '05

18 Jul '05

For those who want to peer there, our content will be available at 3CIX when we launch. If you already peer with the 3CIX route servers then you need do nothing. regards, Richard Hulse Radio NZ >>> Andy Linton <asjl(a)citylink.co.nz> 19/07/2005 14:50 >>> CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DPE and 3CIX
by Andy Linton 18 Jul '05

18 Jul '05

CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/

3 2

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Donald Neal 18 Jul '05

18 Jul '05

On Tue, 19 Jul 2005, Barry Murphy wrote: [...] >> I'm guessing customers connect directly to the erx's, thus if the erxcrash's >> and goes down, customer falling off that node will be effected. >> >> The idea is a pretty map with colors indicating packet loss. >> Let's just see what happens when the next big network fault happens. >It is highly unlikely anyone will give you this information (and in some >cases this is 100% unlikely) as this would tend to be considered >"commercially sensitive" data to many large organisations. >Any information gathered through probing networks will most certainly be >inaccurate and could lead (as pointed out earlier) to increased >frustration in helpdesks when some clueless customer rings up to report an >ERX crash because they saw it on your intarwebnet page. There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "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."

4 3

Re: NZNOG Digest, Vol 31, Issue 14 (Out of Office)
by Lance Edwards 18 Jul '05

18 Jul '05

I will be out of the office starting noon Monday 18 July and will return Friday 22 July. I will be checking email once per day during this period. Regards, Lance ______________________________________________________________________________________________________ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info(a)linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. ______________________________________________________________________________________________________

2 1

[OT]Ispmap / isp locations / core routers
by Barry Murphy 18 Jul '05

18 Jul '05

Hey guys, I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz . 1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice. To gather this info, simply fire up http://status.fast.co.nz/metric.html , zoom in to the closest location to your office/router as possible, center it in the screen and mail me the details of latitude and longitude. http://status.fast.co.nz will soon become apart of ispmap, if you go directly to this URL you will see what my aim is, to have a country map (with the ability to filter by ISP) with the status of each ISP's network. Please mail back (Off list) in the following format: ISP: Contact: Logitude: Latitude: IP Address: Services effected: (optional, but would be nice to see what parts of the country and what services would be effected) Equipment: (optional, but eg cisco, I may add logos to the map later) Thanks. Barry

8 12

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Gordon Smith 18 Jul '05

18 Jul '05

I agree 100% with Steve on this. I doubt that there are many providers that wish to publicise their internal network structure. A pretty map has very little relevance to a modern MPLS-based network without a view of the underlying signalling. All you'll see is the switched paths, not the physical infrastructure. There is such a thing as too much information - I see little point in letting an end user try to diagnose a network fault when said user has little or no understanding of network topologies and protocols, even at layer 3. Cheers, Gordon

1 0

Frame Relay services
by Andy Linton 16 Jul '05

16 Jul '05

I'd appreciate hearing from ISPs who provide connectivity using Frame Relay. Replies off list and please no diatribes about how crap Frame Relay is and how I should use technology X instead.

1 0

RE: [nznog] [Fwd: Buzz.ThePeople]
by Scott Walsh 14 Jul '05

14 Jul '05

Interesting (and un-surprisingly), the privacy statement on their website (http://www.buzzchannel.co.nz/v1.1/research/surveys/privacy.asp?cid=42&sid=1 ) contradicts the statement below. -----Original Message----- From: Richard Patterson [mailto:richard(a)helix.net.nz] Sent: Friday, 15 July 2005 14:01 To: nznog(a)list.waikato.ac.nz Subject: [nznog] [Fwd: Buzz.ThePeople] <snip> IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople.

1 0

[Fwd: Buzz.ThePeople]
by Richard Patterson 14 Jul '05

14 Jul '05

Sorry to disrupt everybody from their ever so important SPF ranting. but, has anybody heard of this NZ spamm0r? registrant_contact_name: Buzz Channel Limited registrant_contact_address1: P.O. Box 68-953 registrant_contact_address2: Newton registrant_contact_city: Auckland registrant_contact_postalcode: 1003 registrant_contact_country: NZ (NEW ZEALAND) registrant_contact_phone: +64 9 5284883 registrant_contact_email: nick.macdonald(a)buzzconsult.com Registered Office 43 Bright St Eden Terrace Auckland Directors VANCE, Mary MACDONALD, Nicholas -------- Original Message -------- From: - Fri Jul 15 13:09:22 2005 X-Account-Key: account3 X-UIDL: 1121390459.30535.skywarp,S=1631 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <buzz(a)buzzchannel.co.nz> Delivered-To: detonate(a)helix.net.nz Received: (qmail 30533 invoked by uid 89); 15 Jul 2005 01:20:58 -0000 Received: from unknown (HELO 216-55-168-48.dedicated.abac.net) (216.55.168.48) by skyfire.helix.net.nz with SMTP; 15 Jul 2005 01:20:58 -0000 Received: from BuzzServer1001.buzzone.buzzchannel.net (unverified [216.55.168.48]) by 216-55-168-48.dedicated.abac.net (SurgeMail 3.0c2) with ESMTP id 73137 for <detonate(a)helix.net.nz>; Thu, 14 Jul 2005 18:08:13 -0700 Return-Path: <buzz(a)buzzchannel.co.nz> From: Buzz.ThePeople <buzz(a)buzzchannel.co.nz> To: detonate(a)helix.net.nz Subject: Buzz.ThePeople Date: Thu, 14 Jul 2005 18:08:13 -0700 Message-ID: <20050714-18081356-cdc(a)BuzzServer1001.buzzone.buzzchannel.net> MIME-Version: 1.0 X-Server: High Performance Mail Server - http://surgemail.com Dear Richard Patterson, Help shape your future PLUS have the chance to win! Buzz.ThePeople is a new online way for you to have your say on lots of different topics. Many people are joining Buzz.ThePeople because they want their views considered by NZ decision makers (e.g. political pollsters, the media, marketers and market researchers). Others are joining because there are going to be great prizes and even opportunities to earn cash. If you are interested and want to know more (plus your chance to go into the draw for a new Dell Inspiron 6000 notebook computer) click on the following link: http://www.buzzthepeople.co.nz?c=43401 IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople. Kind Regards, The Buzz Team.

4 3

SPF Uptake in New Zealand
by Craig Whitmore 14 Jul '05

14 Jul '05

So you ask what is SPF? SPF (Sender Permitted From) is an anti-forgery method used with SMTP which stops people trying to send from your domain. Not designed for stopping spam, but helps reduce the amount of spam as well (stops people sending from other peoples domains). Spammers can add SPF records to their domains yes, (repeat: SPF doesn't stop spam but does a good job of it) but in the future may be improved to include trust factors (ie domain and SPF has been only around for 2 days and its sending 1000 emails to me... strange) There are quite a number of anti-forgery systems around at the moment, and the main ones are SPF, Sender-ID (Microsoft) and DomainKeys (Yahoo), SPF at the moment is the largest used worldwide. (over a million domain names having SPF records) The uptake in New Zealand is pretty small at the moment, but ISP's are starting to add SPF records for their domains. Xtra have added SPF rules for the xtra.co.nz Domain: v=spf1 ip4:210.86.15.0/24 ?all (host -t TXT xtra.co.nz) IHUG have added a SPF rule for ihug hosted domains to include: eg v=spf1 include:_spf.ihug.co.nz -all (host -t TXT _spf.ihug.co.nz) And a lot of Domains (see http://spam.co.nz/spf/working/) have started to add SPF Rules . This list is no where complete at the moment for .NZ (or other domainnames). Also quite a number of NZ domains have broken SPF records for various reasons which (if an ISP is testing for SPF will reject and cause bounces), so its quite important to make your rules correct (see http://www.spam.co.nz/spf/broken - This list is also quite imcomplete) I'm not saying SPF doesn't have its problems, but the major problem (at the moment) is forwarding emails . Ie user(a)ispa.com sends email to user(a)ispb.com and it gets forwarded to user(a)ispc.com. . If user(a)ispc.com checks for SPF it will fail as the user(a)ispa.com email address is coming from ISP B's email server. BUT mechanisms like SRS fix this problem. Mostly importantant is before SPF records are set up for a domain you must know how you users are using your domain. So maybe you think SPF is just something kids play around with and it will never be used for anything important and no one cares about it which is not so as its gaining momentum like just recently the IANA just gave SPF its own DNS RR (SPF) (see http://www.iana.org/assignments/dns-parameters) which will be used instead of the TXT records in the future to SPF records (maybe SPF v3 will use it only) More information can be read at: http://www.openspf.net/ and the mailing list and other information can be read at http://www.openspf.org/ Thanks Craig Whitmore www.spam.co.nz

9 11

RE: [nznog] SPF Uptake in New Zealand
by Nic Wise 14 Jul '05

14 Jul '05

> I'm guessing that this is a precursor to enforcing it for all > Microsoft controlled domains. Though presumably they will > have trouble enforcing it for Microsoft.com, unless they're > already prepping the next version of Exchange to include > spf/senderid support :) > I'm not 100% sure, but I think I read that this is going to be in Exchange 2003 SP2 - I think it's part of the "edge services" thing that's in SP2. Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited. t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

1 0