September 2009 - NZNOG - lists.nznog.org

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 07 Sep '09

07 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

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

03 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: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090408 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 112.109.64.0/20^20-29, 114.134.160.0/20^20-29, 119.47.112.0/20^20-29, 112.109.80.0/21^21-29, 114.134.176.0/21^21-29, 124.150.160.0/21^21-29, 202.189.160.0/21^21-29, 113.197.64.0/22^22-29, 122.102.108.0/22^22-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/23^23-29, 202.49.88.0/23^23-29, 203.84.134.0/23^23-29, 210.54.142.0/23^23-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.37.232.0/24^24-29, 202.46.187.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 205.233.243.0/24^24-29, 210.54.13.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090904 source: NZRR ------------------------------------------------------------

1 0

The New Zealand Network Operators' Group
by Donald Neal 03 Sep '09

03 Sep '09

The New Zealand Network Operators' Group The NZNOG mailing list exists 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. That policy appears later in this posting. The NZNOG Trust is registered as a charitable entity under the Charities Act. The trust exists to provide the legal framework needed to do jobs like operating the bank account which holds the money which allows our annual conferences to happen. Other than the trustees, the NZNOG does not have a formal membership. Conference NZNOG holds New Zealand's only annual technical networking conference. The next conference is scheduled to be held on 27-29 January 2010 in Hamilton, hosted by The University of Waikato's WAND research group. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.nznog.org/?page_id=6 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. About This Mailing List This list has around 1000 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 APN Online, Citylink, and The University of Waikato. 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 -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

Re: [nznog] NZ prefix list
by Richard Hulse 02 Sep '09

02 Sep '09

>>> Matthew Moyle-Croft <mmc(a)internode.com.au> 3/09/2009 15:36:41 >>> > We'll be rich. > (Don't fall into the mistake of taking me seriously here). Someone will... Time for beer.

1 0

NZ prefix list
by Donald Gordon 02 Sep '09

02 Sep '09

Hi I'm in need of a view of what IP prefixes are local to NZ (ideally, what FX considers domestic, but I'm not too picky) for a personal project. My upstream can't provide me with a BGP feed, alas. Is there anyone here who could provide me with a multihop BGP view of their domestic routing table, or a looking glass I could screen-scrape? thanks (and beer?) in advance donald

6 6