- NZNOG - lists.nznog.org

crack!
by Jamie Baddeley 17 Feb '05

17 Feb '05

Ooops! what was that? did I just hear The Internet break? Oh dear. ;-) jamie clue:depeer

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Feb '05

16 Feb '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: AS24318 as-name: NZRR-AS24318 descr: MinEdu descr: WIX peering at '202.7.0.69' descr: see Citylink RT job #1647 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24318 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050217 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24318 descr: Route set advertised to AS9439 by MinEdu - AS24318 members: 192.105.10.0/24^24-29, 202.37.32.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050217 source: NZRR

1 0

NZNOG '05 videos now up
by Jeremy Naylor 16 Feb '05

16 Feb '05

Hey guys, The videos from the NZNOG '05 conference are available online, at: http://www.r2.co.nz/20050203 Feedback to richard.naylor(a)r2.co.nz or jeremy.naylor(a)r2.co.nz Thanks, Jeremy Naylor p: +64 21 374 689 e: jeremy.naylor(a)r2.co.nz w: http://www.r2.co.nz/~jeremy w: http://e-living.wellington.net.nz -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14/02/2005

1 0

Ape looking glass for 202.7.5.32/29
by Barry Murphy 15 Feb '05

15 Feb '05

Hey guys, Looking at ape looking glass for the ip range above (which has been supplied to me by citylink) is already being advertised by another provider (see below). How will this effect me as Maxnet will be advertising this route soon; how does one get an old range removed from rs1 & rs2? BGP routing table entry for 202.7.5.0/24 Paths: (1 available, best #1, table Default-IP-Routing-Table) Advertised to non peer-group peers: 192.203.154.12 192.203.154.14 192.203.154.16 192.203.154.17 192.203.154.28 192.203.154.29 192.203.154.32 192.203.154.33 192.203.154.36 192.203.154.37 192.203.154.44 192.203.154.46 192.203.154.49 192.203.154.67 192.203.154.78 192.203.154.80 192.203.154.81 192.203.154.86 192.203.154.90 192.203.154.91 192.203.154.98 192.203.154.99 192.203.154.101 192.203.154.104 192.203.154.107 192.203.154.108 192.203.154.109 192.203.154.111 192.203.154.112 192.203.154.114 192.203.154.115 23754 192.203.154.4 from 192.203.154.4 (192.203.154.4) Origin IGP, metric 0, localpref 100, valid, external, best Last update: Fri Jan 9 02:11:17 1981 Thanks Barry

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1887] Routing updates for APE Route Servers (fwd) - Date: Wed, 16 Feb 2005 13:57:04 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161356370.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: Route set advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-27, 161.29.0.0/16^16-27, 161.65.0.0/16^16-27, 192.88.85.0/24^24-27, 192.133.31.0/24^24-27, 202.36.226.0/24^24-27, 202.37.86.0/23^23-27, 202.49.80.0/23^23-27, 202.50.52.0/22^22-27, 202.50.196.0/22^22-27, 202.50.200.0/21^21-27, 202.50.208.0/20^20-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050127 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-27, 161.29.0.0/16^16-27, 161.65.0.0/16^16-27, 192.88.85.0/24^24-27, 192.133.31.0/24^24-27, 202.36.226.0/24^24-27, 202.37.86.0/23^23-27, 202.49.80.0/23^23-27, 202.50.52.0/22^22-27, 202.50.196.0/22^22-27, 202.50.200.0/21^21-27, 202.50.208.0/20^20-27, 202.53.176.0/20^20-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1886] Routing updates for WIX Route Servers (fwd) - Date: Wed, 16 Feb 2005 13:56:03 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161352230.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 192.88.85.0/24^24-29, 202.36.226.0/24^24-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.50.200.0/21^21-29, 202.50.208.0/20^20-29, 192.133.31.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: mplant(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.36.226.0/24^24-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.50.200.0/21^21-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Feb '05

15 Feb '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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Wed, 16 Feb 2005 13:51:34 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502161350450.13398(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: aut-num: AS9503 as-name: NZRR-AS9503 descr: FX Networks descr: APE peering at '192.203.154.115' descr: see Citylink RT job #1789 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9503 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050127 source: NZRR REPLACED BY: aut-num: AS9503 as-name: NZRR-AS9503 descr: FX Networks descr: APE peering at '192.203.154.115' descr: see Citylink RT job #1789 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9503 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9503 notify: rpsl-admin(a)nzix.net notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050216 source: NZRR

1 0

FW: [Apnic-announce] Unable to travel to Kyoto to attend APNIC 19?
by Nurani Nimpuno 15 Feb '05

15 Feb '05

While I'm at it, I thought it'd be useful to forward this information too. The APNIC meeting is on next week (Mo-Fri) and as explained below, even if you can't travel to Kyoto for the meeting, you can participate in the meeting remotely through video streams, transcripts and jabber chat. The meeting programme is here: http://www.apnic.net/meetings/19/programme/ It's worth noting that 9am in Kyoto is 1pm in NZ. Cheers, Nurani Nimpuno APNIC -----Original Message----- From: apnic-announce-bounces(a)lists.apnic.net [mailto:apnic-announce-bounces(a)lists.apnic.net] On Behalf Of Secretariat Sent: 14 February 2005 17:24 To: apnic-announce(a)apnic.net Subject: [Apnic-announce] Unable to travel to Kyoto to attend APNIC 19? --------------------------------------------- Unable to travel to Kyoto to attend APNIC 19? --------------------------------------------- Attend online instead! You can participate in the meeting from anywhere in the world by taking advantage of APNIC's online video, transcript and chat features. Live meeting features --------------------- The following APNIC 19 sessions will be video streamed and have live transcripts. You can have your input into each of these sessions via the Jabber chat room "room1". Your questions and comments will then be read out to the onsite attendees: Date Time Session ---- ----- ------- 22 Feb 16:00-17.30 Internet governance open forum 23 Feb 11.00-12.30 IPv6 technical SIG 14:00-17.30 Routing SIG 24 Feb 09:00-12.00 Policy SIG 14:00-15:30 Database SIG 16:00-17:30 DNS operations SIG 25 Feb 09:00-17:30 APNIC Members Meeting Note: all times quoted above are local times in Japan. Other APNIC SIG sessions that are not being video streamed will be available by Jabber chat room "room2". Full details on how to participate remotely are available at: http://www.apnic.net/meetings/19/programme/features.html New: webcast tutorials for participating universities ----------------------------------------------------- With assistance from School of Internet (SOI) Asia and the WIDE project, the following tutorials will be broadcast over the network to SOI partner universities: Date Time Session ---- ----- ------- 21 Feb 09:00-12:30 Dynamics of policy process 14:00-17:30 Spam prevention 22 Feb 09:00-10:30 Keynote: security protocol 11:00-12:30 Certification Authority 14:00-17:30 ISP Security Strategy Information about the broadcasts along with details of participating partners will shortly be available on the APNIC website and at: http://www.soi.wide.ad.jp ______________________________________________________________________ APNIC Secretariat <secretariat(a)apnic.net> APNIC ph +61 7 3858 3100 http://www.apnic.net fx +61 7 3858 3199 ______________________________________________________________________ See you at APNIC-19 Kyoto, Japan, 21 to 25 Feb 2005 and APRICOT 2005 http://www.apnic.net/meetings ---------------------------------------------------------------------- _______________________________________________ Apnic-announce mailing list Apnic-announce(a)lists.apnic.net http://mailman.apnic.net/mailman/listinfo/apnic-announce

1 0

Stuff.co.nz Routing & Peering @ Wix?
by Craig Spiers 15 Feb '05

15 Feb '05

Anyone noticed the ip block maintained by stuff.co.nz is not actually being advertised to the wix route servers? The route I'm receiving, is from Telstra Clear, and is a /24. BGP routing table entry for 202.135.111.0/24, version 235662 Paths: (1 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 4768 2687 203.167.219.181 from 203.167.219.181 (203.97.2.199) Origin incomplete, localpref 100, valid, external, best Are they another 'listen only' peer? Cheers, Craig - ConceptNET

18 26

Notes from NZNOG 05 history of peering session
by Ian McDonald 14 Feb '05

14 Feb '05

Notes from NZNOG 05 history of peering session Folks these are my notes taken down as clarifications/expansions to Joe's notes. Please feel free to tell me where I've got it wrong as I was writing quite quickly…. Talking to Joe there was a suggestion from someone that we put together a Wiki to collect this altogether as a NZ Internet History. Sounds good to me and we could add whole sections on 0867, IPNet and start writing active history on UBS etc. Joe mentioned David Dixon (KCBBS) had done a history page of Internet in NZ which may be a good starting point along with his presentation, these notes and everybody's thoughts... Does anybody have a spare place for a Wiki etc? In the short term do the WLUG members mind if I start a page on there as a temporary home? 1989 KCBBS started Internet link doubled at Waikato from 2.4 to 4.8 Kb/sec Original connection into Waikato was CSNET (sp ??) Connected to DSIR through DSIR routers – 4.8 K links on PC after failing to get working on X25 – Massey was also piggy backed off this as well 1989-1996 Nearly every routing protocol was used except BGP Clear was back through to MCI In effect peering at universities through Tuianet – This was pulled after DOS attack around 1995 at Cybernet conference against ICONZ. Paid for charging for capacity at this time – world leading at the time FreeNet in Wellington 1997/1998 – Home Fibre project canned by Telecom – When did it start? 1998 ADSL launch announced – this was aimed primarily at video July 1998 202.7.0.0/23 – came out of Dunedin City Council. Attempts to give parts of this out to customers through ISPs Citylink – unique as MAN and exchange building out to ISPs 1998 When National Library peered it was on a 386 notebook with two Ethernet cards running Linux 1999 Joe had idea of using Sky tower for peering after riding on a bus and seeing it looming above him ICONZ, Iprolink, KCBBS hosted an abortive exchange through ISDN. Centrex suggested by Max Gustin for this as well. Level 48 at Sky Tower was logical because Clear had fibre and could host internal aerials there also due to type of glass. Correction to a slide – Roger found switch not Richard 1999 192.203.154.0/24 – original owner was Children's Discovery Centre (not sure of this location as didn't hear clearly) Order of acquisitions: Saturn eats Paradise Telstra eats Netlink Telstra eats Saturn i4free was using Clear Network 1994 or 1996 One of International cables broken. Pacrim East built before Pacrim West. Shortly after Pacrim East failed. A couple of people suggested that this was due to a ship pulling anchor just after fixing something else. Between 1995/1996 and 2001. Waikato no longer main connectivity. Rex Croft not looking after .nz. Telecom/Netway got it because nobody else wanted it. Chello ran flat rate cable in Wellington until getting killed in 2001 by Napster. Had a GRE tunnel to Midwest America 2003 MCI were selling Voyager transport. Satellite connection to OzEmail – GRE tunnel also through terrestrial. Subsequent DS3 to Sydney – Late 2003/early 2003 Before Southern Cross Clear and Telecom were sending large packets via satellite and small via cable to help get more traffic through It was May 2004 not Nov 2004 Telstra announce intention to de-peer from APE Early 2004 Telecom withdrew route servers from Exchange Mid 2003 Xtra becomes more residential only. Global Gateway/CID for businesses. Was it at this time Xtra was folded back into Telecom company or earlier?

2 2