October 2007 - NZNOG - lists.nznog.org

list.waikato.ac.nz Has Moved
by Donald Neal 11 Dec '24

11 Dec '24

NZNOG-People, I have just finished migrating all of the mailing lists held at The University of Waikato from one server to another. I don't have any reason to believe that anything's gone wrong, but please bear with me for today if it turns out that something has. - Donald Neal -- Donald Neal | Q: How many Aucklanders does it take to change Systems Programmer/Analyst | a light bulb? The University of Waikato | A: Pass me that candle and I'll tell you. Hamilton, New Zealand | --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

RE: Sort of OT: are there any "Internet enabled" temperature sens ors/servers for Auckland?
by Greg Clare 18 Aug '21

18 Aug '21

May not be exactly what you are after? However DSE have an Internet weather station at the Albany HQ. http://www.dse.gen.nz/public/webdata/weather.htm Regards Greg > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Wednesday, 2 January 2002 2:47 pm > To: NZNOG > Subject: Sort of OT: are there any "Internet enabled" temperature > sensors/servers for Auckland? > > > Measuring the outside temperature, with geographic location given. > > -- > Juha > Take off every sig! > > - > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Charging for IPv6
by Philip D'Ath 24 Aug '08

24 Aug '08

Initially those transit providers and ISPs that do offer IPv6 transit will be able to charge for this service as it will be a premium value add. However I can't see this business model being able to last for more than 6 years (through to 2012), and possibly only three years. After this point in time I expect IPv6 deployment will be standard, and will no longer be a premium service offering - it will be the standard offering, like IPv4 is today. Once IPv4 has become exhausted and you can't actually give a customer an IPv4 address then you definitely wont be able to charge more for IPv6 - otherwise the customer will walk. So do providers start implementing slowly now, and recoup some of their investment while they can, or wait till they are forced to do the upgrades and are not able to recoup any of their "new" investment. Rhetorical question.

23 40

The New Zealand Network Operators' Group
by Donald Neal 31 Dec '07

31 Dec '07

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Meetings Our next annual conference is to be hosted by the WAND group in Hamilton on February 2nd to 4th, 2005. See http://www.nznog.org/ for more information, including the Call For Presentations. Offers to present are due in by 22nd October, and all presenters should have had their acceptance confirmed by 31st October. Also see http://auckland.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://www.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. See http://www.wix.net.nz/ for the Wellington Internet Exchange. About This Mailing List This list has slightly over 700 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 Donald Neal |Palmersdale: Are you in charge here? Technical Specialist |The Doctor: No, but I'm full of Operations Engineering | ideas. Integration & Services Division +----------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

3 16

IPv6 tunnel appliance beta testers wanted
by Nathan Ward 31 Oct '07

31 Oct '07

Righty, As many of you know, I've been working on building some little tunnelling appliances to push IPv6 over IPv4 using well known protocols (6to4 and Teredo). Both 6to4 and Teredo benefit from having relays in as many places as possible. Cisco currently supports 6to4. I'm not sure if anyone else does. Noone supports Teredo. With both 6to4 and Teredo being built in and enabled by default on Vista (and enable-able on XP SP2), the amount of tunnelled IPv6 traffic on the Internet is increasing. I recently posted on the v6ops IETF mailing list about Azureus's support for IPv6 - when I use this client, over half of my DHT peers are IPv6 peers, and 99% of them were over tunnelled IPv6, either with 6to4 or Teredo. So, in light of this, I've put together a small FreeBSD based image for Soekris hardware. This does Teredo and 6to4, and also BGP. It does some funky tricks to hook all of these boxes together, tunnelling over IPv4. So, you get interconnection with many other networks over IPv4 best paths and existing IPv4 transit. I'm also expecting to be able to get you on to the v6IX (Citylink's IPv6 peering) as well if you (or your transit provider) are an existing IPv4 peer at APE or WIX. This software will be freely available when it's ready. Here's the best bit: Thanks to InternetNZ, I'll soon have have 6 boxes to do a live test of the code, and hopefully more down the line when it's ready to go for real. So, I'm looking for people who are running networks that fit one (or more) of the following: - Large numbers of end users - Lots of content on IPv6 (yeah, I'm dreaming) - Universities (or other large private networks) It doesn't matter if you have some IPv6 deployed, or if you only have IPv4 deployed, or if you haven't even thought about IPv6 deployment yet. What I need from you: - A shelf somewhere, and an IEC C13 (a.k.a. jug plug) cable/outlet. - An IPv4 address or two. - A 10/100 ethernet port (or two if you're keen on resiliency). - The ability to statically route a couple of IPv4 addresses at your box. - Also useful (but not necessary!) is an IPv6 allocation, and some form of transit internationally (a free IPv6 tunnel from somewhere overseas is fine- native transit isn't required) What you get: - 6to4 relay - Teredo relay - IPv6 interconnection to other people with these boxes Impacts: - If it breaks, you might end up with customer IPv6 traffic being impacted. (ie. not that much impact at all, right now) I'm working right now on some deployment pictures and all that noise, so there's more info coming. Please let me know if you're interested, or if you're interested but have some concerns, or, whatever. I'm wanting to get boxes in fairly soon - ie. before xmas brownouts. Integration is pretty minimal if you have an IPv4 network - plug in and point a route or two. It's only slightly more if you have an IPv6 network. Cheers! -- Nathan Ward Braintrust Ltd.

1 0

The day the routers died
by Philip D'Ath 31 Oct '07

31 Oct '07

Not on topic, I know, but this is very entertaining and will appeal to people on this group. http://www.youtube.com/watch?v=_y36fG2Oba0

3 2

[nznog-owner@list.waikato.ac.nz: Re: DNS lookup false positives with: com.co.nz > 208.73.212.12 > information.com]
by Richard Haakma 29 Oct '07

29 Oct '07

On Tue, Oct 30, 2007 at 09:43:32AM +1300, Paul Adshead wrote: > Are any others being affected by the fools who have registered "com.co.nz"? > > It's been setup as a 'catch all' search engine, for the 'append parent DNS > suffix' queries. So a lookup on "abcd.com" that should fail, comes back > successful from "abcd.com.co.nz"... :-( I add a line search . in /etc/resolv.conf in my mail servers to fix this sort of stuff. All email addresses should be fully qualified. Regards, RH.

1 0

DNS lookup false positives with: com.co.nz > 208.73.212.12 > information.com
by Paul Adshead 29 Oct '07

29 Oct '07

Are any others being affected by the fools who have registered "com.co.nz"? It's been setup as a 'catch all' search engine, for the 'append parent DNS suffix' queries. So a lookup on "abcd.com" that should fail, comes back successful from "abcd.com.co.nz"... :-(

4 3

114/8 and 115/8 allocated to APNIC
by Leo Vegoda 28 Oct '07

28 Oct '07

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in October 2007: 144/8 and 115/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, Leo vegoda Manager, Number Resources - IANA

1 1

NZRR Route Registry Update
by NZRR Database Notifications 28 Oct '07

28 Oct '07

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: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070928 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071029 source: NZRR ------------------------------------------------------------

1 0