- NZNOG - lists.nznog.org

The New Zealand Network Operators' Group
by Donald Neal 31 Jan '06

31 Jan '06

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information. The most recent speakers to be confirmed are Mike Hughes, CTO of London Internet Exchange and Arron Scott of Cisco New Zealand. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 900 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

Information on Global Web Productions
by Craig Whitmore 30 Jan '06

30 Jan '06

Hi there Has anyone got any information on Global Web Productions and the NZ Commerce Comissions Involvement with them in getting them shut down in 1994 with the US CAN-SPAM? Seaching on the web and on the comcom website I cannot find any information at all what involvement they (the comcom) had or what they did or who the people in New Zealand where. Thanks Craig

4 5

Notification of NZRR Database changes
by NZRR Database Notifications 29 Jan '06

29 Jan '06

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: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons 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 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons import: from AS24385:AS-PRIVATE accept AS24385:RS-ROUTES:PeerAS import: from AS24385:AS-PUBLIC accept AS24385:RS-ROUTES:PeerAS export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PRIVATE announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons 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 20060130 source: NZRR

1 0

NZNOG06
by Andrew Thompson 29 Jan '06

29 Jan '06

Hi, I am trying to find the registration details for the conference this year but only the schedule seems to be up. I'm just after the cost so I can hit up my boss to shout me. cheers, Andrew

2 1

WIX Issues Saturday Afternoon
by Jonathan Brewer 27 Jan '06

27 Jan '06

Hi Folks, There were some issues with the WIX this afternoon, from approx 11:50 until around 15:00, affecting several connected ISPs. Could someone with an in-depth knowledge of what happened fill us in? Cheers, Jon

2 1

Strange NZ Domain Names and Contents
by Craig Whitmore 26 Jan '06

26 Jan '06

I was looking on Google this morning and came across these strange groups of .NZ domain names as below. Most of them are just recently been registered. (Maybe they are domains which have just become available from others who didn't want them and they where picked up to hopefully to get hits. The name of the sites have nothing to do with anything which is on the sites and all they do is link to lots of places and banners. I can't see anything really illegal on them (apart from linking to know spam/buy viagra etc online sites). Just a heads up for people. Does the NZ Internet Community want people registering 100's of generic .nz domain names in the future to just to get hits and advertise others? Thanks Craig http://www.globalchessenterprises.co.nz http://www.aa-auckland.org.nz www.haynesfilm.co.nz http://gt40.co.nz http://www.fastfinish.co.nz http://www.dissidentvoice.org.nz www.promocodirect.co.nz/ www.heavyloungesuite.co.nz www.farmbarn.co.nz http://www.fastaccess.co.nz/ http://www.ecmtoa.co.nz/ http://www.shaktimigrant.org.nz http://www.infobrok.co.nz

5 5

Re: [nznog] Strange NZ Domain Names and Contents
by Craig Whitmore 26 Jan '06

26 Jan '06

> > > Purchasing what are normally perscription drugs, from a website... > > If the clue phone doesnt ring for that one, no policy change will protect > these people. > > But people ARE legally selling drugs on the Net in NZ, but they are doing it legally.. You send the script to them (or get the doctor to), and they will send you the drugs in the mail. Some Legal Pharmacies: http://www.netpharmacy.co.nz/ http://www.pharmacyweb.co.nz http://www.quinspharmacy.co.nz/ Thanks Craig

5 4

Re: [nznog] Strange NZ Domain Names and Contents
by Craig Whitmore 25 Jan '06

25 Jan '06

Replying to myself but... There is even illegal porn advertised on .co.nz domain names with its registered details in the Russian Federation.(I shant say more) I guess registrars can't vet what people are using the domain names for all the time, but a few of the registrar's I've looked at T&C saying the domain names they are charging the customer for must be used for legal purposes. Thanks Craig > > Also good examples are www.pharmacycare.co.nz and > http://www.discountmeds.co.nz/. Talking for myself.

3 2

NZNOG conference
by David Robb 24 Jan '06

24 Jan '06

Is there any further information available for this? ie costs, who else is speaking? I'm going to need to make a decision very soon as to whether or not I can justify my attendance. Thanks, --David

1 0

WorldxChange Peering WIX / APE
by Term 23 Jan '06

23 Jan '06

1 0

LinuxNet / ACS peering at APE
by Lincoln Reid 23 Jan '06

23 Jan '06

Hi, LinuxNet / ACS is now peering at APE. Ideally we would like to peer with pretty much everyone. If we have an existing bilateral peering relationship with you at WIX and you have an APE presence, feel free to get in touch. I am also interested in hearing from people who want to bilaterally IPv6 peer at WIX or APE. Our details are as follows: ASN: 18119 WIX: 202.7.0.245 : 2001:7fa:3:ca07::f5 APE: 192.203.154.117 : 2001:7fa:4:c0cb::9a75 The IPv4 prefix list is at: http://www.linuxnet.co.nz/linuxnet-prefixlist.txt The IPv6 prefix list is at: http://www.linuxnet.co.nz/linuxnet-prefixlist-v6.txt Cheers, -- Lincoln Reid Systems Engineer ACS - AS18119 lincoln(a)linuxnet.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

1 0

Peering Policies
by Webmaster 20 Jan '06

20 Jan '06

I am currently working on a paper about peering in New Zealand. If you are involved with peering policy in your organisation, could you please send me offlist a copy of your company's policy (or a link to it). Many thanks, Richard >>> "Craig Humphrey" <Craig.Humphrey.Work(a)paradise.net.nz> 01/20/06 2:02 PM >>> _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

CISCO 805 Serial/Ethernet to go to a good home...
by Craig Humphrey 19 Jan '06

19 Jan '06

Hi People, I've come across an old CISCO 805 with serial and ethernet ports on the back. No power, no idea if it works. If you want/need one and are in the Auckland area, give me a yell off list, I'll only charge you a beer if it works... Later'ish Craig

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jan '06

19 Jan '06

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:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.182.192.0/19^19-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)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051202 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 19 Jan '06

19 Jan '06

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:AS17435 descr: Route set advertised to AS9439 by WorldxChange Communications - AS17435 members: 58.28.0.0/16^16-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)wxnz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Jan '06

18 Jan '06

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:AS24025 descr: Route set for Helix - AS24025 members: 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040304 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24025 descr: advertised to AS9560 by Helix - AS24025 members: 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.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)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.240.0/22 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.14.217.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- OBJECT BELOW CREATED: route: 202.49.59.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR --- PREVIOUS OBJECT: route: 202.50.176.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040304 source: NZRR REPLACED BY: route: 202.50.176.0/24 descr: Route for Helix - AS24025 origin: AS24025 notify: rpsl-admin(a)nzix.net notify: noc(a)helix.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060119 source: NZRR

1 0

Re: [nznog] Mail issues in/out of China
by Scott Weeks 18 Jan '06

18 Jan '06

> Thanks for many replies. Guess we can add 'China' to the > keywords such as 'beer' to get everyone's attention!! Nah, Chinese beer isn't all that: http://en.wikipedia.org/wiki/Chinese_beer Further... http://www.foodconsumer.org/777/8/Formaldehyde_illegally_used_in_Chinese_be… scott :-) ----- Original Message Follows ----- From: "Gary T. Benner" <gary(a)123.co.nz> To: jabley(a)isc.org Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Mail issues in/out of China Date: Thu, 19 Jan 2006 12:02:40 +1300 > [Reply] > > HI all, > > Thanks for many replies. Guess we can add 'China' to the > keywords such as 'beer' to get everyone's attention!! > > cheers > > Gary > > At 07:21 on 19/01/2006 you wrote > >To : truman(a)suspicious.org,nznog(a)list.waikato.ac.nz > >CC : nznog(a)list.waikato.ac.nz, > >From: Joe Abley, jabley(a)isc.org > >Content Type: text/plain > >Attached: > > > > >On 17-Jan-2006, at 23:57, Truman Boyes wrote: > > > >> I have used SIP phones in China and I can tell you that > some of the >> firewalls are a lot more advanced than just > blocking applications. I >> was able to place some types > of calls via my USA DDI, while others >> were redirected > to a local chinese gateway. Essentially that means >> that > ALGs were inspecting the SIP invite messages ... quite >> > interesting ... > > >Presumably this is the difference between living in a > region where >the authorities are open about intercepting > communications, in >contrast to other places where > communications are routinely >intercepted in secret? > > > > >Joe > > > >_______________________________________________ > >NZNOG mailing list > >NZNOG(a)list.waikato.ac.nz > >http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > Ref#: 41006 > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Mail issues in/out of China
by Gary T. Benner 18 Jan '06

18 Jan '06

[Reply] HI all, Thanks for many replies. Guess we can add 'China' to the keywords such as 'beer' to get everyone's attention!! cheers Gary At 07:21 on 19/01/2006 you wrote >To : truman(a)suspicious.org,nznog(a)list.waikato.ac.nz >CC : nznog(a)list.waikato.ac.nz, >From: Joe Abley, jabley(a)isc.org >Content Type: text/plain >Attached: > > >On 17-Jan-2006, at 23:57, Truman Boyes wrote: > >> I have used SIP phones in China and I can tell you that some of the >> firewalls are a lot more advanced than just blocking applications. I >> was able to place some types of calls via my USA DDI, while others >> were redirected to a local chinese gateway. Essentially that means >> that ALGs were inspecting the SIP invite messages ... quite >> interesting ... > >Presumably this is the difference between living in a region where >the authorities are open about intercepting communications, in >contrast to other places where communications are routinely >intercepted in secret? > > >Joe > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog > Ref#: 41006

1 0

Apricot2006 Registrations
by Andy Linton 18 Jan '06

18 Jan '06

I know may of you will be at NZNOG in March but if you need more conference time then the annual Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) event is happening in Perth, Western Australia from 22nd February to 3rd March 2006. Registrations for the event are open and early bird is closing on the 14th Jan (tomorrow!). This is the first time that APRICOT will be held in Australia and I've been told they'd really love to see lots of us coming over for it! APRICOT consists of workshops, tutorials, conference, as well as the 6 monthly APNIC meeting. The APRICOT 2006 programme includes: Workshops 22 - 26 February Tutorials 27 - 28 February Conference 1 - 2 March APNIC Member Meeting 3 March Full information about APRICOT 2006 can be seen at http://www.2006.apricot.net Program information is at: http://www.apricot2006.net/index.php/fuseaction/home.program Registration information is at: http://www.2006.apricot.net/index.php/fuseaction/home.registration You are encouraged to register as soon as possible as the early bird registration discount expires on the 14th of January. If you aren't an AU or NZ citizen, visa information is at: http://www.apricot2006.net/index.php/fuseaction/home.visas You must register on-line before submitting a visa application - note that application times for visas for non-ETA countries can be quite lengthy, so please start the registration and application process as soon as you can. You can select a checkbox to request an invitation letter from us to be used for your visa application during registration if you require one, this is an automated process. Accommodation information is at: http://www.2006.apricot.net/index.php/fuseaction/home.accommodation You are encouraged to make arrangements for accommodation as soon as possible as the APRICOT discounted room block expires on the 18th of January. After this date we must release remaining rooms, you then need to compete with the general tourist public for room availability. Sponsorship opportunities still exist for interested companies. Information on Sponsorship is available online at: http://www.apricot2006.net/index.php/fuseaction/home.sponsorship

5 4

Mail issues in/out of China
by Gary T. Benner 17 Jan '06

17 Jan '06

HI all, I have a client with staff member in China who has had consistent difficulty accessing our mail server, both using pop *and* the webmail client. Yet access from within NZ has been faultless. If anyone has had experience in this area, are there issues relating to the Chinese Authorities intercepting such communications, or would it be just to do with the connection? regards Gary Benner 123 Internet Ltd

7 6

Re: [nznog] Studio Cam Update
by Webmaster 16 Jan '06

16 Jan '06

Just so that operators are kept informed, we have been running radio interviews with a strong visual component on the Matinee Idle studio cam. Yesterday was Pets, today is Tattoos. Interest in both the live audio and studio cams has been very high. cheers, Richard Hulse Radio NZ

2 1

IPv6 Connect NZ Domain Servers
by Philip D'Ath 15 Jan '06

15 Jan '06

Does anyone offer commercial hosting of NZ zone files on DNS servers that are IPv6 connected?

2 1

Studio Cam Update
by Webmaster 13 Jan '06

13 Jan '06

Operators should be aware that we are planning an on-air promotion using our studio cams next week. This is not yet confirmed, but I thought I'd give everyone plenty of warning just in case we go ahead. The studio cams operate during the Matinee Idle radio show, 12.30 pm - 5pm on weekdays. (www.radionz.co.nz/phil) The promotion is likely to cause a huge increase in the number of simultaneous viewers. To date we've have seen data rates of between 10 and 40 Mb/s during the show. More than half this data is NZ bound from the US server. The 384 kbs stream is the most popular. There was such a high demand from listeners for the higher data rates, that after the first day of the show we opened these up to customers of non-peering ISPs. regards, Richard Hulse regards, Richard

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Jan '06

13 Jan '06

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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 74.0.0.0/8^+, 75.0.0.0/8^+, 76.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 89.0.0.0/8^+, 90.0.0.0/8^+, 91.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 121.0.0.0/8^+, 122.0.0.0/8^+, 123.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 189.0.0.0/8^+, 190.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 changed: rpsl-admin(a)nzix.net 20060113 source: NZRR

6 5

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jan '06

11 Jan '06

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:AS64524 descr: advertised to AS9439 by Institute of Chartered Accountants of NZ - AS64524 members: 202.27.78.0/24^24-29, 202.27.79.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: nathan.cottle(a)icanz.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050221 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64524 descr: advertised to AS9439 by Institute of Chartered Accountants of New Zealand - AS64524 members: 203.97.94.0/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: paul.ross(a)nzica.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060112 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jan '06

11 Jan '06

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:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.20.6.0/24^24-29, 202.36.119.0/24^24-29, 202.46.190.0/24^24-29, 202.49.159.0/24^24-29, 202.78.240.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: netadmin(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050119 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24226 descr: advertised to AS9439 by Catalyst IT - AS24226 members: 202.78.240.0/21^21-29, 202.36.119.0/24^24-29, 202.46.190.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: routing(a)catalyst.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060112 source: NZRR

1 0

IANA IPv4 allocations and bogon updates: 121/8, 122/8, and 123/8
by Rob Thomas 09 Jan '06

09 Jan '06

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those of you who receive this note in multiple forums. ] Hi, team. The numerous Team Cymru bogon projects have been updated as of 05 JAN 2006 to reflect the following IANA allocation made on 05 JAN 2006: 121/8 Jan 06 APNIC (whois.apnic.net) 122/8 Jan 06 APNIC (whois.apnic.net) 123/8 Jan 06 APNIC (whois.apnic.net) IANA allocations change over time, so please check regularly to ensure you have the latest filters if you are not using the bogon BGP feed(s). We do announce updates to the bogon projects to sundry lists, such as the bogon-announce list. We can not stress this point strongly enough - these allocations change. If you do not adjust your filters, you will be unable to access perhaps large portions of the Internet. Worse yet, you may end up blocking access for people who transit through you. Please do not apply any filters or blocks to your network without carefully considering the ramifications of doing so. As a point of reference, the Team Cymru master Bogon Reference Page can be found here: <http://www.cymru.com/Bogons/> A quick summary of the documents and projects that have been updated include the following: HTTP The Bogon List - <http://www.cymru.com/Documents/bogon-list.html> The Text Bogon Lists - <http://www.cymru.com/Documents/bogon-bn-nonagg.txt> - <http://www.cymru.com/Documents/bogon-bn-agg.txt> Secure BIND Template - <http://www.cymru.com/Documents/secure-bind-template.html> Secure IOS Template (Cisco) - <http://www.cymru.com/Documents/secure-ios-template.html> Secure BGP Template (Cisco) - <http://www.cymru.com/Documents/secure-bgp-template.html> Secure JUNOS Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-template.htm> Secure JUNOS BGP Template (Juniper) - <http://www.cymru.com/gillsr/documents/junos-bgp-template.htm> Ingress Prefix Filter Templates, Loose and Strict (Cisco) - <ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix- Filter-Templates/> Ingress Prefix Filter Template, Loose (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-loose.htm> Ingress Prefix Filter Template, Strict (Juniper) - <http://www.cymru.com/gillsr/documents/junos-isp-prefix- filter-strict.htm> BGP Bogon route-server for AUTOMATED updates of bogon filters - All bogon route-server peers have already received the appropriate BGP prefix updates. - <http://www.cymru.com/BGP/bogon-rs.html> RADb fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#radb> RIPE NCC fltr-unallocated fltr-martian fltr-bogons - <http://www.cymru.com/Bogons/index.html#ripe> DNS Bogon (bogons.cymru.com) zone - <http://www.cymru.com/Bogons/index.html#dns> Monitoring Bogon prefix monitoring - <http://www.cymru.com/BGP/robbgp-bogon.html> Bogus ASN monitoring - <http://www.cymru.com/BGP/asnbogusrep.html> Please feel free to contact Team Cymru <team-cymru(a)cymru.com> with any comments, questions, or concerns. Thank you for your continued support. Thanks, Rob. - -- Rob Thomas Team Cymru http://www.cymru.com/ ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQ8MiDlkX3QAo5sgJAQEHwwP/X6Jh/sZ+j46KosfJ6H3+Wzb7sE3xXjl9 ktuNLb7Xfvo0A4PwUSv5NF5aS4Yp1C5NWZcrBDKkwIMA4WcC7DZK+qvFHeOX7EVS vzXzpw2FGCyImU1m49qNR+437vM0CNVaeFeMc+zjHnnXlsAEVVIhwQ7lz0KE+rlM G2ZKbvaQRyw= =qtQ6 -----END PGP SIGNATURE-----

1 0

ANZ website broken?
by Blair Harrison 31 Dec '05

31 Dec '05

Hmm, Maybe someone pushed a wrong button? domain_name: anz.co.nz query_status: 210 PendingRelease domain_dateregistered: 1997-03-10T00:00:00+13:00 domain_datebilleduntil: 2006-01-01T00:00:00+13:00 domain_datelastmodified: 2005-12-31T22:01:03+13:00 domain_datecancelled: 2005-12-31T22:01:03+13:00 Oops. Internet banking still available via www.anz.com/nz at least. -Blair

1 0

Re: [nznog] Studio Cam Update
by Webmaster 26 Dec '05

26 Dec '05

After receiving a number of requests from people viewing the Matinee Idle studio cams, I have opened up access to the 384k and 2M streams to all comers. This means that all NZ consumers can watch the high rate streams if they want to, regardless of whether their ISP peers or not. Non-peering ISPs may see a big increase in international bandwidth usage between 12:30 pm and 5 pm daily on weekdays until 20 Jan 2006. regards, Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Streaming Event
by Ian Cogill 22 Dec '05

22 Dec '05

Hi There We will be providing live streams of the ASB Classic and Heineken Open tennis from Jan 2 - Jan 14 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. As it is the holidays we're not exctly sure how many people will be watching coverage online, so this is just a heads up. Regards Ian Cogill Systems Engineer TVNZ Interactive ===================================================================== CAUTION: This e-mail and any attachment(s) contains information that is intended to be read only by the named recipient(s). It may contain information that is confidential, proprietary or the subject of legal privilege. This information is not to be used by any other person and/or organisation. If you are not the intended recipient, please advise us immediately and delete this e-mail from your system. Do not use any information contained in it. ================================================================ For more information on the Television New Zealand Group, visit us online at http://www.tvnz.co.nz ================================================================

1 0

Studio Cam Update
by Webmaster 22 Dec '05

22 Dec '05

The studio cams for the Matinee Idle radio show are now in operation with a jpg slide: http://www.radionz.co.nz/nr/programmes/matineeidle I have noted on the web cam page that some customers may not be able to get the high bandwidth streams due to their ISP not peering. These consumers will get a message suggesting that they use one of the lower rate streams or contact their ISP. Time for a beer now, my work is done.... regards, Richard

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Dec '05

22 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: 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 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.57.145.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 20051223 source: NZRR --- PREVIOUS OBJECT: 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 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.57.145.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 20051223 source: NZRR

1 0

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

22 Dec '05

Pretty much every Cisco DSL router supports IPv6. We just need an ISP to start selling the IPv6 transit ... -----Original Message----- From: Richard Hector [mailto:richard(a)walnut.gen.nz] Sent: Thursday, 22 December 2005 2:46 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] ipv6 On Thu, 2005-12-22 at 14:35 +1300, Matt Brown wrote: > 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. To offer it on UBS, wouldn't your DSL router have to support IPv6? Do any of them? I suppose you could use either a plain modem, or one of those ones that bridges PPPoA to PPPoE, but I've never tried setting one up. Richard _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

9 11

SANOG VII - Mumbai, India, 16-24 January 2006
by Andy Linton 22 Dec '05

22 Dec '05

South Asian Network Operators Group (SANOG) VII 16-24 January 2006, Mumbai, India Hosted by ISPAI. SANOG VII Program Announcement SANOG VII program and agenda are now published on http://www.sanog.org/sanog7/. SANOG VII is being held by ISP Association of India (ISPAI) in Mumbai, India from 16-24 January 2006. Daniel Karrenberg, Chief Scientist, RIPE NCC and Paul Wilson, DG,APNIC will address the plenary session of SANOG VII. There will be 3 workshops, 10 tutorials, 3 BoFs and over 16 presentations during the event. APNIC will hold a special Open Policy Meeting Showcase at SANOG VII, and for the first time at SANOG, we'll have a Peering Panel and Debate. Registration Discounts available for ISPAI, APNIC, APIA members. Detailed information is available at http:/www.sanog.org/sanog7/ Program and Agenda: Three hands-on workshops: 16-20 January 2006 * ISP Routing and BGP Multihoming Workshop * IPv6 Essentials, Applications and Routing Workshop * Multicast Routing and Applications Workshop Ten Tutorials: 21-22 January 2006 * BGP and High Availability Routing Tutorial, Prasad Babu * DNS / DNSSec Deployment Tutorial, Champika Wijayatunga * IXP Construction and BGP Multihoming, Philip Smith, Gaurab Raj Upadhaya * L2VPN - Changing and Consolidating Networks - Paresh Shah, Md.Waris * Layer2 Attacks and Mitigation techniques, Yusuf Bhaiji * DDoS prevention in Service Provider Networks, Wireless Security,Pravin Mahajan * The Basics of Multicast - Marshall Eubanks, * QoS and Multicast on MPLS Networks , Rajesh Shinde * QoS on Low Bandwidth & High Delay Links, Prakash Shende Birds-of-a-Feather (Special Evening Sessions) : 21-23 January 2006 * Managed Services * Anti-SPAM Tools and Techniques * Internet Society (ISOC) BoF APNIC Special Sessions * APNIC Helpdesk sessions throughout SANOG VII * APNIC Open Policy Meeting Showcase on 24th January 2006 Two Days Conference Program : 23-24 January 2006 * Alternative architectures for Broadcast Video Distribution - Srinath Beldona, Cisco * RA-MPLS services - Kapil Kumar, Reliance * Network Infrastructure for IPTV - Saisree Subramanian, Wipro * Efficient Resource Broker Architecture to Provide Guaranteed QoS - Praveen Kumar, Anna University * Graceful Restart of Routing Protocols - Prasad Babu, Juniper * Backbone Architectures for NLD/ILD: Design; Optmization & Services - Chandan Mendiratta (Cisco) * Network Infrastructure Security in Cellular Data Networks: An Initial Investigation - Vishal Sharma (IIT-Bombay) * Traffic Engineering and Network Planning Tools for MPLS Networks - Dr. Girish P. Saraph (IIT-Bombay) * pmacct; a new player in the network management arena - Paolo Lucente (CNR-Italy) * Flow measurements from the packet-switched NREN PIONIER: technology and experience - Wiktor Procyk (Poznan S&N Center) * Interest Based Group Management Mechanisms for E-learning Design using the Peer to Peer Technologies - Surya (AIT) * Internet Routing Table Update - Philip Smith (Cisco) * INOC - DBA Update - Gaurab Raj Upadhaya ( PCH) * Data Network Management for Telecom Operators in ASIA - Sufi Faruq (AKTEL) Peering Penel and Debate * Nigel Titley, Peering Manager, FLAG Telecom * Sylvie Laperriere, Director- Peering, Teleglobe * Sharad Shangi, Net4India * Gaurab Raj Upadhaya, PCH, (moderator) Local Fellowships are still available. We expect a huge turn out from the region at this SANOG meeting owing to the popularity at previous meets. We also welcome participants from West Asia, with our established collaboration with the RIPE NCC. With more involvement of APNIC in the content of overall program, We hope you would be able to make it to this meeting. The meeting is open to everyone from the operational community, and thus anyone who wants to find out more about Internet operations in South Asia is welcome. You can register for SANOG by sending in the form available at www.sanog.org/sanog7 or using the online registration system. Registrations from inside India can be paid by DD Looking forward to seeing you there. Thanks - SANOG

1 0

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

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

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

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

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

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

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

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

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

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

16 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

NZ Security Notifications
by Brendan Murray 15 Dec '05

15 Dec '05

(apologies to members of members-discuss(a)internetnz.net.nz for duplication) Yesterday the topic of AusCERT came up on nznog. Many of you probably know that InternetNZ has formed a small group to look at the need/feasibility of a NZ based CERT. It is all in early days yet, but it might be a good time to start looking at some ways of improving security awareness here. We hope to raise some ideas for discussion at the nznog conference next year, but the recent email suggests we could start on some practical matters now. We would like to suggest creating a NZ security community with a nz-sec mailing list, for example. This would have the same sort of intent as the nsp-security mailing list, bringing in people with a genuine interest in security practice and incident handling. We feel that the CCIP list, while valuable, is informative rather than collaborative. The nznog list has been used for security issues where relevant, but network operations is the reason for nznog, not security management. Ultimately the list and list membership, or some variant, would become associated with a NZ CERT if one were to happen, but in the meantime InternetNZ would be happy to host and advertise a moderated list. 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) Brendan Murray Chairing the InternetNZ NZCERT Task Force.

7 7

Re: [nznog] NZ Security Notifications
by Barry Greene (bgreene) 14 Dec '05

14 Dec '05

For those who are interested, I've got a draft of some guidelines that can be used to create a group like nsp-sec-nz. Pop me a note and I'll send it. > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Wednesday, December 14, 2005 8:16 AM > To: Joe Abley > Cc: NZNOG List > Subject: Re: [nznog] NZ Security Notifications > > ] While an nsp-sec-nz list sounds like it could be lots of > fun, maybe ] it's also worth mentioning that it's perfectly > possible (and ] reasonable) for operators in nz who fit the > target demographic to ] become subscribers to the existing > nsp-sec list. > > Agreed! The mix of both nsp-sec and nsp-sec-nz would be > quite complimentary and useful. > > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Hotmail
by Jeremy Strachan 14 Dec '05

14 Dec '05

Probably B52 bombers and cruise missiles. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 15 December 2005 12:47 p.m. To: Simon Lyall Cc: nznog Subject: Re: [nznog] Hotmail Simon Lyall wrote: > Violations will result in use of equipment located in California and > other states. Ouuchhhh... that'll stop spammers for sure! Wonder what equipment located in California and other states it is that MSN/Hotmail will use though? -- Juha _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 7

Hotmail
by Simon Lyall 14 Dec '05

14 Dec '05

$ telnet mx2.hotmail.com smtp Trying 65.54.244.168... Connected to mx2.hotmail.com. Escape character is '^]'. 220 bay0-mc6-f18.bay0.hotmail.com Sending unsolicited commercial or bulk e-mail to Microsoft's computer network is prohibited. Other restrictions are found at http://privacy.msn.com/Anti-spam/. Violations will result in use of equipment located in California and other states. Wed, 14 Dec 2005 15:39:37 -0800 helo 250 bay0-mc6-f18.bay0.hotmail.com (3.1.0.17) Hello [202.27.185.139] Mail from:<simon(a)darkmere.gen.nz> 452 Out of memory Connection closed by foreign host. $ -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

Re: [nznog] NZ Security Notifications
by Dean Pemberton 13 Dec '05

13 Dec '05

>Would this list have the same sort of policy for membership as nsp-sec? >i.e. an invite only list for people who actually have to do the work >with a policy of kicking out people who don't meet the membership >criteria on an ongoing basis. > >If that's the case then I can see value in such a list but if it's >going to be similar to NZNOG with an "anybody can join" policy then I'm >less interested. > >andy I agree with Andy here. The only list I would be interested in is one which subscribes to the nsp-sec policy. No lurking. You have to be the person who is able to make the changes. Change jobs and you unsub. And some others. It's the only way. An "anyone can join" list will degrade into.... well my opinions here should remain to myself =) I would suggest that people look at joining nsp-sec rather than re-inventing the wheel. Or at the very least getting Rob to host an nsp-sec-nz list with the same policy around it. If you are a large provider, then there is probably already content on nsp-sec that you should know about. Dean.

1 0

Fwd: King Kong streaming tomorrow
by Paul Adshead 13 Dec '05

13 Dec '05

It may be good for someone in Telecom to let their front line staff know about (de-)peering at some point. After spending 15 minutes on the phone, it was quite amusing when they came back from putting me on hold: "I have talked to our tech guys and no-one in Xtra can get to the page either. They think it is a problem with the routing of data for the site at the far end. You could try power-cycling your router though"... Then when I asked for confirmation by email: "We suspect that there has been some stringent ip filtering and this is what could be causing the problem. We can not confirm this the best source of action would be to contact the host of the website for further information." Obviously either highly qualified in providing BS responses or just stupid. It's still annoying that I can't get to see it though... Paul -----Original Message----- From: Mike [mailto:mike(a)nzbox.com] Sent: Wednesday, 14 December 2005 17:20 To: NZNOG Subject: Re: [nznog] King Kong streaming tomorrow Hi Rich and Si Can I suggest you mention which streams will be available internationally in your announcements. Cant see either of these from Seattle ;-) good message for TCL and TNZ though.... Kia ora! You've reached the Citylink anycast node located in San Francisco, California. If you are in NZ, you should ring your ISP and ask them why your traffic is coming to the USA, rather than staying in New Zealand. Useful phone numbers are at TelstraClear (try the wholesale number if you get no joy from residential/business) and the best number for Telecom would appear to be 0800 CALL XTRA [22 55 98]. If you're feeling particularly cussed, ask them what's changed in the two years between the RoTK (when you could reach these streams nationally) and now. International users, we're sorry, sadly, our non-existent budget means that we can't make the Courtenay Place webcam available internationally. Such is life. Mike On Dec 12, 2005, at 8:10 PM, Simon Blake wrote: > Hi all > > A belated notice that the red carpet TV coverage and Courtenay Place > webcam will be streaming tomorrow as part of the King Kong premiere. > The mms stream will be on ac1-all.r2.co.nz (202.7.7.90), the webcam > from > embassy.citylink.co.nz (202.7.6.10), both anycast at the major > exchanges. The webcam is running now, informal MMS streams will start > about midday, TV coverage about 3pm. > > We're not expecting the same sorts of loads as RoTK, but who can tell. > > Cheers > Si > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0