- NZNOG - lists.nznog.org

New IP to ASN Mapping Services
by Rob Thomas 01 Mar '06

01 Mar '06

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those who receive this post in multiple forums. ] Team Cymru is happy to announce the availability of various service options dedicated to mapping IPv4 numbers to BGP prefixes and ASNs. These services come in various flavors, including: * Whois, DNS, HTTP, HTTPS Each of the services is based on the same BGP feeds from 50+ BGP peers, and is updated at 4 hour intervals. Using a single IP or ASN one can obtain any of the following information: * BGP Origin ASN * BGP Peer ASN * BGP Prefix * Prefix Country Code (assigned) * Prefix Registry (assigned) * Prefix Allocation date * ASN Country Code (assigned) * ASN Registry (assigned) * ASN Allocation date * ASN Description The country code, registry, and allocation date are all based off of data obtained directly from the regional registries including: ARIN, RIPE NCC, AFRINIC, APNIC, LACNIC. The information returned relating to these categories will only be as accurate as the data present in the RIR databases. The ASN descriptions are based off of data obtained from cidr-report. For a summary on how to use these services please visit the following web page: <http://www.cymru.com/BGP/asnlookup.html> If you have any comments, questions, or suggestions please feel free to contact us at: team-cymru(a)cymru.com. Thanks! Rob. - -- Rob Thomas Team Cymru http://www.cymru.com/ ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBRAciKlkX3QAo5sgJAQFS4gP8CXz2ZIlzfK5+/6bj7TZVN33e29eifH0+ WKjfbrVKEchQTwCjvkoowtH9Mcr8H0iqf4vb9sQLAxojedFe39Gi5xtW+BGFQ1Te hwdrF0n5QaGjecV0ID+XAzgGxrwC+4CVfaLtYG8mL/SD2VlUs6SpaN22YGjMRKM2 8y0LT9HAly0= =1moY -----END PGP SIGNATURE-----

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '06

01 Mar '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:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.36.170.0/24^24-29, 202.36.227.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.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.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, 218.101.56.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tsalmen(a)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060302 source: NZRR

1 0

192.203.154.23 natcom.ape.net.nz
by Russell Fulton 01 Mar '06

01 Mar '06

Would whoever is responsible for this router please drop me a line off list. Nothing really urgent :) Or if someone can point me to a contact address... Russell -- Russell Fulton, Information Security Officer, The University of Auckland New Zealand

2 1

NZNOG 06 - March 22-24 , Registrations online
by Simon Lyall 28 Feb '06

28 Feb '06

NZNOG 06 - Registrations now online. http://www.nznog.org The next conference of the New Zealand Network Operators' Group is to be held in Wellington, New Zealand between 22-24 March 2006. The conference is on the week before the ICANN meeting in Wellington so people can attend both events. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of networked services, with particular emphasis on New Zealand. The conference has a strong technical focus with the aim of attracting a strong turnout of technical personnel. The conference fee is affordable to most to encourage greater participation This year we have a strong programme of New Zealand and overseas speakers on a wide range of topics over 3 days. The programme includes talks on VoIP, DNSSEC, IPv6, BGP, 10G Networks, Peering, QoS and Content-delivery. NZNOG 2006 registration fee is $250 for three days See http://www.nznog.org for more details. My apologies if you see multiple copies of this announcement. -- 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

Notification of NZRR Database changes
by NZRR Database Notifications 28 Feb '06

28 Feb '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 AS64646 OR AS9439:RS-ROUTES 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 OR AS9439:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439: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 20060301 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 AS64646 OR AS9439:RS-ROUTES 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 OR AS9439:RS-ROUTES OR AS64646 AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS24385:AS-PUBLIC announce AS24385:RS-ROUTES OR AS9439:RS-ROUTES OR AS64646 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 20060301 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 28 Feb '06

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

1 0

The New Zealand Network Operators' Group
by Donald Neal 28 Feb '06

28 Feb '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 THIS MONTH. See http://www.nznog.org/ to register. Seating is as ever limited, and places are allocated on a "first come, first served" basis. 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://www.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

Re: [nznog] Campbell Live tonight
by Peter Mott 25 Feb '06

25 Feb '06

>So, no it's not public domain (though publicly available, >albeit streaming only) and no the permission of the copyright >holder was not sought. It's just an alternative for those >without the means to stream. Above appears to be a modern day term for justified theft of somebody elses property. If I was TV3 I would be inviting you to an education programme down at the local court house. regards Peter Mott MOTT & ASSOCIATES Tel: +64 9 488 9352 Fax: +64 9 486 7017 -/-

11 14

The Origins of "2006 NZ Census - Are you a New Zealander"
by Craig Whitmore 24 Feb '06

24 Feb '06

A little (lot) OT but.... Does anyone know the origins of this email. It seems its going around like wildfire at the moment. Yes I could ask the person who sent it to me who sent it to them and so on and so on.. its getting a little anoying now.. I have 10 copies already from just this morning. I guess its like the last Census where the email about being a Jedi was sent around. Subject: 2006 NZ Census - Are you a New Zealander? Did you know that New Zealand is pretty much the only place in the world that you can not actually be a New Zealander? Whenever you fill out a form or survey in New Zealand you can tick the box to say you are Maori, Tongan, Samoan, Australian, European (or NZ born of European Decent), Asian, etc but there is no box provided to say "Yes, I am a New Zealander and I am proud to be one" In Australia, you can be an Australian... In fact in Australia you can be a New Zealander. etc.. etc Thanks Craig

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Feb '06

23 Feb '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:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 202.49.128.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050627 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/21^21-29, 202.49.183.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: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060224 source: NZRR

1 0

IMPORTANT: Re NZNOG Registration!
by Mark Foster 23 Feb '06

23 Feb '06

Folks, For all registrations - despite what has been posted previously - please treat the following url as authoritive. All persons registering to attend the conference MUST read the content on this page, even if you've gone direct to VUW's reg page. http://www.nznog.org/register Note that www.nznog.org has had a major overhaul and is probably worth a look. My thanks to Lin, Donald and Joel for their assistance with this. Mark - nznog.org conference webmaster-of-sorts....

2 2

APNIC 21 - Participate in the meeting from anywhere
by Nurani Nimpuno 22 Feb '06

22 Feb '06

+ + + + + NEWSFLASH: New services starting at APNIC 21! - Live streaming audio - Podcasts + + + + + Dear APNIC members and friends APNIC 21 begins in a few days. Here are some last minute tips on making the most of the meeting. 1. Remote participation ----------------------- Can't make it in person to APNIC 21 in Perth? Then follow the events online in real time anywhere in the world via: - Jabber chat rooms - Live transcripts - Streaming video - Streaming audio In addition, you can now access the Jabber chat rooms using your web browser. Archives of the audio, video and transcripts will also be available soon after each session. For more information on how to participate online, go to: http://www.apnic.net/meetings/remote 2. Meeting checklist --------------------- With less than a week remaining before the meeting, it is important to do the following: 1. Register online 2. Choose a voting option for the APNIC EC election 3. Book your hostmaster consultation online For assistance, please go to: http://www.apnic.net/meetings/21 Or contact: <meetings(a)apnic.net> We look forward to seeing you in Perth! Best regards ------------------------------------------------------------------------ APNIC Secretariat <secretariat(a)apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3219 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net ------------------------------------------------------------------------ See you at APNIC 21 Perth, Australia, 27 February - 3 March 2006 http://www.apnic.net/meetings/21 ------------------------------------------------------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 Feb '06

22 Feb '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:AS64551 descr: advertised to AS9439 by Breathe Communications - AS64551 members: 161.29.192.32/27^27-29, 202.135.231.48/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: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050908 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64551 descr: advertised to AS9439 by Breathe Communications - AS64551 members: 161.29.192.32/27^27-29, 202.135.231.48/28^28-29, 202.160.118.224/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: sam(a)onesquared.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060223 source: NZRR

1 0

NZNOG 2006 registration and online payment web page(s)
by Peters MCS Mail 22 Feb '06

22 Feb '06

Apologies to the list for the long wait. Here are the links for NZNOG 2006 conference registration https://www.mcs.vuw.ac.nz/cgi-bin/events/nznog and for those only interested in the APNIC Internet Resource Management tutorial: https://www.mcs.vuw.ac.nz/cgi-bin/events/apnic Regards Peter

1 0

Fwd: FW: SORBs blacklisting Paradise MTAs
by Paul Adshead 22 Feb '06

22 Feb '06

Having previously been listed on the SORBS list, I can say from personal experience that trying to get any information from them is like trying to draw blood from a stone. You just give up - there is quite literally nothing you can do. The legal stuff on their site says something like "you are not supposed to block access based on information on this site", yet that is exactly why their site has been created. That's their legal 'get out' to avoid all liability. Their attitude stinks. They are quite happy to cripple your business for days/weeks at a time and their response time after an issue has been resolved is pathetic. Paul -----Original Message----- From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] Sent: Wednesday, 1 February 2006 14:12 To: nznog(a)list.waikato.ac.nz Subject: [nznog] SORBs blacklisting Paradise MTAs Hi gents (and gentesses) I reported to Paradise that Sorbs was blacklisting a particular Paradise MTA last night (details below) and their response was that sorbs refuse to whitelist them so there's nothing they can do about it... The further state that "SORBS automatically delist the servers after a 48 hour time period, and mail passing through the once affected mail server should flow as per normal." yet the information pasted below seems to indicate that the particular IP I reported has been on the list since Dec 11th 2005. They're spinning me a line right? The Sorbs record hasn't been updated since Dec 11th! *--- Info from sorbs as of 5 minutes ago *--- Address: 203.96.152.180 Record Created: Sun Dec 11 13:53:04 2005 GMT Record Updated: Sun Dec 11 13:53:04 2005 GMT Additional Information: Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by vampire.isux.com (Postfix) with ESMTP id 58986B90C; Sun, 11 Dec 2005 13:52:40 +0000 (UTC) Currently active and flagged to be published in DNS *--- end info from sorbs *--- Why would Paradise deliberately avoid resolving this issue when pointed out to them? If anyone from Paradise / Telstraclear would like to jump in and explain why your helpdesker effectively refused to do anything about the situation then I'm all ears. Yes, I did report to Paradise through the appropriate mechanism, then I replied to their automated response, then this morning I phoned to report it and had my number taken (no-one has phoned back) and a few minutes ago I received the reply to the original message saying they can't do anything. Cheers - Neil G Neil Gardner Product Manager Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

5 5

Re: [nznog] HEADS UP - upcoming webcast
by Richard Naylor 22 Feb '06

22 Feb '06

To save answering this question many times At 04:34 PM 2/22/2006 +1300, you wrote: >On Wed, 22 Feb 2006, Richard Naylor wrote: > > This is an excellent opportunity to show what the Internet can deliver in > > terms of interesting and compelling content. Arrangements have been made > > with Telecom NZ to make traffic flows optimal and we thank them for their > > support and co-operation. > >So does this mean people getting DSL via Xtra will be able to watch it? yes.

15 19

Re: [nznog] Campbell Live tonight
by Donald Neal 21 Feb '06

21 Feb '06

> >So, no it's not public domain (though publicly available, > >albeit streaming only) and no the permission of the copyright > >holder was not sought. It's just an alternative for those > >without the means to stream. > > Above appears to be a modern day term for justified theft of somebody > elses property. If I was TV3 I would be inviting you to an education > programme down at the local court house. > > > regards > > Peter Mott I think we've agreed that advertising on this list copies of copyrighted material made without the consent of the copyright holder is not an acceptable use of the list. Which means this thread can now go away? - Donald Neal Donald Neal |"Mouths are in oversupply but Support Engineer |brains/eyes are not." - Alan Cox NGN Operations | 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.

1 0

FW: HEADS UP - upcoming webcast
by Steve Biddle 21 Feb '06

21 Feb '06

Will this be a single simulcast of the TVNZ feed or will there be multiple feeds available? One of the great things overseas in countries with satellite TV operators covering both the commonwealth and olympic games has been the mutiple feeds allowing you to watch a single channel showing a bit of everything(much like out broadcast in NZ) and then other channels dedicated to showing other events live. I've been trying to find out if TVNZ have any plans to do such a thing with their FTA satellite channels but haven't heard anything as of yet. > -----Original Message----- > From: Richard Naylor [mailto:richard.naylor(a)citylink.co.nz] > Sent: Wednesday, 22 February 2006 16:10 > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] HEADS UP - upcoming webcast > > > Afternoon all, > > R2/Citylink has been contracted by TVNZ to assist with the > webcasting of > the Commonwealth Games next month, starting on 15 March and > concluding on > 26 March. On most days the webcast will run from around 10am > until 1 am > with breaks for things like News and Close Up. > > Because of broadcast rights, this webcast is being restricted > to NZ and > will use TVNZ/R2/CityLink servers located in Auckland and Wellington > connected via APE and WIX. > > In the case of wild demand, there are extra servers on > standby at each > location. > > Operators should be aware that this event is taking place > during business > hours and many viewers only access may be via their PC and > this webcast. > Traffic volumes may be higher than normal and support calls > to Help Desks > may be increased, particularly at sites where ports 80, 554 > or 1755 are > blocked. > > This is an excellent opportunity to show what the Internet > can deliver in > terms of interesting and compelling content. Arrangements > have been made > with Telecom NZ to make traffic flows optimal and we thank > them for their > support and co-operation. > > If you have any concerns, please contact me for further details. > > Thanks - Richard > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '06

21 Feb '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: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050331 source: NZRR REPLACED BY: aut-num: AS23755 as-name: NZRR-AS23755 descr: CityLink descr: DPE peering at '218.100.23.3' descr: see Citylink RT job #1927 descr: WIX peering at '202.7.0.7' descr: see Citylink RT job #4541 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS24384 accept ANY AND NOT fltr-bogons export: to AS24384 announce AS23755 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23755 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/24^24-29, 202.7.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 mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: Route set advertised to AS9439 by MediaNET - AS23755 members: 202.7.4.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060222 source: NZRR

1 0

HEADS UP - upcoming webcast
by Richard Naylor 21 Feb '06

21 Feb '06

Afternoon all, R2/Citylink has been contracted by TVNZ to assist with the webcasting of the Commonwealth Games next month, starting on 15 March and concluding on 26 March. On most days the webcast will run from around 10am until 1 am with breaks for things like News and Close Up. Because of broadcast rights, this webcast is being restricted to NZ and will use TVNZ/R2/CityLink servers located in Auckland and Wellington connected via APE and WIX. In the case of wild demand, there are extra servers on standby at each location. Operators should be aware that this event is taking place during business hours and many viewers only access may be via their PC and this webcast. Traffic volumes may be higher than normal and support calls to Help Desks may be increased, particularly at sites where ports 80, 554 or 1755 are blocked. This is an excellent opportunity to show what the Internet can deliver in terms of interesting and compelling content. Arrangements have been made with Telecom NZ to make traffic flows optimal and we thank them for their support and co-operation. If you have any concerns, please contact me for further details. Thanks - Richard

1 0

Re: [nznog] NZNOG conference
by Donald Neal 20 Feb '06

20 Feb '06

> From: David Robb [mailto:ender(a)paradise.gen.nz] > Sent: Wednesday, 25 January 2006 10:18 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] NZNOG conference > > 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. As to who is speaking, we've run into a problem with a number of speakers agreeing to provide abstracts to go on the web site, then not getting around to providing them. You know who you are. Among our more virtuous speakers are Mark Foster Bridging the Gap Between Support and the NOC Richard Hulse The Economics of Peering Peter Komisarczuk Location Determination for WLAN and 3G Hamish MacEwan Peering - The Customer Perspective Ian McDonald TCP Congestion Control Andrew McMillan Extending SPF to include policy for TLS Dean Pemberton Investigations into Internet Background Radiation Geoff Scrimgeour Welcome to The Loop Scott Walsh Network Security through Firewall Segregation Bill Woodcock Building Global Content-Distribution Networks I expect to announce more during the coming week. - Donald Neal Donald Neal |"I'm busy. I have papers to read, Support Engineer |reports to write, bosses to NGN Operations |infuriate." - Lt. Giardello 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 2

Cisco 3550 replacement
by Jacky Lam 19 Feb '06

19 Feb '06

Hi all, I'm currently looking for a CPE that can replace the Cisco 3550 we currently deploy in our network. Key features that I'm looking for are as follows: Hierarchical QOS Traffic shaping/policing L3VPN functionality(VRF-lite) BGP OSPF dot1q some sort of spanning tree Any help would be really appreciated, Jacky

2 1

Help: Questionaire...
by Mark Foster 18 Feb '06

18 Feb '06

Hi Team, I'm doing some legwork in aid of my presentation at NZNOG06 Conference. If the reader is what you might call 'Helpdesk' and would be interested in answering a brief questionaire about your job, please drop me an email off list. All information collected will be used in aid of the presentation, noones details will be disclosed to anyone else, it'll remain anonymous, etc. I'm particularly after perspective from those who work in tech support, either for ISPs or larger companies. I may have something for 'NOC type people' at a later stage, too. Thanks for your help Mark.

1 0

Re: [nznog] NZNOG Digest, Vol 38, Issue 12
by ganda y situmorang 17 Feb '06

17 Feb '06

On Sat, 18 Feb 2006 12:00:04 +1300 nznog-request(a)list.waikato.ac.nz wrote: > Send NZNOG mailing list submissions to > nznog(a)list.waikato.ac.nz > > To subscribe or unsubscribe via the World Wide Web, >visit > http://list.waikato.ac.nz/mailman/listinfo/nznog > or, via email, send a message with subject or body >'help' to > nznog-request(a)list.waikato.ac.nz > > You can reach the person managing the list at > nznog-owner(a)list.waikato.ac.nz > > When replying, please edit your Subject line so it is >more specific > than "Re: Contents of NZNOG digest..." > > > Today's Topics: > > 1. Notification of NZRR Database changes > (NZRR Database Notifications) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 17 Feb 2006 16:01:02 +1300 >From: NZRR Database Notifications <rpsl-admin(a)nzix.net> > Subject: [nznog] Notification of NZRR Database changes > To: nznog(a)list.waikato.ac.nz > Message-ID: <E1F9vri-0007kB-LU(a)zidane.citylink.co.nz> > > > > 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:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9560:RS-ROUTES:AS24005 > descr: advertised to AS9560 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > --- > PREVIOUS OBJECT: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20051125 > source: NZRR > > > REPLACED BY: > > route-set: AS9439:RS-ROUTES:AS24005 > descr: advertised to AS9439 by SafeNZ Networks >Limited - AS24005 > members: 202.56.32.0/20^20-29, > 202.56.48.0/21^21-29, > 202.137.240.0/21^21-29, > 202.170.160.0/21^21-29, > 203.98.6.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: tonyw(a)tonyw.com > mnt-by: MAINT-NZRR-NZ > changed: rpsl-admin(a)nzix.net 20060217 > source: NZRR > > > > ------------------------------ > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > End of NZNOG Digest, Vol 38, Issue 12 > ************************************* ======================================================================================== Ikuti Lomba Puisi Online Jawa Timur, dapatkan hadiah menarik setiap bulannya dan hadiah total senilai 60 juta rupiah hanya di http://www.plasa.com (Khusus Jawa Timur) ========================================================================================

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Feb '06

16 Feb '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:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060217 source: NZRR

1 0

SMTP Greylisting
by Craig Whitmore 15 Feb '06

15 Feb '06

I have been playing around with greylisting recently on a couple of test domains and it works pretty well (reduces the number of spam coming from malwared machines who don't retry sending their spam by over 90% before any spam checkers get to it), but I've noticed a number of real mail NZ servers not knowing what a 451 SMTP message is, and they treat it like a fail and they don't send the message again. (Yes I know I can whitelist good known NZ SMTP Serversto not Greylist from them) If anyone else has tried greylisting before , or has any comments on it, let me know. Thanks Craig

10 12

Providers located at Northcote DC
by Barry Murphy 15 Feb '06

15 Feb '06

Hey there beer drinkers, Is anyone here hosting equipment at Vectors Data Center on Northcote Road, Auckland? I currently use Orcon as my bandwidth provider (both national & international) but am looking for backup routes, so if you have connectivity to either Telstra or direct to APE at the facility, please give me a hola offlist. Cheers Barry

1 0

Re: [nznog] SMTP Greylisting
by Ewen McNeill 14 Feb '06

14 Feb '06

In message <20060214230142.GZ26689(a)citylink.co.nz>, Simon Blake writes: >We've been using greylisting here for the last six months, and it's made >a huge difference to the amount of noise [.... through other filters ....] >I would set your timeout to be really low - 15 seconds would be as >effective as 30 minutes, as far as I can see. I can't help wondering how long this beneficial effect of greylisting will last. It's not _that_ difficult for a spammer to ask their purchased botnet to run its spam list twice. Worst case they need twice as many bots. It's not like it's hard to buy 0wn3d machines these days. Those with greylisting enabled get the message once; those without may well get it twice. Bonus. If greylisting becomes relatively common that's exactly what I'd expect spammers to do. And viruses to do. (Viruses can simply follow the same PRNG or discovered list twice. Perhaps 30-60 minutes apart. Not much extra work, for much more effectiveness.) So what do we do next? Defer twice before accepting? Give up on greylisting? And then get two copies (or three copies)? Seems to me that the end result of this particular "arms race" is that mail delivery gets permanently delayed (since no one can "safely" turn off greylisting without getting multiple copies of the junk), and we end up no further forward on the spam/virus problem. Not that I really see an option which doesn't end up "email becomes even more useless" over a relatively short period of time. Frankly I'm amazed it's lasted this long. We've had 5+ years of what is effectively a sustained denial-of-service attack on email. Ewen

2 1

Webcasting Heads Up
by Richard Naylor 13 Feb '06

13 Feb '06

(Wearing my R2 hat) It appears we will be webcasting the 2nd reading of the NZ Sign Language Bill on 23 Feb 06 at around 3pm (after Parliament's Question Time). This will last for approximately 1 hour and has a reasonable audience in the low hundreds. (they packed the House last reading as well and overflowed into two rooms). For those who are unaware, the NZ Sign Language Bill will establish NZ Signing as the third Official Language of NZ, so the passage of the legislation is of interest to the Hearing Impaired community both in NZ and internationally. As before we will run 2 sets of streams - the main camera mix plus a fixed shot of the sign language interpreters. As we are not bandwidth constrained, we will also be running a full set of streams (56kbps, 128kbps, 384kbps and 2Mbps) and they will be served off servers at the main NZ IX points, plus the USA. CityLink advise me that anyone wanting help with a quick peering session with my routers should speak to Andy Linton. I'm happy to set up short duration/temp sessions. In addition, tomorrow we will be making Bloomberg TV available on our servers. This premiere news service will be of interest to the financial community. At the moment the streams are limited to 256kbps, but please note the "at the moment". The streams are available across all servers without restriction. For those interested, the link is http://www.r2.co.nz/meta/bloombergtv.asx Thanks and happy viewing. Rich

1 0

Re: [nznog] SMTP Greylisting
by Jeremy Strachan 13 Feb '06

13 Feb '06

I'm ignoring your email, if its an important topic you'll send beer to grab my attention first. -----Original Message----- From: Simon Lyall [mailto:simon(a)darkmere.gen.nz] Sent: Tuesday, 14 February 2006 1:41 p.m. To: nznog Subject: Re: [nznog] SMTP Greylisting On Tue, 14 Feb 2006, Craig Whitmore wrote: > If anyone else has tried greylisting before , or has any comments on > it, let me know. Personally I find greylisting a pain. I am subscribed to a couple of lists that use it and it's annoying when my reply to the list takes half an hour to get through instead on 2 minutes. One important thing to watch for is that for larger sites the server that first tries to send your email might not be the one that tries to resend it later. Greylisting sites will thus block the email for a while until the sending site gets lucky and uses the same machine twice in a row. Generating random error messages to sending sites is just asking for trouble IMHO. You really can't determine exactly they will act and how long they will take to retry to send the message. Any delay is 100% your fault although most people using greylisting seem keen to push the blame to the sending site. It's the equivalent of ignoring someone when they first email/call you and saying "If it's important they'll ring back" . Not very polite and possibly not providing the best service to customers. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Feb '06

12 Feb '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. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9236 descr: advertised to AS9439 by AMP - AS9236 members: 203.118.136.0/25^25-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jimi.wallace(a)ampcapital.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Feb '06

12 Feb '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:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/20^20-29, 203.97.28.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.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.49.115.0/24^24-29, 202.49.125.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 20050920 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, 202.124.96.0/19^19-29, 203.97.28.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.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.49.115.0/24^24-29, 202.49.125.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 20060213 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 Feb '06

09 Feb '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:AS10022 descr: Route set advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.83.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060210 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.83.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060210 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 Feb '06

09 Feb '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. --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS10022 descr: Route set advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.83.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060210 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Feb '06

08 Feb '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: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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 202.191.32.0/24^24-29, 203.97.5.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 20060209 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060209 source: NZRR

1 0

Re: [nznog] iprimus.net.au
by Gordon Smith 08 Feb '06

08 Feb '06

That's what they have listed http://www.abuse.net/lookup.phtml?DOMAIN=iprimus.net.au ________________________________ From: Paul Adshead [mailto:paul.adshead(a)gmail.com] Sent: Thursday, 9 February 2006 11:40 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] iprimus.net.au Can anyone please confirm the "iprimus.net.au" abuse/spam email address - abuse(a)iprimus.net.au? I can't find it listed. Thanks, Paul.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Feb '06

08 Feb '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: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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060201 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 202.191.32.0/24^24-29, 203.97.5.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 20060209 source: NZRR --- 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.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060201 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060209 source: NZRR

1 0

iprimus.net.au
by Paul Adshead 08 Feb '06

08 Feb '06

Can anyone please confirm the "iprimus.net.au" abuse/spam email address - abuse(a)iprimus.net.au? I can't find it listed. Thanks, Paul.

1 0

Someone from Paradise
by Geraint M. Jones 07 Feb '06

07 Feb '06

Would someone from paradise please be kind enough to contact me offlist Geraint Jones Systems Administrator French Maid Foods Limited www.french-maid.net DDI: +64 (0)4 570 7633 Tel: +64 (0)4 568 2687 Fax: +64 (0)4 568 2345 Mob: +64 (0)21 739 240

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Feb '06

02 Feb '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. --- OBJECT BELOW CREATED: aut-num: AS9788 as-name: NZRR-AS9788 descr: Inland Revenue Department descr: WIX peering at '202.7.1.15' descr: see Citylink RT job #4229 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS9788 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: osi(a)ird.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS9788 descr: Route set advertised to AS9439 by Inland Revenue Department - AS9788 members: 138.235.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: osi(a)ird.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Feb '06

02 Feb '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:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050909 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.32.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050909 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.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: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Feb '06

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

Notification of NZRR Database changes
by NZRR Database Notifications 01 Feb '06

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

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

31 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: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.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.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 20050901 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060201 source: NZRR --- 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.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 20050901 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, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.50.200.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.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, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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 20060201 source: NZRR

1 0

SORBs blacklisting Paradise MTAs
by neil gardner 31 Jan '06

31 Jan '06

Hi gents (and gentesses) I reported to Paradise that Sorbs was blacklisting a particular Paradise MTA last night (details below) and their response was that sorbs refuse to whitelist them so there's nothing they can do about it... The further state that "SORBS automatically delist the servers after a 48 hour time period, and mail passing through the once affected mail server should flow as per normal." yet the information pasted below seems to indicate that the particular IP I reported has been on the list since Dec 11th 2005. They're spinning me a line right? The Sorbs record hasn't been updated since Dec 11th! *--- Info from sorbs as of 5 minutes ago *--- Address: 203.96.152.180 Record Created: Sun Dec 11 13:53:04 2005 GMT Record Updated: Sun Dec 11 13:53:04 2005 GMT Additional Information: Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [203.96.152.180]) by vampire.isux.com (Postfix) with ESMTP id 58986B90C; Sun, 11 Dec 2005 13:52:40 +0000 (UTC) Currently active and flagged to be published in DNS *--- end info from sorbs *--- Why would Paradise deliberately avoid resolving this issue when pointed out to them? If anyone from Paradise / Telstraclear would like to jump in and explain why your helpdesker effectively refused to do anything about the situation then I'm all ears. Yes, I did report to Paradise through the appropriate mechanism, then I replied to their automated response, then this morning I phoned to report it and had my number taken (no-one has phoned back) and a few minutes ago I received the reply to the original message saying they can't do anything. Cheers - Neil G Neil Gardner Product Manager Allied Telesyn Research Ltd New Zealand +64 3 339-9509 (ph) +64 3 339-3001 (fax) NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

2 2

Re: [nznog] SORBs blacklisting Paradise MTAs
by Nic Wise 31 Jan '06

31 Jan '06

If it's any help - and I'd expect most people here to know this anyway - Paradise pop up on RBL's so often, I've had to add a whitelist for them in my system, or most of the people I know (who use cable) get blocked. This isn't a new thing at all. :) Cheers Nic > -----Original Message----- > From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] > Sent: Wednesday, 1 February 2006 2:12 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] SORBs blacklisting Paradise MTAs > > Hi gents (and gentesses) > > I reported to Paradise that Sorbs was blacklisting a > particular Paradise MTA last night (details below) and their > response was that sorbs refuse to whitelist them so there's > nothing they can do about it... > > The further state that "SORBS automatically delist the > servers after a 48 hour time period, and mail passing through > the once affected mail server should flow as per normal." yet > the information pasted below seems to indicate that the > particular IP I reported has been on the list since Dec 11th 2005. >

1 0

Update re NZNOG 06 Pricing
by Mark Foster 31 Jan '06

31 Jan '06

In light of recent enquiries, The Organising Committee for NZNOG 06 can confirm that the rates-per-person for attendance at NZNOG06 are likely to be in the ballpark of $250/person. If anything they will wind up lower than this, as sponsorship arrangements are finalised, etc. Note: This does NOT include accomodation, but it does include morning coffee, lunch, and afternoon tea, as well as the conference dinner. More info as it comes to hand; this info will be added to the nznog.org site when I get somewhere that allows SSH out its firewall. :) I hope this info is enough for people to get their respective managers approvals for our excellent-value-for-money event. The guest-speaker list will be further updated tonight as well, so take a peek at nznog.org tomorrow for the latest. Cheers Mark, For the NZNOG Organising Committee.

1 0