- NZNOG - lists.nznog.org

[Fwd: Academic Study - Telephone Interview]
by Gerard Creamer 23 Oct '07

23 Oct '07

The following came into the info (at) nznog email address. Usually such things make their way to the recycle bin (it used to be the deleted, but we've gone PC /and/ green). This one looked like it might be of interest to someone and possibly even on topic for the list, so if it is something of interest to you please contact the person directly. If I'm wrong please flame me without regard for my feelings (as feeling are definitely off topic :^) Regards, Gerard -------- Original Message -------- Subject: Academic Study - Telephone Interview Date: Wed, 24 Oct 2007 14:54:33 +1300 From: Juan Gan <ganju908 (at) student.otago.ac.nz> To: info (at) nznog.org Hi, My name is Juan-Jim Gan and I am a student at the University of Otago. I am currently conducting a study on the Telecommunication Policymaking in New Zealand ─ specifically dealing with issues of the LLU (Local Loop Unbundling). While conducting my research, I stumbled upon NZNOG - an online community of network operators, predominantly in the Internet and Online Services area. This study could benefit from getting feedback from people within this community (people who are either directly or indirectly related to the LLU). I would like to ask for your permission to talk to someone from this community [via a short telephone interview] with regards to their view on the LLU. The participant could be anyone with an interest in the LLU. Information gathered from this interview could be very valuable for my study on the LLU. I would really appreciate it if you [or anyone from the community] agree to participate in this study. Participation in this study is entirely voluntary and you may choose not to participate or to withdraw your consent to be in the study, for any reason, at any time. Materials gathered from this interview will not be published. If you are interested in taking part in this study, please contact me via e-mail to arrange a suitable time to conduct the interview. My supervisor, Dr. Michael Bourk will be supervising this study. If you have any questions, please do not hesitate to contact either myself or Dr Bourk. Dr Bourk could be contacted on 03 ? 479 5751 or via email at Michael.bourk (at) otago.ac.nz. Your involvement in this study would be greatly appreciated. Thank you, Juan-Jim Gan -- 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

1 0

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

23 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: 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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 192.173.16.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071003 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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071024 source: NZRR ------------------------------------------------------------

1 0

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

23 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES: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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 192.173.16.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071003 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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071024 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Re Yahoo and Spam...
by jwkckid1＠ix.netcom.com 22 Oct '07

22 Oct '07

Lenz and all, I am sorry you take the view you do regarding my suggestion. Very unfortunate. None the less, with the amount of spam Yahoo.com and Yahoo.de sems to allow is a huge waste of bandwidth which effects directly the stability of the Internet not to mention irritates unsuspecting users. Hence in part my suggestion. Unless there is a bonified threat of some sort, expecting mass spammers like Yahoo and AOL to curtail their network traffic accordingly, will never occur. However our members routienly block all AOL traffic/Email and all Yahoo.de traffic/Email currently, and have for some time. I suspect they will continue to do so for the forseeable future. -----Original Message----- >From: lengsc(a)coretech.co.nz >Sent: Oct 22, 2007 4:39 PM >To: nznog(a)list.waikato.ac.nz >Subject: Re: [nznog] Re Yahoo and Spam... > >hi, > >i see IMHO no use in spamming ICANN for things that that far away from >their responsibilities like this issue. drop the server in blacklists, >try to raise awarenes for the problem at the companies (spam the board >of yahoo/aol) or do something alike. ICANN has nothing to do with >mailservers and ICANN can not take down any address because they >manage the root not the respective second level domains.yahoo.com is >registered via markmonitor but i am pretty shure that they will not >take down the domain as well. >the approach you suggest is a bit kindergarden like and shows very >little knowledge of the different responsibilities in the internet. > >greets >lenz > >Quoting jwkckid1(a)ix.netcom.com: > >> Mark, >> >> Yahoo and AOL are famous for not addressing Spam or >> any abuse complaints. I have in the recent past suggested >> to ICANN that these sites be taken down unless or until >> they actually address abuse concerns in a direct and meaningful >> way and not with "Canned Email responses". Of course >> ICANN has refused to address this situation with Yahoo or >> AOL as well as Google, simply because of the presence in >> which these Domain names represent, which is IMHO besides >> the point. So I would suggest that every time you get >> one of the "Canned Email responses" you direct it to >> the ICANN bod or vint Cerf at the Email addresses I >> CC'ed this response to, until a ligitimate solution is >> effected. >> >> -----Original Message----- >>> From: Mark Foster <blakjak(a)blakjak.net> >>> Sent: Oct 19, 2007 6:49 PM >>> To: nznog(a)list.waikato.ac.nz >>> Subject: [nznog] Re Yahoo and Spam... >>> >>> Learned NZNOGrs, >>> >>> Some advice, please. >>> >>> Recently an email address that comes to me was sent some Unsolicited >>> Commercial Email from (apparently) a UK based outfit that sells (print) >>> magazine subscriptions. >>> >>> The headers contain this: >>> >>> Received: from smtp107.biz.mail.re2.yahoo.com >>> (smtp107.biz.mail.re2.yahoo.com [206.190.52.176]) >>> by mx.blakjak.net (Postfix) with SMTP id 8C508500D4 >>> for <dest(a)address>; Tue, 16 Oct 2007 12:02:52 +1300 (NZDT) >>> >>> They contain additional Received: headers which would imply that Yahoo >>> themselves received the message via SMTP from an AOL IP address that >>> Traceroute implies is likely in the UK as well. >>> >>> So I took a full-headers copy of the message and forwarded the complaint >>> to the relevant abuse contacts for both Yahoo and AOL. >>> >>> AOL, i've heard nothing (unsuprising). Yahoo, I had a response within 2-3 >>> days which basically absolved them of responsibility, as follows: >>> >>> --8<-- >>> >>> Thank you for writing to Yahoo! Mail. >>> >>> I understand your frustration in receiving unsolicited email. While we >>> investigate all reported violations against the Yahoo! Terms of Service >>> (TOS), in this particular case the message you received was not sent >>> through the Yahoo! Mail system. >>> >>> Yahoo! has no control over activities outside its service, and therefore >>> we cannot take action. You may try contacting the sender's email >>> provider, by identifying the sender's domain and contacting the >>> administrator of that domain. The sender's provider should be in a >>> better position to take appropriate action against the sender's account. >>> >>> The email message itself does contain some information relating to the >>> sender's identity. Yahoo! includes the originating Internet Protocol >>> (IP) address in the full Internet headers of all messages sent through >>> Yahoo! Mail, so that we will have information regarding the origin of >>> messages sent through our system. The originating IP address should be >>> located in the very last "Received" line of the full Internet headers >>> and corresponds to the sender's Internet Service Provider (ISP). >>> >>> Please see the following URL for more assistance: >>> >>> http://help.yahoo.com/help/us/mail/spam/spam-05.html >>> >>> Once you have identified the IP address, you can conduct an IP lookup to >>> determine which ISP provides this person with Internet access. One such >>> lookup tool you may want to try is: >>> >>> http://www.arin.net/whois/ >>> >>> You can then attempt to contact that ISP to report any abuse activities >>> occurring within their service. >>> >>> Please let us know if you still need assistance so I may assist you >>> further. >>> >>> Your patience during this process is greatly appreciated. >>> >>> Thank you again for contacting Yahoo! Mail. >>> >>> Regards, >>> >>> --8<-- >>> >>> I responded back indicating my understanding as being: >>> >>> - That my MTA received it from Yahoo, thus they relayed it... >>> - That headers below the line where my MTA actually is involved, are often >>> untrustworthy... >>> >>> I got a very-slightly-reworded version of exactly the same canned response >>> back. >>> >>> >>> So despite the fact that the sender is very clearly using Yahoo for SMTP >>> (which, one would hope, would establish the sender as a Yahoo! Mail >>> customer), they're pleading ignorance and/or innocence. >>> >>> Any other players had similar dealings with Yahoo (or other free mail >>> providers) ? At what point can the provider realistically abdicate from >>> responsibility when it comes to spam? >>> >>> And the obvious question: Is it fair to expect more from them? Or am I >>> resigned to accept either periodic junk relayed by Yahoo because they >>> can't be held responsible for what individual customers do? (And because >>> in this example, the collateral damage of blackholing them is probably >>> unacceptable? >>> >>> Cheers >>> Mark. >>> >> ======= >> >> 'Regards, >> Jeffrey A. Williams >> Spokesman for INEGroup LLA. - (Over 277k members/stakeholders strong!) >> "Obedience of the law is the greatest freedom" - >> Abraham Lincoln >> >> "Credit should go with the performance of duty and not with what is very >> often the accident of glory" - Theodore Roosevelt >> >> "If the probability be called P; the injury, L; and the burden, B; liability >> depends upon whether B is less than L multiplied by >> P: i.e., whether B is less than PL." >> United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] >> =============================================================== >> Updated 1/26/04 >> CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of >> Information Network Eng. INEG. INC. >> ABA member in good standing member ID 01257402 E-Mail jwkckid1(a)ix.netcom.com >> ======= 'Regards, Jeffrey A. Williams Spokesman for INEGroup LLA. - (Over 277k members/stakeholders strong!) "Obedience of the law is the greatest freedom" - Abraham Lincoln "Credit should go with the performance of duty and not with what is very often the accident of glory" - Theodore Roosevelt "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. ABA member in good standing member ID 01257402 E-Mail jwkckid1(a)ix.netcom.com

4 3

Re: [nznog] Re Yahoo and Spam...
by jwkckid1＠ix.netcom.com 22 Oct '07

22 Oct '07

Mark, Yahoo and AOL are famous for not addressing Spam or any abuse complaints. I have in the recent past suggested to ICANN that these sites be taken down unless or until they actually address abuse concerns in a direct and meaningful way and not with "Canned Email responses". Of course ICANN has refused to address this situation with Yahoo or AOL as well as Google, simply because of the presence in which these Domain names represent, which is IMHO besides the point. So I would suggest that every time you get one of the "Canned Email responses" you direct it to the ICANN bod or vint Cerf at the Email addresses I CC'ed this response to, until a ligitimate solution is effected. -----Original Message----- >From: Mark Foster <blakjak(a)blakjak.net> >Sent: Oct 19, 2007 6:49 PM >To: nznog(a)list.waikato.ac.nz >Subject: [nznog] Re Yahoo and Spam... > >Learned NZNOGrs, > >Some advice, please. > >Recently an email address that comes to me was sent some Unsolicited >Commercial Email from (apparently) a UK based outfit that sells (print) >magazine subscriptions. > >The headers contain this: > >Received: from smtp107.biz.mail.re2.yahoo.com >(smtp107.biz.mail.re2.yahoo.com [206.190.52.176]) > by mx.blakjak.net (Postfix) with SMTP id 8C508500D4 > for <dest(a)address>; Tue, 16 Oct 2007 12:02:52 +1300 (NZDT) > >They contain additional Received: headers which would imply that Yahoo >themselves received the message via SMTP from an AOL IP address that >Traceroute implies is likely in the UK as well. > >So I took a full-headers copy of the message and forwarded the complaint >to the relevant abuse contacts for both Yahoo and AOL. > >AOL, i've heard nothing (unsuprising). Yahoo, I had a response within 2-3 >days which basically absolved them of responsibility, as follows: > >--8<-- > >Thank you for writing to Yahoo! Mail. > >I understand your frustration in receiving unsolicited email. While we >investigate all reported violations against the Yahoo! Terms of Service >(TOS), in this particular case the message you received was not sent >through the Yahoo! Mail system. > >Yahoo! has no control over activities outside its service, and therefore >we cannot take action. You may try contacting the sender's email >provider, by identifying the sender's domain and contacting the >administrator of that domain. The sender's provider should be in a >better position to take appropriate action against the sender's account. > >The email message itself does contain some information relating to the >sender's identity. Yahoo! includes the originating Internet Protocol >(IP) address in the full Internet headers of all messages sent through >Yahoo! Mail, so that we will have information regarding the origin of >messages sent through our system. The originating IP address should be >located in the very last "Received" line of the full Internet headers >and corresponds to the sender's Internet Service Provider (ISP). > >Please see the following URL for more assistance: > > http://help.yahoo.com/help/us/mail/spam/spam-05.html > >Once you have identified the IP address, you can conduct an IP lookup to >determine which ISP provides this person with Internet access. One such >lookup tool you may want to try is: > > http://www.arin.net/whois/ > >You can then attempt to contact that ISP to report any abuse activities >occurring within their service. > >Please let us know if you still need assistance so I may assist you >further. > >Your patience during this process is greatly appreciated. > >Thank you again for contacting Yahoo! Mail. > >Regards, > >--8<-- > >I responded back indicating my understanding as being: > >- That my MTA received it from Yahoo, thus they relayed it... >- That headers below the line where my MTA actually is involved, are often >untrustworthy... > >I got a very-slightly-reworded version of exactly the same canned response >back. > > >So despite the fact that the sender is very clearly using Yahoo for SMTP >(which, one would hope, would establish the sender as a Yahoo! Mail >customer), they're pleading ignorance and/or innocence. > >Any other players had similar dealings with Yahoo (or other free mail >providers) ? At what point can the provider realistically abdicate from >responsibility when it comes to spam? > >And the obvious question: Is it fair to expect more from them? Or am I >resigned to accept either periodic junk relayed by Yahoo because they >can't be held responsible for what individual customers do? (And because >in this example, the collateral damage of blackholing them is probably >unacceptable? > >Cheers >Mark. > ======= 'Regards, Jeffrey A. Williams Spokesman for INEGroup LLA. - (Over 277k members/stakeholders strong!) "Obedience of the law is the greatest freedom" - Abraham Lincoln "Credit should go with the performance of duty and not with what is very often the accident of glory" - Theodore Roosevelt "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. ABA member in good standing member ID 01257402 E-Mail jwkckid1(a)ix.netcom.com

2 1

Of interest - Yahoo mail issues
by Michael J. Densem 22 Oct '07

22 Oct '07

Hi, This is simply some information that may be of interest to those who have had/are having issues with Xtra email since the change over to Yahoo! I had problems with their servers rejecting email from my servers back in August (when Xtra changed to Yahoo for email services). I filled out all the suggested documents and requests to have my server(s) white-listed. Today (23 Oct) I finally had a response (see email below). No further comment! - just FYI -----Original Message----- From: Yahoo! Mail [mailto:mail-abuse-review(a)cc.yahoo-inc.com] Sent: Tuesday, 23 October 2007 7:45 a.m. To: Michael J. Densem Subject: Yahoo! Customer Care - monitor results... (KMM59108720V785******) Hello Mike, We appreciate your patience. We have recently concluded the monitoring of your company's mailings. Based on the information we have gathered, it appears that our users deem that the mailings from your IP address(es) are being directed to the correct folder and we cannot systematically exempt your mailings from our SpamGuard technology for: 202.174.***.*** 202.174.***.*** 202.174.***.*** Please keep in mind that our SpamGuard technology will continually monitor user feedback pertaining to emails coming from your mail server(s), and as such, the user feedback we receive will be one of the factors that influence where your emails are most appropriately delivered. Our studies have indicated that when users see messages miscategorized, they notify us within hours of delivery. Note: If you wish to ensure that your users get your emails in their Inbox, you may want to ask your subscribers to set up a filter in Yahoo! Mail specifically for your emails, or have them add your email address(es) to their Yahoo! Address Book. If you implement significant changes to your mailing practices, feel free to contact us again in 6 months and we will send you our most up-to-date application and reevaluate your mailing practices at that time. You may refer to the Help page below for some information and general guidelines that we have found to be effective in maintaining good mailing lists: http://help.yahoo.com/help/us/mail/bulk/bulk-01.html Please let us know if you still experience problems so we may assist you further to resolve your issue. Your patience during this process is greatly appreciated. Thank you again for contacting Yahoo! Mail. Regards, Thomas Immer Yahoo! Customer Care

1 0

Re: [nznog] Citylink problems?
by Tony Wicks 21 Oct '07

21 Oct '07

Ok, I'll run a pool for cause. Propose possible reasons and I'll come up with odds. All betting to be done in the currency of handles to be settled at the next meeting. Well Its been more than a couple of more hours now ! There had better be a good explanation and I really love the - Network Status - No known fault System Status Normal - No major problems

6 7

Re Yahoo and Spam...
by Mark Foster 19 Oct '07

19 Oct '07

Learned NZNOGrs, Some advice, please. Recently an email address that comes to me was sent some Unsolicited Commercial Email from (apparently) a UK based outfit that sells (print) magazine subscriptions. The headers contain this: Received: from smtp107.biz.mail.re2.yahoo.com (smtp107.biz.mail.re2.yahoo.com [206.190.52.176]) by mx.blakjak.net (Postfix) with SMTP id 8C508500D4 for <dest(a)address>; Tue, 16 Oct 2007 12:02:52 +1300 (NZDT) They contain additional Received: headers which would imply that Yahoo themselves received the message via SMTP from an AOL IP address that Traceroute implies is likely in the UK as well. So I took a full-headers copy of the message and forwarded the complaint to the relevant abuse contacts for both Yahoo and AOL. AOL, i've heard nothing (unsuprising). Yahoo, I had a response within 2-3 days which basically absolved them of responsibility, as follows: --8<-- Thank you for writing to Yahoo! Mail. I understand your frustration in receiving unsolicited email. While we investigate all reported violations against the Yahoo! Terms of Service (TOS), in this particular case the message you received was not sent through the Yahoo! Mail system. Yahoo! has no control over activities outside its service, and therefore we cannot take action. You may try contacting the sender's email provider, by identifying the sender's domain and contacting the administrator of that domain. The sender's provider should be in a better position to take appropriate action against the sender's account. The email message itself does contain some information relating to the sender's identity. Yahoo! includes the originating Internet Protocol (IP) address in the full Internet headers of all messages sent through Yahoo! Mail, so that we will have information regarding the origin of messages sent through our system. The originating IP address should be located in the very last "Received" line of the full Internet headers and corresponds to the sender's Internet Service Provider (ISP). Please see the following URL for more assistance: http://help.yahoo.com/help/us/mail/spam/spam-05.html Once you have identified the IP address, you can conduct an IP lookup to determine which ISP provides this person with Internet access. One such lookup tool you may want to try is: http://www.arin.net/whois/ You can then attempt to contact that ISP to report any abuse activities occurring within their service. Please let us know if you still need assistance so I may assist you further. Your patience during this process is greatly appreciated. Thank you again for contacting Yahoo! Mail. Regards, --8<-- I responded back indicating my understanding as being: - That my MTA received it from Yahoo, thus they relayed it... - That headers below the line where my MTA actually is involved, are often untrustworthy... I got a very-slightly-reworded version of exactly the same canned response back. So despite the fact that the sender is very clearly using Yahoo for SMTP (which, one would hope, would establish the sender as a Yahoo! Mail customer), they're pleading ignorance and/or innocence. Any other players had similar dealings with Yahoo (or other free mail providers) ? At what point can the provider realistically abdicate from responsibility when it comes to spam? And the obvious question: Is it fair to expect more from them? Or am I resigned to accept either periodic junk relayed by Yahoo because they can't be held responsible for what individual customers do? (And because in this example, the collateral damage of blackholing them is probably unacceptable? Cheers Mark.

1 0

JobSpam
by Richard Nelson 17 Oct '07

17 Oct '07

If you are tired of the attractions of the real world, burdened by responsibility and overpaid or just need to move to Hamilton before the V8s get here then you will be pleased to learn that WAND are looking for a Research Fellow. see http://www.waikato.ac.nz/hrm/vacancies/270292.shtml Richard.

1 0

Emails to xtra addresses not being delivered
by Vaughan Chetwynd 16 Oct '07

16 Oct '07

My server generates emails for about 150 members of a choir. 30 of these have xtra addresses, and since the change to yahoo, these are not being delivered. All other addresses work OK. The xtra addresses were OK before the yahoo bubble started up. I receive no notification of non delivery. Can anybody tell me what I need to do to get these emails accepted by the xtra servers? Vaughan Chetwynd 968c Tauwhare Road RD4 Hamilton phone 07 824 0983 mobile 0275 657 724

2 1

Re: [nznog] Citylink problems?
by Anton Smith 16 Oct '07

16 Oct '07

Simon wrote: > I'll do a more in depth explanation tomorrow. Essentially, this started > happening, on every interswitch trunk on most switches on the network: > > Oct 6 14:09:07: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back > detected on FastEthernet0/24. > Oct 6 14:09:07: %PM-4-ERR_DISABLE: loopback error detected on Fa0/24, > putting Fa0/24 in err-disable state Oct 6 14:09:08: %LINEPROTO-5-UPDOWN: > Line protocol on Interface FastEthernet0/24, changed state to down Oct 6 > 14:09:09: %LINK-3-UPDOWN: Interface FastEthernet0/24, changed state to down > Oct 6 14:09:50: %PM-4-ERR_RECOVER: Attempting to recover from loopback > err-disable state on Fa0/24 Oct 6 14:09:55: %LINK-3-UPDOWN: Interface > FastEthernet0/24, changed state to up Oct 6 14:09:57: %LINEPROTO-5-UPDOWN: > Line protocol on Interface FastEthernet0/24, changed state to up Oct 6 > 14:09:57: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back detected > on FastEthernet0/24. Any further word on the more in depth explanation? Interested from both a customer perspective and a technical perspective - good to learn from these things. Regards, Anton

3 2

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

15 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks - 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.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20061026 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 124.155.224.0/20^20-29, 202.170.160.0/20^20-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20071016 source: NZRR ------------------------------------------------------------

1 0

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

15 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks - 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.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20061026 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 124.155.224.0/20^20-29, 202.170.160.0/20^20-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20071016 source: NZRR ------------------------------------------------------------

1 0

Dunedin 5.8GHz
by Stewart Fleming 13 Oct '07

13 Oct '07

Anyone changed anything in Dunedin in ISM band? We're seeing severe operational problems with interference in North Dunedin facing south on channels 5836 (both H and V) and 5736 (H and V). Issue started this morning around 10am and ongoing. -- -- Tel: 03 474 2100 Cell: 021 993 125 Web: www.wic.co.nz Co-location and Web hosting. Dunedin-wide wireless. Independent Internet Service Provider.

2 1

Linkedin NZNOG group
by Simon Lyall 13 Oct '07

13 Oct '07

Please Ignore if you don't use Linkedin Linkedin is "a business-oriented social networking site, mainly used for professional networking" [1] . See the the website http://www.linkedin.com for more details. Anyway since there seem to be a lot of NZNOG people there and they have recently allowed the creation of groups I have added a "NZNOG" group. To join go to the URL below ( No doubt it complains if you are not a member). http://www.linkedin.com/e/gis/37382/36D4B725B06C It'll send me an email and I can then add you. [1] - I think this means it helps you get cool jobs making lots of money. So far I've just been adding people into my network, however if you *do* have a cool job paying lots of money... ;) -- 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

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

08 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by IHUG LTD - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071009 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by IHUG LTD - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: ada.m(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071009 source: NZRR ------------------------------------------------------------

1 0

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

08 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070330 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by IHUG LTD - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071009 source: NZRR ------------------------------------------------------------

1 0

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

08 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070330 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by IHUG LTD - AS7657 members: 118.92.0.0/15^15-29, 130.216.0.0/15^15-29, 121.90.0.0/16^16-29, 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 202.129.64.0/18^18-29, 203.118.128.0/18^18-29, 210.84.0.0/18^18-29, 124.6.192.0/19^19-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.46.160.0/20^20-29, 202.73.192.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.36.16.0/21^21-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.4.208.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.36.24.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 97.64.46.0/24^24-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 192.190.108.0/24^24-29, 198.32.71.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.136.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.31.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: ada.m(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071009 source: NZRR ------------------------------------------------------------

1 0

Admin: More List problems.
by Simon Lyall 05 Oct '07

05 Oct '07

FYI around 35 people were unsubscribed from the NZNOG list around lunchtime Friday. This is due to Waikato mail servers rejecting emails being sent to some @list.waikato.ac.nz addresses that are being used by mailman [1] which causes problems with sites that use SMTP callback to check sending addresses. They rejected the emails to mailman unsubscribed the addresses. Most of the addresses removed were hosted by Orcon. If anyone sees Colin Palmer around can they nudge him ( "nudge" means "/msg him" NOT "Wake him up at 1am" ) to have a look at this since I don't have his contact details. Once things are fixed I'll undisable everybody [2] . [1] $ telecom mx1.its.waikato.ac.nz smtp Trying 130.217.76.2... Connected to mx1.its.waikato.ac.nz. Escape character is '^]'. 220 mx1.its.waikato.ac.nz ESMTP Symantec Mail Security helo fff 250 mx1.its.waikato.ac.nz mail from:<simon(a)darkmere.gen.nz> 250 Ok rcpt to:<nznog-bounces+john=example.net(a)list.waikato.ac.nz> 550 <nznog-bounces+john=example.net(a)list.waikato.ac.nz>: Recipient address rejected: User unknown in relay recipient table [2] I've up'd the "bounce_you_are_disabled_warnings" number from 5 to 50 which I think is the right one, email me directly if I'm wrong. -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 1

Citylink problems?
by blair.robson＠ihug.co.nz 05 Oct '07

05 Oct '07

Hi - is anyone aware of any scheduled or unscheduled Citylink outages? Citylink Helpdesk appear to be unavailable which would indicate an issue of some sort. Just wondering if anyone has any information or a network status / ETA for this? Any help appreciated. Regards, Blair Robson

4 4

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

03 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 202.6.116.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070511 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/24^24-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/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)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071004 source: NZRR ------------------------------------------------------------

1 0

Continued problems with xtra email
by Michael J. Densem 03 Oct '07

03 Oct '07

Can anyone help? Since Xtra changed over its email service to Yahoo! I have had problems. I have a server (outside of the Xtra network) that handles email for around 50 domains. Many of these are collection points that forward to client recipients with @xtra.co.nz addresses. Due to the large volume of email traffic sending to the xtra.co.nz domain, the Yahoo servers are now blocking/grey-listing my server. I have filled out the forms on the Yahoo website and have spoken to Xtra. However, I have had no response from Yahoo and Xtra doesn't seem to understand or appreciate the issue. Is anyone else in a similar situation? Had similar issues? Does anyone know a solution? The response from the Yahoo servers is '451 Message temporarily deferred' (meaning Yahoo first denies the initial attempt and waits for a re-try). However, none of the re-tries is accepted and the message eventually expires. Any suggestions would be appreciated. Cheers, Mike Densem mike(a)massive.co.nz

20 42

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

02 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: 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.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20070809 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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 192.173.16.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071003 source: NZRR ------------------------------------------------------------

1 0

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

02 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES: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.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20070809 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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 192.173.16.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20071003 source: NZRR ------------------------------------------------------------

1 0

186/8 and 187/8 allocated to LACNIC
by Leo Vegoda 30 Sep '07

30 Sep '07

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

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 Sep '07

30 Sep '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.192.160/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070912 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24006 descr: advertised to AS9439 by Knossos Networks Ltd - AS24006 members: 202.160.48.0/20^20-29, 161.29.254.0/23^23-29, 202.53.189.0/28^28-29, 161.29.192.160/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)knossos.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071001 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] NZNOG Digest, Vol 57, Issue 9
by Paul Lester 30 Sep '07

30 Sep '07

Unsubscribe -----Original Message----- From: nznog-request(a)list.waikato.ac.nz [mailto:nznog-request(a)list.waikato.ac.nz] Sent: Saturday, 29 September 2007 12:00 p.m. To: nznog(a)list.waikato.ac.nz Subject: NZNOG Digest, Vol 57, Issue 9 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. NZRR Route Registry Update (NZRR Database Notifications) 2. Admin: More List problems. (Simon Lyall) ---------------------------------------------------------------------- Message: 1 Date: Fri, 28 Sep 2007 12:04:28 +1200 From: NZRR Database Notifications <rpsl-admin(a)nzix.net> Subject: [nznog] NZRR Route Registry Update To: nznog(a)list.waikato.ac.nz Message-ID: <E1Ib3LI-0000l2-N1(a)totti.citylink.co.nz> Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 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.8.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 20070920 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070928 source: NZRR ------------------------------------------------------------ ------------------------------ Message: 2 Date: Fri, 28 Sep 2007 23:16:42 +1200 (NZST) From: Simon Lyall <simon(a)darkmere.gen.nz> Subject: [nznog] Admin: More List problems. To: nznog <nznog(a)list.waikato.ac.nz> Message-ID: <Pine.LNX.4.56.0709282248020.2085(a)localhost.localdomain> Content-Type: TEXT/PLAIN; charset=US-ASCII FYI around 35 people were unsubscribed from the NZNOG list around lunchtime Friday. This is due to Waikato mail servers rejecting emails being sent to some @list.waikato.ac.nz addresses that are being used by mailman [1] which causes problems with sites that use SMTP callback to check sending addresses. They rejected the emails to mailman unsubscribed the addresses. Most of the addresses removed were hosted by Orcon. If anyone sees Colin Palmer around can they nudge him ( "nudge" means "/msg him" NOT "Wake him up at 1am" ) to have a look at this since I don't have his contact details. Once things are fixed I'll undisable everybody [2] . [1] $ telecom mx1.its.waikato.ac.nz smtp Trying 130.217.76.2... Connected to mx1.its.waikato.ac.nz. Escape character is '^]'. 220 mx1.its.waikato.ac.nz ESMTP Symantec Mail Security helo fff 250 mx1.its.waikato.ac.nz mail from:<simon(a)darkmere.gen.nz> 250 Ok rcpt to:<nznog-bounces+john=example.net(a)list.waikato.ac.nz> 550 <nznog-bounces+john=example.net(a)list.waikato.ac.nz>: Recipient address rejected: User unknown in relay recipient table [2] I've up'd the "bounce_you_are_disabled_warnings" number from 5 to 50 which I think is the right one, email me directly if I'm wrong. -- Simon 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 End of NZNOG Digest, Vol 57, Issue 9 ************************************

1 0

NZRR Route Registry Update
by NZRR Database Notifications 27 Sep '07

27 Sep '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 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.8.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 20070920 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.27.77.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070928 source: NZRR ------------------------------------------------------------

1 0

Dual boot lenny and etch on one HD?
by Simon 26 Sep '07

26 Sep '07

Hi There, We have installed lenny on sda1. Once sorted, i have debootstrap'ed etch onto sda3, with sda2 being the swap. So ive then added the last line to /boot/grub/menu.lst on sda1 # lenny title Debian GNU/Linux, kernel 2.6.21-2-686 root (hd0,0) kernel /boot/vmlinuz-2.6.21-2-686 root=/dev/sda1 ro quiet initrd /boot/initrd.img-2.6.21-2-686 savedefault title Debian GNU/Linux, kernel 2.6.21-2-686 (single-user mode) root (hd0,0) kernel /boot/vmlinuz-2.6.21-2-686 root=/dev/sda1 ro quiet single initrd /boot/initrd.img-2.6.21-2-686 savedefault #etch title Debian GNU/Linux, kernel 2.6.18-5-686 (etch) root (hd3,0) kernel /boot/vmlinuz-2.6.18-5-686 root=/dev/sda3 ro quiet initrd /boot/initrd.img-2.6.18-5-686 savedefault But im getting "Selected disk does not exist.. should this be (hd0,3)? or have i got this COMPLETLY wrong? Thanks Simon

2 2

APRICOT 2008 Call for Papers : Deadline nearing
by Gaurab Raj Upadhaya 19 Sep '07

19 Sep '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Taipei, Taiwan 20 - 29 February 2008 http://www.apricot2008.net Summary Call for Papers - --------------------- Please submit online at http://submission.apricot.net/paper/user/login.php?event=7 The APRICOT 2008 Program Committee is now seeking contributions to the program. This is the main call for Presentations & Tutorials before the final program is fixed. We would like to give people the opportunity to submit their proposals early and to encourage people in the Asia Pacific region who have not previously presented their work to do so. They key dates are Call for Papers Opens: 1 July 2007 Deadline for Speaker Submissions: 30 September 2007 First Draft Program Published: 15 October 2007 Final Program Published: 15 January 2008 Topics of interest to the network operations community are invited for both tutorial and conference presentation. APRICOT also co-hosts the APNIC members' meeting, Asia Broadband Summit, Asia Pacific IPv6 Task Force meeting, as well as the members meeting of Asia Pacific Top Level Domains, making it the largest network operations meeting in the region. The full cfp is at : http://submission.apricot.net/apricot08-cfp.htm You can make your submissions online at : http://submission.apricot.net/paper/user/login.php?event=7 Thanks APRICOT Program Committee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8khySo7fU26F3X0RAkE+AJwLb6dKnQkQ5VSceseHHcecNqHUcACgqwx5 CvscVtSzJheU+lEVrnRS2pQ= =a3b6 -----END PGP SIGNATURE-----

1 0

NZRR Route Registry Update
by NZRR Database Notifications 19 Sep '07

19 Sep '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet 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 REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 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.8.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 20070920 source: NZRR ------------------------------------------------------------

1 0

SysAdmin Miniconf 2008: Proposal deadline 1st of October
by Simon Lyall 18 Sep '07

18 Sep '07

As part of the linux.conf.au conference to be held in Melbourne, Australia in January 2008 we will be holding a 1 day mini conference on Linux Systems Administration on Tuesday the 29th of January. A reminder to prospective speakers that proposals must be submitted by the 1st of October in order to have the best chance of being accepted. Submissions received after this date have a much lower chance of being accepted and we strongly urge people interested in submitting a proposal to contact us as soon as possible. The Call for Presentations web page at: http://sysadmin.miniconf.org/cfp08.html We are especially after short "How we do things" presentations from people in the field in order to give others a picture of what is happening in the real world. Submissions (and any questions) should be sent to: lca08 @ sysadmin.miniconf.org.

1 0

NZNOG list problems.
by Simon Lyall 17 Sep '07

17 Sep '07

Please note that the NZNOG list is currently having problems due to what appears to be an error with the MX record for list.waikato.ac.nz . IF anyone knows the best person to contact at waikato for this could they please email Simon Blake, Donald Neal and Myself or if it is quicker contact the correct person directly . I knew things were too quiet...

1 1

Re: [nznog] Akamai HK problem
by Ian Henderson 06 Sep '07

06 Sep '07

Nathan Ward <mailto:nznog(a)daork.net> wrote on Friday, 7 September 2007 9:20 AM: > Akamai (or ANC perhaps) seem to be having some problems in HK at the > moment, and for whatever reason, we're being directed to their > servers there. An example site that doesn't work well is > images.apple.com. We're seeing packet loss to Hong Kong hosted sites, impacting hk.yahoo.com and www.hsbc.com.au. Waiting to hear back from ANC. -- Ian Henderson, CCIE #14721 Senior Network Engineer, iiNet Limited

2 1

Akamai HK problem
by Nathan Ward 06 Sep '07

06 Sep '07

Akamai (or ANC perhaps) seem to be having some problems in HK at the moment, and for whatever reason, we're being directed to their servers there. An example site that doesn't work well is images.apple.com. We worked around this by finding someone nice who was getting non-HK addresses for Akamai hosted properties, and forwarding our recursive name lookups to them. NB. Only do this if you have low load on your recursive servers, and make sure you check with the owner of the people you direct your lookups to first. -- Nathan Ward

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 06 Sep '07

06 Sep '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:AS24183 descr: advertised to AS9439 by DTS - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.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: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070821 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24183 descr: advertised to AS9439 by DTS Ltd - AS24183 members: 202.68.80.0/20^20-29, 210.48.160.0/20^20-29, 117.18.80.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.27.88.0/23^23-29, 202.174.178.0/23^23-29, 202.174.190.0/23^23-29, 192.173.17.0/24^24-29, 202.27.90.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.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: support(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070907 source: NZRR

1 0

Opt in / opt out requirements for mailing lists
by Andy Linton 05 Sep '07

05 Sep '07

With the new legislation re spam do the members of this list need to be seen to be validated in some way? I know we're all grownups here who can ask to be taken off a list if we want to etc but is there any requirement to be seen to do the right thing? What about other lists that people operate?

6 5

Re: [nznog] Opt in / opt out requirements for mailing lists
by Steven Heath 05 Sep '07

05 Sep '07

On 06/09/07, Jim Cheetham <jim(a)gonzul.net> wrote: > On 06/09/07, Steven Heath <sheath(a)foxbane.co.nz> wrote: > > The operator needs explicit method of knowing that the person has > > agreed to join a list or be sent ad hoc messages. Double op in for a > > list or a signature on a form type thing is ideal. > > I went to the DIA presentations, so although I'm not a lawyer I have > listened carefully. > > The new NZ legislation does not need explicit consent - it will > operate with implicit consent. It also only triggers for "commercial" > emails, which this list is not :-) Sorry I should have said that 'good business approach' is explicit and then you don't have to worry about commercial or not. It was pointed out on another list that having a URL listed in your email sig could deem a message to be commercial if that site relates to the content of the message. I am not a lawyer either and nor do I play one on TV. -- Steven Heath Director Foxbane Consulting DDI: +64 4 978-7306 Cell: +64 21 706-067

3 2

Remote participation in APNIC 24
by Elly Tawhai 04 Sep '07

04 Sep '07

Hi, If you are an APNIC member, you may be interested in the APNIC fee discussions taking place at the APNIC 24 meeting in New Delhi this week. I encourage you all to have your say during the fee discussion working group sessions today and in the APNIC Member Meeting on Friday. Fee discussion sessions at APNIC 24: APNIC fees discussion Wednesday 5 September 2007 14:30 - 16:00 (New Delhi time) http://www.apnic.net/meetings/24/program/feeswg/ Fee discussions at the APNIC member meeting Friday 7 September 2007 11:30 - 13:00 (New Delhi time) http://www.apnic.net/meetings/24/program/amm/ You can follow and participate in the fee discussions online via: - Jabber chat rooms - Live transcripts - Streaming video - Streaming audio Archives of the audio, video and transcripts will also be available soon after the fee discussion sessions have ended. For more information on how to participate online, go to: http://www.apnic.net/meetings/remote Kind regards, Elly APNIC

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Sep '07

04 Sep '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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.171.4.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070814 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 202.174.190.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.171.4.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070905 source: NZRR

1 0

Microsoft Updates for the upcoming Daylight Savings Time Change
by Nick MacKechnie (thenet) 02 Sep '07

02 Sep '07

Hi All, In case you're not across the Microsoft Updates for DST, here's some information that maybe of use to you. This information is being updated regularly and available here - http://www.microsoft.co.nz/timezone. A summary of the status of product updates appears in the table below. Notes regarding specific updates appear below the table. Mainstream Supported Products Product Version Status Reference Windows Vista, XP (SP2), Server 2003 SP1 & SP2, (SBS) 2003 Available KB933360 <http://support.microsoft.com/kb/933360/en-us> Windows Mobile 6.0 (PPC & SP) Available Download <http://www.microsoft.com/downloads/details.aspx?FamilyID=b8aa650c-dd77- 4c11-b3a2-dacdd2ce2aa9&DisplayLang=en> 5.0 (PPC & SP) Available Download <http://www.microsoft.com/downloads/details.aspx?FamilyID=d9c64531-6621- 4e33-9170-de9c1aaf71c3&DisplayLang=en> Desktop Tool Available Download <http://www.microsoft.com/downloads/details.aspx?FamilyID=a3cc98c4-ab57- 49b7-bd1d-e24013ab16cf&DisplayLang=en> Exchange Server 2007 (CDO update only) Available KB940006 <http://support.microsoft.com/kb/940006/> KB937656 <http://support.microsoft.com/kb/937656> Server 2003 (SP2) (CDO update only)see note arround SBS Available KB926666 <http://support.microsoft.com/kb/926666> KB937653 <http://support.microsoft.com/kb/937653/en-us> Notes Connector Available Notes Update <http://www.microsoft.com/downloads/details.aspx?FamilyID=c14932a1-55f4- 4256-af7e-617639d46024&DisplayLang=en> Outlook 2007 (CDO update only) Available KB939596 <http://support.microsoft.com/kb/939596/en-us> 2003 (CDO update only) TBC TBC Sharepoint WSS V2 / SPS 2003 (SP2) 1st September 2007 WSS V3 / MOSS 2007 1st September 2007 WSS V3 / MOSS 2007 - Timer Service Available KB938663 <http://support.microsoft.com/kb/938663> Dynamics CRM 3.0 Available KB937667 <http://support.microsoft.com/default.aspx/kb/937667> Manually Updating Windows If you are unable to obtain an update for your version of Microsoft Windows, you can manually update the Windows registry to reflect the new daylight saving times. Refer to the Manual Updates page <http://www.microsoft.com/nz/msdn/timezone/manual.mspx> for more information. Windows Small Business Server 2003 Apply KB933360 <http://support.microsoft.com/kb/933360/en-us> to Small Business Server 2003 to ensure correct operation of the system clock during the WA daylight saving trial. If you use the Exchange Server component of Small Business Server, you should also apply the Microsoft Exchange Server updates after installing Exchange Server 2003 Service Pack 2. Windows(r) Vista; XP; Server 2003 KB933360 <http://support.microsoft.com/kb/933360/en-us> is a cumulative time zone update and supersedes all previous time zone updates, including KB931836 <http://support.microsoft.com/kb/931836/en-us> , KB929120 <http://support.microsoft.com/kb/929120> and KB928939 <http://www.microsoft.com/downloads/details.aspx?FamilyId=C6A2C8FE-ABDA- 4051-A24F-3EC933089747&displaylang=en> . KB933360 <http://support.microsoft.com/kb/933360/en-us> will be distributed via Windows Update as a high priority update on 28th August 2007 (US Pacific Time). The New Zealand Daylight Savings Changes Guidance Document can be found here <http://www.microsoft.com/nz/msdn/timezone/guidance.mspx> . Cheers, Nick. web <blocked::blocked::http://nick.mackechnie.co.nz/> msn <blocked::blocked::mailto:nick(a)mackechnie.co.nz> skype <blocked::blocked::callto://nickmack/> icq <blocked::blocked::http://www.icq.com/whitepages/wwp.php?Uin=5160535> bbs <blocked::blocked::http://bbs.thenet.gen.nz/> voip <blocked::http://voip.mackechnie.co.nz/> webphone <blocked::blocked::http://www.thenet.gen.nz/webphone/default.asp>

1 0

New Zealand Daylight Savings changes
by Jean-Francois Pirus 02 Sep '07

02 Sep '07

For those who have yet to check/change the NZST on your servers: Minister of Internal Affairs - Daylight saving to be extended http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Dayl… Linux - HOWTO: New Zealand Daylight Savings changes for GNU/Linux http://www.geekzone.co.nz/barf/3483 PS: The datafile is now tzdata2007g.tar.gz so use: wget ftp://elsie.nci.nih.gov/pub/tzdata2007g.tar.gz Microsoft - New Zealand 2007 Daylight Saving Changes Guidance Document http://www.microsoft.com/nz/msdn/timezone/guidance.mspx Apple - About Daylight Saving Time changes in 2007 http://docs.info.apple.com/article.html?artnum=305056 -- ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------

4 3

Notification of NZRR Database changes
by NZRR Database Notifications 02 Sep '07

02 Sep '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: AS24074 as-name: NZRR-AS24074 descr: NZ Post descr: WIX peering at '202.7.1.2' descr: see Citylink RT job #10237 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24074 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070807 source: NZRR REPLACED BY: aut-num: AS24074 as-name: NZRR-AS24074 descr: NZ Post descr: WIX peering at '202.7.1.2' descr: see Citylink RT job #10237 descr: APE peering at '192.203.154.39' descr: see Citylink RT job #10506 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24074 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24074 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070903 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS24074 descr: Route set advertised to AS9560 by New Zealand Post Limited - AS24074 members: 202.12.248.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: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070903 source: NZRR

1 0

Recent Xtra email changes
by Glen Eustace 28 Aug '07

28 Aug '07

We have just spent the last few days trying to solve an email issue, which I am starting to think might be related to the whole yahoo changes as the time scale is the same. One of our clients has their ADSL through Xtra but all their other services through us. Starting on Monday, they haven't been able to send any email, via smtp.xtra.co.nz. We are presuming, that their outbound addresses have contained their domain for which Xtra is neither the registrar nor the MX of. Debugging the issue has been particularly difficult as the customer is not very computer literate and English is not their natural language. We are unable to complete the diagnosis of the issue as the client has now taken Xtra's advice ( Xtra continually maintained that we were the problem - kind of difficult to see when the mail was coming nowhere near us ) and have now transferred their domain to Xtra. We had a similiar situation a while back with two client who were using Paradise in a similiar way. There issue was more related to not being able to have mailboxes on Paradise's servers anymore because Paradise didn't host the domain. The solution was for us to provide the mailboxes instead. I would be interested if this really is an isolated case, or has Xtra tightened up on their inbound mail policy for their own customers. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Glen and Rosanne Eustace GodZone Internet Services, a division of AGRE Enterprises Ltd. P.O. Box 8020, Palmerston North, New Zealand 4446. Ph: +64 6 357 8168, Fax +64 6 357 8165, Mob: +64 21 424 015 http://www.godzone.net.nz "A Ministry specialising in providing low-cost Internet Services to NZ Christian Churches, Ministries and Organisations."

6 7

Re: [nznog] Auckland Datacentres
by Skeeve Stevens 27 Aug '07

27 Aug '07

Hey all, Thanks for your responses. I literally have too many to respond to. ICONZ has been strongly recommended and we shall be talking to them in the first instance. -- Skeeve Stevens, RHCE eintellego, General Manager skeeve(a)eintellego.net / www.eintellego.net Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there? From: Skeeve Stevens [mailto:skeeve(a)eintellego.net] Sent: Monday, 27 August 2007 4:11 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Auckland Datacentres Hey guys, I'm looking for a DC in Auckland. I know nothing about the NZ internet carrier scene - such as who has connectivity where and so on. But I'm looking for a DC with wired access to APE and cross-connect ability to TNZ. A neutral DC would be nice, but as I said, I don't know your scene over there and if these even exist. Is there anything else I should know? .Skeeve -- Skeeve Stevens, RHCE eintellego, General Manager skeeve(a)eintellego.net / www.eintellego.net Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there?

1 0

Why is xtra.mail in AU?
by Don Gould 26 Aug '07

26 Aug '07

Doing some traceroutes to the xtra mail servers, it would appear they've moved all their mail handling to AU. Does anyone have any idea why? It would seem nuts to use international capacity to move all the mail from NZ --> AU --> NZ. Or am I (and others on some other lists) just missing something? Cheers Don

4 3

Auckland Datacentres
by Skeeve Stevens 26 Aug '07

26 Aug '07

Hey guys, I'm looking for a DC in Auckland. I know nothing about the NZ internet carrier scene - such as who has connectivity where and so on. But I'm looking for a DC with wired access to APE and cross-connect ability to TNZ. A neutral DC would be nice, but as I said, I don't know your scene over there and if these even exist. Is there anything else I should know? .Skeeve -- Skeeve Stevens, RHCE eintellego, General Manager skeeve(a)eintellego.net / www.eintellego.net Cell +61 (0)414 753 383 / skype://skeeve -- NOC, NOC, who's there?

1 0

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

23 Aug '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:AS17435 descr: advertised to AS9439 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17435 descr: advertised to AS9439 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435 members: 58.28.0.0/16^16-29, 202.49.240.0/22^22-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: lsmith(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17435 descr: advertised to AS9560 by WorldxChange Communications Ltd - AS17435 members: 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 202.49.204.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: cbarr(a)wxc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070824 source: NZRR

1 0

wxnz.net Prefix update
by Callum Barr 23 Aug '07

23 Aug '07

Hi All, Please update your prefix list for WorldxChange to include: 58.28.0.0/16 118.90.0.0/16 Please note that we will not be advertising our old range anymore; 202.182.19.0/19 Please update filters accordingly - and have a good weekend... -- Callum Barr Network Engineer WorldxChange Communications Ltd.

1 0

New spam type - death threats?
by Scott Newton 22 Aug '07

22 Aug '07

First time I've seen a message like this. Thought other people might be interested. Apart from the legal side of it I loved the Yahoo footer on it. ---------- Forwarded Message ---------- Subject: WHY ARE YOU INVOLVE TO BE KILLED,REPLY OR YOU WAIT FOR YOUR DEATH?? Date: Tuesday, 21 August 2007 From: Robert Payne <rbpynekill147(a)yahoo.com> To: sblewitt(a)email.com HELLOW, I NORMALLY INTRODUCE MY SELF BEFORE I EXECUTE MY JOB,AM MR DON FABIANO JUTOLIO CHICHI,AN ITALIAN CITIZEN,YOU CAN SEE THAT BY MY NAME AND AT THE SAME TIME A HIRED ASSASSINE (AN ASSASINATOR) THAT IS MY JOB. I LIKE TO GO STARIGHT TO THE POINT,SOME BODY PAID ME US $350,000.00 (THREE HUNDRED AND FIFTY THOUSAND UNITED STATES OF AMERICAN DOLLAR) FOR ME TO KILL YOU WHILE THE REMAINING BALANCE OF 150,000.00 (ONE HUNDRED AND FIFTY THOUSAND) WILL BE PAID AFTER THE JOB IS COMPLETED. BUT BEFORE I CARRY ON MY DUTY,I NORMALLY LIKE TO HER FROM THE PERSON BEFORE HE OR SHE WILL MEET HIS SUDDEN DEATH,I WILL LIKE YOU TO BRIEF ME THE REASON WHY YOU ARE INVOLVED/ABOUT TO BE ASSASSINATE. MY BOYS ARE NOW AFTER YOU,THAT IS TO SAY,THEY ARE NOW MONITORING YOUR MOVEMENTS,8 OF THEM HAVE ARRIVED YOUR COUNTRY (THE SPIES TEAM) WHILE THE REMAINING 7 WILL BE ARRIVED NEXT WEEK WHICH IS (THE EXECUTION TEAM) AS SOON AS THE EXECUTION TEAM ARRIVED,CONSIDER YOUR SELF AS A DEAD PERSON BECAUSE THEY WILL NOT ACCEPT ANY OFFER OR WHAT EVER FROM YOU.I WANT TO INFORM YOU THAT YOUR FAMILY MEMBERS MAY BE INVOLVED ONLY IF YOU MAKE THE REPROT TO THE POLICE OR ANY ENFORMENT AGENCIES,THAT IS TO SAY,IF YOU TAKE THE MATTER TO THE POLICE,ALL,I SAID ALL YOUR FAMILY MEMBERS WILL BE DEAD WITHIN A SHORT TIME BECAUSE I NEVER MISS A TRAGET,I HAVE BEEN IN THE FIELD FOR GOOD 34 YEARS AND SINCE THEN,I HAVE NEVER FAILED/DISAPPOINT ANY OF MY CUSTOMERS. SO,BE WARNED TILL I HEAR FROM YOU IF YOU LIKE. DON FABIANO. --------------------------------- Need a vacation? Get great deals to amazing places on Yahoo! Travel. ------------------------------------------------------- -- Regards Scott Newton

18 24

Incident Reporting
by Jonathan Brewer 21 Aug '07

21 Aug '07

Hi Folks, Occasionally things go wrong, resulting in daytime outages for end users. In the aftermath, some of the service providers we work with are very thorough, providing standard reports with a reasonable amount of technical detail. Others keep quiet, or try to pass the blame to their suppliers. I'm interested in hearing about what ISPs are doing for incident reporting - in general or specific, on or off-list. If I get a fair amount of replies, I'll send some stastics back to the list. Cheers, Jon

2 2

Yahoo Xtra's Website..
by Craig Spiers 21 Aug '07

21 Aug '07

While this is a relatively small issue, has anyone else noticed that on xtra's new portal page.. in the top right hand corner - the time.. http://xtra.my.yahoo.com/ It's not even in our time zone.. last time I checked it wasn't 6:54pm yesterday :-) Cheers

5 4

Kiwicon 2k7 - Registration Open, First round of speakers announced
by Adam Boileau 21 Aug '07

21 Aug '07

Hi NZNOG, Preparations for Kiwicon 2k7 - New Zealand's first Hacker Con, 17-18 Nov, Wellington - are well under way. Media coverage is brewing[1] and things are shaping up to be a really good event. At this time, the Kiwicon Team is pleased to announce the first round of presentations[2], which include topics (hopefully) of interest to an NZNOGgy sort of crowd. So, come along and drink a beer with the hackers, "security consultants" and researchers who use, abuse and pwn your networks ;) If you'd like to present, the CFP[3] is still open, but spaces are going fast. Registration is now available[4], and we'd encourage you to do so to help with our planning. See y'all then. -- Regards, Adam on behalf of the Kiwicon Team [1] http://www.smh.com.au/news/security/hackers-do-the-haka/2007/08/20/11874621… [2] https://kiwicon.org/presentations [3] https://kiwicon.org/ [4] https://kiwicon.org/register

1 0

Re: [nznog] Yahoo Xtra's Website..
by Craig Spiers 21 Aug '07

21 Aug '07

Oh indeed it does.. Appears to take the current time every time you reload the page - although might have been nice to have it in the current time zone - people will think they are reading old news! _____ From: Richard Dingwall [mailto:rdingwall(a)gmail.com] Sent: Wednesday, August 22, 2007 2:10 PM To: Craig Spiers Subject: Re: [nznog] Yahoo Xtra's Website.. On 8/22/07, Craig Spiers <craig(a)spiers.gen.nz> wrote: While this is a relatively small issue, has anyone else noticed that on xtra's new portal page.. in the top right hand corner - the time.. Mine says "last update", not "your current time"... Richard http://xtra.my.yahoo.com/ It's not even in our time zone.. last time I checked it wasn't 6:54pm yesterday :-) Cheers _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Orcon's Nameservers Changes from the 21th of August
by Craig Whitmore 15 Aug '07

15 Aug '07

Hi NZNOGers On the morning of 21th of this month Orcon will disable recursive name server lookups from non-Orcon IP Ranges. This will mean that people outside our network using our name servers will not be able to look up DNS for any domain which we are not authorative for. This should not cause any issues at all unless people have hardcoded our name servers (60.234.1.1/60.234.2.2 or 210.55.12.1/210.55.12.2) into their machines and are not on our network. Thanks Craig Whitmore Systems Administrator Orcon Internet.

1 0

Call for Presentations : AusNOG01
by Simon Lyall 14 Aug '07

14 Aug '07

FYI. ---------- Forwarded message ---------- From: James Spenceley <jrs(a)iroute.org> Subject: Call for Presentations : AusNOG01 --------------------------------- Call for Presentations - AusNOG01 --------------------------------- The Australian Network Operators Group is please announce AusNOG01. The inaugural event will be held in Sydney, Australia between 15th and 16th of November 2007 The AusNOG meeting provides the Australian community with a forum to exchange information and experiences on a number of issues relating to the operation and support of networks, with a specific focus on the coming 6-12months. The conference is low priced and is expected to have a strong technical representation for companies operating networks in Australia. The AusNOG conference will incorporate a half day 'National Peering Forum' which will be the first independently held peering forum. For a the conference overview please see the website http:// 2007.ausnog.net ------------ Submissions ------------ Please read the below carefully. Send you proposed topics and details to ausnog-meeting(a)ausnog.net. Be sure to specify which part of the conference best suits your proposal (Topic Sessions, Panel Discussions, Keynote Address or Peering Forum), include a detailed overview including the expected length of your presentation. The program committee will confirm your application and may get back to you with questions. Please remember this is a technical event for network operators and presentations should be representative of this. --------------- Important Dates --------------- - 15th August 2007 - Call for Presentations Opens - 15th September 2007 - Deadline for Proposals - 21st September 2007 - Response to presentation - 30th September 2007 - Draft program published to website - 10th October 2007 - Final program published ------------------- Expenses and Travel ------------------- The organizing committee has attempted to keep the cost of operating the event (and therefore ticket costs) low. There maybe a limited amount of funding available for international speakers. Conference presenters will not have to pay any registrations fee for the entire event. --------------------------------------------- Presentations are Required for the Following: --------------------------------------------- Topic Sessions -------------- - Required Speakers: Variable - Presentation Length: Variable - Number of Topics: 4 The conference will consist of 4 Topics Sessions, each running for approximately 90 minutes. There are no fixed requirements on length of presentation, speakers will have the opportunity to present a longer formal presntation or a smaller lightening talk. This is your chance to share your experiences with the industry. The Topics Sessions selected for AusNOG01 are. 1. Broadband Technologies (Broadband over Power, xxGbps Ethernet, xDSL Technology, Managing BB Users, BB Statics, Accounting Billing) 2. Infrastructure and Deployments (Updates and experiences on deploying Infrastructure. G9 Update, OPEL update, The Who, the Where and the How) 3. Regulatory, Market Data and Overseas Trends (Regulatory and Industry Bodies Updates, Market Data and Statistics, Trends from Overseas Markets) 4. Convergence (Everything about Convergence, QoS, VoIP, Voice, Unified Communicstions, Video on Demand) Panel Discussions ----------------- - Required Panalists: 8-10 - Panel Length: 45 mins - Number of Panels: 2 Panels are the interactive part of the conference. The job of Panelists will be to stimulate and moderate the discussion. Whether you are on the panel or in the audience your input would be appreciated. The two Panel Topics will be related to the industry at the time of the conference, propose a topic that you think will be interesting, or if you think you yourself are interesting, propose yourself :-) Keynote Addresses ----------------- - Required Speakers: 2 - Presentation Length: 45 mins - Number of Topics: 2 We are seeking 2 speakers for Keynotes Addresses. Each Keynote will be of 45 mins in length, including time for input from the industry. If you would like to be considered for a Keynote topic, please email ausnog-meeting(a)ausnog.net with details of yourself and your topic. National Peering Forum ---------------------- (Kindly sponsored by Equinix and PIPE Networks) Required Speakers: 6 Presentation Length: 30-40 mins Number of Topics: 6 We are seeking presentations of interest to the peering community, from individuals, companies or exchange point operators. Presentation can be variable in length, but all speakers are encouraged to leave some amount of time for industry input and discussion. Topics are encouraged to be from the IP and Voice world. ---------------- More Information ---------------- For more information please visit the event website http:// 2007.ausnog.net or join the event mailing list at http:// www.ausnog.net/mailman/listinfo/ausnog07 We look forward to seeing you there.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Aug '07

13 Aug '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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070801 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 117.104.176.0/21^21-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-29, 202.49.183.0/24^24-29, 203.171.4.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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070814 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Aug '07

12 Aug '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:AS9245 descr: Route set advertised to AS9439 by Compass Communications Limited - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.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: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060815 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9245 descr: advertised to AS9439 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070813 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 12 Aug '07

12 Aug '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:AS9245 descr: Route set advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.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: dquigan(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060810 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9245 descr: advertised to AS9560 by Compass Communications - AS9245 members: 203.152.96.0/19^19-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 117.104.176.0/21^21-29, 202.36.121.0/24^24-29, 202.36.157.0/24^24-29, 202.37.112.0/24^24-29, 202.37.234.0/24^24-29, 203.171.4.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: davey.goode(a)compass.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070813 source: NZRR

1 0

Can you help me
by jamie baddeley 11 Aug '07

11 Aug '07

Operators, I've been asked by our friends at TVNZ to assist with a minor issue. For various reasons some folks at TVC would appreciate it if you could flush the information you have in your recursive/caching nameservers for the zone images.tvnz.co.nz That would help clear up some TTL badness. cheers jamie

9 11

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '07

08 Aug '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.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.122.171.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.36.119.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 20070705 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.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20070809 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Aug '07

08 Aug '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.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.122.171.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.36.119.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 20070705 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.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.122.171.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.36.119.0/24^24-29, 202.36.218.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 20070809 source: NZRR

1 0

Sysadmin Miniconf at NZNOG 08
by Simon Lyall 07 Aug '07

07 Aug '07

A reminder that we are looking for talks for the Sysadmin Miniconf at NZNOG 2008 in January ( see http://nznog.miniconf.org/ ) . Last year we had quite a good turnout and talks presented ( http://nznog.miniconf.org/2007.html ) We are really keen to get a good programme for 2008. As such we would be very interested in suggestions both from potential speakers and also from people who might want to hear about particular topics or technologies . On thing we are doing this year is encouraging people to give a talk about their site, what technologies, hardware, software, methods, policies they may use etc. The idea is to give others an idea about what other people use in the "real world" . It could be wide ranging or just about one thing like how you handle logs or documentation. We'd really like to encourage people to give these sort of talks. Anyway if you have an idea either for yourself or someone else (or suggestions on who we could approach) then please send an email to the team at talks08 @ nznog.miniconf.org Full details on the website: http://nznog.miniconf.org/ -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

A passing.
by Jamie Baddeley 06 Aug '07

06 Aug '07

http://www.stuff.co.nz/4156176a28.html A moments silence please. A True Electronic pioneer of New Zealand. Rest in peace Angus. jamie

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 06 Aug '07

06 Aug '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: AS24074 as-name: NZRR-AS24074 descr: NZ Post descr: WIX peering at '202.7.1.2' descr: see Citylink RT job #10237 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24074 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070807 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24074 descr: Route set advertised to AS9439 by NZ Post - AS24074 members: 202.12.248.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: MatthewDa(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070807 source: NZRR

1 0

global-gateway.net.nz and possible MTU problems
by Scott Howard 03 Aug '07

03 Aug '07

We've got a client in Thailand who is having having trouble with traffic from a number of sites - all of which go through global-gateway.net.nz. Based on the symptoms I'm guessing it may be an MTU issue (along with the other end blocking ICMP) - anyone seen this with global-gateway.net.nz before? If anyone here is responsible for that network I'd appreciate it if you could contact me off-list. Thanks, Scott.

6 6

29 Peering Points
by Philip D'Ath 02 Aug '07

02 Aug '07

Just thinking about all these Telecom peering points. Assuming that Telecom allocate IP addresses as they are requested by incoming broadband connections, as opposed to by geographic peering point, then there will be no way to summarise addresses at these peering points. So this will imply that those ISP which do peer at these points will have to listen to a good 100k odd /32 announcements (at the larger peering points). I could easily see the routing table having to contain 200k to 300k additional /32 routes if you want to allow least cost routing to work its best. If there are redundant paths then this could increase a lot more. Then consider the case when a /32 appears to be from Dunedin, and then the next second it appears to be from Wellington (because the Dunedin broadband user lost their session, and a new Wellington use just acquired their dynamic IP address). Then consider all the places these routes could be redistributed to within different ISPs, and potentially outside of their own AS. Then consider [non telecom] peering points that only accept a /24 or bigger. Not that anything is wrong with asymmetric routing, but doing it almost to the customer edge is going to make solving connectivity issues much more difficult (I can access this web site, but not that web site ...). I can see a lot of potential for route flapping, and for frequent routing updates to occur. I can also see the potential for short term route loops occurring. I see route stability issues arising in NZ's future, or have I missed something?

11 14

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

31 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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 116.89.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 203.144.32.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070801 source: NZRR

1 0

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

31 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: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.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.37.114.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 20070713 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.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.37.114.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.7.40.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 20070801 source: NZRR

1 0

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

31 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:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.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.37.114.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 20070713 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, 153.111.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.37.114.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.7.40.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 20070801 source: NZRR

1 0

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

31 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:AS17649 descr: Route set advertised to AS9560 by DMZGlobal Ltd - AS17649 members: 203.144.40.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.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070521 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17649 descr: advertised to AS9560 by DMZGlobal - AS17649 members: 116.89.224.0/20^20-29, 203.144.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070801 source: NZRR

1 0

Spare Sky Tower comms rack
by John Johnston 29 Jul '07

29 Jul '07

Guys, ICONZ has a spare standard sized sky tower comms rack available on L48 in the tower. Unfortunately the rack does not come with any rental space. This would suit anyone that has space but no rack currently. If anyone is interested in purchasing this off us send me an email. Regards, John Johnston Information Systems and Services Manager ICONZ Ltd DDI +64 9 977 3500 MOB +64 21 277-5692 www.iconz.co.nz <http://www.iconz.co.nz/> ICONZ Ltd | Level 7 ICONZ House, 60 Airedale Street, Private Bag 92142, Auckland, 1020, New Zealand Telephone +64 9 977 3500 | Facsimile +64 9 977 3535

1 0

94/8, 95/8 allocated to the RIPE NCC
by Leo Vegoda 29 Jul '07

29 Jul '07

Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to the RIPE NCC in July 2007: 94/8 and 95/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space Please update your filters as appropriate. Regards, -- Leo Vegoda IANA Numbers Liaison

1 0

Netlantis - Routing Table Geoanalysis
by Philippe Bourcier 29 Jul '07

29 Jul '07

Hi, Sorry for the cross-post. The Netlantis team (Pascal Gloor and me) is pleased to announce a new BGP routing tables visualization project. This project is called Routing Table Geoanalysis and aims at representing various statistics based on the analysis of a BGP routing table. The result of this analysis is a poster-size computer-generated image (12+ Megapixels) which you can easily print. Project's URL : http://rtg.netlantis.org/ The statistics for each routing table we analyse are : - The distribution across continents (or more precisely geo-political areas) of the total number of IP addresses announced - The number of IP addresses announced for 100 inhabitants of these areas - The number of routes, IP addresses and the average number of IP addresses per route - The main upstream AS's share in the routing table (in number of IP) and the geographic distribution of IP addresses announced through or by them - The distribution of AS path length by continent - The prefix size distribution The geo-political areas (I'm abusively calling continents) used for the statistics are : Africa, Asia, Central America, Europe, Middle-East, North America, Oceania and South America. When it's relevant, I also use the area World which is simply a way to display the average statistics for the whole routing table. The posters (and statistics) will be automatically updated every month. English not being my native language, I'll be happy if some people can help me fix or improve my wording and explanations so they can be better understood, especially on this page: http://rtg.netlantis.org/?info=rtg I'm thinking about adding a page on which you could automatically upload (via curl) your clogin -c "term len 0\rsh ip bgp" every month so that any AS could also be listed without the need to peer anywhere... tell me if you are interested by this feature. Thanks to routeviews for providing the routing tables and to our sponsors : IP-MAN, OVH and MaxMind. ps: If you want to sponsor Netlantis, we found a piece of hardware which might help us return in a short time to production, the thing is a DDRAM-based hard-disk (more details on my blog), contact me in private if you can help us get one. Sincerely, Philippe Bourcier web : http://sysctl.org/ blog : http://netlantis.blogspot.com

1 0

29 Peering Points
by Stewart Fleming 25 Jul '07

25 Jul '07

> > >On Thu, 2007-07-26 at 12:40 +1200, Philip D'Ath wrote: >>/ Just thinking about all these Telecom peering points. >/>/ >/>/ >/>/ >/>/ Assuming that Telecom allocate IP addresses as they are requested by >/>/ incoming broadband connections, as opposed to by geographic peering >/>/ point, then there will be no way to summarise addresses at these >/>/ peering points. >/ >Not quite right. The points architecturally are driven by BRAS location. >BRAS have their own summarisible range assigned. It's that range which >will be announced. End customers are allocated out of those pools. > > Does this mean that we will be putting BRAS on CHIX, or taking them off...? -- -- Tel: 03 474 2100 Cell: 021 993 125 Web: www.wic.co.nz Co-location and Web hosting. Dunedin-wide wireless. Independent Internet Service Provider.

2 1

nzwireless (ISP, ASN 24111) requesting peering with any interested parties on WIX and APE
by Anton Smith 23 Jul '07

23 Jul '07

Hi, As in the subject line, we would like to establish direct peering sessions with any interested parties at WIX and/or APE. Anyone interested please reply off-list to me to arrange peering :). Regards, Anton

1 0

Re: [nznog] History of the Internet in New Zealand
by Ian Batterbee 23 Jul '07

23 Jul '07

You reckon Mikey Havoc could turn that into a documentary ? I'm sure it would be just the sort of thing he'd love to do. > Note: About 3/4s of the above occurred at companies I was not working > for at the time or have never worked for and at least 2 have happened in > the last 12 months. My knowledge of most is 3rd hand ( except the "hacker > in the Star Wars tie" ). Some of them have appeared in the press though.

2 1

CFP: Systems Administration Mini-Conference at NZNOG 08
by Simon Lyall 23 Jul '07

23 Jul '07

Call for Presentations for NZNOG 2008: Systems Administration Mini-Conference http://nznog.miniconf.org We will be holding a network systems administration mini-conference in Dunedin, New Zealand on Wednesday 2008-01-23, as part of the New Zealand Network Operators' Group 2008 conference (http://2008.nznog.org/) The NZNOG 2008 conference will be held between 2008-01-23 and 2008-01-25. Registration at the NZNOG 2008 conference is a mandatory prerequisite for attendance at the mini-conference; we expect there will be no additional charge. Note: A similar Mini-conference is also intended to be held in Melbourne, Australia, a week later as part of linux.conf.au 2008. The mini-conference's focus is on "Layer 7" issues to do with network and ISP operations, including providing customer services (email, DNS, etc) and provisioning and management topics. We are now seeking proposals for presentations at the mini-conference. We have openings for: - 50-60 minute full presentations - 25-30 minute half presentations - 5-10 minute "lightning talks" - 5-10 minute "How we do things" presentations Presentations are expected to be directed at a technical audience, and focused on a system administration area related to network or ISP operations. Some possible topics: - Email servers and spam filtering techniques - DNS servers, registry systems - server security and best sysadmin practices in an Internet provider environment - VoIP servers - network management / monitoring tools - RADIUS/TACACS/LDAP - Netflow, routing, and traffic analysis tools - server tuning for high performance networking - provisioning tools - honeypots and other security techniques - network based storage - high availability and disaster recovery for network services - virtual machine technology for network services - *nix based routing and fire-walling - tools you need that you may not know about We are happy to discuss the suitability of other topics with intending presenters. The 10 minute "How we do things" presentations are intended for people to talk about their sites. Information could include: Servers, talks, tools, people and roles, experiences, software, operating systems, monitoring, alerting, provisioning etc. The intent is to give other attendees a picture of what is happening in the "real world" and some understanding of how other sites work and how to interact with them. Timeline: - Proposals due by 2007-11-19 - Selection advised by 2007-11-27 - Draft program published by 2007-11-30 - Presentations 2008-01-23 Please send all proposals and questions to <talks08(a)nznog.miniconf.org> Andrew McMillan, Ewen McNeill and Simon Lyall (Conveners)

1 0

peering mailing lists for NZIXs?
by Anton Smith 23 Jul '07

23 Jul '07

Hi all, I have a question for you all that has come up for me after spending most of my recent time up here in good old Iceland. The company I work for are connected to both LINX and AMSIX, and as some of you may know both of these exchanges have mailing lists that are used for such things as.. well, asking everybody else if they would like to peer. As part of the process of a new member coming onto the exchange, it is sent to the mailing list and all existing members can say 'yes, that organisation is perfectly fine to come on board, and yes, we will peer with them'.. or something along those lines (they might say, yes we don't mind them connecting but we won't peer with them). Where would be an appropriate place here in NZ to broadcast a desire to peer with anyone present at WIX and APE? How many organisations 'trust' the route servers? Is there a significant amount of missed peering traffic because some organisations have an open peering policy, but don't trust the route servers, and don't know where to broadcast a 'we would like to peer' message? The large carriers aside, are entities on WIX, APE, etc, missing out on some free peering simply because they don't know who else has an open peering policy? I notice that up here on AMSIX and LINX, it's very no nonsense and organisations often have a 'peering(a)xyz.com' mailbox, and anyone who is a member of the exchange can feel free to send mail to it (or just to the mailing list as happens reasonably frequently). In fact, it is built into the rules (at least on LINX), that you must monitor the mailbox and must respond within some time limit. Perhaps we don't need anything so formal, but maybe a peering mailing list for our IXs would be a good start. Or should we just use NZNOG? Regards, Anton

2 1

IPv6 Workshop
by Keith Davidson 22 Jul '07

22 Jul '07

All, What: IPv6 Technical Workshop, 6 - 10 August 2007 Where: InternetNZ, 10th Floor, Exchange Place, 5 - 7 Willeston St, Wellington When: 6 - 10 August 2007 What: Five day, hands-on workshop - IPv6 lab equipment, for up to 28 participants Who: Any technical people wanting to gain in depth knowledge of IPv6 Faraz Shamim (Cisco) and Gaurab Upadaya (Packet Clearing House) have kindly agreed to deliver their five day IPv6 Workshop in NZ. This workshop has been delivered at several APRICOT / APNIC / SANOG meetings in recent years. Faraz and Gaurab are experienced, world-class instructors on IPv6. The lab equipment consists of at least 14 Cisco routers and switches, a minimum of 1 set per 2 attendees. Nathan Ward will also be helping out with some of the sessions, particularly those relating to IPv6 transition strategies, and providing NZ specific insights. More details on this workshop at <www.internetnz.net.nz/events/ipv6workshop/ipv6workshop> The workshop is strictly limited to 28 attendees, on a first come, first served basis. Please confirm your attendance by emailing Susi Fookes, susi at internetnz.net.nz. Please include your daytime telephone contact number, and advise if you are able to supply your own laptop computer and advise if you are an InternetNZ member. For any details on the course contents contact Jonny Martin at internetnz.net.nz or by phone on 021 2304323. Regards Keith Davidson Executive Director - InternetNZ

1 0

Cisco 5500 bits
by Nathan Ward 21 Jul '07

21 Jul '07

I now work for WIC in Dunedin. We've got some Cisco 5500s, as we're keepin' it real, old-school style. Your Internet will likely traverse one (or more) of these 5500s when you attend NZNOG in January, so pay attention if you want reliable access to IRC. I'm interested in hearing from people who have spare parts for these that they'd be keen to move (for $, of course). It's better for the environment than throwing them out or dumping them in a store room, as they're not (AFAIK) RoHS compliant! Particular interest in: - GE modules - FE modules - Rack mount hardware (for 5513 - the one with 5 screws on to the chassis) - PSUs Additionally, if anyone has info RE the internal LEDs on a 5500 RSM (seemingly named CRXX, where X is a number), please let me know - we've got what appears to be a faulty one, and I'd like to figure out why. (Yes I know they're EOL) (Replies RE parts offlist please) (Also, any other unwanted router or switch hardware, I'd be interested to hear about too. If other people are after parts, I'll circulate some offlist summaries of what's out there to those who register interest with me.) -- Nathan Ward

1 0

Kiwicon 2k7 - Call For Presenters
by Simon Howard 20 Jul '07

20 Jul '07

[-----------------------------------------------------------------------] __ _ __ _ _ / ('>- / /__ (_) __(_)______ ___ '07 \__/ / '_// / |/|/ / / __/ _ \/ _ \ L\_ /_/\_\/_/|__,__/_/\__/\___/_//_/ [-----------------------------------------------------------------------] After travelling the world to attend many excellent security conferences with our compatriots, we decided it was time to pull finger and organise one in Aotearoa, New Zealand. This is the call for presenters for the inaugural Kiwicon. [WTF?] Kiwicon '07 will be a largely informal conference, organised by the security community for the security community. It will be held in Wellington, New Zealand, on the weekend of the 17th and 18th of November, 2007. It will focus on sharing information; ideas, code, and catching up with other like-minded people from around New Zealand (and further abroad). [Venue] Our hosts for the weekend will be Victoria University of Wellington. This location has the advantage of being close to cheap accommodation and, more importantly, several good pubs. Details will be provided closer to the conference date. [Costs] Kiwicon '07 is a non-profit event. Attendance for the entire weekend will cost $50 for employed individuals (self-employed and salaried). There is a discounted rate of $30 for students and the unemployed. Please do note that there are several good pubs in close proximity. We anticipate the total cost of the weekend in money and dignity may be higher. [Topics] Suggested topics include but are not limited to: - Information Warfare / Industrial Espionage - Satellite Hacking - Echelon - Waihopai & Tangimoana - Lockpicking / Wiretapping / Bugs - Biometrics - Cellular Networks (GSM,GPRS,CDMA,3G,4G) - Phreaking / VoIP - Web Security - Wireless / Bluetooth / Infrared / Fibre - Exploitation Techniques - Access Control and Authentication - Reverse Engineering - Application Security, Testing, Fuzzing - Code Auditing - Virtualization - Malware (Viruses, Spam, Phishing, Botnets) - Banking / ATMs / Carding - Crypto - Forensics / Antiforensics - 0dayz!!! We do not plan on having pre-determined time slots for presentations. If your talk is only 20 minutes long, then you will only be talking for 20 minutes. The goal of the weekend is to share useful information - this means flexible time limits. We already have a number of excellent speakers confirmed, to get a slot for a talk send an email to cfp(a)kiwicon.org with the following information: Name: Handle: Country of Residence: Employer (if applicable): Brief Bio: Presentation Title: Presentation Length: Presentation Synopsis: [The Team] Kiwicon is being duct taped together by the following people: pipes - Doing it all wrong since 1973 bogan - Proprietor of fine minced emails since 1822 antic0de - What is Freelist[] anyways? shammah - I know i left a rootkit around here somewhere hntr - Will you post my bail? metlstorm - True Norwegian back bacon Joshua - Defcon 3: I lost my password [Contacts & Further Information] Email us: kiwicon(a)kiwicon.org Check the site: http://www.kiwicon.org Drop by silc: silc.isig.org.nz:2706/kiwicon Join the list: kiwicon-subscribe(a)lists.isig.org.nz :wq

1 0

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

19 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:AS17705 descr: advertised to AS9560 by Inspire Net Ltd - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: james(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050728 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17705 descr: advertised to AS9560 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

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

19 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: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by Inspire.Net Ltd. - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 203.96.157.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: mds(a)inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS17705 descr: advertised to AS9281 by InspireNet - AS17705 members: 203.114.128.0/18^18-29, 203.79.88.0/23^23-29, 192.138.251.0/24^24-29, 203.96.157.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: brenden(a)staff.inspire.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070720 source: NZRR

1 0

TelstraClear RPF and caching
by David Robb 19 Jul '07

19 Jul '07

Hi all, Given the thread over the last couple of days asking how TCL is implementing RPF and transparent caching I thought a semi-official reponse might be useful. We have RPF (the ERXs call it SA Validate) enabled on DSL connections, and the filters applied to the cable modems implement the same functionality there. RPF is not enabled on non-residential services, nor it is configured within the core of the network. Regarding transparent caching, all international traffic passes through the caching infrastructure, although only certain IP ranges are matched for redirection to the caches. There's nothing in there which takes into consideration whether you have a mixed international/domestic link (sorry Philip :). Wholesale customers are very much in the "do not redirect" category, as most are multi-homed and the probability of encountering problems due to asymmetric routing are high. Residentially allocated IP Hi all, The caches themselves spoof the source IP of the client when making an outbound connection to the greater internet, because we've found that although there are occasionally issues caused by asymmetry the problems of cache IPs being blacklisted or DoSd are much fewer. Probably the most commonly observed scenario is where more specific routes are advertised by someone to their upstream (and thus internationally) than domestically (either directly to TCL or via Telecom or whatever) - a number of the routers on the TCL network carry a full routing table, and will prefer the more specific route out via the international path, thus feeding packets to the caches. The return path's then via the path one would normally expect, with the ensuing breakage of port 80 traffic. While this obviously isn't ideal, we do our best to work with the other ISPs to resolve this as fast as possible. --David Robb Network Design Engineer TelstraClear

1 1

History of the Internet in New Zealand
by Susi Fookes 19 Jul '07

19 Jul '07

Hi all, InternetNZ has commissioned Keith Newman to write a history of the Internet in New Zealand. The book will go to the publishers later this year. I have read the first few chapters and it is a fantastic read (I look forward to reading it all). He is near the final stages of writing and is now in search of photographs to help document the history. Can you help? If you have a photo(s) that could be of use – please contact Keith (wordman(a)wordworx.co.nz) or myself. And of course we will give you credit in the publication for allowing us to use the image. We are very eager to hear from you! Susi Fookes -- Project Administrator InternetNZ w +64 4 495 2117 | f +64 4 495 2115 | m +64 21 119 7539 susi(a)internetnz.net.nz | http://internetnz.net.nz PO Box 11-881, Manners Street, Wellington 6142, NEW ZEALAND

7 6

Re: [nznog] Telstra contact - BGP advertisements
by Anton Smith 18 Jul '07

18 Jul '07

> Message: 1 > Date: Wed, 18 Jul 2007 10:17:27 +1200 > From: "Nick Larsen (ZeroOne Operations)" <nick(a)zeroone.co.nz> > Subject: [nznog] > To: "nznog(a)list.waikato.ac.nz" <nznog(a)list.waikato.ac.nz> > Message-ID: > <E50D0676A6F98941BC86ED082F8F2AA407F9286275(a)e12be1.anywhereexchange.com> > > Content-Type: text/plain; charset="us-ascii" > > Hi, > > Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). > It's regarding our prefix advertisements / asymmetric routing. > > Kind regards, > > Nick Larsen Hi.. sorry but I'm going to hijack this a bit. How many operators out there are using strict RPF? With a lot of interconnection points around the place to me it seems a bit harsh to use strict RPF. And in fact, I wonder if Telstra Clear are using it, since a lot of times I notice broken connectivity due to what appears to be asymmetric routing, and I then have to work around it. It seems to me that the internet is inherently asymmetrical, particularly between ISPs and their carriers. So, can someone please give me the low-down on what the most commonly thing done is w.r.t. asymmetry? Cheers :) Anton

7 8

Telstra contact - BGP advertisements
by Nick Larsen (ZeroOne Operations) 17 Jul '07

17 Jul '07

Hi, Could someone from the Telstra Clear routing team please contact me by phone (04 471 4447). It's regarding our prefix advertisements / asymmetric routing. Kind regards, Nick Larsen Network Technician ZeroOne (NZ) Limited 0800 ZEROONE www.zeroone.co.nz

1 0

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

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

1 0

Decent bandwidth required - Invercargill and AKL
by Richard Naylor 14 Jul '07

14 Jul '07

Hi there, I'm looking for some decent bandwidth in Invercargill for an event in August. 2 Mbps symmetric is all I need at the Ascot Park Hotel. Of course we'll always use more than 2Mbps if its available. The main thing is symmetric. Traffic will all be national, with the other end points at AKL and WLG and I'll probably hub out of WLG, so thats where most of the traffic will come from/to. Also looking for the same at ASB Arena (is this the showgrounds ?). It will also hub out of WLG and needs to be around 2Mbps. The event is one day, so we would be looking for (and pay for) connectivity on the Saturday, testing, rehearsals on the Sunday and Live on the Monday. Pack out Tuesday. Please save me the trouble of driving everywhere installing satellite dishes......then pulling them out..... Contact me off list of you can help. Thanks - Rich

1 0

gmail blacklisted at ahbl
by Blair Harrison 12 Jul '07

12 Jul '07

Hey folks, I've just discovered[1] that gmail appears to have been listed on the ahbl blacklist, which it appears at least one NZ ISP is using. If you're using the ahbl blacklist then I'd suggest either whitelisting gmail, or dropping this blacklist from your filters, I'd imagine there are quite a lot of legitimate messages getting blocked by this. [1] http://oldwww.temp.ahbl.org/tools/lookup.php?ip=gmail.com Cheers, Blair

3 2

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

12 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: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 REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.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.37.114.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 20070713 source: NZRR

1 0

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

12 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: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 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: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070606 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS23655 descr: advertised to AS24388 by Snap Internet - AS23655 members: 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 153.111.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.37.114.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 20070713 source: NZRR

1 0

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

12 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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 202.65.160.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070713 source: NZRR

1 0

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

10 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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 58.84.224.0/20^20-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 203.110.28.0/23^23-29, 192.173.17.0/24^24-29, 202.21.130.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR

1 0

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

10 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:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070330 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Kordia - AS24324 members: 124.157.64.0/19^19-29, 202.56.32.0/20^20-29, 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.49.16.0/21^21-29, 202.49.128.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 218.185.224.0/21^21-29, 202.27.88.0/23^23-29, 192.173.17.0/24^24-29, 202.27.83.0/24^24-29, 202.27.90.0/24^24-29, 202.36.75.0/24^24-29, 202.36.137.0/24^24-29, 202.36.154.0/24^24-29, 202.36.173.0/24^24-29, 202.37.168.0/24^24-29, 202.37.197.0/24^24-29, 202.49.158.0/24^24-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: smc(a)kordia.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070711 source: NZRR

1 0

New daylight savings setting for cisco...
by Barry Murphy 10 Jul '07

10 Jul '07

Hi, Can anyone confirm these daylight saving changes for cisco are correct? Solaris and a few other O/S's have already released their patches. Current: clock summer-time nzdt recurring 1 Sun Oct 3:00 3 Sun Mar 2:00 New: clock summer-time nzdt recurring last sun sep 3:00 first sun apr 2:00 Ref: http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Services-Daylight-Saving-Index Can't find anything else on the net where people have discussed this. Cheers Barry

4 3

Various email issues, including domains without MX records
by Martin Kealey 09 Jul '07

09 Jul '07

Hi all I've been paying attention to our mail logs lately and seeing some "interesting" stuff. So I was wondering... Does anyone run a serious (commercial) email operation in New Zealand without having appropriate MX records these days? (i.e. relying on the legacy behaviour of using A records in the absence of MX records.) What about web forms? What about embedded devices? What proportion of valid mail in NZ is sent from an address that doesn't have an MX record? Do you check? What do you do if it's not? If one were to block email from addresses without MX records, how much would break? How many complaints would one get? -Martin -- Martin D Kealey, ihüg engineering

9 9

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

08 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. --- OBJECT BELOW CREATED: aut-num: AS38602 as-name: NZRR-AS38602 descr: Pronet descr: APE peering at '192.203.154.38' descr: see Citylink RT job #9881 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS38602 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS38602 descr: Route set advertised to AS9560 by Pronet - AS38602 members: 117.53.144.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: daniel.kinross(a)pronet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070709 source: NZRR

1 0

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

05 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. --- OBJECT BELOW CREATED: aut-num: AS17484 as-name: NZRR-AS17484 descr: The Wellington Schools Loop Network descr: WIX peering at '202.7.0.40' descr: see Citylink RT job #9974 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17484 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17484 descr: Route set advertised to AS9439 by The Wellington Schools Loop Network - AS17484 members: 117.18.80.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: sid(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR

1 0