- NZNOG - lists.nznog.org

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

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

21 Jun '05

> Replies off-list, please. Or phone me or Rob on this number: > Phone 64 4 384 4153 Thanks in anticipation. Lesley

1 0

Help with configuring router
by Lesley Walker 21 Jun '05

21 Jun '05

I need some help with setting up a borrowed Network iQ 1000 series router. (Also labelled securicor 3net if that helps) I have got as far as connecting to the serial port, watching it boot up and produce the login prompt, then it doesn't seem to respond to input, and hangs my Hyperterm (sorry!) session. I'm told the config has been set back to factory defaults, but the person who loaned it to me is in the middle of a crisis and can't help me set it up. If anyone could spare a few minutes to point me in the right direction I would be very grateful. I have all the config info I need, I just can't talk to it. (This is a temporary replacement for a very dodgy router that's providing our internet connection, and quite urgent) Replies off-list, please. Lesley Walker Datamine Limited - turning numbers into people 103 Ghuznee Street PO Box 11-452 Wellington, New Zealand Phone 64 4 384 4153 http://www.datamine.co.nz

1 0

Re: Paradise MX , was: [nznog] Anyone awake at Ihug NOC/Security?
by Ewen McNeill 21 Jun '05

21 Jun '05

In message <Pine.LNX.4.56.0506221253110.2350(a)green.darkmere.gen.nz>, Simon Lyall writes: >Does anyone know why pop3.paradise.net.nz doesn't seem to listen on port >25? [1] I wouldn't normally mind but it is listed as the primamry MX for >the domain. > >[1] - Since Monday at least, might be a lot longer. It's been like that for a year.[0] The response I got when I reported it said "We have permanently blocked SMTP requests to pop3.paradise.net.nz.". After some discussion, and me suggesting some more sensible approaches to route their mail,[1] they eventually said: "Despite how our mail system may look to the outside world it is functioning in a manner that we require at this particular stage of development." >From where I sit it still looks fairly clueless to firewall your primary MX off from the world. But I concluded then that I would be best served by excluding the instances of "failed connection to pop3.paradise.net.nz" from my log reports and forgetting about it. If you're able to get hold of someone clueful at Paradise and get them to fix it, I'll be grateful too.[2] Ewen [0] I know this because I found the auto-response to my ticket reporting the problem, and it's dated 21 June 2004. [1] Eg, modern mailers mail forwarding from their preferred MX to pop3.paradise.net.nz when appropriate, split DNs, etc. [2] The wellylug mailing list I host has several @paradise.net.nz addresses subscribed to it, so I get instances of this in my log pretty much daily.

1 0

IANA IPv4 allocations and bogon updates: 74/8, 75/8, 76/8, 189/8, 190/8
by Rob Thomas 21 Jun '05

21 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- [ Apologies to those of you who receive this note in multiple forums. ] Hi, all. The numerous Team Cymru bogon projects have been updated as of 17 JUN 2005 to reflect the following IANA allocation made on 17 JUN 2005: 074/8 Jun 05 ARIN (whois.arin.net) 075/8 Jun 05 ARIN (whois.arin.net) 076/8 Jun 05 ARIN (whois.arin.net) 189/8 Jun 05 LACNIC (whois.lacnic.net) 190/8 Jun 05 LACNIC (whois.lacnic.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. Rob, for Team Cymru. - -- Rob Thomas http://www.cymru.com Shaving with Occam's razor since 1999. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQrjLPlkX3QAo5sgJAQFHwAP/Z8KrLp9id6PD51KNEjAlveJCxRnvP4ev RofqRMex1SB5itogkB4O6JmrpSqIjqgM2GsnAUREZr5/r2ekdAZwejT85zHftl92 3ExvEec3P2PVDdfWF5v9TSVWfzwwbMW2HWwymzUYT7klWpjblcUUPdAWl+khD+FU /C8cCA2b8qk= =JvMq -----END PGP SIGNATURE-----

1 0

Thanks to TelstraClear for providing service during the major outage on Monday
by Adrian Smith 21 Jun '05

21 Jun '05

The National Library of New Zealand would like to thank TelstraClear New Zealand for providing a quick alternate National and International Internet service to us by setting up a BGP routing/Peering connection over our existing CityLink Network connections to bypass the major Telecom network outage on Monday. Our organisation was back up on the Internet several hours before the Telecom Network failure was restored. Due to the nature of Mondays Telecom Network failure we lost both our primary and backup Internet connections at 10:49am, leaving only our CityLink connection working, and peering with the CityLink WIX route servers, which still provided some 300 routes to us. After an hour of not being able to get any news on the cause and duration of the Telecom outage we approached one of TelstraClear's Internet BGP routing wizards and asked how can we route past this problem, he advised us to talk to their wholesale people. After explaining the situation to wholesale, authorisation was given to one of their Internet BGP routing wizard's to make it happen. Within a short time BGP Peering was set-up and implemented over the phone, and our full National and International Internet service was fully restored over CityLink to TelstraClear. We do not have any sort of contract with TelstraClear. The point here is that although TelstraClear stopped peering at WIX :( they are still connected to the CityLink Network :) and still connect to customers over it. We would not have had this option open to us if we were not already connected and using the CityLink Network and CityLink's Neutral Peering Exchange. http://www.citylink.co.nz/community/peering.html So Thanks to TelstraClear for providing a temporary Internet pipe with no notice; and Thanks also to the CityLink team /NGI/MORST Advanced Network for running some Internet BGP routing courses last week. The information was put into action on our router to bypass Monday's problem. http://www.ngi.org.nz/ http://www.morst.govt.nz/?CHANNEL=IT+INFRASTRUCTURE&PAGE=IT+Infrastructure The recently released Government Digital Strategy http://www.digitalstrategy.govt.nz/ encourages co-operation and collaboration in as many ways possible between all New Zealand people, and organisations both Government and private sector. When the many technical people on this NZNOG list receive this email, please take it to your leaders and explain the many benefits of Internet Peering at Neutral Internet Peering Exchanges to create a fully meshed, distributed Internet for New Zealand. Digital Strategy Launch http://www.r2.co.nz/20050516/ recording from Parliament. When the big one hits New Zealand and we have a full-scale major civil defence emergency it will be far too late for the very capable technical people in each of the organisations to implement Internet peering. They will not be able to use the phone networks due to outages and overloading, and the current New Zealand Internet will fail because peering was not put in place and working. It is in the interest of every single New Zealander that every New Zealand Telco, ISP and organisation connects their networks to the nearest Neutral Internet Peering Exchange and starts peering; and helps to create a real New Zealand Internet. The original Internet was designed for this very reason for the US Defence Department to prevent a total failure of communications during major infrastructure outages and emergencies. There would also be benefits for the Telco's and ISP's if this peering was already in place before the Telecom outage on Monday. It may have been a non-event, when both fibres were cut, the Telecom network could have re-routed traffic around the damage over TelstraClear's equally capable backbone network. Even if Telecom had to pay TelstraClear for the temporary transit traffic, it would have probably been a far less cost to pay both financially and politically. And the major disruptions caused to a lot of people waiting at airports, unable to use EFTPOS networks etc. may have been avoided, and Telecom customers would still have trust in them to provide Internetworking services. This would also work in reverse should such an event hit TelstraClear's network. So come on New Zealanders, please get the important message and do something about this situation today. Without realising it, you may save lives in the future because the NZ Internet does not break, just because a couple of fibre optic cables get cut by accident or equally by a natural disaster event. To all journalists on this list, please feel free to put this full message in as many papers, magazines and web sites as possible. With a further message to encourage every New Zealander who reads it, to email their ISP and request that their ISP set-up Internet Peering at a Neutral Internet Peering Exchange to create a robust New Zealand Internet. Come on Kiwi's, lets just do it. Adrian Smith, Network Specialist, National Library of New Zealand >>> Michael Newbery <Michael.Newbery(a)team.telstraclear.co.nz> 20/06/2005 17:26:36 >>> At 5:01 PM +1200 20/6/05, Andy Linton wrote: >So is this a good time to ask about the design of a network that concentrates >so much of its core service in Auckland? Is TelstraClear's network design any >better? I'd like to think so. :) For a start, it takes more than two fibre cuts in the North Island to disrupt us (that's new since you fled Andy :) Currently the core network is distributed and I prefer to follow that mantra whenever possible, though sometimes resources are naturally 'clumpy' (is that a word?) -- Michael Newbery IP Architect TelstraClear Limited Tel: +64-4-920 3102 Mobile: +64-29-920 3102 Fax: +64-4-920 3361 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0