December 2005 - NZNOG - lists.nznog.org

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

22 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 22 Dec '05

22 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 22 Dec '05

22 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 22 Dec '05

22 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 22 Dec '05

22 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 21 Dec '05

21 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 19 Dec '05

19 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 19 Dec '05

19 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 18 Dec '05

18 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 17 Dec '05

17 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