-original message- Subject: NZNOG Digest, Vol 88, Issue 15 From: nznog-request(a)list.waikato.ac.nz Date: 24/04/2010 12:00 pm Send NZNOG mailing list submissions to nznog(a)list.waikato.ac.nz To subscribe or unsubscribe via the World Wide Web, visit http://list.waikato.ac.nz/mailman/listinfo/nznog or, via email, send a message with subject or body 'help' to nznog-request(a)list.waikato.ac.nz You can reach the person managing the list at nznog-owner(a)list.waikato.ac.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of NZNOG digest..." Today's Topics: 1. NZRR Route Registry Update (NZRR Database Notifications) 2. Xtra BBA Issue with Cisco 877 (Terry Wilson) 3. Re: Xtra BBA Issue with Cisco 877 (Philip D'Ath) 4. Re: Request for Information from anyone providing V6 services in NZ (Joel Wiramu Pauling) 5. Re: Xtra BBA Issue with Cisco 877 (Terry Wilson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 Apr 2010 12:03:29 +1200 From: NZRR Database Notifications <rpsl-admin(a)nzix.net> To: nznog(a)list.waikato.ac.nz Subject: [nznog] NZRR Route Registry Update Message-ID: <E1O56Mj-0004w8-I7(a)totti.citylink.co.nz> 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: AS9281:RS-ROUTES:AS38477 descr: Route set advertised to AS9281 by Unleash - AS38477 members: 113.130.120.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: michael(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100415 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS38477 descr: advertised to AS9281 by Unleash - AS38477 members: 116.90.128.0/20^20-29, 113.130.120.0/22^22-29, 131.203.134.0/23^23-29, 202.6.116.0/23^23-29, 131.203.133.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)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100423 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 2 Date: Fri, 23 Apr 2010 12:30:20 +1200 From: "Terry Wilson" <terry(a)pds-dn.co.nz> To: <NZNOG(a)list.waikato.ac.nz> Subject: [nznog] Xtra BBA Issue with Cisco 877 Message-ID: <8C5232314BEE4D43A980918BD0EE1B7C7ED5F3(a)pds-mail02.PDS> Content-Type: text/plain; charset="us-ascii" Afternoon, I'm struggling with an issue that I'm hoping someone might be able to shed some light on for us. New connection in Queenstown (new phone + data) with ADSL enabled on line. Had some issues initially with the connection going down while the IP address was assigned, Telecom have resolved this and the 2Wire modem now reports that it is up and connected. Trying to connect a Cisco 877 into the same line, we get ATM to come up (CD light is on) but PPP will not come up; talking user through it but everything looks ok. I have had the router sent back down here and it tests fine on our existing Telecom ADSL test connection, back on site and it still won't get an IP or authenticate. T3G coverage is pretty rubbish so I can't remote control from here; may need to find a competent tech in Queenstown to go over and have a look for us. Any suggestions would be appreciated; been working on this with Telecom for four days now and as far as they are concerned it's a Cisco issue. Thanks, Terry ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal #####################################################################################