- NZNOG - lists.nznog.org

10Gig BiDi Optics
by Simon Allard 19 Apr '12

19 Apr '12

Anyone had any experience with 10Gig BiDi optics? Interested in feedback on reliability etc. Simon Orcon (AS17746, AS4610)

1 0

After somebody from Trademe's web team
by Simon Lyall 19 Apr '12

19 Apr '12

I'm after one of the guys from tradme's web team who looks after the http accelerators (who I was on a course with last year). Could you please send me an email. Hopefully this email will get through, the last copy I sent was blocked by the spam filters in front of the list ( Postini ), might be Xtra's MTA again. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Linux Mirror server ftp.wicks.co.nz
by Tony Wicks 17 Apr '12

17 Apr '12

Hi all, after many years the service provider that has kindly been providing the hosting and bandwidth for my Redhat (Centos / Fedora / Scientific Linux) has decided to discontinue the free colo service. If any provider would like to donate some space/capacity please let me know off list. The servers also run a couple of game servers. Requirements - 3u rack space, 100Meg minimum of internet (one port), /28 ipv4, v6 optional cheers

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Apr '12

16 Apr '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS45950 descr: advertised to AS9439 by Gareth Morgan Investments - ASAS45950 members: 202.134.48.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: mike(a)gmi.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20091208 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS45950 descr: advertised to AS9439 by Gareth Morgan Investments - AS45950 members: 103.8.80.0/24^24-29, 202.134.48.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: mike(a)gmi.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120417 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Apr '12

16 Apr '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by ACSData - AS18119 members: 114.110.32.0/21^21-29, 202.126.80.0/21^21-29, 103.5.156.0/22^22-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.134.48.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20111020 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by ACSData - AS18119 members: 114.110.32.0/21^21-29, 202.126.80.0/21^21-29, 103.5.156.0/22^22-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 103.8.80.0/24^24-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.0/24^24-29, 202.134.48.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120417 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Apr '12

16 Apr '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS24388:RS-ROUTES:AS24183 descr: advertised to AS24388 by DTS Limited - AS24183 members: 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.174.184.0/21^21-29, 202.174.180.0/22^22-29, 202.27.88.0/23^23-29, 202.36.172.0/23^23-29, 202.174.178.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 203.170.56.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: tim(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20110923 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS24183 descr: advertised to AS24388 by DTS Limited - AS24183 members: 175.176.224.0/19^19-29, 202.174.128.0/19^19-29, 203.88.64.0/19^19-29, 210.89.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.174.184.0/21^21-29, 202.174.180.0/22^22-29, 202.27.88.0/23^23-29, 202.36.172.0/23^23-29, 202.174.178.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 203.170.56.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: tim(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120417 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Apr '12

16 Apr '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24183 descr: advertised to AS9439 by DTS LIMITED - AS24183 members: 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.27.88.0/23^23-29, 202.174.184.0/23^23-29, 202.174.190.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 203.170.56.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: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100202 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24183 descr: advertised to AS9439 by DTS Limited - AS24183 members: 175.176.224.0/19^19-29, 202.174.128.0/19^19-29, 203.88.64.0/19^19-29, 210.89.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.174.184.0/21^21-29, 202.174.180.0/22^22-29, 202.27.88.0/23^23-29, 202.36.172.0/23^23-29, 202.174.178.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 203.170.56.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: tim(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120417 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 16 Apr '12

16 Apr '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. 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. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS45279:RS-ROUTES:AS24183 descr: advertised to AS45279 by DTS Limited - AS24183 members: 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.174.184.0/21^21-29, 202.174.180.0/22^22-29, 202.27.88.0/23^23-29, 202.36.172.0/23^23-29, 202.174.178.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 203.170.56.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: tim(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20110923 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS24183 descr: advertised to AS45279 by DTS Limited - AS24183 members: 175.176.224.0/19^19-29, 202.174.128.0/19^19-29, 203.88.64.0/19^19-29, 210.89.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.174.184.0/21^21-29, 202.174.180.0/22^22-29, 202.27.88.0/23^23-29, 202.36.172.0/23^23-29, 202.174.178.0/23^23-29, 124.150.166.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 203.170.56.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: tim(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120417 source: NZRR ------------------------------------------------------------

1 0

Bruce Schneier Event Invitation
by NZITF Info 11 Apr '12

11 Apr '12

Good Afternoon, The New Zealand Internet Task Force, NZITF, would like to invite NZNOG members to attend a public lecture by Bruce Schneier. Bruce will be talking about the topic of his latest book Liars and Outliers. For those of you unable to attend this event in person, it will be streamed live at www.nzitf.org.nz. This event will be held from 10:00am – 12:00pm on Tuesday 1 May 2012 at the St James Theatre, 63-95 Courtenay Place, Wellington. Doors will open at 9:30am and following the lecture there will be a book signing by Bruce, and Capital books will be onsite with copies of his books available for purchase as well. There will also be tea and coffee and a chance to network with others from the industry. Thanks to the sponsorship by InternetNZ and Telecom New Zealand this event is free to attend, however due to the expected interest RSVP’s are essential. Please email rsvp(a)nzitf.org.nz no later than 12pm Thursday 26 April 2012. Registration will be confirmed by email. Please include the names of attendees, a contact email, and their organisation. Please find the event flyer attached. Regards, NZITF. New Zealand Internet Task Force PO Box 11-881 Manners Street Wellington 6142 New Zealand Fax: +64 4 495 2115 Web: www.nzitf.org.nz

1 0

Conference wifi usage?
by Richard Hector 11 Apr '12

11 Apr '12

Hi all, Hopefully this isn't too off-topic, or too vague ... If one was running wifi for a conference - not for IT types - does anyone have an idea what the likely usage of wifi by participants would be, on a per-user per-day basis? There will probably be beer, but unfortunately I can't invite you all. Is mentioning that necessary to get past the filter? Thanks, Richard

1 1