- NZNOG - lists.nznog.org

DoS against TCL last night
by David Robb 15 Sep '09

15 Sep '09

Hi all, In case anyone noticed/was wondering why things were running a bit slowly through TCL last night, we were receiving somewhere >1Gbit of DoS traffic (mostly large TCP, random ports) across a couple of links which got a bit saturated. As soon as it was brought to the network team's attention, the target (a poor DSL customer, I don't think DSL supports 1Gbit yet!) was null routed. --David Robb

3 3

NEWS: Government broadband proposal announced
by Matthew Poole 15 Sep '09

15 Sep '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dark fibre features heavily, no government investment in fibre companies that have a shareholder that has retail telecomm's operations, and various other goodness. The central/local holding companies model will be followed. http://computerworld.co.nz/news.nsf/netw/B9DE9FBAF33A6A1ACC257632007699A6 Looks like a pretty good result, all things considered. - -- Matthew Poole "Don't use force. Get a bigger hammer." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkqwGvsACgkQTdEtTmUCdpwv4gCdHNIzzIu9V9MzR75nRXB4tFqc /m8AnR/eoIBosjEgY4FWaLUv3cRnW8Ls =WmUm -----END PGP SIGNATURE-----

1 0

IPv6 Deployment Monitoring Survey
by Elly Tawhai 14 Sep '09

14 Sep '09

Hi there! APNIC is now conducting our "IPv6 Deployment Monitoring Survey". It'd be great if you could spend about 15 minutes to complete the survey. The survey closes on 28 September 2009. Survey results will be presented at RIPE59 in October 2009. We will also publish the survey analysis and results as soon as they become available on the APNIC website. We also intend to present it at APNIC 29 in February 2010. Let's find out about the global status of IPv6 deployment! Please visit: http://www.surveymonkey.com/s.aspx?sm=YahORYFZHoqKo2Kc8R1R4Q_3d_3d Apologies if you have received more than one copy of this email. Thank you! Kind regards, Elly ------------------------------------------------------------------------ Elly Tawhai email: elly(a)apnic.net Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188 http://www.apnic.net fax: +61 7 3858 3199 ------------------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Sep '09

10 Sep '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.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.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.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.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090826 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 130.123.0.0/16^16-29, 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 121.79.192.0/19^19-29, 202.154.128.0/19^19-29, 112.109.64.0/20^20-29, 119.47.112.0/20^20-29, 124.248.128.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.86.96.0/20^20-29, 202.191.32.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 203.96.128.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 202.27.192.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 113.59.224.0/22^22-29, 202.27.200.0/22^22-29, 202.27.212.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.37.48.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 122.248.172.0/23^23-29, 202.14.32.0/23^23-29, 202.27.136.0/23^23-29, 202.27.210.0/23^23-29, 202.36.68.0/23^23-29, 202.36.204.0/23^23-29, 202.37.70.0/23^23-29, 202.169.194.0/23^23-29, 202.169.198.0/23^23-29, 202.175.142.0/23^23-29, 203.84.134.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.17.0/24^24-29, 192.173.18.0/24^24-29, 192.173.20.0/24^24-29, 192.195.219.0/24^24-29, 192.203.216.0/24^24-29, 202.8.13.0/24^24-29, 202.12.0.0/24^24-29, 202.12.91.0/24^24-29, 202.12.105.0/24^24-29, 202.14.45.0/24^24-29, 202.14.63.0/24^24-29, 202.14.102.0/24^24-29, 202.20.65.0/24^24-29, 202.20.92.0/24^24-29, 202.20.97.0/24^24-29, 202.21.157.0/24^24-29, 202.27.77.0/24^24-29, 202.27.83.0/24^24-29, 202.27.160.0/24^24-29, 202.27.209.0/24^24-29, 202.27.222.0/24^24-29, 202.27.236.0/24^24-29, 202.27.247.0/24^24-29, 202.27.251.0/24^24-29, 202.36.12.0/24^24-29, 202.36.29.0/24^24-29, 202.36.33.0/24^24-29, 202.36.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.198.0/24^24-29, 202.36.218.0/24^24-29, 202.37.68.0/24^24-29, 202.37.117.0/24^24-29, 202.37.118.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.37.254.0/24^24-29, 202.46.176.0/24^24-29, 202.46.183.0/24^24-29, 202.46.188.0/24^24-29, 202.46.190.0/24^24-29, 202.49.5.0/24^24-29, 202.49.6.0/24^24-29, 202.49.106.0/24^24-29, 202.49.141.0/24^24-29, 202.49.144.0/24^24-29, 202.49.159.0/24^24-29, 202.49.183.0/24^24-29, 202.49.189.0/24^24-29, 202.50.95.0/24^24-29, 202.50.240.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.89.57.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.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.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.169.193.0/24^24-29, 202.169.196.0/24^24-29, 202.169.206.0/24^24-29, 202.169.212.0/24^24-29, 202.169.223.0/24^24-29, 203.89.178.0/24^24-29, 203.89.181.0/24^24-29, 203.89.187.0/24^24-29, 203.92.25.0/24^24-29, 203.96.119.0/24^24-29, 203.163.68.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.7.46.0/24^24-29, 219.88.230.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: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090911 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 10 Sep '09

10 Sep '09

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by Citylink - AS23755 members: 202.7.4.0/22^22-29, 202.8.44.208/28^28-29, 202.8.47.64/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: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080804 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23755 descr: advertised to AS9439 by StreamingNET - AS23755 members: 202.7.4.0/22^22-29, 192.33.14.0/24^24-29, 192.58.128.0/24^24-29, 202.8.44.208/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: dylan(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090911 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] Orcon Network Speeds
by andrew＠borg.co.nz 08 Sep '09

08 Sep '09

Neil: We have only seen this issue with out own link but are now getting reports from others stating they have been having similar issues for the past couple of months. Brett: Apparently we are really close to the cabinet, I am not sure but suspect it is the one about 150M down the road. Mode: G.DMT Type: Interleave Line Coding: Trellis On Status: No Defect Link Power State: L0 Downstream Upstream SNR Margin (dB): 14.4 12.0 Attenuation (dB): 4.0 3.0 Output Power (dBm): 7.8 11.9 Attainable Rate (Kbps): 9184 936 Rate (Kbps): 7616 768 K (number of bytes in DMT frame): 239 25 R (number of check bytes in RS code word): 16 16 S (RS code word size in DMT frame): 1 8 D (interleaver depth): 64 8 Delay (msec): 16 16 Super Frames: 105395061 105395059 Super Frame Errors: 2 110 RS Words: 2871896918 358987089 RS Correctable Errors: 764 170 RS Uncorrectable Errors: 28 N/A HEC Errors: 2 110 OCD Errors: 0 0 LCD Errors: 0 0 Total Cells: 2118506566 0 Data Cells: 862336822 0 Bit Errors: 0 0 Total ES: 1 0 Total SES: 0 0 Total UAS: 16 0

20 20

Re: [nznog] ADMIN: Re: Orcon Network Speeds
by Farhan Sattar 08 Sep '09

08 Sep '09

On 9/09/2009 10:37 a.m., Andy Linton wrote: > You're all clearly asking 'cat' to do things it wasn't designed for - > see: > > http://harmful.cat-v.org/cat-v/unix_prog_design.pdf Maybe we need a few pigeons among the cats...help reduce international bandwidth costs http://www.faqs.org/rfcs/rfc1149.html Farhan Sattar NZNet - business grade internet services Tel +64 9 280 4876 | Mobile +64 21 1266500 | Fax +64 9 914 0040 C1-5 Douglas Alexander Pde, Albany, PO Box 101-069 NSMC, Auckland, NZ Visit us at www.nznet.co.nz

1 0

Block of AS Numbers allocated to APNIC
by Leo Vegoda 08 Sep '09

08 Sep '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA AS Numbers registry has been updated to reflect the allocation of a block of AS Numbers to APNIC. 55296-56319 Assigned by APNIC whois.apnic.net 2009-09-02 The registry can be found at: http://www.iana.org/assignments/as-numbers/as-numbers.xml http://www.iana.org/assignments/as-numbers/as-numbers.xhtml http://www.iana.org/assignments/as-numbers/as-numbers.txt Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj4DBQFKpohJvBLymJnAzRwRAncHAJiRWENmmK+qwpvAZIaPrs/urIa/AJ9f1A05 PM9TJWxzbAxpSiXyIgzvfA== =MGZ2 -----END PGP SIGNATURE-----

1 0

Orcon Network Speeds
by andrew＠borg.co.nz 07 Sep '09

07 Sep '09

For the last 3 months or so we have been having issues with Orcon's DSL network and as Orcon have chosen not to bother communicating over this issue and ignoring requests to resolve this matter in a timely manner I would like to know if there are any others who are having similar issues or can throw some light on to what the problem may be. Firstly around 7PM most nights up until 10PM our DSL started dropping 50% of its packets and any extern web services became unusable. We were prompted by Orcon to reset our router and did so but the issue persisted. They then suggested it was the router so we replace this with a new one and still the problem persisted. Using the new router we were able to ping the Orcon DNS server but still getting the packet loss. Orcon then turned off Interleave and the problem was still not resolved however apparently the issue was handed up to Telecom and eventually after about 2 months there was an improvement and the packet loss seems to no longer be an issue. However during these times the speeds have dropped to a level where some services are almost unusable, we have a server on a fiber tail connected to APE and from the DSL speeds to that server and any adjacent server seem to drop out or are reduced to a point where they are unusable. We seem to also be having issues with VoIP service where as what appears to be a micro outage drops calls intermittently doe no reason and the same goes for some RDP sessions. We are nearing month 4 and the issue persists and there has been little communications from Orcon as to how the issue is to be resolved other than the comment that Internet service is not a guaranteed service. Any suggestions would be welcomed as I would like to resolve this one way or another. Regards Andrew Hooper.

3 2

Re: [nznog] Orcon Network Speeds
by andrew＠borg.co.nz 07 Sep '09

07 Sep '09

Thanks for the responses. Ticket numbers are as follows. FPI-934198 PDT-333835 BVP-710368 KGL-788789 I have not over the last few days to conduct some tests while the issue is visible however these are a couple from a few days ago as well as a previous one. (Attached at end of email) Changing providers is all fine and dandy BUT if the issue is with the scalability of the infrastructure or the owner of the infrastructure then this is not likely to resolve anything I believe that in this instance Telecom is the owner of the DSL infrastructure. AFAIK we are on the normal DSL network and not on the Orcon+ network Although I partly agree that this may not be the forum to bring such a matter to light the fact is that it is not a residential service it is a business service I pay for and use it as a management port to the rest of the network. Criggie: I am starting to get the feeling that DSL is really not a scalable solution. May just have to crawl back in my hole and stick with my wireless world. Tracing route to ***.***.***.177 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.254 2 1 ms 1 ms 1 ms 192.168.90.253 3 125 ms 50 ms 48 ms lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 47 ms 49 ms 79 ms 121.98.9.21 5 48 ms 49 ms 50 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13] 6 49 ms 49 ms 49 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10] 7 49 ms 50 ms 48 ms gigabit.fx1.ape.net.nz [192.203.154.115] 8 47 ms 49 ms 51 ms ***.***.***.177 Tracing route to ***.***.***.190 over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 <1 ms 1 ms <1 ms 192.168.90.253 3 47 ms 49 ms 50 ms lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 49 ms 50 ms 48 ms 121.98.9.21 5 49 ms 48 ms 52 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13] 6 49 ms 49 ms 49 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10] 7 143 ms 641 ms 600 ms gigabit.fx1.ape.net.nz [192.203.154.115] 8 53 ms 50 ms 49 ms bushwireless.fx.net.nz [131.203.253.78] 9 60 ms 54 ms 59 ms ***.***.***.190 Tracing route to ns1.orcon.net.nz [210.55.12.1]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.254 2 1 ms <1 ms 1 ms 192.168.90.253 3 62 ms * * lo1.erx2.nct.orcon.net.nz [60.234.8.18] 4 62 ms 60 ms * 121.98.9.21 5 * * * Request timed out. 6 62 ms 60 ms * ns1.orcon.net.nz [210.55.12.1] 7 62 ms 60 ms 59 ms ns1.orcon.net.nz [210.55.12.1] Pinging 210.55.12.1 with 32 bytes of data: Request timed out. Request timed out. Reply from 210.55.12.1: bytes=32 time=61ms TTL=59 Reply from 210.55.12.1: bytes=32 time=60ms TTL=59 Ping statistics for 210.55.12.1: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 61ms, Average = 60ms

2 1