- NZNOG - lists.nznog.org

Trojan "MS Windows TCP/IP Patch" spam run
by matthew＠auscert.org.au 31 Jul '06

31 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've had a few reports of a spam run for a fake MS Windows TCP/IP Patch (as below) that leads to a trojan site. Anyone else seeing much of this? Any feedback appreciated. - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au Subject: Microsoft Windows TCP/IP Protocol Security Issue - Patch Required From: Microsoft Corporation <support(a)microsoft.com> Date: 31 Jul 2006 19:31:57 +0200 To: auscert(a)auscert.org.au Dear Customer, Our anti-virus labs have detected a new 0-day vulnerability in the Microsoft Windows TCP/IP protocol, that could allow an attacker to takeover an unpached computer.We dont have too many details, since we have recently become aware of the vulnerability, but if patch is not applied as soon as possible, you risk your computer to be exploited.Because the vulnerability affects the kernel of Microsoft Windows, we cannot provide the patch using the Microsoft Update Service, so we have decided to notify all our customers that have registered their Microsoft Windows Operating System about this new threat. Because the security of our customers is very important to us, we have developed a patch to fix the kernel of Microsoft Windows, and to prevent your computer from being attacked. Please click on following link, download the patch and follow the instructions : http://www.microsoft.com/security/tcp-ip/download.php?country=AU,234,242,211 1.Download the patch on your Desktop. 2.Run the patch. 3.Reboot your computer. Each customer has an unique link to download the patch that will expire in 24 hours, so you have to apply within 24 hours after you receive this email. If you fail to do so, you risk your computer to be attacked and exploited by hackers. Thank you Microsoft Corp. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRM65yCh9+71yA2DNAQLbEgP+Kwuu5ldbrEkyYu1jmgCenjGIF7cCSDCa ht7GQOGZL5ss9ZsZS2SfYk3Hi4v5NhtJ47KWmFumputa/H4chCAZ3bFxIzMsvO2+ IeP+7YVqQgXM3sXVd4HNAHRZlmY4SYfDrJ7RX836lmYtOionUg3NxhruJKV25rEc p9lpFhPs5QY= =dQxq -----END PGP SIGNATURE-----

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Ian Batterbee 31 Jul '06

31 Jul '06

Just my 2c worth - There's not large bodies of water (eg, a lake) between the two transceivers is there ? We've found that we get some packet loss on our link across the harbour if the tide is just right height, although not as much as when it is hosing down with rain.. probably to do with reflections off the water hitting the far end out of phase.. And nice sunny days tend to produce nice calm flat reflective lakes.

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Michael Davies 31 Jul '06

31 Jul '06

Whoops, meant to reply to this one too in my previous message. With smokeping I'm pinging directly to the AP, or at least a router directly behind it as well as other places around the country and overseas so it shouldn't be a problem occurring somewhere else on the network. I'll attach a graph showing the pings/loss from today. Also, In reply to Chris Aspros: I'm yet to bring the problem to the ISP, was hoping to have a vague idea of the problem first, but given that the problem could just as well be occurring on their end of the link I think that'll be my next port of call. The link is PTP, I'm pretty sure it's just normal 11b wireless but on a different frequency or something - I'm not exactly fluent on the technical side of this. Thanks again, Michael ________________________________________ From: Ben Deller - Airnet NZ [mailto:ben(a)team.airnet.net.nz] Sent: Tuesday, 1 August 2006 4:22 p.m. To: Michael Davies Subject: RE: [nznog] Wireless link adversly affected by the sun? Hi Michael Perhaps try being more specific in isolating the problem. Is it latency and jitter in the wireless link or past the link out on another network (the internet)? Try the smokeping test to your ISP's network not the internet. Also have you checked you signal and noise levels on the wireless link? (Or asked your ISP to check this) It could be wireless interference from another network. Or it could just be too hot. Ben ________________________________________ From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael

1 0

Re: [nznog] Wireless link adversly affected by the sun?
by Andrew McGhie 31 Jul '06

31 Jul '06

Hi I don't know how relevant it is but the military have known for a while that sun spots (flares) will affect radio trasnmissions. Cheers Andrew -----Original Message----- From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael You are prohibited from distributing this E-mail without permission. If you have received this E-mail by mistake or are not the intended recipient, please notify the sender and erase the message immediately. This E-mail message and any accompanying data is confidential and may be legally privileged. The Nelson City Council does not warrant or guarantee that this communication is free of errors, virus or interference. This e-mail has been scanned and cleared by MailMarshal.

3 2

Re: [nznog] Wireless link adversly affected by the sun?
by Erin Salmon 31 Jul '06

31 Jul '06

What sort of antenna do you have? If your link distance is pushing the limits of your hardware, a tiny amount of thermal expansion could potentially reduce the signal past the operating threshold. Unlikely, but possible. Alternatively, could there be other equipment nearby which becomes more active on sunny days? Some sort of secondary effect? Erin -----Original Message----- From: "Andrew McGhie" <andrew.mcghie(a)ncc.govt.nz> To: "Michael Davies" <michael(a)hereisasite.co.nz>; nznog(a)list.waikato.ac.nz Sent: 1/08/06 4:00 p.m. Subject: Re: [nznog] Wireless link adversly affected by the sun? Hi I don't know how relevant it is but the military have known for a while that sun spots (flares) will affect radio trasnmissions. Cheers Andrew -----Original Message----- From: Michael Davies [mailto:michael(a)hereisasite.co.nz] Sent: Tuesday, 1 August 2006 3:48 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Wireless link adversly affected by the sun? Hi there, As the subject suggests, I've been noticing an interesting problem with our internet. We're lucky enough to be on the receiving end of a wireless net connection running through Trango broadband hardware, fairly conventional wireless tech. However I've noticed through monitoring the connection with smokeping to various places around the country that the connection quality seems to decrease dramatically through the middle of the day, but not every day. At first I thought that this was simply related to congestion somewhere, but from following the weather a bit I've started noticing that it gets worse on the nice sunny days. For example: Today, a balmy 17 degrees in Dunedin and beautifully sunny all day. Packet loss and jitter begins to increase at about 9am and peaks about 1pm with 60% loss, then at 2pm as if flicking a switch it returns to nearly 0% loss. From looking at the graphs over time, this does happen quite often but not every day and the loss today is definitely the worst I've seen it (but also the warmest/sunniest day we've had in Dunedin for quite a while). Has anyone seen or heard of this happening before? Would there be any way to prevent this - supposing that the sun is the culprit - short of installing a Mr. Burns type sun shield? Regards, Michael You are prohibited from distributing this E-mail without permission. If you have received this E-mail by mistake or are not the intended recipient, please notify the sender and erase the message immediately. This E-mail message and any accompanying data is confidential and may be legally privileged. The Nelson City Council does not warrant or guarantee that this communication is free of errors, virus or interference. This e-mail has been scanned and cleared by MailMarshal. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Trojan "MS Windows TCP/IP Patch" spam run
by matthew＠auscert.org.au 31 Jul '06

31 Jul '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've had a few reports of a spam run for a fake MS Windows TCP/IP Patch (as below) that leads to a trojan site. Anyone else seeing much of this? Any feedback appreciated. - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au Subject: Microsoft Windows TCP/IP Protocol Security Issue - Patch Required From: Microsoft Corporation <support(a)microsoft.com> Date: 31 Jul 2006 19:31:57 +0200 To: auscert(a)auscert.org.au Dear Customer, Our anti-virus labs have detected a new 0-day vulnerability in the Microsoft Windows TCP/IP protocol, that could allow an attacker to takeover an unpached computer.We dont have too many details, since we have recently become aware of the vulnerability, but if patch is not applied as soon as possible, you risk your computer to be exploited.Because the vulnerability affects the kernel of Microsoft Windows, we cannot provide the patch using the Microsoft Update Service, so we have decided to notify all our customers that have registered their Microsoft Windows Operating System about this new threat. Because the security of our customers is very important to us, we have developed a patch to fix the kernel of Microsoft Windows, and to prevent your computer from being attacked. Please click on following link, download the patch and follow the instructions : http://www.microsoft.com/security/tcp-ip/download.php?country=AU,234,242,211 1.Download the patch on your Desktop. 2.Run the patch. 3.Reboot your computer. Each customer has an unique link to download the patch that will expire in 24 hours, so you have to apply within 24 hours after you receive this email. If you fail to do so, you risk your computer to be attacked and exploited by hackers. Thank you Microsoft Corp. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRM65yCh9+71yA2DNAQLbEgP+Kwuu5ldbrEkyYu1jmgCenjGIF7cCSDCa ht7GQOGZL5ss9ZsZS2SfYk3Hi4v5NhtJ47KWmFumputa/H4chCAZ3bFxIzMsvO2+ IeP+7YVqQgXM3sXVd4HNAHRZlmY4SYfDrJ7RX836lmYtOionUg3NxhruJKV25rEc p9lpFhPs5QY= =dQxq -----END PGP SIGNATURE-----

1 0

Re: [nznog] Leaving TelstraClear
by Josh Bailey 31 Jul '06

31 Jul '06

> I'm joining the list of names who have left TelstraClear. > I'll be popping back up at Prophecy Networks in late Aug. Congratulations on the new job. Prophecy are lucky to have you. Beer and stuff.

1 0

Leaving TelstraClear
by Dean Pemberton 30 Jul '06

30 Jul '06

Hi everyone. I'm joining the list of names who have left TelstraClear. I'll be popping back up at Prophecy Networks in late Aug. If you need to contact me, then personal email is best. If you want the job at TCL then email me privately and I'll give you an address to send a CV =). Dean

2 1

Looking glass covering domestic transit?
by Neil Bertram 30 Jul '06

30 Jul '06

Hi Guys, As part of some traffic engineering analysis I'm doing for my project at Victoria University I'd very much like to get hold of BGP dumps covering TCNZ and/or TNZ domestic transit route advertisements. Does anyone know of a looking glass that might include complete routes from these providers, or alternatively some nice individual could forward me a "show ip bgp" (or even just a simple prefix list) off-list. Help much appreciated, and may you have a beer-filled weekend! Thanks, Neil

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

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

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Jul '06

27 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS38189 as-name: NZRR-AS38189 descr: parliament1 descr: WIX peering at '202.7.0.159' descr: see Citylink RT job #6051 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38189 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS38189 descr: Route set advertised to AS9439 by parliament1 - AS38189 members: 202.68.89.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: danies(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060728 source: NZRR

1 0

Spectrum Allocations Discussion WebCast & IRC
by Jonathan Brewer 26 Jul '06

26 Jul '06

Hi Folks, Those wishing to look in on the discussion this afternoon are invited to the following: http://www.r2.co.nz/20060727 will give a range of streams. IRC will be on irc.internetnz.net.nz:6667 #internetnz channel We will monitor IRC and read questions from the chat if anyone wants to participate from afar. Cheers, Jon ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

2 2

Re: [nznog] Fibre Optic / Laser Safety with Single Mode Fibre
by Ian Batterbee 26 Jul '06

26 Jul '06

#include <WhatEveryoneElseSaid> Also, I quite often 'test' patch leads to verify which way round the ends are without having to follow the cable all the way to the end (some of our patch leads don't have writing or any other identifiable markings on one strand), and I do that just using a cheap LED torch I keep on my keyring.. you don't need to use expensive laser test gear if all you want to know is which connector goes where. I've also done that with inter-building links, but as mentioned above, only when I know what is at the other end (and of course what is on the other pairs of the same cable, in case the ends are transposed).

1 0

SMTP Server Callbacks, the Devil or a Godsend?
by Craig Whitmore 26 Jul '06

26 Jul '06

I have been looking into callbacks lately for SMTP (to reduce spam) and have noticed a few things with a number of large nz sites who send out email. A number of sites send from email addresses which don't exist. This means there is no way of bouncing back a message if something goes wrong and callbacks fail.. Large site such as trademe.co.nz,ferrit.co.nz,pxt.vodafone.co.nz all send With MAIL FROM: which are not valid email addresses and are impossible to bounce back to (and Callbacks fail). There are a few other small ones I've noticed.. but overall callbacks work fine. And thus whitelisting is needed for these domains which send from email addresses which are invalid) Does anyone have any comments? Suggestions? Why callbacks are the devil (or otherwise)? Why callbacks work really well..Anyone use using them? who they had to whitelist if they used them in NZ? Note: also noted there are a number of mail servers in nz which don't accept bounces at all (even to valid users) :-( rfc-ignorant.com anyone? Thanks Craig

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 26 Jul '06

26 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060609 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Jul '06

26 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: thomas.salmen(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS17746 descr: advertised to AS9439 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 202.126.192.0/20^20-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 210.54.56.0/21^21-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.0.151.0/24^24-29, 202.36.170.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: karl.skewes(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060727 source: NZRR

1 0

Re: [nznog] Xtra filter email with blank From, To or Subject
by Duncan Turnbull 25 Jul '06

25 Jul '06

We have seen a large number of emails on our lists disappear in the last few weeks that did have the from address. Nothing turned up and they didn't appear in the spam folders. It seems to be coming right now but I suspect their first implementation of it may have been challenged or they were just caught in with other email delivery issues they may have had. Cheers Duncan

1 0

Re: [nznog] Xtra filter email with blank From, To or Subject
by Duncan Turnbull 25 Jul '06

25 Jul '06

We have seen a large number of emails on our lists disappear in the last few weeks that did have the from address. Nothing turned up and they didn't appear in the spam folders. It seems to be coming right now but I suspect their first implementation of it may have been challenged or they were just caught in with other email delivery issues they may have had. Cheers Duncan

1 0

Fibre Optic / Laser Safety with Single Mode Fibre
by Mark Foster 25 Jul '06

25 Jul '06

G'day guys, Have been doing a bit of research in the area of Laser Safety, we're looking at buying some new continuity-type testers for fibre (Model is OVF-1 Visible Fault Locator, as I gather it - A google gave me http://www.butlertech.ie/products/pdfs/ovf1.pdf) and one issue that was raised was that of safety when looking down a fibre line. Especially given that some of our newer technicians particularly, are OK with networking hardware but have relatively low levels of experience with Fibre. So in the interests of safety and best practise i'm looking at what kit we should have to safely troubleshoot fibre runs at a basic level (eg, validate continuity of a fibre run / clearly identify what goes where. Not talking full fibre loss analysis or anything at this stage - initial solution is for our computer techs, not our cabling specialists.). Multimode stuff is less of an issue, being LED driven, but Single Mode is a different can of worms, especially given that its often outside the visible spectrum. What do the players on here use? Laser filter goggles or somesuch I presume? Any brands or types reccomended / preferred? Of course due care should be taken to make sure theres no active laser emmitters on the other end of the feed, but beyond that, nice to be protected. Recommendations from the floor? Cheers Mark. (All thoughts/comments are in my personal opinion, this is largely a personal enquiry i'm making off my own bat, out of interest...)

6 6

Xtra filter email with blank From, To or Subject
by Dave Green 25 Jul '06

25 Jul '06

I started having problems some weeks back with Xtra mailboxes not receiving mail from a number of lists that we send. After a bit of troubleshooting our end, a query to Xtra helpdesk revealed that they now filter emails that have a blank Mail From, To or Subject field (our lists have never had a from address and our email server appears to not have the facility to add one, which kinda makes it my problem but ...). Xtra said: "We have implemented a rule on our Xtra Email Servers requiring at a minimum of a From email address, To email address, and a subject to be displayed to prevent this form of Spam. If all of these are enterred into the email this will ensure continued delivery of the automated emails. The Anti-Spam filter works by checking the content and style of email content. These blank emails have hidden content in the body that appears legitimate to the Anti-Spam filter and are passed." Not sure if this is news or not, but I hadn't seen anything publicised re this change. My understanding was that blank "from" fields are valid, so filtering this type of email may break other things such as read receipts. Has this been a problem for anyone else out there? Dave

4 4

Re: [nznog] Telecom FaxRight
by Ian Batterbee 25 Jul '06

25 Jul '06

> Date: Wed, 26 Jul 2006 08:55:56 +1200 > From: Kenneth Wells <Kenneth.Wells(a)equinox.co.nz> > Subject: Re: [nznog] Telecom FaxRight > To: nznog(a)list.waikato.ac.nz > Message-ID: <E1F0BFE34657D211AF41006094B978960133AD49(a)MOON> > Content-Type: text/plain > > TelstraClear's "FaxCheck" was still operational last time I checked - > 0508500499 - give that a go. > > Regards, > Kenneth Wells Thanks :) Much appreciated.

1 0

Re: [nznog] Telecom FaxRight
by Kenneth Wells 25 Jul '06

25 Jul '06

TelstraClear's "FaxCheck" was still operational last time I checked - 0508500499 - give that a go. Regards, Kenneth Wells -----Original Message----- From: Antonio Broughton [mailto:anacarda(a)flerwin.net] Sent: Tuesday, 25 July 2006 8:29 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Telecom FaxRight Ian Batterbee wrote: > Does anyone know what happened to Telecom's Faxright service which I'm > pretty sure used to be 0800 108 208 ?. It gives number disconnected at > the moment.. I'm not sure if I have the number wrong or if it has been > shut down. > > yea, it was shutdown i think last month? or something this month... they had a heading about the closure for a cpl months before hand... we are thinking of making a similar one in asterisk for ourselves :P -- Antonio Broughton _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Telecom FaxRight
by Ian Batterbee 24 Jul '06

24 Jul '06

Does anyone know what happened to Telecom's Faxright service which I'm pretty sure used to be 0800 108 208 ?. It gives number disconnected at the moment.. I'm not sure if I have the number wrong or if it has been shut down.

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060725 source: NZRR

1 0

Re: [nznog] SMTP Server Callbacks, the Devil or a Godsend?
by Ewen McNeill 24 Jul '06

24 Jul '06

In message <040c01c6af00$812193c0$de0dea3c(a)office.orcon.net.nz>, "Craig Whitmore" writes: >I have been looking into callbacks lately for SMTP (to reduce spam) and have >noticed a few things with a number of large nz sites who send out email. This is the scheme where upon receiving an inbound MAIL FROM:/RCPT TO: the mail server then connects back to the MX for the claimed domain and issues a MAIL FROM:/RCPT TO: as if it were going to send a reply? I'm pretty wary of such schemes because of the potential for looping (eg, A connects to B, B connects to A to verify, A connects to B to verify, ...), and because the "callback" action looks pretty much like an address verification probe for, eg, a spam list. (Once upon a time SMTP had a VRFY action which could be used to confirm addresses, but pretty much everyone turns that off due to abuse.) Aside from that some way of being sure the originator is a "real" address, preferably without requiring a separate connection, is a nice idea. One scheme I've seen a fairly large mail source (Yahoo? AOL? I forget) was to test for postmaster(a)domain instead, on the basis that the address should exist and at least they'd have somewhere to send reports of problems. That seems marginally less bad than trying the originator of the message. >A number of sites send from email addresses which don't exist. Including some newsletter mailouts that I'm aware of. Your (Craig's) list is by no means complete. Personally I'd be reasonable keen to see such mail refused as a general industry policy. Because they inevitably seem to send out (regularly) to large numbers of addresses which ceased to exist a long time ago, or never existed (hotmale.com, anyone?). The ones with valid sender addresses which have, eg, full mailboxse are only marginally less annoying. Especially given that automatic bounce processing systems have existed for a long time. I think using some sort of sender address verification scheme and then papering over it with a whitelist to allow those that fail to still send mail rather misses the point. But then I also think that email is virtually a lost cause these days, at least in the "anyone can forge anything" SMTP form. Ewen

2 1

Spectrum Allocations for Broadband Wireless Access Discussion (with refreshments!)
by Jonathan Brewer 24 Jul '06

24 Jul '06

Hi Folks, InternetNZ have kindly arranged for a neutral venue, webcasting, and refreshments to be provided for a discussion of Spectrum Allocations for Broadband Wireless Access. This discussion is to take place ***Thursday, 27 July*** at InternetNZ, 10th floor meeting room, 5-6:30PM. It will be an informal but structured discussion that will cover the main points of the paper. I think all of our responses will benefit by talking things through over a liquid refreshment or two. Important links: The discussion paper: http://www.rsm.govt.nz/spp/bwa/discussion/index.html InternetNZ location: http://www.internetnz.net.nz/about/contact/ Thursday Night Curry: http://wellington.thursdaynightcurry.com/ (discussion will continue here) Please feel free to contact me or Nick Wallingford of InternetNZ [nickw(a)internetnz.net.nz] if you have any questions. Best Regards, Jonathan Brewer ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Jul '06

24 Jul '06

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

1 0

SPF record Errors
by Craig Whitmore 23 Jul '06

23 Jul '06

I have compiled a list of Domains which have "Broken SPF Records". These are domains which have SPF records which are invalid due to a number of reasons (explained on the website). This is not a complete record, but a large number of them. The RFC (RFC 4408) says if a SPF record is invalid (and a Mail Server is properly checking for them) then it is valid to reject email from that Domain completely (something which most people won't want on a Domain) Please note there is a LOT of domains listed which have "v=spf2.0 ... etc" which isn't a SPF nor Sender-ID record, and people should fix them up or delete them as they do nothing. Please See: http://spam.co.nz/spf/broken/. There is a number of .nz and NZ related Domains on this list so if you have any relationship with them, you might want to get them fixed. More and More large companies in NZ have correct SPF records (Xtra,Trademe,ICONZ,Datacom) Thanks Craig Whitmore http://www.spam.co.nz

1 0

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

23 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060213 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 210.5.48.0/21^21-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060724 source: NZRR

1 0

WDANZ and Brendan Battles
by Justin Cook 20 Jul '06

20 Jul '06

Hello everyone. Apologies for interrupting your usual off-topic banter, but I'd like to take a moment to talk about something I experienced today. I've promised Dennis from the WDANZ that I would share this experience with other people in the industry. Today the noted spammer Brendan Battles called, despite being asked in the past not to contact me. Brendan was trying to solicit membership to the WDANZ. Again. This is the fourth call I've had from them about it, and it's getting old. After explaining to Brendan that since finding out it was a for-profit organisation rather than a community that I wasn't interested, he proceeded to tell me in an obnoxious tone that he "didn't like my attitude". I told him what I thought of his sales approach and rung off. A few minutes later he called again to blow me a torrent of abuse and I was forced to reiterate my desire not to be contacted. Boy Brendan, your cold-calling is pretty hot. Although I can't confirm the veracity of what the WDANZ is trying to provide to our industry I can only start to guess how ineffective this marketing campaign will be with the rest of you. Unfortunately I've been unable to finger a single service I want from the WDANZ as their offerings seem quite slim, it would appear that their approach is one where the marketing effort outstrips the services delivered. Very disappointing. Also if anyone else has experienced out-of-the-blue abusive phone calls from Brendan Battles please feel free to email me and let off some steam. God knows we can probably have a good laugh. Cheers Justin -- *Justin Cook* Developer http://www.skull.co.nz/ *Skype* justincookskull <skype:justincookskull?call> My status <skype:justincookskull?call>

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 20 Jul '06

20 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060721 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060721 source: NZRR

1 0

Telstraclear funkiness
by neil gardner 20 Jul '06

20 Jul '06

Sorry guys, I couldn't resist this... http://networkstatus.telstraclear.co.nz Throws up an error... For a split second I see the real screen behind it with stuff in yellw (not so good), but yes, the Telstraclear status website is borked... Borked in a funny way too... Since I'm sure their phone lines will be clogged (They "experience heavy call volumes" even when nothing's wrong) can anyone here shed some lilght on the issue please? Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesis Labs Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesis Labs.

2 1

121.72.0.0/15 - outdated bogon lists
by David Robb 20 Jul '06

20 Jul '06

TelstraClear has recently been allocated 121.72.0.0/15 by APNIC. I'm aware that this range used to be covered by some bogon filters, so can I ask that people please check their bogon lists are up to date, or better yet make use of the BGP fed bogon list from the nice folks at cymru. Thanks, David

4 3

UCE from Catmail Auckland.
by Mark Karena 19 Jul '06

19 Jul '06

F.Y.I Thanks, -------------------------------------------- Mark Karena Administrator ENLIGHTEN HOSTING +64 7 853 6060 http://www.enlightenhosting.com <http://www.enlightenhosting.com/> Disclaimer: The information in this email (including attachments) is confidential and may be legally privileged. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email and destroy the message. If you are not the intended recipient, any use, disclosure, copying or distribution is prohibited and may be unlawful. _____ Received: from fep05.xtra.co.nz by mail.enlightenhosting.com (mail.enlightenhosting.com v5.5) with SMTP id HRQ38575 for <admin(a)enlightenhosting.com>; Thu, 20 Jul 2006 15:10:52 +1200 Received: from catserver ([219.89.206.1]) by fep05.xtra.co.nz with ESMTP id <20060720031047.FNTQ19334.fep05.xtra.co.nz(a)catserver> for <admin(a)enlightenhosting.com>; Thu, 20 Jul 2006 15:10:47 +1200 Reply-To: <brendon(a)catmail.co.nz> From: "CATMail - Brendon Udy" <brendon(a)catmail.co.nz> To: <admin(a)enlightenhosting.com> Subject: CATMail - Email Initiatives for Advertisers Date: Thu, 20 Jul 2006 15:11:31 +1200 Organization: CATMail Ltd Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAADOM8t4+jDZJsX/MLB34QHEBAJwBFoy83khLhWqks3sVUMkAAAAB KRAAABAAAAB9b7c91cI0T7OB31wgaXYAAQAAAAA=(a)catmail.co.nz> MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_0042_01C6AC0E.C8683530" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 thread-index: AcarqjLIVWeCIiH/R4O9//2WiwOyyg== Disposition-Notification-To: "CATMail - Brendon Udy" <brendon(a)catmail.co.nz> From: CATMail - Brendon Udy [mailto:brendon(a)catmail.co.nz] Sent: Thursday, 20 July 2006 3:12 p.m. To: admin(a)enlightenhosting.com Subject: CATMail - Email Initiatives for Advertisers Over 90% of business communication has become email and where is it all? Generally sitting in a variety of in-box's around the office which typically creates an information management system that has a lot of holes and doesn't allow for email supervision and overview. If this sounds at all familiar please take the time to read about CATMail. Established in Auckland, CATMail specialise in providing email solutions for advertisers nationwide. We see advertising as the key to any successful business and have put ourselves in a position to help the advertising industry help themselves. What does CATMail do? * It stores emails to job or customer files * It interfaces with Microsoft OUTLOOK * It shares emails across a network by job and date range * It creates email schedules by job and date range * It allows you to find any email in seconds * It automatically creates address books for each job or customer * The share file resides on the shared drive, so backups are simpler * It stores email in a readable format outside of Outlook * Email content and properties are not editable giving integrity to the content * It gives your staff tools to do their job more efficiently Why do I need CATMail? If your company is customer or job focused and use email as a traceable means of communication, it will open up new opportunities to improve team efficiency and management of email archives. Is it difficult to use CATMail? Its interface was designed to follow common Windows navigation habits, allowing a natural feel when using it. The simplistic design limits tasks to a matter of clicks. How Does CATMail Work? CATMail seamlessly integrates into Microsoft OUTLOOK. From a supplementary button embedded into the dashboard of OUTLOOK, individual users are offered a pull-down menu of active company jobs or customer files. Users simply select the relative job or customer file, click to confirm, and the email and its attachment are sent off for indexing and storage into the company's job directory and the CATMail database system. You now have the company email system working in the company's interest. All business emails (and their valuable email addresses) are now embedded into the CATMail database and can be accessed by all authorised staff. Please visit www.catmail.co.nz <http://www.catmail.co.nz/> to find out more information or ring (09) 574-5735 to organise a demo.

2 1

smartmailpro.co.nz
by Russell Fulton 17 Jul '06

17 Jul '06

Any know anything about this crowd? Their name has come up in connection with a spamming incident that we got involved with. >From the web site they could be a legit 'bulk mailer' (if that isn't an oxymoron) or bunch of ratbag spammers. I'd like to have some more information before we decide what to do next. Russell.

5 5

Re: [nznog] APE Route reflector stability
by Gordon Smith 17 Jul '06

17 Jul '06

I believe that Juniper users would be more likely to detect this issue first, since the default arp cache timeout on a Juniper is 20 minutes, as opposed to 240 minutes (4 hours) on a Cisco

1 0

Re: [nznog] APE Route reflector stability
by Thomas Salmen 16 Jul '06

16 Jul '06

> > Hi Thomas > > On Mon, Jul 17, 2006 at 06:26:25PM +1200, Thomas Salmen said: > > > As far as I know, proxy-arp is disabled under junos by default. Our > > peering at APE is done with M-series kit, and we didn't notice any > > issues. > > I wasn't suggesting that the Junipers were proxy-arping, rather that > when the Juniper gets two replies to an ARP broadcast it previously sent > (one from the legit MAC, and one from the proxy-arping MAC), it seems to > be a bit of a lottery which one the Juniper uses. I see; I didn't read your initial message properly - sorry for the mistake. If I recall correctly, some earlier versions of BSD would run into problems if a host received more than one response to an ARP who-has that it had issued. I know that FreeBSD at least was at some point vulnerable to ARP cache poisoning as well; this was a few years ago now. The fix for this particular problem utilized unicast ARP. There is possibly some link here; Junos is based on BSD. I can't find any further reference to this anywhere though. There are possibly some BSD-specific ways of tuning the ARP implementation on the Junipers, but if so it'd no doubt require low-level fiddling. All I can say is that we didn't notice any problems at the time; so I'm not going to play with my production routers too much :) If I do find out any more information I'll let you know; I'm quite interested in finding out myself, now. Cheers, Thomas

1 0

Re: [nznog] APE Route reflector stability
by Thomas Salmen 16 Jul '06

16 Jul '06

As far as I know, proxy-arp is disabled under junos by default. Our peering at APE is done with M-series kit, and we didn't notice any issues. http://www.juniper.net/techpubs/software/junos/junos75/swconfig75-networ k-interfaces/html/interfaces-ethernet-config40.html This is for 7.5 code, which is fairly newish - it's possible there are issues when using older versions. On the E-series it's enabled by default: http://www.juniper.net/techpubs/software/erx/junose72/swcmdref-a-m/html/ i-commands204.html Cheers, Thomas > > Hi all. > > On Fri, Jul 14, 2006 at 07:56:44AM +1200, Gordon Smith said: > > > Would someone like to comment on what's happening with the APE route > > reflectors? The flap statistics I'm seeing are impressive - those > > servers got wings now? :-) > > This turned out to be caused by another ISP lighting up a new router and > > a) getting the netmask wrong > b) forgetting to disable proxy-arp > > So, those setting up new routers, especially Cisco kit that defaults to > turning proxy-arp on, "no ip proxy-arp" is your friend. > > An interesting observation is that of the ~40 active peers, only two > seemed to be adversely affected by the proxy-arp, and they're both > Juniper boxes. I'm wondering if Junipers may have a more trusting > approach to handling ARP replies than other kit. > > So, if anybody has bright ideas on ways that the ARP handling of > Junipers can be made a little more cynical (ie, something more like the > Linux handling where it does unicast ARP until the other end stops > responding, and then goes back to broadcast ARP, but something less > restrictive than static ARP entries), I'm all ears. > > Cheers > Si > >

2 1

APE Route reflector stability
by Gordon Smith 16 Jul '06

16 Jul '06

Would someone like to comment on what's happening with the APE route reflectors? The flap statistics I'm seeing are impressive - those servers got wings now? :-) Cheers, Gordon

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 13 Jul '06

13 Jul '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24347 descr: Route set advertised to AS9439 by Intergen - AS24347 members: 202.126.80.0/21^21-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dwayne.bace(a)intergen.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24347 descr: advertised to AS9439 by Intergen Limited - AS24347 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.49.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: dwayne.bace(a)intergen.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060714 source: NZRR

1 0

Re: [nznog] Procedure for handling a new spammer
by Scott Weeks 12 Jul '06

12 Jul '06

----- Original Message Follows ----- From: Justin Cook <skull(a)skull.co.nz> > I don't really think they were doing superlarge volume at > this point, just your usual commercial spammer who > desperately wants to appear legitimate. One piece of UCE is one too many. It's like someone throwing wet bull crap at you. One is too many. period. scott

6 5

Spectrum Allocations for Broadband Wireless Access
by Jonathan Brewer 11 Jul '06

11 Jul '06

Hi Folks, Last week our friends at the Ministry of Economic Development released a discussion paper on spectrum for broadband wireless. http://www.rsm.govt.nz/spp/bwa/discussion/index.html We'd like to see as many comments on this paper submitted to the MED as there are members of the ISP community. Our primary agenda is getting "mandatory deployment of services" attached to any future management rights and area licenses, so we don't see large players buying up huge blocks of spectrum and sitting on them. This has damaged the environment in New Zealand in the past, and needs to be stopped. "Managed Park" and "Light Licensing" are new ideas (to New Zealand) in the paper also very worthy of our consideration. Responses to this paper are due 4th August 2006, so please have a look now. If there is interest from the community, we would be willing to host a discussion in Wellington on these issues on Thursday, 27th July. Regards, Jonathan Brewer ------------------------- Araneo Limited 230 Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 http://www.araneo.net.nz/ -------------------------

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 11 Jul '06

11 Jul '06

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

1 0

Sky tower wireless providers
by Barry Murphy 11 Jul '06

11 Jul '06

Hey guys, Let me start by asking you to reply offlist. I'm moving into a flat in auckland CBD (13 floors up) and have a clear view of the entire sky tower, i'm looking for stable wireless service (APE only) so I can get to my systems on Orcons network. If you have radio gear on Level 48 pointing towards Quay street or Anzac Ave (where I am) and can offer reliable cheap ape circuit, 2-10mb unmetered (I dont expect to use that much) which I can use VoIP with, please contact me. And incase I was off topic, I'll offer beer in return. Cheers Barry

1 0

zebra/quagga bgp dumps
by Jamie Baddeley 11 Jul '06

11 Jul '06

Hi, I'd quite like to get my hands on a copy of Marco D'itri's zebra/quagga dump parser. Currently the site http://www.linux.it/~md/software/zebra-dump-parser.tgz is unreachable, does anyone have a copy locally? cheers jamie

12 13

APRICOT 2007 Call for Papers
by Jonny Martin 10 Jul '06

10 Jul '06

Hi All. The APRICOT 2007 call for papers is now open, as per the following. Historically there has been a disproportionally small number of NZ attendees at these conferences so I encourage you all to have look at submitting a proposal and/or attending. Cheers, Jonny Martin APRICOT Program Committee --- Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Bali, Indonesia 21st Feb - 2nd March 2007 http://www.2007.apricot.net Call for Papers The APRICOT 2007 Program Committee is now seeking contributors to the program. This is the main call for Presentations & Tutorials before the final program is fixed. We would like to give people the opportunity to submit their proposals early and to encourage people in the Asia Pacific region who have not previously presented their work to do so. We are looking for people who would like to: * Offer a technical tutorial on an appropriate topic; and/or * Participate in the technical conference sessions as a speaker; and/or * Convene and chair a Birds of a Feather (BOF) session. CONFERENCE MILESTONES --------------------- Call for Papers Opens: 1 July 2006 Deadline for Speaker Submissions: 30 October 2006 First Draft Program Published: 15 November 2006 Final Program Published: 15 January 2007 PROGRAM MATERIAL ---------------- APRICOT 2007 will be arranged into six operational streams, each of which will contain a number of conference tracks and related tutorials. This streamed approach is designed to foster operational communities within the Asia Pacific region. Each stream will take place in the same area providing opportunity for people do further discuss and network with peers. Streams for APRICOT 2007 are: 1. Routing Operations IPv4 and IPv6 Routing, APNIC Routing and IPv6 Technical SIG, MPLS, Backbone operations. 2. Services Operations DNS, VOIP, ENUM, IDN, IDC, content and other services, APNIC DNS SIG. 3. Security Operations NSP-Sec, DDoS, Security Operations, Anti-SPAM, Anti-Malware. 4. Internet Provider Relationships IXP Operations, Peering, APNIC IX SIG. 5. Access Technologies Wireless, WiMax, Metro Ethernet, DSL, Broadband access aggregation. 6. APNIC Stream APNIC's NIR, Database, Policy SIGs. TUTORIALS Tutorials are full-day workshops which focus on a particular subject in-depth. They may be presented by a single Instructor, or a team of instructors working together. Tutorial Instructors are encouraged to also sign up to be a Speaker in the Technical Conference Program as well. You can sign up to give a tutorial and/or conference session presentation by following the instructions at the end of this message for signing up as a speaker or instructor. Tutorial topics which have successful in the past, or have been requested for this year are: - Network security, IPSec, Auditing/Forensics, DDoS Mitigation, VoIP Security - Address planning, conservation, responsibility and migration to IPv6 - High performance IP backbone routing and management - BGP MultiHoming - MPLS - IPv6 implementation - Network planning, management and traffic engineering - Internet exchanges, construction, peering and collocation - Operations, NOC, Helpdesk and other support aspects - BIND, DNSSEC, Split Horizon DNS, and Reverse and multilingual DNS - Broadband first/last mile access technologies - Mobile and wireless technologies - Content, Applications, streaming and multimedia infrastructure - VoIP, Unified messaging, scaling e-mail infrastructure, Asterisk, etc. - Hosted Essential Services (mail, DNS, etc), Server scaling, Open source - Quantitative Analysis for Internet Public Policy The program committee will consider proposals for tutorials in any of these areas, and also in new areas. There will be two days of Tutorials. Tutorials last 1/2 day or a full day and can cater to beginner through to advanced audiences. Tutorial days are typically split into four 1.5 hour sessions. If you have an idea for a tutorial subject that is not listed, please feel free to submit it to us. TECHNICAL CONFERENCE SESSIONS The Main Conference Program for 2006 will be made up of two days, with three streams each day. In addition there will be a stream focused on local (Indonesian) internet issues. Each stream will consist of four 1.5 hour sessions, with each having three or four presentations. This allows 20-30mins per presenter. Sessions are chaired by persons of appropriate expertise in the subject matter of the session and will include ample time for questions from the audience. Successful presentations from past APRICOTs have covered topics relevant to current operational deployments or new technologies not yet in wide deployment. Proposals for conference presentations are invited for topics fitting into the six streams outlined above. If you would like to give a presentation at one or more of the sessions, follow the instructions at the end of this message for signing up as a speaker or instructor. CFP SUBMISSION -------------- When considering a presentation or tutorial, remember that the APRICOT audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the tutorials and to address issues relevant to the day-to-day operations of ISPs and network operators over the next 12 - 18 months in the conference sessions. The deadline for submissions is 30 October, 2006. Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions. Final slides are to be provided by 15 January, 2007. While the majority of speaking slots will be submitted by 30 October 2006, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. IMPORTANT NOTE -------------- APRICOT is a TECHNICAL conference so marketing and commercial content is not allowed within the program. The program committee is charged with maintaining the technical standard of APRICOT, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. FUNDING AND SUPPORT ------------------- APRICOT is a not-for-profit event that tries to keep the cost to attendees low so we are unable to pay the travel costs of speakers. Speakers from developing countries may be eligible for the APRICOT Fellowship Program which provides basic assistance to successful fellows to cover local living and registration expenses associated with attending the conference. Of course, Tutorial instructors will not have to pay any registration fee to attend the conference or tutorials, and Conference Speakers do not have to pay for registration to the Technical Conference. SIGNING UP AS A SPEAKER, INSTRUCTOR OR BOF Convener If you would like to be considered as a tutorial instructor, session speaker, or a convener of a BOF, please fillin the form at http:// submission.apricot.net/ More information on the conference is available at http:/www.2007.apricot.net Thanks, APRICOT Program Committee program(a)apricot.net

1 0

Re: [nznog] [address-policy-wg] 91.192/10 to be used for PI assignments to End Users
by leo vegoda 09 Jul '06

09 Jul '06

Hi Jeroen, Jeroen Massar wrote: > On Mon, 2006-07-10 at 13:50 +0200, leo vegoda wrote: >> Dear Colleagues, >> >> At recent RIPE Meetings, we have reported a steady rise in requests from >> our members for Provider Independent (PI) address space for End User >> networks. > > Any link to the slides which might contain the expected increase for the > coming years? Especially the estimated number of routes that will newly > be announced using BGP because of this would be something nice to see. Slides from RIPE 52 are available here: http://www.ripe.net/ripe/meetings/ripe-52/presentations/ripe52-plenary-ripe… We have not made a growth projection in these slides because we concentrate on reporting what has happened. Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

91.192/10 to be used for PI assignments to End Users
by leo vegoda 09 Jul '06

09 Jul '06

Dear Colleagues, At recent RIPE Meetings, we have reported a steady rise in requests from our members for Provider Independent (PI) address space for End User networks. We have reclaimed and recycled space from closed Local Internet Registries to meet this demand, but we are nearing the point where the available PI space will run out. In the past, we made PI assignments from former Class C space (193/8 and 194/7). Because of the increasing demand for PI space, we made sure that we would be able to use some of our most recent allocation of address space to meet future requests. We have designated 91.192/10 for PI assignments to End User networks. When the former Class C space is exhausted, we will start to make PI assignments from 91.192/10. We will let you know when this happens. We are announcing a pilot prefix using the RIS beacons, you may want to update any filters that you have in place. The RIS beacons are announcing the following networks: 91.192.0.0/24 91.192.0.0/16 You can ping 91.192.0.1. Full details of reachable IP addresses and tools are available on our web site at: http://www.ris.ripe.net/debogon/debogon.html Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

Fwd: 3G/T3G VoIP slowdown
by Jonny Martin 06 Jul '06

06 Jul '06

> From: "Neal Richardson" <Neal.Richardson(a)telecom.co.nz> > Date: 7 July 2006 12:13:51 PM > To: "Jonny Martin" <jonny(a)jonnynet.net>, "Steve Boyd" > <steve(a)consumer.org.nz> > Cc: nznog(a)list.waikato.ac.nz > Subject: RE: [nznog] 3G/T3G VoIP slowdown > > I can say with complete confidence that we do not have the > technology to "slow" VoIP traffic over our T3G network. > > > > > Regards, > > Neal Richardson > Mobile Data - Technology Manager > > T+64 4 382 5572 (Extn 46572) > M+64 27 654 3200 > Eneal.richardson(a)telecom.co.nz > Wwww.telecom.co.nz > > Level 4 - Unit 4, Telecom Centre, 49-55 Tory Street > P O Box 293, Wellington > > > > > "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." > > > > -----Original Message----- > From: Jonny Martin [mailto:jonny(a)jonnynet.net] > Sent: Thursday, 6 July 2006 12:16 p.m. > To: Steve Boyd > Cc: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] 3G/T3G VoIP slowdown > > > Anyone know about VoIP packets being slowed on either Telecom or > > Vodafones 3G networks? > > I've always had good experiences running VoIP packets over both T3G > and Vodafone's 3G network. Of course, I don't form a very large > sample. > > Telecom have in the past spent many an engineer's time on projects to > specifically bust the VoIP, however by far their most effective > weapon to date is a largely crap (pick your metric) access network. > That said, there are some quite impressive RTP/P2P busters available > if required - verso.com, amongst others. What's it called, oh yeah, > QOS :). > > As with most providers they're simply reserving the right to block/ > jumble/charge a premium for particular traffic types. Each to their > own. > > Cheers, > Jonny. > >

1 0

3G/T3G VoIP slowdown
by Steve Boyd 05 Jul '06

05 Jul '06

Hi I'm helping one of my colleages do some research for a follow up to this article on 3G VoIP being slowed: http://www.consumer.org.nz/newsitem.asp?docid=2624&category=News&topic=I SPs%20able%20to%20slow%20down%20VoIP%20services Anyone know about VoIP packets being slowed on either Telecom or Vodafones 3G networks?

3 2

Re: [nznog] Procedure for handling a new spammer
by Justin Cook 05 Jul '06

05 Jul '06

I don't really think they were doing superlarge volume at this point, just your usual commercial spammer who desperately wants to appear legitimate. Cheers though, I'll keep it in mind. TreeNet Admin wrote: > Give iconz a day or so to handle the problem. > Then if they are still there and spamming. > You may want to check all the details you can of the outfit with the > spammer database at spamhaus.org. Like with brendan battles, they may > already have a listing and certainly have the ability to negotiate > with iconz on a large scale. > > I also have a few other channels I can push the info down depending on > the nature of the spam, to get it spread around if you want to send > some of the messages (in full) to my abuse(a)treenetnz.com box. > > Amos Jeffries > > ----- Original Message ----- From: "Justin Cook" <skull(a)skull.co.nz> > To: "NZNOG" <nznog(a)list.waikato.ac.nz> > Sent: Wednesday, July 05, 2006 11:50 AM > Subject: [nznog] Procedure for handling a new spammer > > >> There's a new outfit who seem to like bulk unsolicited email. It's >> pretty annoying as they're using Iconz as well and while I'm not totally >> clear on the specifics, this can't be good for any Iconz customers like >> me who don't want to be RBLed through someone else's behaviour. >> >> I've sent the spammer a short and sharp email as well as a note to >> abuse(a)iconz, is there anything else worth doing to help stop it in its >> tracks? >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> > > > >

1 0

Re: [nznog] 3G/T3G VoIP slowdown
by Barry Murphy 05 Jul '06

05 Jul '06

Umm to my knowledge VoIP traffic is againts their terms and conditions for data calls on the T3G and vodafone. Barry > Hi I'm helping one of my colleages do some research for a follow up to > this article on 3G VoIP being slowed: > > http://www.consumer.org.nz/newsitem.asp?docid=2624&category=News&topic=I > SPs%20able%20to%20slow%20down%20VoIP%20services > > Anyone know about VoIP packets being slowed on either Telecom or > Vodafones 3G networks? > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Procedure for handling a new spammer
by Justin Cook 04 Jul '06

04 Jul '06

There's a new outfit who seem to like bulk unsolicited email. It's pretty annoying as they're using Iconz as well and while I'm not totally clear on the specifics, this can't be good for any Iconz customers like me who don't want to be RBLed through someone else's behaviour. I've sent the spammer a short and sharp email as well as a note to abuse(a)iconz, is there anything else worth doing to help stop it in its tracks?

4 5

Statistics for domain names in the .nz space.
by Dean Pemberton 03 Jul '06

03 Jul '06

Hi all. So I was thinking. It's been about 3 years now since we all banded together and voted for .geek.nz (You did all vote FOR it right?). I figured that even though there was a large takeup initially, that there would be a pretty severe dropoff over time, leaving about 6 people who actually wanted them. I asked Debbie if she could give me some stats and she pointed me at the following page. http://dnc.org.nz/story/30221-51-1.html It has statistics for all the .nz 2lds so I decided to graph them. You can see the entire spreadsheet here. http://deanpemberton.com/domainz.xls (Yes it's excel, yes I've confirmed that it opens in OpenOffice (Although the regression lines might not), no I don't want to hear any of your wingeing =) ) As a teaser, I've attached the graph for .geek.nz. You can clearly see that every year about Aug, there is a drop off as people figure they don't want their domains anymore (just after they get a bill). This dropoff is more than covered by the increase throughout the year though. So .geek.nz looks pretty strong. Much stronger than .maori.nz or .iwi.nz. There are even some 2ld's which are slowing down in their growth. Altough on the whole, the regression lines are pretty poorly fitting. Better fit models are welcome. What is interesting is that the .co.nz, .org.nz and therefore the Total can be modeled pretty well on a power curve. While it's not that much different to the linear it is food for thought. There is a possibility that these are growing faster than linear. Anyway - it was all interesting stuff and I thought you might all like to have a gander. Dean

1 0

The New Zealand Network Operators' Group
by Donald Neal 29 Jun '06

29 Jun '06

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

1 0

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

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 202.49.152.0/21^21-29, 202.36.204.0/23^23-29, 192.100.53.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

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

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060525 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

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

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060523 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

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

28 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9872 descr: advertised to AS9439 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9872 descr: advertised to AS9439 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 202.49.152.0/21^21-29, 202.36.204.0/23^23-29, 192.100.53.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)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR --- PREVIOUS OBJECT: route: 202.49.152.0/21 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.49.152.0/21 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060629 source: NZRR

1 0

Time to post something on topic for the list
by Juha Saarinen 28 Jun '06

28 Jun '06

http://www.theregister.co.uk/2006/06/28/beer_better_than_wine/ -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

2 1

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

21 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR

1 0

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

21 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.55.5.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mark.crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060622 source: NZRR

1 0

NZ regional IPs
by Steve Boyd 20 Jun '06

20 Jun '06

Hi there - we've recentely put a fairly simple broadband speedtest online at http://www.consumerspeedtest.org.nz <http://www.consumerspeedtest.org.nz/> (hosted on a VPS on www.openhost.co.nz <outbind://2/www.openhost.co.nz> which uses www.maxnet.co.nz <outbind://2/www.maxnet.co.nz> as their ISP in case you're interested) Along with the the provider, plan, download and upload speeds we're also recording the users IP address - I'm wondering if it's possible to work out what city / region the user is from based on their IP? Cheers Steve

2 1

Re: [nznog] NZ regional IPs
by Simon Allard 20 Jun '06

20 Jun '06

Depends on the ISP and how they configure their network. In IHUG's case, no, as all users terminate in Auckland on LNS's, and given IP's out of the same pool. Simon Allard Ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz _____ From: Steve Boyd [mailto:steve(a)consumer.org.nz] Sent: Wednesday, 21 June 2006 3:07 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NZ regional IPs Hi there - we've recentely put a fairly simple broadband speedtest online at http://www.consumerspeedtest.org.nz <http://www.consumerspeedtest.org.nz/> (hosted on a VPS on www.openhost.co.nz <outbind://2/www.openhost.co.nz> which uses www.maxnet.co.nz <outbind://2/www.maxnet.co.nz> as their ISP in case you're interested) Along with the the provider, plan, download and upload speeds we're also recording the users IP address - I'm wondering if it's possible to work out what city / region the user is from based on their IP? Cheers Steve

1 0

Hardware Request
by John S Russell 20 Jun '06

20 Jun '06

All: I'm currently working (personally, not with my ICONZ hat on) on a collective community network project and I find myself in need of a cisco 6000 series chassis. I'm after a WS-C6006 or 6009 (though a 6003 would also be fine, at this stage).[1] Just the chassis required, no need for a supervisor or any other modules. If anyone has upgraded to a 6500 or higher unit and has one of the older chassis hanging around, with _or without any PSU modules_, I am more than willing to exchange some (limited) cash, or beer, or fetching of coffee, or OUTRAGEOUS flattery[2] for it. I'd be willing to pick up or arrange shipping from almost anywhere in NZ or AU. If you can help, please let me know. Thanks in advance. JSR [1] If you have a spare 6500 chassis, that's a bit overkill for this project - but don't let that stop you from contacting me! [2] For example, an elaborate posting to the mailing list/blog/web forum/newsgroup of your choice detailing how your pure transcendant geek kung fu makes it seem like jets of fire shoot from your very soul and light up the lives of all around you.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jun '06

15 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 15 Jun '06

15 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 202.182.192.0/19^19-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060203 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 138.235.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060616 source: NZRR

1 0

WIC-1ADSL?
by Craig Spiers 15 Jun '06

15 Jun '06

Anyone out there got any wic-1adsl cards for 1700/2600/3600 series routers available? Cheers

1 0

Anyone from or know anyone at: Moebius Systems Ltd ...?
by Matthew Sullivan 14 Jun '06

14 Jun '06

Anyone on here responsible for: inetnum: 202.37.129.0 - 202.37.129.255 netname: MOEBIUS-NZ descr: Moebius Systems Ltd descr: Auckland country: NZ admin-c: JM113-AP tech-c: JM113-AP status: ASSIGNED PORTABLE mnt-by: APNIC-HM mnt-by: MNT-HIST-NZT-MOEBIUS-NON-NZ or anyone know this twit: Registrant Contact: SitesOnline Warwick Berg (soa(a)soa.net) +64.800943268 Fax: +64.75723129 P O Box 4556 Mt Maunganui, 3002 NZ ... he manages a server (202.37.129.44) and just spent a great amount ot time insulting me, and telling me how the message I gave him (that I recorded as spam here) didn't actually originate from his server (which must mean someone is faking my logs as well as the headers?!?!?!) and not actually doing anything about the fact his server is spewing 419 scam emails... If anyone can shed any light on the issue or the admin there, please contact me. Thanks, Matthew (BCC'd to the netblock registrant just incase it is still a live address)

5 7

Re: [nznog] Anyone from or know anyone at: Moebius Systems Ltd ...?
by Ewen McNeill 14 Jun '06

14 Jun '06

In message <1150318480.2779.3.camel(a)agree-17>, Glen Eustace writes: >On Thu, 2006-06-15 at 08:02 +1200, Justin Cook wrote: >> He's offering Squirrelmail. I've seen squirrelmail used to relay spam >> lately (some of it using my domain as the return address, grr.) [...] > >We have been a victim of this several times in the last couple of months. It's not just squirrelmail either. I have a client with a webmail system that has been abused in a similar manner to send spam. In that case it appears that the spammers have created "legitimate" webmail mailboxes, and then used some automated tool as a way of injecting their messages in bulk. They've been closing the accounts and blocking the origin IPs as they find them, but it's been a bit of a case of whack-a-mole. They're working on other measures to block the spam/spammers. I must admit being surprised that the spammers aren't content using 0wn3d Microsoft Windows boxes as there's enough of those out there (and/or waiting to be 0wn3d). But perhaps the going rate for renting them is now too high. Or maybe outbound port 25 blocking is having some effect (much as I wish it weren't necessary to resort to that). Ewen

4 3

Spam filtering
by John 14 Jun '06

14 Jun '06

Hello all. Anyone have any expereince with Postfix + Dspam + Clam AV ? How well do these work together? Cheers.

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 14 Jun '06

14 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS38037 as-name: NZRR-AS38037 descr: InternetNZ descr: WIX peering at '202.7.0.158' descr: see Citylink RT job #5932 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38037 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060615 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS38037 descr: Route set advertised to AS9439 by InternetNZ - AS38037 members: 202.46.176.0/21^21-29, 131.203.101.48/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060615 source: NZRR

1 0

ISP for IP?
by greminn＠gmail.com 14 Jun '06

14 Jun '06

Hi there, I have an ip address of 203.167.252.27, can anyone enlighten me as to which ISP this is attached too? I think its TelstraClear, and it looks to be on the end of a wireless link of some sorted (really long final trace hop)?? Thanks Simon

9 10

SORBS and Dynamic/Static listings.
by Matthew Sullivan 13 Jun '06

13 Jun '06

All, Sorry this is possibly a little off topic (it might also be on topic - depends on your view point). If anyone still has unresolved SORBS listings regarding static space listed as dynamic please to submit them to the support system - I have 56 tickets outstanding that have not been resolved - I personally have resolved over 1200 tickets in the past 3-4 days and the queues are finally back to normal (we were at 4000 outstanding tickets 2 weeks ago). For obvious reasons off list please. Regards, Mat

1 0

Re: [nznog] NZ Akamai Contacts
by James Brunskill 13 Jun '06

13 Jun '06

You can't complain about 0ms ping time though! 17 61.213.191.201 a61-213-191-201.deploy.akamaitechnologies.com 0ms :) James ________________________________________ From: Jonathan Brewer [mailto:jon.brewer(a)araneo.net.nz] Sent: Wednesday, 14 June 2006 11:00 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] NZ Akamai Contacts Hi Folks, Anyone with Akamai contacts watching NZNOG today? I'd like to help them sort out geographic locations of IP address blocks. I think our distributed content should probably not be coming from Japan via the US. :-) 1 210.48.101.113 ip-210-48-101-113.iconz.net.nz 15ms 2 210.48.49.65 f3-0-2.core1.wlg.iconz.net.nz 31ms 3 210.48.118.39 f4-0-4.core1.akl.iconz.net.nz 31ms 4 202.14.100.254 f0-0.gw2.akl.iconz.net.nz 31ms 5 210.48.1.1 f0-0-sl-br-01a.akl.iconz.net 78ms 6 203.222.35.197 sl-gw1-auk-6-0-1.sprintlink.net 78ms 7 203.222.33.22 sl-bb21-syd-1-1.sprintlink.net 94ms 8 203.222.32.49 sl-bb21-syd-14-1.sprintlink.net 109ms 9 144.232.8.130 sl-bb21-sj-3-2.sprintlink.net 250ms 10 144.232.3.210 sl-bb25-sj-12-0.sprintlink.net 265ms 11 144.232.9.240 sl-st21-sj-12-0.sprintlink.net 250ms 12 144.232.19.22 unknown 250ms 13 129.250.5.61 xe-0-1-0.r20.mlpsca01.us.bb.gin.ntt.net 250ms 14 129.250.4.42 p64-1-3-0.r20.tokyjp01.jp.bb.gin.ntt.net 297ms 15 61.213.162.238 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net 297ms 16 61.213.162.74 ge-3-0-0.a08.tokyjp01.jp.ra.gin.ntt.net 297ms 17 61.213.191.201 a61-213-191-201.deploy.akamaitechnologies.com 0ms Cheers, Jon ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 Mb: 021 345 054 http://www.araneo.net.nz/ -------------------------

1 0

NZ Akamai Contacts
by Jonathan Brewer 13 Jun '06

13 Jun '06

Hi Folks, Anyone with Akamai contacts watching NZNOG today? I'd like to help them sort out geographic locations of IP address blocks. I think our distributed content should probably not be coming from Japan via the US. :-) 1 210.48.101.113 ip-210-48-101-113.iconz.net.nz 15ms 2 210.48.49.65 f3-0-2.core1.wlg.iconz.net.nz 31ms 3 210.48.118.39 f4-0-4.core1.akl.iconz.net.nz 31ms 4 202.14.100.254 f0-0.gw2.akl.iconz.net.nz 31ms 5 210.48.1.1 f0-0-sl-br-01a.akl.iconz.net 78ms 6 203.222.35.197 sl-gw1-auk-6-0-1.sprintlink.net 78ms 7 203.222.33.22 sl-bb21-syd-1-1.sprintlink.net 94ms 8 203.222.32.49 sl-bb21-syd-14-1.sprintlink.net 109ms 9 144.232.8.130 sl-bb21-sj-3-2.sprintlink.net 250ms 10 144.232.3.210 sl-bb25-sj-12-0.sprintlink.net 265ms 11 144.232.9.240 sl-st21-sj-12-0.sprintlink.net 250ms 12 144.232.19.22 unknown 250ms 13 129.250.5.61 xe-0-1-0.r20.mlpsca01.us.bb.gin.ntt.net 250ms 14 129.250.4.42 p64-1-3-0.r20.tokyjp01.jp.bb.gin.ntt.net 297ms 15 61.213.162.238 xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net 297ms 16 61.213.162.74 ge-3-0-0.a08.tokyjp01.jp.ra.gin.ntt.net 297ms 17 61.213.191.201 a61-213-191-201.deploy.akamaitechnologies.com 0ms Cheers, Jon ------------------------- Araneo Limited 230B Left Bank 116 Cuba Street Wellington 6011 Ph: 04 978 7350 Fx: 04 978 7355 Mb: 021 345 054 http://www.araneo.net.nz/ -------------------------

3 2

Re: [nznog] Fwd: PHONE SERVICES AFFECTED BY POWER OUTAGES
by yuri 13 Jun '06

13 Jun '06

On 12/06/06, Dean Pemberton wrote: > Heh - Well I had assumed that peoples phones (cordless aside) would > still work if their power was dead. > I was also assuming that people weren't going to be calling Telecom to > see when their power was coming back on =) My phone (West Melton, Rural Canterbury near Christchurch) was dead for most of Monday. I assumed the battery in the exchange or mux box must've died. I'm not sure how long the exchange batteries last, but power was off for a long time (30+ hours). Yuri

1 0

Telstra Clear fault in Christchurch
by Don Gould 12 Jun '06

12 Jun '06

Some customer in chch on tc cable have been sent an email re changing their ip numbers (in this case my mother in law - need I say more :) because of increase in data. Is there a web page I can view that has the instructions as to what to do so I can talk her thru it. She's tried calling the hd and it's a 20 min wait currently, would prefer to just fix it for her. If there is a known other issue with network could someone please advise. Cheers Don

3 3

Re: [nznog] Telstra Clear fault in Christchurch
by Jeremy Strachan 12 Jun '06

12 Jun '06

"better" "adequate" "queue" "debate" "clever" "lose" I'm sure its only the other party that makes mistakes and not you ... -----Original Message----- From: Don Gould [mailto:don(a)bowenvale.co.nz] Sent: Tuesday, 13 June 2006 7:33 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Telstra Clear fault in Christchurch 1. I have had several answers, direct to me, thank you. 2. NOG IS AN ANSWER and if it's not then direct your comments to Telstra Clears management. If the ISP failed to (which in this case they did) provide adaquite instructions to their customer (who is paying them well over $1000 a year for services) so that they can fix their issues without contacting me then the community can expect to all hear about it. For those of you who are not Telstra Clear then I suggest you past on this note to your sales team so they understand their competition. For those of you who are Telstra Clear then I suggest you start providing your customers with beter service than a 20 minute wait in a call que for what (has been pointed out by 3 of you so far) is a very simple problem. Additionally, WHY is a simple data up grade requiring the end user to change the configuration in their router?! Finally, if anyone would like to take me on in debase about the the quality of service status pages in this industry then feel free to call me on a telephone -- that is is you can get me on 03 348 7235 (which I'm guessing you won't unless you're cleaver - because the transfer from Woosh, via Telstra Clear, to Telecom wasn't done properly and now I loose caller ID on my phone every day, causing me to phone faults and 123 to get it back, and who ever did the repatch in the exchange didn't stamp the pair down properly because the PSTN connection keeps dropping out (unless the SLIC is faulty as well?). Cheers Don Richard Patterson wrote: >Umm, did you just email the nog requesting help for your mother-in-laws >intarwebnet connection? > >*sigh* > > >Don Gould wrote: > > > >>Some customer in chch on tc cable have been sent an email re changing >>their ip numbers (in this case my mother in law - need I say more :) >>because of increase in data. >> >>Is there a web page I can view that has the instructions as to what to >>do so I can talk her thru it. >> >>She's tried calling the hd and it's a 20 min wait currently, would >>prefer to just fix it for her. >> >>If there is a known other issue with network could someone please advise. >> >>Cheers Don >> >>_______________________________________________ >>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

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

12 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS18058 as-name: NZRR-AS18058 descr: VoiceValley descr: APE peering at '192.203.154.27' descr: see Citylink RT job #5854 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS18058 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kamy(a)itsm.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060613 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS18058 descr: Route set advertised to AS9560 by VoiceValley - AS18058 members: 202.182.96.0/19^19-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kamy(a)itsm.com.au mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060613 source: NZRR

2 2

Re: [nznog] NTP
by Gordon Smith 12 Jun '06

12 Jun '06

> In the interests of making this thread go away, since it's > getting silly. > > 1) Your timezone is set to UTC. You might want to check or fix that. > 2) NTP will require 2 way communications, so your firewall > will either need to keep state, or allow 123 back into your network. > 3) If you're having issues with your firewall, tcpdump, > ethereal, and snoop are your friends. You might also want to > look at your firewall logs to figure out what traffic is > being dropped and why. Plus, of course, NTP uses UDP not TCP as a transport. Try creating a bidirectional rule allowing port 123

1 0

Re: [nznog] [SPAM] Re: NTP
by John 11 Jun '06

11 Jun '06

So the machine X can reach the NTP server @ massey uni for example. Default outbound = deny. > Why Outbound? > > -----Original Message----- > From: John [mailto:john(a)nettrust.net.nz] > Sent: Tuesday, 13 June 2006 3:24 a.m. > To: jfp; nznog(a)list.waikato.ac.nz > Subject: [SPAM] Re: [nznog] NTP > Importance: Low > > Ok- > > It appears that allowing outbound UDP to port 123 doesn't cut it past > the firewall. > > Does anyone have any ideas please? > > > > Is NTP still available on ntp.massey.ac.nz and > > > ntp.public.otago.ac.nz ? > > > > They work for me, here's the ones I use including contact emails. > > > > server ntp.massey.ac.nz # ntp(a)massey.ac.nz server > > ntp.public.otago.ac.nz # ntp(a)otago.ac.nz server tk1.ihug.co.nz # > > ntp(a)staff.ihug.co.nz server tk2.ihug.co.nz # ntp(a)staff.ihug.co.nz > > > > > > jfp. > > ------------------------------------------------------------------------ > > > Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software > > Engineer > > > Phone (+64-9) 358 2081 Clearfield Software > > Ltd > > > Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker > > Place > > > Mob (+64-21) 640 779 P O Box 3901 Auckland, New > > Zealand > > > ---------------------------------------------------------------------- > > -- > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] NTP
by John 11 Jun '06

11 Jun '06

Different computer and that problem is not resolved because other software reports the correct time. Also NTP uses ports 123 UDP and TCP right ? > NTP won't help with you picking the wrong time zone on your computer. > > John wrote: > > Hello all. > > > > Is NTP still available on ntp.massey.ac.nz and ntp.public.otago.ac.nz ? > > > > Cheers. > > J. > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

NTP
by John 11 Jun '06

11 Jun '06

Hello all. Is NTP still available on ntp.massey.ac.nz and ntp.public.otago.ac.nz ? Cheers. J.

2 1

Anyone know why power is down?
by Barry Murphy 11 Jun '06

11 Jun '06

Looks to be auckland CBD, hamilton and my partner cant get any radio signal.. Barry

16 21

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

11 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64598 descr: advertised to AS9439 by Araneo - AS64598 members: 210.48.109.104/29, 210.48.109.112/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64598 descr: advertised to AS9439 by Araneo Limited - AS64598 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR

1 0

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

11 Jun '06

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo - AS64597 members: 202.53.189.128/29, 210.48.101.64/27^27-29, 210.48.101.112/28^28-29, 210.48.109.224/27^27-29, 202.174.161.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: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041209 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo Limited - AS64597 members: 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 210.48.101.112/28^28-29, 210.48.101.240/28^28-29, 202.53.189.128/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR --- PREVIOUS OBJECT: route: 210.48.101.64/27 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route: 210.48.101.64/27 descr: Route for Araneo Limited - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR --- PREVIOUS OBJECT: route: 210.48.109.224/27 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route: 210.48.109.224/27 descr: Route for Araneo Limited - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR --- PREVIOUS OBJECT: route: 202.53.189.128/29 descr: Route for Araneo - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jon.brewer(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041028 source: NZRR REPLACED BY: route: 202.53.189.128/29 descr: Route for Araneo Limited - AS64597 origin: AS64597 notify: rpsl-admin(a)nzix.net notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR

1 0

Re: [nznog] NTP
by John 11 Jun '06

11 Jun '06

Ok- It appears that allowing outbound UDP to port 123 doesn't cut it past the firewall. Does anyone have any ideas please? > > Is NTP still available on ntp.massey.ac.nz and > > ntp.public.otago.ac.nz ? > > They work for me, here's the ones I use including contact emails. > > server ntp.massey.ac.nz # ntp(a)massey.ac.nz > server ntp.public.otago.ac.nz # ntp(a)otago.ac.nz > server tk1.ihug.co.nz # ntp(a)staff.ihug.co.nz > server tk2.ihug.co.nz # ntp(a)staff.ihug.co.nz > > > jfp. > > ------------------------------------------------------------------------ > Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer > Phone (+64-9) 358 2081 Clearfield Software Ltd > Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place > Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand > ------------------------------------------------------------------------

2 1

Re: [nznog] Anyone know why power is down?
by Jeremy Strachan 11 Jun '06

11 Jun '06

I'm no weather forecaster, but it looks like the South Island and the lower half of the North Island are going to get hammered tonight. Not a good time to be on a boat anywhere ... or on land ... Jeremy

2 1

Re: [nznog] NTP
by John 11 Jun '06

11 Jun '06

> on 13/06/2006 3:23 AM John wrote: > > Ok- > > > > It appears that allowing outbound UDP to port 123 doesn't cut it past the > > firewall. > > > > Does anyone have any ideas please? > > Buy a watch? I already have one - a Casio G-stock.

2 1

Re: [nznog] Jobs... (semi-operational)
by Criggie 11 Jun '06

11 Jun '06

Scott Walsh wrote: > Putting together a new NOC style team in Wellington Good Morning - Are there any plans for a similar structure in Christchurch? I've been a multi-talented network admin at Avonside Girls' High for the last 7 1/2 years, where I have taken the network from about 70 machines to a site-wide network of 300 machines and 10 servers. But I'm looking to move onwards and upwards. I've got a B.Sc in computer science, and a bunch of other qualifications as well as old-fashioned common sense. (hows that for a three-sentance CV summary?) -- Criggie http://criggie.dyndns.org/ http://www.avonside.school.nz/

1 1

Re: [nznog] Anyone know why power is down?
by Philip D'Ath 11 Jun '06

11 Jun '06

They don't run diverse fibre. So a primary fibre failure wipes out their network. BCL is used for redundancy, but BCL doesn't have anywhere enough capacity to carry the capacity being used on the fibre. As a result, a fibre break will result in a large loss of service. I think it will be 2 to 5 years before sufficient fibre has been built to give stable redundant access. -----Original Message----- From: Drew Whittle [mailto:drew(a)earthlight.co.nz] Sent: Monday, 12 June 2006 10:28 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Anyone know why power is down? Erin Salmon - Unleash wrote: > He's right. One of the three has all but given up their own infrastructure > and uses BCL instead. Rats love fibre... > > So from that your saying that either Telecom or TelstraClear no longer run their own fibre up Country? Thats news to me, and of course which one?? _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Fwd: PHONE SERVICES AFFECTED BY POWER OUTAGES
by Ian McDonald 11 Jun '06

11 Jun '06

---------- Forwarded message ---------- From: media(a)telecom-media.co.nz <media(a)telecom-media.co.nz> Date: Jun 12, 2006 10:47 AM Subject: PHONE SERVICES AFFECTED BY POWER OUTAGES To: ian.mcdonald(a)jandi.co.nz PHONE SERVICES AFFECTED BY POWER OUTAGES Telecom customers may be having problems accessing phone, Internet and data services in parts of Auckland due to a significant power outage in Auckland and Manukau City areas and some other parts of the country. The Telecom network currently has no power issues and all systems including Telecom Call Centres are operating on back-up generator and battery systems. Customers should be aware that if they are having problems accessing Telecom services, the problems are likely to be related to power outages, Telecom spokesperson John Goulter said today. Call centres are receiving a lot of calls, and Telecom is urging customers to listen to media updates on the power outages. We understand the main problem relates to a power substation at Otahuhu in Auckland, caused by the high winds and stormy weather sweeping the country. North Shore and Waitakere cities are unaffected. Power outages have also been affecting phone services in Northland, Asburton and Timaru. ENDS For more information please contact: Sarah Berry Media Relations Executive 04 498 9481 027 470 7900 sarah.berry(a)telecom.co.nz This message was sent to you because your email address is on the Telecom media releases mailing list. To be removed from this mailing list please visit http://www.telecom-media.co.nz/lists/?id=1171&e=ia IMPORTANT: Security is limited with current Internet email technology. If you have doubts about the contents or source of this message, please verify that this release comes from Telecom New Zealand by checking the Telecom website at: http://www.telecom-media.co.nz/releases.asp -- Ian McDonald Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group Department of Computer Science University of Waikato New Zealand

4 4

Radio NZ Podcasts - Heads Up
by Webmaster 11 Jun '06

11 Jun '06

>From today we are offering some of our daily programmes as podcasts. These include Nine To Noon, Afternoons, and Nights. These are very popular programmes, and operators who do not peer with us in NZ may see an increase in traffic on their international circuits. Those operators may also see an increase in help desk calls as we are starting to get complaints about poor download rates at peak times. Our US server is well within capacity at these times, so we are referring complainants back to their own ISPs. As always, we are happy to provide this content locally to anyone that wants it via either WIX, APE, or PNIX. We do not charge for this service. If you prefer a direct connection to our servers this can be arranged, however there will be a cost. regards, Richard Hulse Radio NZ

1 0

Re: [nznog] Anyone know why power is down?
by Philip D'Ath 11 Jun '06

11 Jun '06

I know at least one of those major players doesn't use satellite out of Dunedin, and they use BCL for their backup already. I think you'll find there is two ways out, at best. -----Original Message----- From: Drew Whittle [mailto:drew(a)earthlight.co.nz] Sent: Monday, 12 June 2006 9:46 a.m. To: tony(a)prophecy.net.nz Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Anyone know why power is down? Tony Wicks wrote: > haha... you do know what a thin and venerable set of fibers connects > Dunedin to the rest of the country then ? > There are at least 4 ways out of Dunedin that I can think of: Satellite, Telecom,TelstraClear, BCL.

4 5

Re: [nznog] Telecom BRI
by Sam Banks 11 Jun '06

11 Jun '06

Cheers, I thought the same about the tx and rx gain but the option is there? On 6/12/06, Philip D'Ath <pid(a)ifm.net.nz> wrote: > > If it is a Cisco router, you want: > > > > isdn switch-type basic-net3 > > > > interface BRI0/0/0 > > no ip address > > isdn switch-type basic-net3 > > isdn point-to-point-setup > > isdn incoming-voice voice (if your using it for voice) > > > > And if being used for voice: > > > > voice-port 0/0/0 > > compand-type a-law > > cptone NZ > > > > > > Point to multipopint, but you can happily define a static tei. I > sometimes use a static tei of 10. TE,. TX and RX gain don't make much > sense, since it is a digital circuit. > > > ------------------------------ > > *From:* Sam Banks [mailto:dodgywhitemaori(a)gmail.com] > *Sent:* Monday, 12 June 2006 8:17 a.m. > > *To:* nznog(a)list.waikato.ac.nz > *Subject:* Re: [nznog] Telecom BRI > > > > Thanks > > On 6/10/06, *Matt Mariu* <Matt.Mariu(a)secure24.ihost.com> wrote: > > Definitly Point to multipoint. > > > > > > -----Original Message----- > *From:* Sam Banks [mailto:dodgywhitemaori(a)gmail.com] > *Sent:* Wednesday, 7 June 2006 10:30 > *To:* nznog(a)list.waikato.ac.nz > *Subject:* [nznog] Telecom BRI > > Hi Guys > > Does anyone know the default settings for Telecom BRI ISDN lines. > Point to multipoint or Point to point? > TE or NT? > TX and RX gain? > > Thanks > > Sam > > -- > A good friend will help you move, a really good friend will help you move > a body. > > > > > -- > A good friend will help you move, a really good friend will help you move > a body. > -- A good friend will help you move, a really good friend will help you move a body.

1 0

Re: [nznog] Anyone know why power is down?
by Matt Mariu 11 Jun '06

11 Jun '06

A Substation feeder cable melted(?) in Otahuhu knocked out pretty much all of Auckland and Parts of Waikato... Hows your DR plan working out now ? ;] - Matt -----Original Message----- From: Barry Murphy [mailto:barry(a)unix.co.nz] Sent: Monday, 12 June 2006 08:59 To: nznog(a)list.waikato.ac.nz Subject: [nznog] Anyone know why power is down? Looks to be auckland CBD, hamilton and my partner cant get any radio signal.. Barry _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0