- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jul '07

01 Jul '07

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070702 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jul '07

01 Jul '07

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070702 source: NZRR

1 0

The Choice: IPv4 Exhaustion or Transition to IPv6
by JORDI PALET MARTINEZ 30 Jun '07

30 Jun '07

Hi all, I've published a document trying to analyze the IPv4 exhaustion problem and what is ahead of us, considering among others, changes in policies. http://www.ipv6tf.org/index.php?page=news/newsroom&id=3004 I guess this could be useful in order to understand possible implications of modifying existing policies, or setting up new ones, or even just to create some debate about those changes. The document was completed last April, but didn't had the time to tidy up until a few days ago. Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

SixXS tunnel broker pop in .nz
by Lincoln Reid 30 Jun '07

30 Jun '07

Hi, Thanks to the post forwarded onto the list by Andy Linton I have been inspired to get in touch with the SixXS guys and arange a local SixXS pop within New Zealand. The nzwlg01 pop runs within the ACSData network ( still known in places as LinuxNet or ACSOnline ). We run our ipv6 network on the same routers, switches and circuits as our IPv4 network, we v6 peer at WIX and APE and use the same international transit provider as for our ipv4 network. It would be great if some people would sign up and make some use of it, if there are any network issues ( or you want a peering session etc. ) feel free to get in touch directly with me or noc(a)acsdata.co.nz. http://www.sixxs.net/signup/ Cheers, -- Lincoln Reid Systems Engineer ACSData - AS18119 lincoln(a)acsdata.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

2 1

116.0.0.0/8 allocations
by Gerard Creamer 30 Jun '07

30 Jun '07

Hi all, Through our own stupidity we were inadvertently blocking a recent allocation from APNIC and thought I'd mention it here. We had a bogon list with 112.0.0.0/5 in it and misread it as /8 several times before growing a brain and sorting it out. Just thought I'd mention it so folks can recheck their bogon lists to ensure that the following aren't being stopped by a larger aggregation. 116/8 APNIC 117/8 APNIC 118/8 APNIC 119/8 APNIC 120/8 APNIC Cheers, Gerard -- Netspace Services Limited http://www.netspace.net.nz Phone +64 4 917 8098 Mobile +64 21 246 2266 Level One, 220 Thorndon Quay, Thorndon PO Box 12-082, Thorndon, Wellington 6004, New Zealand

10 18

ICANN Board Resolution on the Deployment of IPv6
by JORDI PALET MARTINEZ 29 Jun '07

29 Jun '07

I think this resolution that has been taken unanimously by the board today here in San Juan deservers this email at least: http://www.ipv6tf.org/index.php?page=news/newsroom&id=3052 Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

6to4 and Teredo relays deployment
by JORDI PALET MARTINEZ 29 Jun '07

29 Jun '07

Some weeks ago I started to work in documenting how to setup 6to4 and Teredo relays/servers in several platforms for the afripv6-discuss mailing list. There are many 6to4 relays already, but it becomes even more important to have them where the bandwidth is more expensive, because it avoids traffic going thru upstream links. The first message on this is here: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000061.html More information about 6to4 also available at: http://www.ipv6tf.org/index.php?page=using/connectivity/6to4 Similarly for Teredo: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000080.html And more info about Teredo at: http://www.ipv6tf.org/index.php?page=using/connectivity/teredo Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

Broadband Measurement in NZ - Analysis Skills Required
by Michael Cranna 27 Jun '07

27 Jun '07

Hi All As you may have read in the papers in the last few days or so, Epitiro has launched a service in NZ which measures the broadband performance of NZ's 5 largest DSL ISPs in Auckland, Wellington and Christchurch ie Xtra, TCL, Callplus, ihug and Orcon. Our methodology is quite comprehensive; we connect up to the premium service of each ISP and then run tests every 15 minutes, to measure, among other things, connection speed, time to connect, DNS response times, cached and un-cached http traffic performance, ping times etc etc. The data provides an interesting look at the performance of the ISPs' service; from DSLAM to peering exchange and beyond. All major ISPs in the UK use our service. What we are keen to do - once we have about a month or so of data - is to conduct analysis on this data, to help us understand what the various combinations of variable fluctuations mean in the NZ context. While we have a lot of experience in the UK, the NZ network topography is very different, so we are looking for some local expertise to help us. Anyone interested? For the few months or so it's probably going to be more love than money, although I am hoping to create a position in the near future, or at least have some budget to pay for casual contracting. This is a unique opportunity to see data of this nature in NZ for the first time. However, the potentially controversial nature of the data means any involvement in this project will have to be strictly governed by confidentiality agreements, threats of immolation etc. If you're interested, drop me an email, and we could either catch up for a coffee if you are in Auckland, or have a chat on the phone if you are elsewhere. If you want more information about us, check out the URL below. Thanks and regards Mike Michael Cranna Managing Director Epitiro Technologies (Australasia) Ltd Level 27 PWC Tower, 188 Quay St, AUCKLAND Tel. +64 (0) 9 363 2995 Mob. +64 (0) 27 482 9256 mcranna(a)epitiro.com www.epitiro.com

1 0

telecom peering
by Anton Smith 26 Jun '07

26 Jun '07

Hello all, Has anybody seen or heard of any further development of this: http://computerworld.co.nz/news.nsf/news/EA57668828E0FEEFCC2572AC0070D766 Basically Telecom saying they would establish 29 regional points of interconnection, where providers could interconnect with them. The article mentions paying for a circuit into Telecom's network, with them reciprocating a circuit back (in the case of an ethernet interconnect, does this mean paying half each?). I am also wondering if any of these "regional points of interconnection" will be at the existing IXs, and in which case it doesn't seem that either Telecom or the other provider should have to pay anything for interconnect. What's the current word on the street? Has anybody engaged Telecom over this, or know what stage they are at? On another note, it seems funny that I am almost scared to post to nznog these days given the recent 'moderation by the people' ;). Regards, Anton

6 5

Systems Administration and Monty Python
by Jamie Baddeley 24 Jun '07

24 Jun '07

Right. Now that the subject matter has got your attention.. FX Networks (http://www.fx.net.nz/) has a position available for a junior/medium level systems administrator with some experience in looking after Debian Linux systems. Ideally they should have experience with Asterisk (or an enthusiasm for it), and a willingness to learn Cisco Networking technology. Perl hacking is also good. This person should not be afraid of customer interaction and working in a small tight team that has fun. Natural talent in dealing with the killer white rabbit of Caerbannog and the knights who say neh! is also a plus. I should also mention beer to keep it OT. Oh, and Wellington as well. Now I shall don my flame proof suit to deal with the slings and arrows of those who've taken it upon themselves to become defacto moderators of this fine list. For those of you moderately interested, drop me a line. thanks! jamie

1 0

NZNOG 08 - Call for Participation and Papers
by Simon Lyall 23 Jun '07

23 Jun '07

NZNOG 08 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Dunedin, New Zealand between 23 January and 25 January 2008. Our host is WIC. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. Conference Overview ------------------- NZNOG 2008 will consist of one day workshop and tutorial day followed by two days of conference presentations. There will also be opportunity for more informal and small lightening talks. These are typically around five minutes long and are organised closer to the actual conference. Important Dates --------------- Call for Papers opens: 25 June 2007 Deadline for speaker submissions: 6 August 2007 Responses to speaker submissions: 24 August 2007 Draft program published: 3 September 2007 Final program published: 1 November 2007 NZNOG 2008 Conference: 23 - 25 January 2008 SIG / Miniconf / Tutorials -------------------------- The first day of the conference will again be a workshop and tutorial day. It is usually run as one or more parallel 'interest group' streams and practical or interactive workshops of interest to Network Operators. This is a call for papers and activities for the first day of conference. Examples of past activities workshops include 'MPLS and fixed access networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet Resource Management Essentials', and a System Administrators mini-conference which included talks on 'Using Debian packages for system administration' and '42 hosts in 1U: Using virtual machines'. Conference Presentations ------------------------ The main conference program for 2008 will be made up of two days with a single stream where possible. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. NZNOG conferences have traditionally spanned the entire operational spectrum, and then some. Proposals for conference presentations are invited for virtually any topic with a degree of relevance to the NZNOG community. Past years' talks have included the following: - Internet exchange operations - Global anycast networks and the building thereof - Peering, peering, and peering - Network security - 10GB ethernet operations - Advanced networks in NZ - Current Internet research in NZ - Wireless networking - QOS over carrier networks - Content distribution networks and media streaming - How we paid the construction guys 18 pints of beer and they gave us a free metro fibre network in Palmy North - Open Source VoIP Platform in Carrier Environments If you are interested in submitting a talk please fill out the questions at then end of this document and email them to prog08(a)nznog.org . Submission Guidelines --------------------- When considering a presentation or SIG, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but each will help us determine the quality of your proposal and increase the likelihood it will be accepted. Final slides are to be provided by 21 January 2008. Note: While the majority of speaking slots will be submitted by 6 August 2007, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. The NZNOG conference is a TECHNICAL conference so marketing and commercial content is NOT allowed within the program. The program committee is charged with maintaining the technical standard of NZNOG conferences, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and unforgiving, and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. Funding and Support ------------------- NZNOG conferences are community run and funded events that try to keep the cost to attendees as low as possible so generally we are unable to pay the travel costs of speakers. There is a limited amount of funding available to international speakers. Conference presenters will not have to pay any registration fee for the day they are presenting. Discounts for SIG and lightning talk presenters may be available but are not automatic. Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG 2008 it is planned that there will be at least one hour long lightning talk session. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information Contact ------- Website * http://2008.nznog.org General Enquiries * info(a)nznog.org Talks and Papers * prog08(a)nznog.org Talk Proposals -------------- Please send all talk proposals (including lightning talks) to prog08(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Author's short biography: Title of Talk: Abstract: Length of talk: Please provide details if a version of this talk has previously been given: Will travel and accommodation assistance be required:

1 0

Bytes, Gigabytes and "GB" on the bill
by Paul Adshead 23 Jun '07

23 Jun '07

Bearing in mind most switches/routers output traffic stats in Bytes and most bills go to customers in GigaBytes, which of the following options are being used by each of us to convert between the two when creating the bill? A, divide by 1024 * 1024 * 1024; B, divide by 1024 * 1024 * 1000; C, divide by 1024 * 1000 * 1000; D, divide by 1000 * 1000 * 1000. Option A gives what anyone associated with computers would expect. Whilst the later options give a larger GB figure (- that can appear on the bill and be charged more). What is in use out there by ISPs? According to Wikipedia (http://en.wikipedia.org/wiki/Gigabyte) "The usage of the word "gigabyte" is ambiguous, depending on the context. When referring to RAM sizes and file sizes, it traditionally has a binary definition, of 1024³ bytes (typically assimilated or approximated to 1000³, for convenience). For every other use, it means exactly 1000³ bytes. In order to address this confusion, currently all relevant standards bodies promote the use of the term "gibibyte" for the binary definition."

5 4

[Fwd: [SixXS] gblon02 PoP open for Australian and New Zealand]
by Andy Linton 19 Jun '07

19 Jun '07

This may be of interest to some readers. andy -------- Original Message -------- Subject: [SixXS] gblon02 PoP open for Australian and New Zealand Date: Tue, 19 Jun 2007 16:40:51 +0100 From: Jeroen Massar <jeroen(a)sixxs.net> Reply-To: info(a)sixxs.net Organization: SixXS To: info(a)sixxs.net Hi, We have been trying to get an ISP from Australian or New Zealand on board, unfortunately it seems that we have met little interest up to now. In case you do know an ISP who might be interested of course don't hesitate to let point us to them, or let the, contact us. From several people we understood that IPv6 connectivity that is provided in the AU/NZ region is quality wise not the best and that there is no real alternative. We recently opened a new PoP in London, UK. The owner of which (Goscomb Technologies) has permitted any and all endpoints to be connected to this PoP. As such, if you don't mind the latency, which will most likely be around the 300-350ms range at least, you can now request a tunnel to the gblon02 PoP and it will be approved. See below for an example traceroute, or test it yourself using http://www.sixxs.net/tools/traceroute/ This at least allows one to get connectivity and start using it. Spread the word and let your friends enjoy too. In case you don't have enough credits to request a tunnel&subnet, don't hesitate to give a shout and we'll make that in order. Greets, Jeroen -- traceroute to 60.241.43.12 (60.241.43.12), 30 hops max, 40 byte packets 1 ge-0-0-0-1235.rt0.lon4.goscomb.net (77.75.104.121) 6.347 ms 8.645 ms 0.457 ms 2 cr02.ldn01.pccwbtn.net (195.66.224.167) 0.958 ms 0.621 ms 0.748 ms 3 ge3-4.br01.lax04.pccwbtn.net (63.218.50.86) 145.981 ms 144.941 ms 145.831 ms 4 reach.ge2-16.br01.lax04.pccwbtn.net (63.218.51.82) 147.341 ms 145.926 ms 146.323 ms 5 i-1-2.wil-core02.net.reach.com (202.84.251.201) 148.638 ms 149.345 ms 148.358 ms 6 i-4-0.sydp-core02.net.reach.com (202.84.144.102) 308.198 ms 308.394 ms 308.181 ms 7 unknown.net.reach.com (134.159.126.134) 304.362 ms 303.994 ms 304.543 ms 8 202.92.64.140 (202.92.64.140) 304.016 ms 304.783 ms 304.452 ms 9 202.92.127.86 (202.92.127.86) 305.379 ms 305.236 ms 304.571 ms 10 bri-pow-ibo-zeu-1-pos-4-0.tpgi.com.au (202.7.162.241) 318.572 ms 316.667 ms 317.729 ms 11 bri-nxg-ibo-zeu-1-pos2-2.tpgi.com.au (202.7.162.178) 318.023 ms 318.791 ms 318.606 ms 12 bri-nxg-ibo-nik-1-ge-0-1.tpgi.com.au (220.245.180.205) 316.950 ms 317.960 ms 317.714 ms 13 60-241-43-12.static.tpgi.com.au (60.241.43.12) 334.618 ms 333.790 ms 334.346 ms -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Jeroen Massar / http://unfix.org/~jeroen/ iHUEARECADUFAkZ3+QMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I1TfAJ9grjh3/f2SA4RyEGim+xJboM4L tACgiA7ZDsod680zORKjd1W8QTpox48= =TohL -----END PGP SIGNATURE-----

1 0

ihug DNS problems?
by bigalownz 15 Jun '07

15 Jun '07

I think its now 203.109.129.67

1 0

Soekris ?
by Craig Spiers 13 Jun '07

13 Jun '07

Hi guys, Anyone out there got a soekris 4521 (with pcmcia slots) for sale? The 4801 model is commonly used by citylink for route servers - I have a couple of these I would be willing to swap for a 4521 with pcmcia if anyone is interested :) Cheers

1 0

(no subject)
by mark10＠compass.net.nz 13 Jun '07

13 Jun '07

Perfect. Thanks Jamie. -----Original Message----- From: Jamie Baddeley [mailto:jamie.baddeley(a)vpc.co.nz] Sent: Wednesday, 13 June 2007 9:33 p.m. To: Mark Frater Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Bill Nortons "Asia Pacific Peering Ecosystems" Hi Mark, It doesn't look like it's in the NZNOG archive, but I dug through mine. See attached. It looks like it's early draft but hopefully it should give you what you need. Cheers jamie On Wed, 2007-06-13 at 17:09 +1200, mark10(a)compass.net.nz wrote: > Does anyone have a copy of Bill Nortons presentation titled "Asia > Pacific Peering Ecosystems" from NZNOG 2005 in Hamilton? > > I had a look at http://2005.nznog.org/ but the cupboard was bare. > > Mark > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Bill Nortons "Asia Pacific Peering Ecosystems"
by mark10＠compass.net.nz 12 Jun '07

12 Jun '07

Does anyone have a copy of Bill Nortons presentation titled "Asia Pacific Peering Ecosystems" from NZNOG 2005 in Hamilton? I had a look at http://2005.nznog.org/ but the cupboard was bare. Mark

5 4

[Fwd: Re: Bill Norton’s "Asia Pacific Peering Ecosystems"]
by Gerard Creamer 12 Jun '07

12 Jun '07

2004 and 2005 are now up. http://2004.nznog.org/ http://2005.nznog.org/ Just the conference sites for now - we'll get the galleries etc up as time allows. If you find anything busted please email details to info at nznog.org Cheers, Gerard mark10(a)compass.net.nz wrote: > Does anyone have a copy of Bill Norton’s presentation titled "Asia Pacific > Peering Ecosystems" from NZNOG 2005 in Hamilton? > > I had a look at http://2005.nznog.org/ but the cupboard was bare. > > Mark > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

ihug DNS problems?
by Simon Lyall 12 Jun '07

12 Jun '07

I'm seeing problems with doing DNS lookups against 203.109.252.42 which I believe is still ihug's main recursive DNS server [1]. For at least the last week around 20% of DNS queries are not being replied to. Testing to other ihug DNS servers is not showing any problems. Not sure if this is a problem since I am testing from non-ihug IP space and possibly they have put in ACLs[2]. No luck contacting them via email or phone [3]. [1] It might not be, they don't list one on their webpage anywhere. [2] If someone is a customer of theres they could probably check themselves, something like this will work: while [ 1 ] do dig www.ihug.co.nz @203.109.252.42 +tries=1 | grep "msec\|timed" sleep 5 done [3] They might want to update their details at http://www.nznog.org/?page_id=6 -- 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

Dunedin 5.8
by Bill Walker 12 Jun '07

12 Jun '07

Anyone put up anything new last Saturday. Have spoken to the usual suspects and no luck. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited ------------------------------------------------------------------------------------------------ Tel: 03 348 8747 / 0800 500638 Email: bill.walker(a)team.snap.net.nz<mailto:bill.walker(a)team.snap.net.nz> Web: www.snap.net.nz<http://www.snap.net.nz/> ------------------------------------------------------------------------------------------------

1 0

IPv6 .nz name servers
by DNS 12 Jun '07

12 Jun '07

NZRS is today pleased to announce that the .nz name servers are now operating with IPv6 connectivity in what can be regarded as the first phase of the .nz IPv6 rollout. The name servers are named ns8.dns.net.nz and ns9.dns.net.nz, and are located in Wellington and Albany repsectively. Both are connected to the NZ IPv6 Internet Exchange and there is a .nz Whois server accessible at whois.ipv6.srs.net.nz. NZRS thanks Open Contributors Corporation for Advanced Internet Development (OCCAID) and US telco Sprint for providing the IPv6 tunnels, and thanks Citylink for help in connecting to the NZ IPv6 Internet Exchange. .nz Registry Services is responsible for the operation of the register of domain names and the Domain Name System (DNS) in the .nz domain name space. For further information contact: support<at>nzrs.net.nz

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jun '07

11 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS24388:RS-ROUTES:AS17435 descr: Route set advertised to AS24388 by World Exchange - AS17435 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: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR

1 0

CHIX opens, finally!
by Simon Blake 11 Jun '07

11 Jun '07

Hi all, apologies in advance, this isn't strictly operational, but is likely to be of interest to most ISP's. Feel free to flame me directly. A somewhat belated announcement, those of you with sharp eyes will have noticed the CHIX RPSL database changes cropping up in NZNOG over the last few days. Essentially, CHIX is up and running and ready to carry traffic. There's a short press release up on http://www.citylink.co.nz/, currently Snap, ServerWorks and Net24 are configured to peer, and we'll have FX, WorldxChange and StreamingNet peering shortly. For those interested in connecting, the exchange is available in several buildings around Christchurch, including TVNZ, PWC, State Insurance (Division St in Riccarton) and the Sir William Pickering Business Park. The exchange runs within a VLAN on the distributed ethernet that runs over the Canterbury Fibre Networks fibre infrastructure - there is a somewhat dated coverage map at http://www.cfnl.co.nz/index.php?option=com_content&task=view&id=13 If you're interested in peering, please get in touch. Cheers Si

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jun '07

11 Jun '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS18202 as-name: NZRR-AS18202 descr: Net24 descr: CHIX peering at '218.100.24.12' descr: see Citylink RT job #9729 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24388 accept ANY AND NOT fltr-bogons export: to AS24388 announce AS18202 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nikolai(a)net24.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR --- OBJECT BELOW CREATED: route-set: AS24388:RS-ROUTES:AS18202 descr: Route set advertised to AS24388 by Net24 - AS18202 members: 210.5.48.0/21^21-29, 210.55.30.0/23^23-29, 210.55.4.0/24^24-29, 210.55.7.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: nikolai(a)net24.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070612 source: NZRR

1 0

www.nznog.org
by Gerard Creamer 10 Jun '07

10 Jun '07

Hi, A quick announcement to let everyone know that the site at http://www.nznog.org has been updated. It now has info on NZNOG, with links to conference sites and the NOC list. There is a NOC list as part of the site - please check your entries and if they are incorrect or incomplete please *follow the instructions on the page* to get them updated / adjusted. The NOC list is a fairly informal affair, but I have made a spur of the moment decision that we'll (there's three of us in the NZNOG08 conference web team who will be updating these) only update requests originating from a URL that matches the URL in the table or is so obviously related that we're willing to take the risk. In other words please don't ask for updates from some disposable email address as we will most likely ignore them. Most things on the historical conference sites work, but some things are broken. We're still working on getting them sorted out, but thought it better to get the NZNOG and the 2008.nznog.org sites out. Comments and feedback of a useful and constructive nature would be appreciated. Cheers, Gerard NZNOG08 Public Relations Team

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jun '07

10 Jun '07

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:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17412 descr: advertised to AS9439 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 116.93.128.0/20^20-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070611 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jun '07

10 Jun '07

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:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17412 descr: advertised to AS9560 by Woosh Wireless Limited - AS17412 members: 203.211.64.0/18^18-29, 202.74.192.0/19^19-29, 202.89.128.0/19^19-29, 116.93.128.0/20^20-29, 202.21.16.0/20^20-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sysadmin(a)woosh.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070611 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 07 Jun '07

07 Jun '07

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:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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.petrie(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 123.255.0.0/18^18-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070608 source: NZRR

1 0

[Fwd: Dear Sir/Madam Would You Want This Income?]
by Justin Cook 07 Jun '07

07 Jun '07

Although this isn't strictly a phish, it passed my spam filters and is obviously a scam. Worth blocking.

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '07

05 Jun '07

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: AS23655 as-name: NZRR-AS23655 descr: Snap Internet descr: WIX peering at '202.7.1.240' descr: see Citylink RT job #2857 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23655 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: aut-num: AS23655 as-name: NZRR-AS23655 descr: Snap Internet Limited descr: CHIX peering at '218.100.24.10' descr: see Citylink RT job #9020 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24388 accept ANY export: to AS24388 announce AS23655 notify: rpsl-admin(a)nzix.net notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070606 source: NZRR

1 0

Re: [nznog] APE / WIX route list Quagga RAM
by Gerard Creamer 05 Jun '07

05 Jun '07

Stuff all. WIX + a 1 route from an upstream is using a total of ~7% of 64Mb on a Soekris here = ~4.5Mb (zebra and bgpd) A full route table an a different router is only using about 25Mb. Gerard On 6/06/2007 9:45 a.m., Michael Fincham wrote: > Hey All, > > Does anyone have some rough figures for how much RAM Quagga uses to keep > the routing tables for WIX or APE in memory? > > -- Netspace Services Limited http://www.netspace.net.nz Phone +64 4 917 8098 Mobile +64 21 246 2266 Level One, 220 Thorndon Quay, Thorndon PO Box 12-082, Thorndon, Wellington 6004, New Zealand

2 1

APE / WIX route list Quagga RAM
by Michael Fincham 05 Jun '07

05 Jun '07

Hey All, Does anyone have some rough figures for how much RAM Quagga uses to keep the routing tables for WIX or APE in memory? -- -Michael Fincham Unleash Technology Solutions

2 1

Code for IPv6 test for content providers
by Nathan Ward 01 Jun '07

01 Jun '07

During a discussion on the NANOG list this week, I came up with an idea that would allow content providers to test their IPv6-ability ie. what would happen if they turned on AAAA records for their websites, which is currently a big reason that content providers aren't "6-ing up". The general idea is to do GETs to several different URLs on different hostnames, and have the different hostnames have IPv4-only, IPv6-only and IPv4+IPv6, and then report the stats. After some playing+testing, I've come up with some code, and it's available here: http://www.braintrust.co.nz/ipv6wwwtest/ I'm not really a JavaScript hacker so it probably isn't terribly amazing quality, but it seems to work OK for me - I've been running it on several of my websites with a large range of user clue+access+OS +browser+ISP as visitors and I've had no complaints. The code is running on the page above, too. Also, the default timeout in the tarball is too high, 10000-20000 is probably adequate. Please let me know if you use it, or if you do something similar or use it for inspiration or whatever. In addition, I'm sure we'd all love to see any statistics you can share when using this. Enjoy! -- Nathan Ward

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

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: advertised to AS9560 by AT&T - 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.14.252.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.146.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, 203.196.121.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 20060622 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - 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, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.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.146.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, 203.196.121.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 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

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:AS24111 descr: advertised to AS9560 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061005 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24111 descr: advertised to AS9560 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

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 - 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.14.252.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.146.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, 203.196.121.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 20060622 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - 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, 125.236.50.0/24^24-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.252.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.146.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, 203.196.121.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 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

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:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: soa(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 116.90.129.0/24^24-29, 116.90.130.0/24^24-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '07

31 May '07

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:AS24111 descr: Route set advertised to AS9439 by NZwireless - AS24111 members: 203.110.28.0/23^23-29, 210.54.151.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: andrew.tipton(a)nzwireless.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040810 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24111 descr: advertised to AS9439 by NZWIRELESS - AS24111 members: 58.84.224.0/20^20-29, 203.110.28.0/23^23-29, 202.21.130.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: anton(a)huge.geek.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070601 source: NZRR

1 0

RIPE NCC DNS Monitoring Service (DNSMON) for .nz name servers
by DNS 30 May '07

30 May '07

The .nz secondary name servers have been added to the RIPE NCC DNS Monitoring Service (DNSMON). DNSMON provides a comprehensive, objective and up-to-date overview of the quality of the service provided by DNS servers. Graphs and further details about DNSMON can be found here: http://dnsmon.ripe.net/ -- Dave Baker .nz Registry Services

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 29 May '07

29 May '07

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070226 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 29 May '07

29 May '07

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070328 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070530 source: NZRR

1 0

Dunedin 5.8
by Bill Walker 29 May '07

29 May '07

Hi all, Anyone in Dunedin put up any new 5.8 gear around Monday lunchtime? Or changed channels on existing gear? We're seeing heaps of noise between 5808Mhz and 5824Mhz. Cheers, Bill -- Bill Walker Senior Network Engineer Snap Internet Limited ------------------------------------------------------------------------------------------------ Tel: 03 348 8747 / 0800 500638 Email: bill.walker(a)team.snap.net.nz<mailto:bill.walker(a)team.snap.net.nz> Web: www.snap.net.nz<http://www.snap.net.nz/> ------------------------------------------------------------------------------------------------

1 0

NZIX looking glasses
by Andy Linton 28 May '07

28 May '07

You may find this alternative Looking Glass view of the NZIX Route Servers useful. http://nzix.net/cgi-bin/lg.cgi At this stage this is in addition to the original interfaces.

3 2

Problems with WIX route servers late last week.
by Simon Blake 28 May '07

28 May '07

Hi folks This is a somewhat belated reply to those who might have noticed wiggyness with the WIX route servers late last week. Thanks to Lee from WorldExchange who first pointed out the problem. We eventually tracked it down fumble fingering at a local ISP, which caused a full route table to be sent to the route servers. As the route servers are RAM and CPU constrained, they didn't cope outstandingly well with this - while they didn't crash, they ran sufficiently slowly that other BGP sessions were getting randomly dropped. Once the offenders were tracked down and had their ways mended, it all came right. So we're currently thinking about ways to avoid this sort of DOS in future. Boxes with more headroom would be a start, so we're considering alternative hardware options at the moment. We're also considering the merits of running one RS with quagga, and one RS with OpenBGPD - that's a possibility into the future, but will require a certain amount of RPSL and looking glass rejigging before we could go live. Relatedly, Andy has been playing with alternate looking glass code, and has this under testing - the "looking glass for amiga users" (tm) http://nzix.net/cgi-bin/lg.cgi put your keyboard in the garage, click submit, and then keep clicking. Any feedback welcome. Cheers Simon

1 0

Network Engineer position available at Smartlinx 3 Ltd Upper Hutt
by Adrian Smith 27 May '07

27 May '07

we currently have a Network Engineer position available at Smartlinx 3 Ltd in Upper Hutt. http://smartlinx3.co.nz/ For further information on this position please contact David Haynes, Managing Director, Smartlinx 3 Ltd david.haynes (AT) smartlinx3.co.nz Phone/FAX +64 4 939 1444 Cheers Adrian Smith

10 10

Soliciting peers for the root servers located in NZ...
by Peter Losher 27 May '07

27 May '07

Hi, ISC is currently in the process of upgrading our routers in Auckland, and it behooves us to remind the local community that there is a local instance of f.root-servers.net here at the SkyTower, connected to APE. With the DDoS against several of the root servers back in February which proved our anycast model (most folks never noticed there was even a issue), we are once again soliciting peers across our 40+ nodes so we can "keep root server traffic local" wherever possible. So if you are not already peering with us and would wish to do so, please fill out our peering form here: http://www.isc.org/ops/peering/request/ For those of you that don't wish to peer with us over public IX's, we will consider private peering arrangements if you are already present (in the case of Auckland) at the SkyTower. For those of you only present at the WIX, might I suggest contacting Autonomica, who operate a instance of i.root-servers.net there. Hope to be peering with you soon (if we don't already). Best Wishes - Peter -- Peter_Losher(a)isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow"

1 0

Alert: Kiwibank scam
by Clark Mills 27 May '07

27 May '07

Hi all. Don't know if this is new/old but I got this an hour ago: Kiwibank wrote: > *Reminder:* Customers are reminded that User Maintenance personal > information requires update. At Kiwibank online banking, We are so > confident with our online security system that we guarantee your money. > This is provided you have complied with our Kiwibank Online Banking > Product Disclosure Statement. Please proceed to your Kiwibank online > banking personal internet banking below for more update on your account > maintenance : > > Proceed to Kiwibank Internet Banking Here > <http://www.zachcone.com/kiwibank/> It didn't trip Thunderbird's scam alert due to the way the link was constructed. I've the full message text and screenshot here if anyone's interested. http://c.mills.ctru.auckland.ac.nz/KiwibankScam/ Cheers... Clark

5 4

Notification of NZRR Database changes
by NZRR Database Notifications 23 May '07

23 May '07

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:AS18353 descr: advertised to AS9439 by Revera - AS18353 members: 202.55.99.0/24^24-29, 202.55.96.176/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: Marc.Nienkemper(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060601 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18353 descr: advertised to AS9439 by Revera Limited - AS18353 members: 192.88.85.0/24^24-29, 202.55.99.0/24^24-29, 202.55.100.96/27^27-29, 202.55.96.176/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: networkteam(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070524 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 May '07

23 May '07

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:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.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.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 20070522 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.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 20070524 source: NZRR

1 0

Link-bonding scheduler on Allied Telesyn boxes
by Matthew Poole 23 May '07

23 May '07

Hi Does anyone happen to know the link-bonding scheduling method used by AT 9812T and Switchblade 2008 boxes? We've seen _reduced_ performance with link bonding on these systems when connecting them to Linux boxes, and were wondering if there's a particular scheduling method that should be enabled on the Linux end. -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0