- NZNOG - lists.nznog.org

Hostile takeover of Indonesia's .it registrar
by Mark Derricutt 13 Jul '05

13 Jul '05

Just saw a discussion of a hostile takeover of the .it domain management on IRC (#joiito @ freenode ) and thought it might be of interest to you NZNOGers: http://lists.apdip.net/pipermail/igovap/Week-of-Mon-20050711/000374.html Mark

2 2

ENUM Consultation Report by M-co for InternetNZ
by Michael Sutton 12 Jul '05

12 Jul '05

Members of NZNOG. On behalf of InternetNZ's ENUM Task Force we are pleased to provide you with a link to the full M-co report, "The staging of the first ENUM trial in New Zealand" (~100pages) <http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete .pdf> http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf This report was commissioned to provide advice to InternetNZ including recommendations and questions to be addressed in respect of ENUM's implementation in New Zealand. In parallel to the preparation and release of this report InternetNZ has agreed with the Telecommunication Carriers Forum (TCF) to form a joint Industry ENUM Steering Group as part of our initiative to provide a platform to plan and implement ENUM for New Zealand. We look forward to receiving feedback with a nominal close off date of July 21st 2005. If you require an extended period please let us know by that date. All comments should be sent to <mailto:enum-tf(a)internetnz.net.nz> mailto:enum-tf(a)internetnz.net.nz. Written submissions can also sent to our Office at: ENUM Task Force, InternetNZ, P.O.Box 11-881, Wellington, New Zealand, or can be faxed to the Task Force at +64 4 495 2115. The Consultation Report is also to being printed and to receive a physical copy please send a request and mailing address to Jordan Carter at <mailto:jordan(a)internetnz.net.nz> mailto:jordan(a)internetnz.net.nz. The Report in subsections (PDF format), are also available on the InternetNZ web site <http://www.internetnz.net.nz/public/enum/> http://www.internetnz.net.nz/public/enum/. You will also find links to the ENUM workshop and initiatives at this URL. You are welcome to distribute this Report to anyone this would be of interest too. Best Regards Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chairman - Enum Task Force InternetNZ Project Manager - UCI PUA Enum Prototype Telephone: +64 4 475 9235 Mobile: +64 21 305500 InternetNZ: +64 4 4721600 ext 730 <mailto:michael.sutton(a)internetnz.net.nz> mailto:michael.sutton(a)internetnz.net.nz> [ Please note this email is in HTML format to prevent long URL links being broken - my apologies to those who prefer plain text]

1 0

Not quite 255
by Juha Saarinen 10 Jul '05

10 Jul '05

Intelenet-Communications-Intelenet-Communications.so-6-0-0.ar3.LAX1.gblx.net -- Juha

1 0

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

10 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.118.128.0/18^18-29, 203.173.192.0/18^18-29, 203.96.192.0/19^19-29, 202.46.160.0/20^20-29, 202.126.80.0/20^20-29, 203.109.144.0/20^20-29, 203.173.144.0/20^20-29, 203.109.192.0/21^21-29, 203.173.136.0/21^21-29, 203.173.168.0/21^21-29, 202.50.188.0/22^22-29, 203.109.132.0/22^22-29, 203.109.252.0/22^22-29, 203.173.164.0/22^22-29, 203.173.188.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.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 203.173.160.0/23^23-29, 203.173.186.0/23^23-29, 192.107.113.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.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, 203.109.163.0/24^24-29, 203.109.230.0/24^24-29, 203.109.233.0/24^24-29, 203.173.162.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 20050518 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.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.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.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.89.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, 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 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.109.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 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 20041116 source: NZRR REPLACED BY: route: 203.109.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.173.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 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 20041116 source: NZRR REPLACED BY: route: 203.173.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 202.49.140.0/24 descr: Route for ihug - AS7657 origin: AS7657 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 20041116 source: NZRR REPLACED BY: route: 202.49.140.0/24 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR

1 0

Noc Contact list.
by Simon Lyall 10 Jul '05

10 Jul '05

Okay first up a big apology for getting behind with updates to this list, I've just gone though mail box and grabbed all the old ones so I have should have all the updates. Which means if they page isn't correct then please send me a new update. http://www.usenet.net.nz/noc/ Note that I'm not just including ISPs on the list but hosting companies and other large Internet connected organisations. Basically people who might need to be connected in a hurry. PS: I believe APNIC lets you do role based owners of IPs and AS numbers now, so there isn't really an excuse to not have your details updated 8 months after somebody leaves.. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 203.97.231.224/28^28-29, 203.79.85.80/29, 203.109.195.72/29, 210.48.103.0/29, 210.48.103.112/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050621 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23754 descr: advertised to AS9439 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 203.118.144.0/24^24-29, 202.7.4.32/28^28-29, 203.97.231.224/28^28-29, 203.79.85.80/29, 203.109.195.72/29, 210.48.103.0/29, 210.48.103.112/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9343 descr: Route set advertised to AS9439 by DTS - AS9343 members: 192.100.53.0/24, 192.173.17.0/24, 202.68.80.0/20^20-24, 202.20.0.0/21^21-24, 202.49.158.0/23^23-24, 202.36.173.0/24, 202.36.204.0/23^23-24, 202.37.197.0/24, 202.46.190.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: technical(a)dts.net.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040114 changed: rpsl-admin(a)nzix.net 20040624 changed: rpsl-admin(a)nzix.net 20041006 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9343 descr: advertised to AS9439 by DTS - AS9343 members: 202.68.80.0/20^20-29, 202.20.0.0/21^21-29, 202.36.204.0/23^23-29, 202.49.158.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

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

07 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64522 descr: advertised to AS9439 by Change Training Consultants Ltd - AS64522 members: 202.49.158.112/28^28-29, 202.20.7.160/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: hamish(a)change.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050201 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64522 descr: advertised to AS9439 by Change Training Consultants Ltd - AS64522 members: 202.20.5.224/27^27-29, 202.20.7.160/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: hamish(a)change.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050708 source: NZRR

1 0

[ot] nz opensource websites
by Barry Murphy 07 Jul '05

07 Jul '05

Hey guys, Bit off topic but it's Friday and the weeks been slow, just a few more hours now before beer time. Anyways, if you run an opensource website or an ISP and you'd like to offer downloads to save on your precious international bandwidth, then you might want to take a look at this, the catch, you need to be wix or ape connected as it's an anycast range. http://www.isp.fast.co.nz/mirror.htm The above link will give instructions to showing your name on the page, i.e. http://www.linuxnet.isp.fast.co.nz (Single word name) http://www.kiwi-online.isp.fast.co.nz (2 word name) This may save you quite a bit of traffic on your international connectivity if you have links from your homepage. If anything is out of date or you'd like to request other mirrors, please don't hesitate to contact me. Cheers Regards Barry

2 1

[nznog] IANA IPv4 allocations and bogon updates: 89/8, 90/8 and 91/8
by Rob Thomas 06 Jul '05

06 Jul '05

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

1 0

Transfer of management now complete
by Elly Tawhai 03 Jul '05

03 Jul '05

Hi, Transfer of historical IP address ranges ---------------------------------------- The following address ranges were transferred from NZTelecom to APNIC's management on 1 July 2005: 202.27/16 202.37/16 202.36/16 202.49/16 202.50/16 For more information about how to update your resources, please refer to section 4 of "Historical resource policies" at: http://www.apnic.net/docs/policy/historical-resource-policies.html#4 If you have further queries, please feel free to contact APNIC at: <helpdesk(a)apnic.net> Regards, APNIC Secretariat

1 0

Another Technical Announcement
by Richard Naylor 03 Jul '05

03 Jul '05

Wearing my R2 hat.... R2 has recently installed a streaming media server at the Palmerston North (PNIX) internet exchange in addition to servers already at WIX and APE. We also have a server located in California, USA to serve content to New Zealanders overseas. These have been tested during the current Lions Rugby tour and are now fully operational. They will shortly be carrying the previously announced RNZ service. This announcement is to advise that all the streams carried by R2 on behalf of Rhema Broadcasting Group (RBG) are now available on all servers. These streams are Radio Rhema www.rhema.co.nz Southern Star www.sstar.co.nz LifeFM www.lifefm.co.nz ShineTV www.shinetv.co.nz The audio streams are available in bit rates up to 64kbps and TV up to 384kbps. We expect to make a 2Mbps TV stream available by the end of the month. Details of the streams is available via the station websites listed above. RBG content is both live streams and on-demand content. We have chosen to deploy a multi-homed architecture for the following reasons: 1. Greater diversity and redundancy than a single site/provider architecture. 2. Reduced network latency for improved streaming performance. 3. Shortest path for broadband consumers (reducing network congestion for Operators). 4. Scalability, allowing us to add servers at new exchanges in the future. 5. To minimise national transit costs for the ISP's of customers using the content. 6. Lowest cost to serve content. 7. Ability to better serve international viewers and listeners of NZ stations. The servers have a globally consistent anycast IP address which is advertised at each exchange to ensure that the content is delivered from the nearest server to the consumer. In order to get the best performance we recommend that you peer directly with the anycast routers at all the exchanges where you have connectivity. Any peering questions should be directed to me at richard.naylor(a)r2.co.nz Thanks Richard

1 1

Re: [nznog] Archived stream of this morning's Nat Radio programme(s)
by Webmaster 03 Jul '05

03 Jul '05

There is a long standing caching (as I understand it) problem. If you press reload/refresh a couple of time it clears the error. cheers, Richard Hulse >>> Dan Clark <dan(a)synaptic.net.nz> 4/07/2005 11:35 >>> used to be http://www.radionz.co.nz/audio I think, for some reason it go's to some broken Telecom Xtra link. Dan Juha Saarinen wrote: > Is there one somewhere? RadioNZ? R2? > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Archived stream of this morning's Nat Radio programme(s)
by Juha Saarinen 03 Jul '05

03 Jul '05

Is there one somewhere? RadioNZ? R2? -- Juha

2 2

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

03 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

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

03 Jul '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons export: to AS64646 announce ANY AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

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

30 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24385 as-name: NZRR-AS24385 descr: Smartlinx3 descr: WIX peering at '202.7.1.20' descr: see Citylink RT job #2729 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24385 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR REPLACED BY: aut-num: AS24385 as-name: NZRR-AS24385 descr: 3CIX admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS64646 accept ANY export: to AS64646 announce AS24385:RS-ROUTES AND NOT {0.0.0.0/0} AND NOT fltr-bogons notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050701 source: NZRR

1 0

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

30 Jun '05

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

1 0

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

30 Jun '05

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

1 0

Re: [nznog] Technical Announcement
by Richard Naylor 30 Jun '05

30 Jun '05

At 10:14 PM 6/29/2005 +1200, Simon Lyall wrote: >On Wed, 29 Jun 2005, Jamie Baddeley wrote: > > Have you considered multicast as an option, and if so, what stopped you > > from deploying it? Client support or Network support? > >Does anyone have full end to end support of multicast? I would guess with >bitstream and people having layer-2 all the way it might be possible to >do it these days. In a pure L2 network multicast is a dangerous technology. Think of what happens to a 10meg user when a 100meg user kicks off a 25meg multicast stream. The trend seems to be to use multicast inside tunnels in this environment. Thats the way the Access Grid folks are going. It also allows user groups within a network to opt in and out of multicast sessions. Theres quite a few tunnels tools around. >Not sure what it would be any practical use for though. Lots of chickens >and eggs here. yes. A few "broken network" days ahead. Multicast is good for synchronous events - like TV watching or LOTR Premieres etc. But for asynchronous events - like day to day watching of video, which is tending towards "on-demand", then multicast has almost no value. With the usual availability of bandwidth, I feel multicast is going to be of declining importance but will be implemented more for niche applications, which will become more important in themselves. The "tv" world is fascinated by "video on demand" and the radio (Audio) world is fascinated by Podcasting (aka on-demand listening - mobile). Neither of these is aided by multicast and in themselves they don't impose huge demands on both servers and networks. What we do know is 50x 2meg streams doesn't require 100Mbps. The technology certainly doesn't work that way - the playout buffer is your friend. So unicast streams are not overly heavy on the network or the server. Having said all that, we will be playing with multicast and probably making it available. The other thing we'll be playing with is better quality and alternate compressions. We're very close to be able to originate those nice HD streams we demo'd last year. So maybe NZNOG-06 will be in 10Mbps HD streams....... Rich

2 1

RE: [nznog] Technical Announcement
by Richard Naylor 30 Jun '05

30 Jun '05

At 02:26 PM 7/1/2005 +1200, Simon Allard wrote: > > > > In a pure L2 network multicast is a dangerous technology. Think of >what > > happens to a 10meg user when a 100meg user kicks off a 25meg multicast > > stream. > >But doesn't that depend on how your switches are setup?. My >understanding is the use of IGMP fixes this problem. The switch will >only sent that multicast packets to switch ports which want it. > >(of course the switch has to support IGMP) Having a bad day. THat was teh 2nd attempt to send....think I may just go for a quiet walk and see if I can find whats left of my brain......

1 0

RE: [nznog] Technical Announcement
by Simon Allard 30 Jun '05

30 Jun '05

> > In a pure L2 network multicast is a dangerous technology. Think of what > happens to a 10meg user when a 100meg user kicks off a 25meg multicast > stream. But doesn't that depend on how your switches are setup?. My understanding is the use of IGMP fixes this problem. The switch will only sent that multicast packets to switch ports which want it. (of course the switch has to support IGMP)

1 0

The New Zealand Network Operators' Group
by Donald Neal 30 Jun '05

30 Jun '05

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

1 0

Re: NZ IP-Range (nzip.meta.net.nz)
by Drew Broadley 30 Jun '05

30 Jun '05

Sorry to hijack the topic slightly, Could the person from the origination IPs please stop sucking the xml subnet file every 5 minutes, it only gets updated ONCE a day! 202.27.251.36 - - [01/Jul/2005:08:49:38 +1200] "GET /files/nzip/nzsubnets.xml HTTP/1.0" 200 17498 "-" "-" 202.27.251.34 - - [01/Jul/2005:08:51:08 +1200] "GET /files/nzip/nzsubnets.xml HTTP/1.0" 200 17498 "-" "-" I have blocked you until further notice. If you would like to contact me offlist to discuss this bandwidth rapage, that would be appreciated :) That will be all. - Drew P.S TGIF

1 0

DSL Tails in NZ
by Sam Sarkis 30 Jun '05

30 Jun '05

Hey All, We are looking for around 50 - 60 DSL tails in NZ for our customers. Is there a way we can resell DSL in NZ or a way we can get a Layer 2 Hand off for DSL Tails ? These connections are required all over NZ. Regards Sam Sarkis United IP Director Ph 61 2 8825 5586 Fax 61 2 8825 5577 ======================================================================== This message has been scanned for spam & viruses by Mail Sleuth. To report SPAM forward the message to: spam(a)mailsleuth.com.au Mail Sleuth www.mailsleuth.com.au ========================================================================

2 1

RE: [nznog] NZ IP-Range
by Kerry Milestone 30 Jun '05

30 Jun '05

Hi there, but from the top of that file it grabs it states: # # Note that this is *not* an definitive guide, and does not cover all of the # APNIC ranges. (see whois.apnic.net) is there a definitive guide? Kerry. ________________________________ From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Thursday, 30 June 2005 9:30 a.m. To: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range I got this script from Paul of linuxsystems, grabs the APNIC IP database and compiles a list of NZ ip ranges: #!/usr/local/bin/php <?php $in_file = "ftp://ftp.apnic.net/pub/apnic/dbase/data/country-ipv4.lst"; // $in_file = "country-ipv4.lst"; $out_file = "nzipranges.txt"; $handle_input = @fopen($in_file,"r") or die("Unable to open $in_file\n\n"); $handle_output = fopen($out_file, "w"); $now = date ("r"); fwrite ($handle_output,"# Generated: $now\n\n"); while (!feof($handle_input)) { $buffer = fgets($handle_input); if ( ereg ( "nz", $buffer) ) { // echo $buffer; $this_range = trim(preg_replace ( "#([\d\.]+) \- [\d\.]+ : [\d\.]+(\/\d+) .+#","$1$2", $buffer )); fwrite ($handle_output,"\n" . $this_range); } } fclose($handle_input); fwrite ($handle_output,"\n"); fclose($handle_output); ?> ----- Original Message ----- From: James J. Guidera <mailto:james(a)miracle.co.nz> To: NZNOG(a)list.waikato.ac.nz Sent: Thursday, June 30, 2005 9:00 AM Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614 ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

RE: [nznog] NZ IP-Range
by Kerry Milestone 29 Jun '05

29 Jun '05

I know what I asked, 'tis why I did. I have often wondered about the fact that the internet can _be_ definitive only for the moment its queried. -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 30 June 2005 4:27 p.m. To: Steve Phillips Cc: Kerry Milestone Subject: Re: [nznog] NZ IP-Range Steve Phillips wrote: > Think of what you ask. The simple answer is "no" Oh gowon... I know you've got it. Let Kerry have your definitive NZIP guide now, and don't be so mean.

4 4

police mail tech
by jamie.baddeley＠vpc.co.nz 29 Jun '05

29 Jun '05

Can someone from NZ Police please contact me offlist. thanks jamie

2 1

RE: [nznog] NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Cheers for the warning, -----Original Message----- From: Russell Fulton [mailto:r.fulton(a)auckland.ac.nz] Sent: Thursday, 30 June 2005 11:40 a.m. Cc: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range Steve Phillips wrote: > > Just be aware that these solutions will give you a list of "NZ IP > Ranges" but may not be New Zealand based netwise. > > If you are looking for traffic originating in NZ and not traversing any > international links then thats an entirely different story and only your > ISP can provide you with this. > > If this is a bill saving exercise then it may pay to be a little prudent. > I echo Steve's warning. It really depends how relaible you need the data to be. Back in the days when everything went throug NZGate at Waikato they kept lists of NZ addresses based upon the BGP tables. These contain quite a few small blocks of non NZ addresses -- mainly belonging to large multination companies and Telcos. I imagine it has got worse not better. If accuracy is crucial then you really need something based on the routing tables that gets updated frequently. Russell

1 0

NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614

9 10

Re: [nznog] Technical Announcement
by Webmaster 29 Jun '05

29 Jun '05

> Have you considered multicast as an option, and if so, what stopped you > from deploying it? Client support or Network support? Multicast is only usefull for live streams (which we are still working on rights issues for). I remember hearing a lot about Multicast at the NAB coference in 1997. The website is still there (http://www.ipmulticast.com/) For ISPs who peer with us in NZ, we'd certainly look at enabling it (subject to some solid testing being done of course). cheers, Richard

1 0

RE: [nznog] NZ IP-Range
by James J. Guidera 29 Jun '05

29 Jun '05

Thanks for the script Paul, might have look into the software and IP2location for the windows based machines, and script for linux. James ________________________________ From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Thursday, 30 June 2005 9:30 a.m. To: James J. Guidera; NZNOG(a)list.waikato.ac.nz Subject: Re: [nznog] NZ IP-Range I got this script from Paul of linuxsystems, grabs the APNIC IP database and compiles a list of NZ ip ranges: #!/usr/local/bin/php <?php $in_file = "ftp://ftp.apnic.net/pub/apnic/dbase/data/country-ipv4.lst"; // $in_file = "country-ipv4.lst"; $out_file = "nzipranges.txt"; $handle_input = @fopen($in_file,"r") or die("Unable to open $in_file\n\n"); $handle_output = fopen($out_file, "w"); $now = date ("r"); fwrite ($handle_output,"# Generated: $now\n\n"); while (!feof($handle_input)) { $buffer = fgets($handle_input); if ( ereg ( "nz", $buffer) ) { // echo $buffer; $this_range = trim(preg_replace ( "#([\d\.]+) \- [\d\.]+ : [\d\.]+(\/\d+) .+#","$1$2", $buffer )); fwrite ($handle_output,"\n" . $this_range); } } fclose($handle_input); fwrite ($handle_output,"\n"); fclose($handle_output); ?> ----- Original Message ----- From: James J. Guidera <mailto:james(a)miracle.co.nz> To: NZNOG(a)list.waikato.ac.nz Sent: Thursday, June 30, 2005 9:00 AM Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614 ________________________________ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] NZ IP-Range
by Mark Karena 29 Jun '05

29 Jun '05

Not sure if there is a single list within the community but there are places that sell IP<-> location software that pulls info from APNIC, ARIN etc. Here is one place. http://www.ip2location.com/?AfID=23224 HTH, ------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING (07) 853 6060 (021) 141 3792 _____ From: James J. Guidera [mailto:james(a)miracle.co.nz] Sent: Thursday, 30 June 2005 9:00 a.m. To: NZNOG(a)list.waikato.ac.nz Subject: [nznog] NZ IP-Range Just a quick question, Is there a singular complete list of NZ ip range?? I am wanting to allow only NZ traffic access to servers. Thanks James Guidera Systems Engineer Miracle Electronics Ltd Ph:+64-4-385-1293 Cel: +64-21-705-614

1 0

Re: [nznog] Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

>>> Barry Murphy <barry(a)unix.co.nz> 06/29/05 2:38 PM >>> > For providers not connected to the peering exchanges > will the content be delivered from the USA? Yes, at the 'standard' rate of 16 or 24 kbs. This rate is on a par with other Public Broadcasters. Peering ISPs get higher rates from the local servers. > This would mean those providers will only get the USA > content and wont be allowed to hear the copyright audio? NZ Restricted audio, actually. We use the exchange infrastructure to limit the distribution of some content. At the start there won't be any NZ restricted content (apart from Enzology). We expect demand for the service to be quite high, and don't want to have to sort between help desk calls from consumers who's ISPs do not peer and people who have a genuine problem. R.

3 2

RE: [nznog] Technical Announcement
by Regan Murphy 28 Jun '05

28 Jun '05

>>For providers not connected to the peering exchanges such as telecom and telstra The way I see it is that while these two providers are connected to the one or more exchanges, its just that they don't openly peer with everybody at the exchanges. Therefore they may choose to peer directly with radionz at one of these exchanges thus enabling the content to be provided to their subscribers. -- Regan -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Wednesday, 29 June 2005 2:38 p.m. To: Webmaster; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Technical Announcement Hi, For providers not connected to the peering exchanges such as telecom and telstra, will the content be delivered from the USA? I'm guessing this is the case so you don't have to purchase domestic links from those providers. This would mean those providers will only get the USA content and wont be allowed to hear the copyright audio? Thanks Barry P.S. www.ispmap.co.nz is backup and running people, sorry the hardware died and took a while to replace. ----- Original Message ----- From: "Webmaster" <Webmaster(a)radionz.co.nz> To: <nznog(a)list.waikato.ac.nz> Sent: Wednesday, June 29, 2005 2:24 PM Subject: [nznog] Technical Announcement > Hi, > > Radio New Zealand has recently installed content servers at the > Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet > exchanges. We also have a server located in California, USA to serve > content to New Zealanders overseas. > > These servers have been deployed within the R2 infrastructure and will > be used for the soon-to-be-launched on-demand and simulcast audio > service. > There will be a range of on-demand content from programmes broadcast > on both networks, and we are hoping to provide live streams of > National Radio and Concert FM (subject to resolving some outstanding > copyright issues). When the service commences we expect about 60 hours > of new content to be available each week. The servers will also be > used by Radio NZ International for their on-demand and simulcast audio. > > All streams will initially be 16 kbs maximum, and this may increase to > 24 kbs once we have a handle on traffic flows. Everyone will be able > to access content at this rate. > > We have chosen to deploy a multi-homed architecture for the following > reasons: > 1. Greater diversity and redundancy than a single site/provider > architecture. > 2. Reduced network latency for improved streaming performance. > 3. Shortest path for broadband consumers (reducing network congestion > for Operators). > 4. Scalability, allowing us to add servers at new exchanges in the > future. > 5. To minimise national transit costs for the ISP's of customers using > the content. > 6. Lowest cost to serve content. > > The servers have a globally consistent anycast IP address which will > be advertised at each exchange to ensure that the content is delivered > from the nearest server to the consumer. > > As new exchanges are installed throughout the country we intend to > deploy content servers at them, subject to certain minimum criteria > being met. This also includes MUSH style networks outlined in the NZ > Government's Digital Strategy. > > In order to get the best performance we recommend that you peer > directly with the anycast routers at all the exchanges where you have > connectivity. > > For those who wish to peer locally an enhanced service is available > from the NZ exchange-based content servers. Maximum data rates will > increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for > live streams. The live simulcasts (when available) will be available > in stereo at these rates. > > Where content is limited to NZ for copyright reasons there will be no > international route, meaning customers of non-peering ISPs will not be > able to access the content. This is currently the case with the > Enzology series (www.radionz.co.nz/enzology/) > > Please contact our peering coordinator at peering(a)radionz.co.nz if you > need to establish a peering session with our content servers. > > We will be maintaining a list of peers and a help page on our new > website so that consumers can be informed about how to access the > enhanced service. > > Operators may expect increased help desk activity due to their > customers not being able to access NZ restricted content, or asking > for access to the enhanced service. > > We are publishing our intentions to this list in advance of the launch > so that Operators can prepare for what we expect will be a very > popular service with the 686,000 people who listen each week to > National Radio and Concert FM. > > We expect to go live in 2-3 weeks. > > > regards, > > > Richard Hulse > New Media Manager > Radio New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Technical Announcement
by Webmaster 28 Jun '05

28 Jun '05

Hi, Radio New Zealand has recently installed content servers at the Auckland (APE), Wellington (WIX), and Palmerston North (PNIX) internet exchanges. We also have a server located in California, USA to serve content to New Zealanders overseas. These servers have been deployed within the R2 infrastructure and will be used for the soon-to-be-launched on-demand and simulcast audio service. There will be a range of on-demand content from programmes broadcast on both networks, and we are hoping to provide live streams of National Radio and Concert FM (subject to resolving some outstanding copyright issues). When the service commences we expect about 60 hours of new content to be available each week. The servers will also be used by Radio NZ International for their on-demand and simulcast audio. All streams will initially be 16 kbs maximum, and this may increase to 24 kbs once we have a handle on traffic flows. Everyone will be able to access content at this rate. We have chosen to deploy a multi-homed architecture for the following reasons: 1. Greater diversity and redundancy than a single site/provider architecture. 2. Reduced network latency for improved streaming performance. 3. Shortest path for broadband consumers (reducing network congestion for Operators). 4. Scalability, allowing us to add servers at new exchanges in the future. 5. To minimise national transit costs for the ISP's of customers using the content. 6. Lowest cost to serve content. The servers have a globally consistent anycast IP address which will be advertised at each exchange to ensure that the content is delivered from the nearest server to the consumer. As new exchanges are installed throughout the country we intend to deploy content servers at them, subject to certain minimum criteria being met. This also includes MUSH style networks outlined in the NZ Government's Digital Strategy. In order to get the best performance we recommend that you peer directly with the anycast routers at all the exchanges where you have connectivity. For those who wish to peer locally an enhanced service is available from the NZ exchange-based content servers. Maximum data rates will increase to 32 or 48 kbs for on-demand content and 48 or 64 kbs for live streams. The live simulcasts (when available) will be available in stereo at these rates. Where content is limited to NZ for copyright reasons there will be no international route, meaning customers of non-peering ISPs will not be able to access the content. This is currently the case with the Enzology series (www.radionz.co.nz/enzology/) Please contact our peering coordinator at peering(a)radionz.co.nz if you need to establish a peering session with our content servers. We will be maintaining a list of peers and a help page on our new website so that consumers can be informed about how to access the enhanced service. Operators may expect increased help desk activity due to their customers not being able to access NZ restricted content, or asking for access to the enhanced service. We are publishing our intentions to this list in advance of the launch so that Operators can prepare for what we expect will be a very popular service with the 686,000 people who listen each week to National Radio and Concert FM. We expect to go live in 2-3 weeks. regards, Richard Hulse New Media Manager Radio New Zealand

2 1

Telstra Problems
by Lyndon 27 Jun '05

27 Jun '05

I took a traceroute this morning as Telstra were fixing the issue, it was indeed interesting. First 3 hops are removed (my firewall, local router and next hop). I am connected by Cable Modem. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * 20 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251] 8 153 ms 153 ms 154 ms so.jb.wils.telstraclear.net [203.98.42.66] 9 155 ms 156 ms 154 ms GigabitEthernet3-0.GW1.LAX1.ALTER.NET [157.130.245.21] 10 148 ms 147 ms 147 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 11 156 ms 157 ms 154 ms 0.so-1-1-0.XL1.LAX7.ALTER.NET [152.63.57.78] 12 154 ms 153 ms 155 ms 0.so-6-0-0.BR1.LAX7.ALTER.NET [152.63.112.41] 13 148 ms 148 ms 146 ms so-2-0-0.gar1.LosAngeles1.Level3.net [209.0.227.37] 14 148 ms 149 ms 146 ms so-0-1-0.bbr2.LosAngeles1.Level3.net [4.68.96.89] 15 167 ms 169 ms 168 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157] 16 167 ms 168 ms 168 ms ae-23-54.car3.SanJose1.Level3.net [4.68.123.109] 17 217 ms 213 ms 213 ms unknown.Level3.net [64.152.102.58] 18 205 ms 207 ms 205 ms po3-0.gw1.akl1.asianetcom.net [202.147.55.213] 19 206 ms 204 ms 204 ms ip-202-147-45-74.asianetcom.net [202.147.45.74] 20 206 ms 205 ms 206 ms 203-109-156-100.ihug.net [203.109.156.100] 21 206 ms 204 ms 205 ms oldresolver3.ihug.co.nz [202.36.94.1] Cheers L

1 0

RE: [nznog] TelstraClear/ICONZ Fault (IHUG as well?)
by Simon Allard 27 Jun '05

27 Jun '05

There was earlier, we had to shut down our BGP session to TCL because of some weirdness in the BGP advertisements from TCL. It has been resolved now and the BGP session was brought back up. > -----Original Message----- > From: Tony Wicks [mailto:nzog(a)road.gen.nz] > Sent: Tuesday, 28 June 2005 9:55 a.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] TelstraClear/ICONZ Fault (IHUG as well?) > > No issues to Ihug via TCL Auckland. > > > [root(a)fire root]# traceroute ihug.co.nz > traceroute to ihug.co.nz (203.109.252.75), 30 hops max, 38 byte packets > 1 router2 (203.97.9.132) 0.982 ms 1.136 ms 0.993 ms > 2 203.97.85.221 (203.97.85.221) 25.973 ms 27.754 ms 25.487 ms > 3 ge9-0-954.u11.pnr.telstraclear.net (218.101.61.41) 25.982 ms > 30.724 ms 30.487 ms > 4 g1-0-927.u11.tspn.telstraclear.net (218.101.61.6) 27.482 ms > 30.195 ms 29.486 ms > 5 g1-926.u12.brh.telstraclear.net (218.101.61.35) 26.982 ms 27.230 > ms 26.486 ms > 6 lnk1-ihug-ge-1-0-1642.u12.telstraclear.net (203.98.18.162) 28.482 > ms 30.234 ms 25.486 ms > 7 203-109-156-97.ihug.net (203.109.156.97) 35.982 ms 36.202 ms > 45.986 ms > 8 ihug.co.nz (203.109.252.75) 26.974 ms 28.200 ms 25.985 ms > [root(a)fire root]# > Simon wrote: > > Michael Bordignon wrote: > > > >>> Since then we have about 55% packet loss, with ICONZ as at 12:05 > >> > >> > >> saying that they have not been given an ETA by TelstraClear. > >> > >>> 12 hours of substandard performance with no ETA seems a bit poor to > >> > >> > >> me. > >> > >>> If anyone has any updates on this please feel free to let me know. > >> > >> > >> > >> Same here - unusable. > > > > > > I am possibly seeing the same problem here? we are on tesltraclear DSL > > and cant get to any of IHUG's network... Anyone seeing this same issue > > this morning? Other major ISP's are fine. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

RE: [nznog] TelstraClear/ICONZ Fault
by Michael Bordignon 27 Jun '05

27 Jun '05

> Since then we have about 55% packet loss, with ICONZ as at 12:05 saying that they have not been given an ETA by TelstraClear. > 12 hours of substandard performance with no ETA seems a bit poor to me. > If anyone has any updates on this please feel free to let me know. Same here - unusable. Michael

5 5

RE: [nznog] Trademe problems ?
by Jay Rama 27 Jun '05

27 Jun '05

Hi Simon, Telstra/Paradise are currently having some DNS issues, there is a quickfix in place, but I believe problems still persist... Regards, Jay ________________________________ From: Simon Byrnand [mailto:simon(a)igrin.co.nz] Sent: Tue 28/06/2005 9:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Trademe problems ? Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trademe problems ?
by Simon Byrnand 27 Jun '05

27 Jun '05

Hi All, Anyone else seeing problems getting to trademe this morning ? Seems to die somewhere between global gateway and telstraclear... Regards, Simon

3 2

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

26 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24324 descr: Route set advertised to AS9560 by BCL - AS24324 members: 202.49.128.0/24^24-29, 202.49.135.0/24^24-29, 202.49.133.0/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050610 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324 members: 202.49.128.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: sainesh.singh(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050627 source: NZRR

1 0

APNIC Updates @ Telstra
by Jonathan Brewer 26 Jun '05

26 Jun '05

Hi Folks, Would someone at Telstra capable of performing updates to Telstra-managed AS9436 please contact me off-list? Thanks, Jonathan Brewer

1 0

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

23 Jun '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.4.0/24^24-29, 202.7.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: rpsl-admin(a)nzix.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050228 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 202.7.6.0/24^24-29, 203.118.144.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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050621 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by CityLink - AS23754 members: 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.7.6.0/23^23-29, 198.32.71.0/24^24-29, 202.7.5.0/24^24-29, 203.118.144.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR

1 0

TelstraClear/ICONZ Fault
by Chris Woodrow 22 Jun '05

22 Jun '05

Apparently TelstraClear made some 'changes' to the primary ICONZ WGTN-AUCK circuit around midnight last night. Since then we have about 55% packet loss, with ICONZ as at 12:05 saying that they have not been given an ETA by TelstraClear. 12 hours of substandard performance with no ETA seems a bit poor to me. If anyone has any updates on this please feel free to let me know. Regards Chris Woodrow BDT

1 0

Re: [nznog] Anyone awake at Ihug NOC/Security?
by Mark Foster 21 Jun '05

21 Jun '05

Glen Wilson wrote: *snip* > I enquired about your email today and was told that you had lodged a fault > regarding smtp relay attempts in which the offending ip was not an Ihug > ip and the issue was dropped. It was also brought to my attention > that in a follow up email from you to the abuse mailbox stated the > following,... > > "If I don't get some sort of acknowledgement of my reports soon I will > start dropping ihug IP ranges at the highest supernet I can see... " Unfortunately you're taking my frustration and desire-to-get-SOME-sort-of-response out of context, and its a shame you did this on NZNOG. I don't make a habit of misreporting complaints, and i'm wary of the fact that as an end user (at least in the capacity I was reporting this particular abuse case in) I don't exactly have any 'clout'. So I was simply reporting a fact - that my frustration level was such that i'd rather add all of ihug to my RBL than deal with the ongoing virus payload that was (apparently) being ignored. I have sent another response offlist but I felt the need to make it clear that I am not a cry-wolf type and am familiar with the concepts of dns lookup and whois. ;-) Good luck to those at ihug with the thankless task of clearing that backlog! Mark.

5 4

RE: [nznog] Anyone awake at Ihug NOC/Security?
by Blair Robson 21 Jun '05

21 Jun '05

It was just a suggestion, that email was a few days old and none of you guys had responded (obviously cos it was sorted) - I was just trying to help. >> All your comments are just rumour and speculation. Yeah, absolutely I don't _know_ anything and I said that. Again just a suggestion. _b -----Original Message----- From: Simon Allard [mailto:simona(a)staff.iinet.net.au] Sent: Wednesday, 22 June 2005 9:23 a.m. To: Blair Robson; nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? Blair. Please don't comment on ihug matters which you know nothing about. All your comments are just rumour and speculation. None of the senior type jobs have gone. Yes some have left for other jobs, but they have all been replaced with new staff. abuse(a)iinet.net.au has no visibility into the ihug NZ network, so they will be no help to you. abuse(a)ihug.co.nz is the correct email to use. For the record, Mark was contacted minutes after his email and his problem was sorted. Cheers Simon Allard IHUG Security Monkey > -----Original Message----- > From: Blair Robson [mailto:blair.robson(a)ihug.co.nz] > Sent: Wednesday, 22 June 2005 2:52 a.m. > To: jon.brewer(a)att.net; 'Mark Foster'; nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > Seriously - try abuse(a)iinet.net.au , explain that you have tried > contacting > abuse(a)ihug.co.nz (I assume you have?) > I don't know weather that will work or not, but I do know that nearly all > the senior people at Ihug in NZ are gone..And I think you will find Simon > no > longer works for Ihug. > As far as I can gather everything is being run or in the process of being > run from Perth now. > > Blair > > -----Original Message----- > From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] > Sent: Tuesday, 21 June 2005 3:25 p.m. > To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > We too need a reply from Ihug security, and have unanswered mail in to > noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a > better address? > > To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated > 30 GB of http traffic in the past month for one of our customers - > repeatedly downloading one file. (2400 times at last count) Our customer > would rather like it to stop. > > JB > > -------------- Original message from "Blair Robson" > <blair.robson(a)ihug.co.nz>: -------------- > > > > abuse(a)iinet ? > > > > > > > > -----Original Message----- > > From: Mark Foster [mailto:blakjak(a)blakjak.net] > > Sent: Wednesday, 15 June 2005 5:05 p.m. > > To: nznog(a)list.waikato.ac.nz > > Subject: [nznog] Anyone awake at Ihug NOC/Security? > > > > Repeat emails over the last week or two to abuse@ and noc@ havn't had > any > > sort of response or acknowledgement - can someone from Ihug NOC or > > security please contact me offlist. > > > > Thanks > > Mark. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Anyone awake at Ihug NOC/Security?
by Glen Wilson 21 Jun '05

21 Jun '05

Glen Wilson Network Operations Manager Ihug Ltd, Auckland, New Zealand www.ihug.co.nz On Wed, 22 Jun 2005, Glen Wilson wrote: > > Again I clarify that noc(a)ihug and abuse(a)ihug remain the appropriate > channels. The mailbox is currently backlogged by several weeks, for the > benefit of the list if there are any urgent issues please feel free to > raise them with me directly (off list) for adequate responce. > > Your points are valid, but as the abuse autoresponder states, not all > emails warrent a reply. > > I can assure you that the matter was looked into and recommendations > were made to the responsible parties to improve the process. > > Abuse emails are treated seriously, however genuine cases of abuse are > dealt with faster than complaints of portscans, relay attempts and > blackice alarm logs. > > I enquired about your email today and was told that you had lodged a fault > regarding smtp relay attempts in which the offending ip was not an Ihug > ip and the issue was dropped. It was also brought to my attention > that in a follow up email from you to the abuse mailbox stated the > following,... > > "If I don't get some sort of acknowledgement of my reports soon I will > start dropping ihug IP ranges at the highest supernet I can see... " > > I recognise that current response times to abuse emails is somewhat > lacking but may I presume to recommend a more professional approach in > future Mark. > > Further comments should be off list. > > Regards > > Glen Wilson > Network Operations Manager > Ihug Ltd, Auckland, New Zealand > www.ihug.co.nz > > On Wed, 22 Jun 2005, Mark Foster wrote: > > > Glen - > > I dare say that instead of 'habitual abuse emailer' you might call me > > 'someone who's not willing to simply ignore situations for which ISPs > > and end users should actually be responsible'. > > > > And in case you missed what I stated in my original email, I had tried > > both addresses. Repeatedly. Over WEEKS. > > > > Further I suggest that the 'I'm having the same problem too' format of > > responses to my post to NZNOG might imply that maybe you need to examine > > your own internal processes before you decide to get snarky on a public > > mailing list. > > > > If Ihug abuse team actually acknowledged complaints and committed to > > actioning them within a specific timeframe - as many ISPs do - I would > > not have felt the need to post to NZNOG - which was an act of desparation. > > > > I've been responsible for the abuse@ mailboxes for 3 different ISPs in > > the past and funnily enough, each of those ISPs took abuse reports > > seriously. Nomatter how much they might have wanted to killfile reports > > from particularly frequent reporters. :-) > > > > So I hope you have a great day, Glen. :-) > > > > Mark. > > > > PS: In case anyone hasn't registered it, Simon Lyall's NOC Contact List > > at http://www.usenet.net.nz/noc is pretty damn useful. Most of the time. > > :) [And isn't related to Simons past employment with Ihug.] > > > > Glen Wilson wrote: > > > > > noc(a)ihug.co.nz or abuse(a)ihug.co.nz. > > > > > > As a habitual abuse emailer, Mark Foster knows the appropriate channels. > > > > > > > > > Glen Wilson > > > Network Operations Manager > > > Ihug Ltd, Auckland, New Zealand > > > www.ihug.co.nz > > > > > > On Wed, 22 Jun 2005, Blair Robson wrote: > > > > > > > > >>Seriously - try abuse(a)iinet.net.au , explain that you have tried contacting > > >>abuse(a)ihug.co.nz (I assume you have?) > > >>I don't know weather that will work or not, but I do know that nearly all > > >>the senior people at Ihug in NZ are gone..And I think you will find Simon no > > >>longer works for Ihug. > > >>As far as I can gather everything is being run or in the process of being > > >>run from Perth now. > > >> > > >>Blair > > >> > > >>-----Original Message----- > > >>From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] > > >>Sent: Tuesday, 21 June 2005 3:25 p.m. > > >>To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz > > >>Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? > > >> > > >>We too need a reply from Ihug security, and have unanswered mail in to > > >>noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a > > >>better address? > > >> > > >>To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated > > >>30 GB of http traffic in the past month for one of our customers - > > >>repeatedly downloading one file. (2400 times at last count) Our customer > > >>would rather like it to stop. > > >

2 1

RE: [nznog] Anyone awake at Ihug NOC/Security?
by Blair Robson 21 Jun '05

21 Jun '05

Seriously - try abuse(a)iinet.net.au , explain that you have tried contacting abuse(a)ihug.co.nz (I assume you have?) I don't know weather that will work or not, but I do know that nearly all the senior people at Ihug in NZ are gone..And I think you will find Simon no longer works for Ihug. As far as I can gather everything is being run or in the process of being run from Perth now. Blair -----Original Message----- From: jon.brewer(a)att.net [mailto:jon.brewer(a)att.net] Sent: Tuesday, 21 June 2005 3:25 p.m. To: Blair Robson; 'Mark Foster'; nznog(a)list.waikato.ac.nz Subject: RE: [nznog] Anyone awake at Ihug NOC/Security? We too need a reply from Ihug security, and have unanswered mail in to noc(a)ihug.net - address from Simon Lyall's NOC Contact List. Is there a better address? To air some dirty laundry, 203-173-155-220.bliink.ihug.co.nz has generated 30 GB of http traffic in the past month for one of our customers - repeatedly downloading one file. (2400 times at last count) Our customer would rather like it to stop. JB -------------- Original message from "Blair Robson" <blair.robson(a)ihug.co.nz>: -------------- > abuse(a)iinet ? > > > > -----Original Message----- > From: Mark Foster [mailto:blakjak(a)blakjak.net] > Sent: Wednesday, 15 June 2005 5:05 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Anyone awake at Ihug NOC/Security? > > Repeat emails over the last week or two to abuse@ and noc@ havn't had any > sort of response or acknowledgement - can someone from Ihug NOC or > security please contact me offlist. > > Thanks > Mark. > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

7 6

RE: [nznog] Help with configuring router
by Lesley Walker 21 Jun '05

21 Jun '05

As you were. I found out what my problem was. Sorry for the distraction, I no longer need help. > I need some help with setting up a borrowed Network iQ 1000 series > router. (Also labelled securicor 3net if that helps) Lesley

1 0