- NZNOG - lists.nznog.org

Studio Cam Update
by Webmaster 22 Dec '05

22 Dec '05

The studio cams for the Matinee Idle radio show are now in operation with a jpg slide: http://www.radionz.co.nz/nr/programmes/matineeidle I have noted on the web cam page that some customers may not be able to get the high bandwidth streams due to their ISP not peering. These consumers will get a message suggesting that they use one of the lower rate streams or contact their ISP. Time for a beer now, my work is done.... regards, Richard

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Dec '05

22 Dec '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:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - 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.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.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.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 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 20051219 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - 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.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.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 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 20051223 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - 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.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.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.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 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 20051219 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - 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.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.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 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 20051223 source: NZRR

1 0

Re: [nznog] ipv6
by Philip D'Ath 22 Dec '05

22 Dec '05

Pretty much every Cisco DSL router supports IPv6. We just need an ISP to start selling the IPv6 transit ... -----Original Message----- From: Richard Hector [mailto:richard(a)walnut.gen.nz] Sent: Thursday, 22 December 2005 2:46 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:35 +1300, Matt Brown wrote: > With the introduction of UBS I'm hoping that it's going to become a > lot more common for ISPs to be able to offer IPv4/IPv6 circuits, even > if it is only on ad Ad-Hoc basis to the 'geeks' to start with. To offer it on UBS, wouldn't your DSL router have to support IPv6? Do any of them? I suppose you could use either a plain modem, or one of those ones that bridges PPPoA to PPPoE, but I've never tried setting one up. Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 11

SANOG VII - Mumbai, India, 16-24 January 2006
by Andy Linton 22 Dec '05

22 Dec '05

South Asian Network Operators Group (SANOG) VII 16-24 January 2006, Mumbai, India Hosted by ISPAI. SANOG VII Program Announcement SANOG VII program and agenda are now published on http://www.sanog.org/sanog7/. SANOG VII is being held by ISP Association of India (ISPAI) in Mumbai, India from 16-24 January 2006. Daniel Karrenberg, Chief Scientist, RIPE NCC and Paul Wilson, DG,APNIC will address the plenary session of SANOG VII. There will be 3 workshops, 10 tutorials, 3 BoFs and over 16 presentations during the event. APNIC will hold a special Open Policy Meeting Showcase at SANOG VII, and for the first time at SANOG, we'll have a Peering Panel and Debate. Registration Discounts available for ISPAI, APNIC, APIA members. Detailed information is available at http:/www.sanog.org/sanog7/ Program and Agenda: Three hands-on workshops: 16-20 January 2006 * ISP Routing and BGP Multihoming Workshop * IPv6 Essentials, Applications and Routing Workshop * Multicast Routing and Applications Workshop Ten Tutorials: 21-22 January 2006 * BGP and High Availability Routing Tutorial, Prasad Babu * DNS / DNSSec Deployment Tutorial, Champika Wijayatunga * IXP Construction and BGP Multihoming, Philip Smith, Gaurab Raj Upadhaya * L2VPN - Changing and Consolidating Networks - Paresh Shah, Md.Waris * Layer2 Attacks and Mitigation techniques, Yusuf Bhaiji * DDoS prevention in Service Provider Networks, Wireless Security,Pravin Mahajan * The Basics of Multicast - Marshall Eubanks, * QoS and Multicast on MPLS Networks , Rajesh Shinde * QoS on Low Bandwidth & High Delay Links, Prakash Shende Birds-of-a-Feather (Special Evening Sessions) : 21-23 January 2006 * Managed Services * Anti-SPAM Tools and Techniques * Internet Society (ISOC) BoF APNIC Special Sessions * APNIC Helpdesk sessions throughout SANOG VII * APNIC Open Policy Meeting Showcase on 24th January 2006 Two Days Conference Program : 23-24 January 2006 * Alternative architectures for Broadcast Video Distribution - Srinath Beldona, Cisco * RA-MPLS services - Kapil Kumar, Reliance * Network Infrastructure for IPTV - Saisree Subramanian, Wipro * Efficient Resource Broker Architecture to Provide Guaranteed QoS - Praveen Kumar, Anna University * Graceful Restart of Routing Protocols - Prasad Babu, Juniper * Backbone Architectures for NLD/ILD: Design; Optmization & Services - Chandan Mendiratta (Cisco) * Network Infrastructure Security in Cellular Data Networks: An Initial Investigation - Vishal Sharma (IIT-Bombay) * Traffic Engineering and Network Planning Tools for MPLS Networks - Dr. Girish P. Saraph (IIT-Bombay) * pmacct; a new player in the network management arena - Paolo Lucente (CNR-Italy) * Flow measurements from the packet-switched NREN PIONIER: technology and experience - Wiktor Procyk (Poznan S&N Center) * Interest Based Group Management Mechanisms for E-learning Design using the Peer to Peer Technologies - Surya (AIT) * Internet Routing Table Update - Philip Smith (Cisco) * INOC - DBA Update - Gaurab Raj Upadhaya ( PCH) * Data Network Management for Telecom Operators in ASIA - Sufi Faruq (AKTEL) Peering Penel and Debate * Nigel Titley, Peering Manager, FLAG Telecom * Sylvie Laperriere, Director- Peering, Teleglobe * Sharad Shangi, Net4India * Gaurab Raj Upadhaya, PCH, (moderator) Local Fellowships are still available. We expect a huge turn out from the region at this SANOG meeting owing to the popularity at previous meets. We also welcome participants from West Asia, with our established collaboration with the RIPE NCC. With more involvement of APNIC in the content of overall program, We hope you would be able to make it to this meeting. The meeting is open to everyone from the operational community, and thus anyone who wants to find out more about Internet operations in South Asia is welcome. You can register for SANOG by sending in the form available at www.sanog.org/sanog7 or using the online registration system. Registrations from inside India can be paid by DD Looking forward to seeing you there. Thanks - SANOG

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

Not being from a service provider my view is somewhat simplistic. Telecom offers a layer 2 service called UBS, which uses L2TP between their RAN and the ISP. Over this PPP runs. So I don't see any reason why an ISP couldn't offer IPv6 over UBS. -----Original Message----- > Pretty much every Cisco DSL router supports IPv6. We just need an ISP > to start selling the IPv6 transit ... The last I knew (which was admittedly many years ago) Telecom's wholesale DSL was a layer-3 service, with frames being routed through a twisty maze of RFC1918-numbered routers before they arrived at the user's ISP. If that was still the case, then surely Telecom would need to route v6 frames between the customer and the ISP for the customer to receive native v6 service? If there has been a subsequent layer-2 wholesale DSL service offered, along the lines that is done elsewhere, is there not still a requirement for Telecom to switch v6 frames from PPPoA into L2TP, or whatever framing is used to present a user's traffic to an ISP?

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

I've tried: Orcon Maxnet WorldXchange Telecom told me that are playing with it, at best, and had no plans to offer it commercially. Didn't bother trying Xtra. I tried to speak to TelstraClear about it, but couldn't really find the right people to understand what I was asking. -----Original Message----- From: Matt Brown [mailto:matt(a)mattb.net.nz] Sent: Thursday, 22 December 2005 2:35 p.m. To: Philip D'Ath Cc: Simon Lyall; nznog Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:26 +1300, Philip D'Ath wrote: > I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've > contacted is prepared to sell me one. Are you able to share who you tried to purchase one off? There seem to be three NZ providers advertising v6 prefixes at the present time: http://www.sixxs.net/tools/grh/dfp/all/?country=nz With the introduction of UBS I'm hoping that it's going to become a lot more common for ISPs to be able to offer IPv4/IPv6 circuits, even if it is only on ad Ad-Hoc basis to the 'geeks' to start with. Cheers -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

1 0

Re: [nznog] ipv6
by Philip D'Ath 21 Dec '05

21 Dec '05

I've tried to buy a dual stack IPv4/IPv6 circuit, but no one I've contacted is prepared to sell me one. I'm having to use 6to4 tunnelling at the moment. -----Original Message----- Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ?

3 2

Streaming Event
by Webmaster 21 Dec '05

21 Dec '05

Over the summer break we will be providing a Studio Cam for the top rating Matinee Idle radio show, hosted by Phil O'Brien. HTTP://www.radionz.co.nz/nr/programmes/matineeidle This is a first for Radio NZ and as far as I am aware a first for New Zealand Radio in general. We'll be providing video streams at 56k, 128k, 384k and 2 Mbs. Operators should be aware that the Studio Cam will be promoted extensively on air. To ensure all New Zealanders get the best possible service we strongly recommend peering with the R2/Citylink anycast cluster at 202.7.7.90 via WIX, APE and/or PNIX. The US node is intended to serve consumers outside New Zealand. Limited NZ bound bandwidth has been allocated for this event, and operators may experience an increase in help desk calls when this allowance is exceeded. regards, Richard Hulse Radio New Zealand

2 1

ipv6
by Simon Lyall 21 Dec '05

21 Dec '05

Interesting wee discussion about real world IPv6 usage on NANOG that some here might be interested in, some have said things have improved a little in the last 18 months though: http://www.merit.edu/mail.archives/nanog/msg14543.html Is anyone in NZ actually using IPV6 for "real world" / "People paying for IPv6 service" stuff as against "just playing with IPv6" ? Ob Friday Afternoon link (many will have seen before): http://www.livejournal.com/users/pjammer/153928.html -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

New IPv6 Address Block Allocated to the RIPE NCC
by filiz＠ripe.net 20 Dec '05

20 Dec '05

[Apologies for Duplicates] Dear Colleagues The RIPE NCC received the IPv6 address range 2A01:0000::/16 from the IANA in December 2005. 2A01:0000::/23 was allocated to the RIPE NCC in July 2005. This latest range includes that previous allocation. You may wish to adjust any filters you have in place accordingly. You can find more information about the IP space administered by the RIPE NCC on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, Filiz Yilmaz RIPE NCC

1 0

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

18 Dec '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:AS2687 descr: Route set advertised to AS9439 by AT&T Global - AS2687 members: 152.158.254.0/24^24-29, 152.158.255.0/24^24-29, 202.14.142.0/24^24-29, 202.27.160.0/24^24-29, 202.36.68.0/24^24-29, 202.36.69.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.46.160.0/20^20-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.48.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.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.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, 203.163.68.0/24^24-29, 203.163.70.0/24^24-29, 203.163.71.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.119.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050303 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - 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.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.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.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 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 20051219 source: NZRR

1 0

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

18 Dec '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:AS2687 descr: Route set advertised to AS9560 by AT&T - AS2687 members: 152.158.254.0/23^23-29, 203.163.70.0/23^23-29, 152.158.213.0/24^24-29, 202.14.141.0/24^24-29, 202.14.142.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.28.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.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.86.0/24^24-29, 202.135.112.0/24^24-29, 202.135.115.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.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, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.98.0/24^24-29, 219.88.103.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Mark.Crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050503 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - 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.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.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.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 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 20051219 source: NZRR

1 0

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

17 Dec '05

The Systems Administration Miniconf which will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 We are pleased to announce that our programme is 95% finalised and is available online at: http://sysadmin.miniconf.org/program.html and more details of each presentation are on this page: http://sysadmin.miniconf.org/presentations.html Please note that for now the actual times of each presentation have not been finalized while we work with other miniconfs to avoid clashes. While we are no longer accepting full length talks we still have space for Lightning talks, please contact us if you are interested: http://sysadmin.miniconf.org/lightning.html Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Re: [nznog] NZ Security Notifications
by John Martin 16 Dec '05

16 Dec '05

Brendan Murray wrote: > > > If you think there would be some value in this, please email me. > > You can find information about the nsp-security mailing list at > https://puck.nether.net/mailman/listinfo/nsp-security) > > I believe such a closed security mailing list would have a great deal of value, not only to Universities and ISP's within New Zealand (re: aka Russell Fulton) but also to Critical Infrastructure Providers, financial services too. With a great number of sources from Phishing, Pharming attacks being reported with USA and EMEA from APAC, this could also provide an early warning system and possibly assist in shutting down such activity via the participating ISP's. However, in terms of running a script through various snort databases, the issue of privacy looms and authorisation, a better answer might be to use the New Zealand nominated CERT for such operations i.e. Centre for Critical Infrastructure Protection (CCIP) locally as a central collection point etc.. To ensure anonymity etc. It would also be good to add ISC (sans.org) logs to the collective.. With compliance issues only around the corner, New Zealand is relatively unscathed by regulatory/legislation within USA, EMEA, Australia, which statistically looks like it will take a hold within the next 1-2 years. Such a group may provide guidance to organisations, not prepared for the ongoing associated issues of compliance. John Martin Security Practice Leader IBM NZ

1 0

NZ Security Notifications
by Brendan Murray 15 Dec '05

15 Dec '05

(apologies to members of members-discuss(a)internetnz.net.nz for duplication) Yesterday the topic of AusCERT came up on nznog. Many of you probably know that InternetNZ has formed a small group to look at the need/feasibility of a NZ based CERT. It is all in early days yet, but it might be a good time to start looking at some ways of improving security awareness here. We hope to raise some ideas for discussion at the nznog conference next year, but the recent email suggests we could start on some practical matters now. We would like to suggest creating a NZ security community with a nz-sec mailing list, for example. This would have the same sort of intent as the nsp-security mailing list, bringing in people with a genuine interest in security practice and incident handling. We feel that the CCIP list, while valuable, is informative rather than collaborative. The nznog list has been used for security issues where relevant, but network operations is the reason for nznog, not security management. Ultimately the list and list membership, or some variant, would become associated with a NZ CERT if one were to happen, but in the meantime InternetNZ would be happy to host and advertise a moderated list. If you think there would be some value in this, please email me. You can find information about the nsp-security mailing list at https://puck.nether.net/mailman/listinfo/nsp-security) Brendan Murray Chairing the InternetNZ NZCERT Task Force.

7 7

Re: [nznog] NZ Security Notifications
by Barry Greene (bgreene) 14 Dec '05

14 Dec '05

For those who are interested, I've got a draft of some guidelines that can be used to create a group like nsp-sec-nz. Pop me a note and I'll send it. > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Wednesday, December 14, 2005 8:16 AM > To: Joe Abley > Cc: NZNOG List > Subject: Re: [nznog] NZ Security Notifications > > ] While an nsp-sec-nz list sounds like it could be lots of > fun, maybe ] it's also worth mentioning that it's perfectly > possible (and ] reasonable) for operators in nz who fit the > target demographic to ] become subscribers to the existing > nsp-sec list. > > Agreed! The mix of both nsp-sec and nsp-sec-nz would be > quite complimentary and useful. > > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Hotmail
by Jeremy Strachan 14 Dec '05

14 Dec '05

Probably B52 bombers and cruise missiles. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 15 December 2005 12:47 p.m. To: Simon Lyall Cc: nznog Subject: Re: [nznog] Hotmail Simon Lyall wrote: > Violations will result in use of equipment located in California and > other states. Ouuchhhh... that'll stop spammers for sure! Wonder what equipment located in California and other states it is that MSN/Hotmail will use though? -- Juha _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 7

Hotmail
by Simon Lyall 14 Dec '05

14 Dec '05

$ telnet mx2.hotmail.com smtp Trying 65.54.244.168... Connected to mx2.hotmail.com. Escape character is '^]'. 220 bay0-mc6-f18.bay0.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states. Wed, 14 Dec 2005 15:39:37 -0800 helo 250 bay0-mc6-f18.bay0.hotmail.com (3.1.0.17) Hello [202.27.185.139] Mail from:<simon(a)darkmere.gen.nz> 452 Out of memory Connection closed by foreign host. $ -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

Re: [nznog] NZ Security Notifications
by Dean Pemberton 13 Dec '05

13 Dec '05

>Would this list have the same sort of policy for membership as nsp-sec? >i.e. an invite only list for people who actually have to do the work >with a policy of kicking out people who don't meet the membership >criteria on an ongoing basis. > >If that's the case then I can see value in such a list but if it's >going to be similar to NZNOG with an "anybody can join" policy then I'm >less interested. > >andy I agree with Andy here. The only list I would be interested in is one which subscribes to the nsp-sec policy. No lurking. You have to be the person who is able to make the changes. Change jobs and you unsub. And some others. It's the only way. An "anyone can join" list will degrade into.... well my opinions here should remain to myself =) I would suggest that people look at joining nsp-sec rather than re-inventing the wheel. Or at the very least getting Rob to host an nsp-sec-nz list with the same policy around it. If you are a large provider, then there is probably already content on nsp-sec that you should know about. Dean.

1 0

Fwd: King Kong streaming tomorrow
by Paul Adshead 13 Dec '05

13 Dec '05

It may be good for someone in Telecom to let their front line staff know about (de-)peering at some point. After spending 15 minutes on the phone, it was quite amusing when they came back from putting me on hold: "I have talked to our tech guys and no-one in Xtra can get to the page either. They think it is a problem with the routing of data for the site at the far end. You could try power-cycling your router though"... Then when I asked for confirmation by email: "We suspect that there has been some stringent ip filtering and this is what could be causing the problem. We can not confirm this the best source of action would be to contact the host of the website for further information." Obviously either highly qualified in providing BS responses or just stupid. It's still annoying that I can't get to see it though... Paul -----Original Message----- From: Mike [mailto:mike(a)nzbox.com] Sent: Wednesday, 14 December 2005 17:20 To: NZNOG Subject: Re: [nznog] King Kong streaming tomorrow Hi Rich and Si Can I suggest you mention which streams will be available internationally in your announcements. Cant see either of these from Seattle ;-) good message for TCL and TNZ though.... Kia ora! You've reached the Citylink anycast node located in San Francisco, California. If you are in NZ, you should ring your ISP and ask them why your traffic is coming to the USA, rather than staying in New Zealand. Useful phone numbers are at TelstraClear (try the wholesale number if you get no joy from residential/business) and the best number for Telecom would appear to be 0800 CALL XTRA [22 55 98]. If you're feeling particularly cussed, ask them what's changed in the two years between the RoTK (when you could reach these streams nationally) and now. International users, we're sorry, sadly, our non-existent budget means that we can't make the Courtenay Place webcam available internationally. Such is life. Mike On Dec 12, 2005, at 8:10 PM, Simon Blake wrote: > Hi all > > A belated notice that the red carpet TV coverage and Courtenay Place > webcam will be streaming tomorrow as part of the King Kong premiere. > The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam > from > embassy.citylink.co.nz (202.7.6.10), both anycast at the major > exchanges. The webcam is running now, informal MMS streams will start > about midday, TV coverage about 3pm. > > We're not expecting the same sorts of loads as RoTK, but who can tell. > > Cheers > Si > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

King Kong streaming tomorrow
by Simon Blake 13 Dec '05

13 Dec '05

Hi all A belated notice that the red carpet TV coverage and Courtenay Place webcam will be streaming tomorrow as part of the King Kong premiere. The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam from embassy.citylink.co.nz (202.7.6.10), both anycast at the major exchanges. The webcam is running now, informal MMS streams will start about midday, TV coverage about 3pm. We're not expecting the same sorts of loads as RoTK, but who can tell. Cheers Si

5 4

NZ use of AusCERT
by Jonathan Brewer 11 Dec '05

11 Dec '05

Hi folks, Are there many among us who are members of AusCERT? Any in the practice of reporting incidents on NZ based hosts to AusCERT? Do AusCERT care to hear about incidents from non-members? Cheers, Jon

2 1

woosh
by Garrrett Stoupe 11 Dec '05

11 Dec '05

Can someone from woosh please contact me off list

1 0

National Bank Phising Scam
by Ashley Petherick 11 Dec '05

11 Dec '05

Morning all, awoke today to a National bank Phishing scam - a pretty ugly one, they didnt put much effort into the email, but the 'verification web page' looks pretty authentic (save the URL http://202.93.254.35:443/cxk/) They ask for your First and Last name, and credit card number, your ATM PIN, and expiration date. Sent from security(a)nationalbank.co.nz / Subject - Verification Required I have advised the site. Account Confirmation Required! Valued National Bank Client, Recently there have been a large number of identity theft attempts targeting National Bank customers. In order to safeguard your account we require that you verify your banking details. This process is mandatory. You may do so by clicking Here <http://202.93.254.35:443/cxk/> <a href="http://202.93.254.35:443/cxk/"> and submitting the required information. Failure to do so may result in a temporary cessation of your account services pending submission. Thank you for your prompt attention to this matter and your co-operation in helping us maintain the integrity of our customers accounts. Please do not reply to this e-mail, as this is an unmonitored alias. If you require further assistance refer to our support centre <http://nationalbank.co.nz/personal/contacts/> <A HREF="http://nationalbank.co.nz/personal/contacts/" TARGET="_blank">. National Bank respects your privacy. Click here <http://nationalbank.co.nz/terms/default.htm> <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank"> to read the National Bank Group Privacy Policy Statement. Electronic Banking services are issued by the National Bank of New Zealand (Electronic Banking services include telephone banking, Netbank and Bpay). A Product Disclosure Statement (PDS) <http://nationalbank.co.nz/terms/default.htm> <A HREF="http://nationalbank.co.nz/terms/default.htm" TARGET="_blank"> is available for these products on this website or from any branch of the National Bank. © 2005 The National Bank of New Zealand, part of ANZ National Bank Limited

1 0

Re: [nznog] (OT?) Phishers targetting Kiwibank
by Donald Neal 08 Dec '05

08 Dec '05

Andy Linton wrote: > > It would be good if these phishing discussions focussed on > technical aspects > of what can be done by people on this list once the list > knows about the > latest scam. The banks I suspect will make their own > decisions without seeking > advice here. > This thread should now turn to a technical topic or go away. - Donald Neal NZNOG List Administrator Donald Neal |"You know what young, carnivorous, Support Engineer |alien mammal-like monsters are like. NGN Operations |Always getting into scrapes." 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.

4 3