September 2008 - NZNOG - lists.nznog.org

Cisco advisories 24 Sept 2008
by Nathan Ward 24 Sep '08

24 Sep '08

Sorry if you've seen this already. Big day over at Cisco, 12 advisories. http://www.cisco.com/warp/public/707/cisco-sa-20080924-bundle.shtml Of particular interest to operators I know about in NZ are: - L2TP bug that causes a specially crafted packet to trigger a reload - Bug on uBR7200 and 10000 that causes a reload with a special crafted packet - MPLS bug on newer boxes that causes a reload with a special packet - Bugs in the SIP stack that can cause a reload of the device remotel Check out the URL above for more juicy details. -- Nathan Ward

1 0

Solarix - Peering on APE
by Craig Spiers 23 Sep '08

23 Sep '08

Hi All, We are now peering on APE. Those wishing to peer with us directly, please contact me off list. I would strongly suggest it.. as it appears that most people seem to have an advertise all, accept none policy in regards to the route servers. Cheers Kind Regards, Craig Spiers - Network Manager Solarix Limited DDI: +64 9 974 4753 | FAX: +64 9 523 8057 MOB: +64 21 857 183 | <mailto:craig.spiers(a)solarix.co.nz?subject=From%20Signature> email: craig.spiers(a)solarix.co.nz The information contained in this email is privileged and confidential and intended for the addressee only. If you are not the intended recipient you are asked to respect that confidentiality and not disclose, copy or make use of its contents. If received in error you are asked to destroy this email and contact the sender immediately.

4 3

Re: [nznog] Solarix - Peering on APE
by Andy Linton 23 Sep '08

23 Sep '08

I sent this to Craig directly when I wanted you all to see it (:-) On Wed, Sep 24, 2008 at 8:43 AM, Andy Linton <asjl(a)lpnz.org> wrote: > On Tue, Sep 23, 2008 at 7:35 PM, Craig Spiers <craig(a)spiers.gen.nz> wrote: >> Hi All, >> >> >> >> We are now peering on APE. Those wishing to peer with us directly, please >> contact me off list. >> >> I would strongly suggest it.. as it appears that most people seem to have an >> advertise all, accept none policy in regards to the route servers. > > If that's the case then it's kind of disappointing. Arranging to have > assymetric routing would seem to rather defeat the object of peering > with the route servers. > > All the route servers operate a strong policy of only importing the > routes that peers have said they'll advertise and exporting the union > of those sets minus default and a list of bogons as defined on the > Team Cymru website. > > It's quite easy to look at what the route servers are importing and > exporting wrt a particular AS on the Looking Glass page at > http://nzix.net > > Of course that doesn't tell anyone if a particular peer is running an > "accept none" policy. You'd have to wonder if anyone who does this > will make a better fist of getting a bilateral peering set up any > better. >

2 1

Sell me your unused outbound capacity.
by Nathan Ward 22 Sep '08

22 Sep '08

Sorry for this post, but it's a request that few sales droids understand, this seems to be the only way to get it to all the people in-country who do understand this without having to call you all up individually. My current colocation provider have consistently demonstrated their inability to provide service to the CIR that I pay for, so I'm looking around at alternative options. If you are a provider with lots of megabits of traffic that is predominantly inbound (ie. you have lots of customers on ADSL tails or whatever), you have lots of outbound capacity that you're paying for but not selling. Sell it to me, cheaper than your sales droids would normally sell a symmetric circuit for, because I'm the opposite of you - I push significantly more traffic than I than pull - and I don't want to buy bits I don't use either. I'm interested in both international and domestic capacity, for web hosting and media streaming (no, not for P2P or anything like that). IPv6 is a bonus. Also, anyone else who has a similar need for outbound capacity for this sort of thing give me a yell, it might be worthwhile hooking up. All responses off-list please, including flames. Um, beer for anyone who hooks me up with someone I eventually buy from. Phew. Beer flowing in the same direction as the money, *and* a preference for IPv6 service? You saw it here first. -- Nathan Ward

1 0

23 September
by Richard Naylor 22 Sep '08

22 Sep '08

Tomorrow is 23 September and TVNZ 7 and InternetNZ have their ICT Debate scheduled to start at around 9pm, after the news. While you wait for this exciting event to start, you can watch the Tawa Schools Music Festival, live from the Michael Fowler Center in Wellington. http://www.r2.co.nz/20080923 starting at 7:30pm and running for around 2 hours. On 4 Oct 1994, our first public webcast, was the Tawa Schools Music Festival, so the webcast tomorrow is for us a trip down memory lane. Its also a fun event. You can see the 1994 event at http://www.r2.co.nz/19941004 In 1994, the MFC was connected to the Internet by fiber via WCC, which was connected to VUW by 2Mbps microwave. The concert webcast had 16 viewers in 12 countries. It impressed then Mayor Fran Wilde so much that she wrote about it in her weekly column in the Evening Post. So maybe a question for the politicians in the debate is - why after 14 years are people still debating whether we need fiber ? Why is it all taking so long ? But maybe its just better to drink beer and enjoy the concert. Cheers - Richard

8 7

MTUs on internet transit and peering
by Alastair Johnson 21 Sep '08

21 Sep '08

Hi, I was wondering if anyone has seen a general trend to supporting >1500B MTUs on Internet transit and peering sessions? I recall from years ago that AGC/ANC/PacNet supported interface-default MTUs, meaning that ATM connected customers had 4470B MTU. Obviously these days with most people running GE or XE in their networks with MPLS and 802.1Q you are looking at networks capable internally of jumbograms, but is anyone running this across network boundaries? Are there any plans for the NZ IXs to be jumbo-capable? I'd be interested in hearing from anyone who is jumbo-enabled on their transit connections, and particularly interested in hearing if they are seeing any significant number of packets that are >1500B on the Internet. aj

6 7

Auckland IPv6 Internet Exchange
by Andy Linton 21 Sep '08

21 Sep '08

We've been working on changes to the IPv6 exchange so that we have a process for IPv6 that is similar to that for IPv4. There's a new web page at http://v6ix.nzix.net/ape6/ with more info. For those who are current peers (http://v6ix.nzix.net/ape6/peers.html) you'll be able to request changes in the same way as you can for IPv4 using this page http://v6ix.nzix.net/cgi-bin/ape6/ChangeRoutes.cgi You'll also be able to see what's going on at the Looking Glass at http://nzix.net/cgi-bin/lg.cgi?router=rs1-v6.ape.net.nz and http://nzix.net/cgi-bin/lg.cgi?router=rs2-v6.ape.net.nz We'll be adding a second IPv6 route server rs2-v6.ape.net.nz very shortly. Changes to IPv6 route announcements will come to the nznog list as they currently do for IPv4. If you're not already peering with IPv6 see the link to the application form at http://v6ix.nzix.net/ape6/

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Sep '08

21 Sep '08

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: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 descr: APE peering at '192.203.154.5' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink remarks: DPE peering at '218.100.23.3' remarks: see Citylink RT job #1927 remarks: WIX peering at '202.7.0.7' remarks: see Citylink RT job #4541 remarks: APE peering at '192.203.154.5' remarks: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 21 Sep '08

21 Sep '08

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: ------------------------------------------------------------ --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS24021 descr: Route set advertised to AS9560 by Tui Gateway - AS24021 mp-members: 2402:6000:0:0:0:0:0:0/32^32-64, 2406:E000:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nward(a)daork.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS17435 descr: Route set advertised to AS9560 by WorldxChange - AS17435 mp-members: 2001:E20:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: gsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080911 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS18119 descr: Route set advertised to AS9560 by LinuxNet - AS18119 mp-members: 2001:4428:0:0:0:0:0:0/32^32-64 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 20080911 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS4770 descr: Route set advertised to AS9560 by ICONZ - AS4770 mp-members: 2001:F50:0:0:0:0:0:0/32^32-64, 2405:6000:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080911 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS24005 descr: Route set advertised to AS9560 by SafeNZ - AS24005 mp-members: 2407:1000:0:0:0:0:0:0/32^32-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)safenz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS23710 descr: Route set advertised to AS9560 by ISC - F Root - AS23710 mp-members: 2001:500:2f::/48 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)safenz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS9896 descr: Route set advertised to AS9560 by SDS-Net - AS9896 mp-members: 2001:4403:DEAD:0:0:0:0:0/48^48-64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.robb(a)team.telstraclear.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR --- NEW OBJECT CREATION: route-set: AS9560:RS-ROUTES6:AS23754 descr: Route set advertised to AS9560 by CityLink - AS23754 mp-members: 2001:4410:0:0:0:0:0:0/32^32-64 mp-members: 2001:470:1f01:3795::/64 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080922 changed: rpsl-admin(a)nzix.net 20080922 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Net outage last night?
by Dave Green 21 Sep '08

21 Sep '08

Justin Cook wrote: > On Fri, Sep 19, 2008 at 6:42 AM, Dave Green <dave.green(a)snowline.co.nz > <mailto:dave.green(a)snowline.co.nz>> wrote: > > Simon Lyall wrote: > > >Seriously, we've had people complaining about Orcon continuously for > >months here, if it's bad enough then there must be a few other > companies > >willing to take your money. Obviously it's not putting any > pressure on > >Orcon to fix it. > > > > > FWIW ... I use a supposedly 1Mbps Orcon sattelite service and, using > Youtube as my download test, find I can get .7-1.5Mbps sustained > download rates early morning ~4am-7am but only 200-300kbps most > evenings. I've checked with consumerspeedtest.org.nz > <http://consumerspeedtest.org.nz> at times when the > download is really slow and it tells me that I still have ~1Mpbs > download rate so not sure where the bottleneck is. Given that Orcon or > others seem to be pushing cheap sattelite service out to rural areas I > don't expect performance to improve any time soon. > > Dave > > > Simon obviously outlined the proper steps to take here, but if you're > going to ghettotest it, try using speedtest.net > <http://speedtest.net>. At least then you can try testing against > remote locations. Yes, tried that. Remote speedtest locations give similar poor results 200-300kbps, while consumer gives ~1Mbps measured at the same time of day. I'd be interested to know where the consumer test is run from, it uses Ookla as do many of the other test sites and I don't know if Ookla hosts the tests or provides an app to be used by the test provider. Dave

11 13