- NZNOG - lists.nznog.org

traffic shaping
by Jodi 14 Mar '12

14 Mar '12

Hi All Currently we're running a couple of Packeteers (one for each of our upstreams) to give users a fair slice of the pie. However they're starting to wilt under the increased load and it's time to look at replacing. I've been looking around at some of the more popular appliances that I am aware of (Packeteer, Exinda, Netequalizer), however I don't want to buy a lemon. The other thought was to shape directly on the routers - have a couple of Cisco 2821's at our borders. I'm familiar with the shaping process but have never attempted on Cisco kit before so don't want to start down that path if it's the wrong way to go (especially as I would be the only one who could manage it and I like the occasional day off). My main focus to is to shape at the border by IP for different classes based on our plans e.g. burst to 4meg, 2meg dedicated, 2.5 burst to 10, etc Secondary to that is reporting and 3rdly QoS Any and all advice welcome, on and off list Cheers Jodi -- Jodi Thomson Network & Systems Engineer [Description: Description: Wasp New Zealand] Ph +64-6-8355800 Fax +64-6-8355811 Mob +64-21-903712 E-Mail jodi(a)team.waspnet.co.nz www.waspnet.co.nz<http://www.waspnet.co.nz/>

9 17

NZRR Route Registry Update
by NZRR Database Notifications 13 Mar '12

13 Mar '12

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: 124.248.128.0/20^20-29, 103.5.80.0/22^22-29, 202.27.216.0/22^22-29, 202.36.192.0/22^22-29, 202.169.192.0/22^22-29, 210.79.48.0/22^22-29, 32.114.24.0/23^23-29, 32.234.80.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.27.136.0/23^23-29, 202.36.68.0/23^23-29, 202.37.70.0/23^23-29, 202.169.198.0/23^23-29, 202.169.202.0/23^23-29, 202.169.206.0/23^23-29, 202.169.212.0/23^23-29, 202.175.142.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.190.0/24^24-29, 192.203.216.0/24^24-29, 194.196.251.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.20.92.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.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.43.0/24^24-29, 202.36.75.0/24^24-29, 202.36.80.0/24^24-29, 202.36.154.0/24^24-29, 202.36.198.0/24^24-29, 202.37.68.0/24^24-29, 202.37.167.0/24^24-29, 202.37.168.0/24^24-29, 202.37.187.0/24^24-29, 202.37.254.0/24^24-29, 202.49.189.0/24^24-29, 202.49.216.0/24^24-29, 202.50.240.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.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.196.0/24^24-29, 202.169.201.0/24^24-29, 202.169.205.0/24^24-29, 202.169.209.0/24^24-29, 202.169.223.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 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 20111213 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.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, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.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.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.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, 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 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 20120314 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] [Fwd: [OPSAWG]draft-weil-shared-transition-space-request]
by Scott Weeks 13 Mar '12

13 Mar '12

----- brian.e.carpenter(a)gmail.com wrote: ------ From: Brian E Carpenter <brian.e.carpenter(a)gmail.com> In other words, 100.64.0.0/10 is now legalised bogon space and needs to be filtered just like RFC 1918 space. --------------------------------------------------- ------------------- Original Message ------------- Subject: [OPSAWG] raft-weil-shared-transition-space-request/ From: Bradner, Scott <sob(a)harvard.edu> fyi - the address block has been registered see http://whois.arin.net/rest/net/NET-100-64-0-0-1/pft ---------------------------------------------------- I guess this means the "final bogon list" RFC (or whatever the correct name is; I couldn't find it) needs to be updated. scott ----------------------- ------------------ -------------------

2 1

[Fwd: [OPSAWG]draft-weil-shared-transition-space-request]
by Brian E Carpenter 13 Mar '12

13 Mar '12

In other words, 100.64.0.0/10 is now legalised bogon space and needs to be filtered just like RFC 1918 space. Brian (please do not shoot messenger) -------- Original Message -------- Subject: [OPSAWG] raft-weil-shared-transition-space-request/ Date: Wed, 14 Mar 2012 00:38:33 +0000 From: Bradner, Scott <sob(a)harvard.edu> To: opsawg(a)ietf.org <opsawg(a)ietf.org> fyi - the address block has been registered see http://whois.arin.net/rest/net/NET-100-64-0-0-1/pft thanks to all who worked so hard on this Scott _______________________________________________ OPSAWG mailing list OPSAWG(a)ietf.org https://www.ietf.org/mailman/listinfo/opsawg -- Regards Brian Carpenter

1 0

Async Routing across ape to pipe return via vocus & Internode speedtest
by Barry Murphy 12 Mar '12

12 Mar '12

Hey Guys, I just saw Glen Eustace's post which reminded me of an issue we have seen of late with regards to 'my internet seems slow'. Just wondering if anyone else has seen this similar issue since PIPE joined the APE, then again it's not just PIPE, but a mixture of Oz providers accepting traffic over the APE and then returning the transit via international links such as Vocus. I have a few customers that buy dedicated international and dedicated domestic bandwidth. These customers have a stub address that resides in the Domestic VRF & another stub in the International VRF. Since PIPE came on-board we have noticed that customers trying to do a whois (whois.apnic.net) using their router that connects the stubs, that the traffic goes out thinking its Domestic, but then gets no response because it attempts to return in via the International (Transit) VRF to which has no access to stubs in the Domestic VRF. Another issue we see where 'slow' comes into play is internode have recently been added to speedtest.net as a NZ speedtest server in Auckland. While tracing to this node it does appear to go across APE, the return path is via Vocus. When a customer attempts a speed test and they see they are only able to obtain say 30mbps rather than the 100mbps they would expect from a "NZ" server they start thinking something is broken, when actually it's because the server is International and they are in a pool of bandwidth. I've tried to contact internode & so has a colleague of mine but with no luck. We've tried to pre-pend AS's to the vocus communities but again this hasnt helped at all. Just wondering if anyone else has seen issues arise since ASYNC routing between Oz & NZ, to do with either STUBs getting no internet due to VRF nature, or these 'slow' speeds being reported. thanks Barry

10 21

Re: [nznog] traffic shaping
by Liam Farr 12 Mar '12

12 Mar '12

Forgot the reply all... ---- Liam Farr +64-22-6107884 +64-27-5222624 Sent using my BlackBerry -----Original Message----- From: "Liam Farr" <liamfarr(a)me.com> Date: Tue, 13 Mar 2012 01:58:48 To: Jonathan Brewer<jon.brewer(a)gmail.com> Reply-To: liamfarr(a)me.com Subject: Re: [nznog] traffic shaping I have a couple of said junipers and a dual core 1ghz android. The juniper is fine in production for hundreds of mbits and many users (even the bittorrenting ones) if you disable all the connection tracking and firewalling. The smartphone on the other hand is the biggest price of shit ever shipped. YMMV. Cheers ---- Liam Farr +64-22-6107884 +64-27-5222624 Sent using my BlackBerry -----Original Message----- From: Jonathan Brewer <jon.brewer(a)gmail.com> Sender: nznog-bounces(a)list.waikato.ac.nzDate: Tue, 13 Mar 2012 14:40:20 To: <nznog(a)list.waikato.ac.nz> Subject: Re: [nznog] traffic shaping _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 2

Re: [nznog] traffic shaping
by Jodi 10 Mar '12

10 Mar '12

Yep intend to collate results and flick them through once i've got my head around it all :) Sent from Samsung Mobile jamie baddeley <jamie.baddeley(a)vpc.co.nz> wrote: I'm sure the list would appreciate some distillation of that feedback. Once the weekend is over of course :-) Cheers Jamie On 9/03/2012, at 4:44 PM, Jodi <jodi(a)team.waspnet.co.nz<mailto:jodi(a)team.waspnet.co.nz>> wrote: Thanks to all who sent advice and recommendations. Time for some ‘light’ reading over the weekend Hope you all enjoy yours ☺ Kind Regards Jodi From: nznog-bounces(a)list.waikato.ac.nz<mailto:nznog-bounces(a)list.waikato.ac.nz> [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Jodi Sent: Thursday, 8 March 2012 4:38 p.m. To:

1 0

DKIM Š.
by Craig Whitmore 08 Mar '12

08 Mar '12

I just recently started checking DKIM on a mail server and I've noticed it is rejecting a number of emails including one particular persons posts on the NZNOG mailing list because of DKIM. In this particular case this is because they are using their domain on gmail and gmail signs its messages with DKIM and the message is going thu the list. As the NZNOG mailing list changes the subject and other things in the header it invalidates the DKIM signature (and the signature says certain things shouldn't change) So.. Ideas? Looking on the internet it says the mailing list can strip out the DKIM headers thus it won't be checked when resent and/or better re-sign (if possible) the message at the mailing list level when resent out. (from mailman) # Some list posts and mail to the -owner address may contain DomainKey or # DomainKeys Identified Mail (DKIM) signature headers <http://www.dkim.org/>. # Various list transformations to the message such as adding a list header or # footer or scrubbing attachments or even reply-to munging can break these # signatures. It is generally felt that these signatures have value, even if # broken and even if the outgoing message is resigned. However, some sites # may wish to remove these headers by setting this to Yes. REMOVE_DKIM_HEADERS = Yes Ideas? Thoughts? Craig..

2 1

NZRR Route Registry Update
by NZRR Database Notifications 07 Mar '12

07 Mar '12

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:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/19^19-29, 202.27.78.0/23^23-29, 202.37.218.0/23^23-29, 218.101.2.0/23^23-29, 103.4.121.0/24^24-29, 103.247.247.0/24^24-29, 202.36.47.0/24^24-29, 202.36.162.0/24^24-29, 202.50.109.0/24^24-29, 202.70.130.0/24^24-29, 203.97.152.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120216 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/19^19-29, 103.11.240.0/22^22-29, 202.27.78.0/23^23-29, 202.37.218.0/23^23-29, 218.101.2.0/23^23-29, 103.4.121.0/24^24-29, 103.247.247.0/24^24-29, 202.36.47.0/24^24-29, 202.36.162.0/24^24-29, 202.50.109.0/24^24-29, 202.70.130.0/24^24-29, 203.97.152.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dion.hallam(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120308 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Mar '12

07 Mar '12

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: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.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.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.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.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.37.17.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.89.57.0/24^24-29, 202.129.253.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, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 202.89.43.0/25^25-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 20120220 source: NZRR REPLACED BY: route-set: AS9281:RS-ROUTES:AS9503 descr: advertised to AS9281 by FX Networks - AS9503 members: 130.123.0.0/16^16-29, 130.217.0.0/16^16-29, 131.203.0.0/16^16-29, 139.80.0.0/16^16-29, 150.206.0.0/16^16-29, 156.59.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 161.66.0.0/16^16-29, 166.65.0.0/16^16-29, 116.251.128.0/18^18-29, 121.79.192.0/18^18-29, 203.114.128.0/18^18-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 112.109.64.0/20^20-29, 114.134.0.0/20^20-29, 114.134.160.0/20^20-29, 116.90.128.0/20^20-29, 116.199.208.0/20^20-29, 119.47.112.0/20^20-29, 120.138.16.0/20^20-29, 124.248.128.0/20^20-29, 202.37.0.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.160.48.0/20^20-29, 202.174.160.0/20^20-29, 210.48.160.0/20^20-29, 223.165.64.0/20^20-29, 112.109.80.0/21^21-29, 116.251.192.0/21^21-29, 117.18.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.2.8.0/21^21-29, 202.36.96.0/21^21-29, 202.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.50.208.0/21^21-29, 202.78.240.0/21^21-29, 202.160.112.0/21^21-29, 203.190.208.0/21^21-29, 210.4.208.0/21^21-29, 210.79.48.0/21^21-29, 218.185.224.0/21^21-29, 14.128.4.0/22^22-29, 27.96.64.0/22^22-29, 27.121.96.0/22^22-29, 49.0.28.0/22^22-29, 49.143.228.0/22^22-29, 103.10.44.0/22^22-29, 103.11.124.0/22^22-29, 103.247.192.0/22^22-29, 110.232.144.0/22^22-29, 113.130.120.0/22^22-29, 113.197.64.0/22^22-29, 114.23.96.0/22^22-29, 114.31.212.0/22^22-29, 116.251.200.0/22^22-29, 117.53.156.0/22^22-29, 140.200.248.0/22^22-29, 175.111.100.0/22^22-29, 182.50.160.0/22^22-29, 192.206.152.0/22^22-29, 202.37.28.0/22^22-29, 202.37.48.0/22^22-29, 202.44.60.0/22^22-29, 202.50.216.0/22^22-29, 202.89.4.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 223.165.16.0/22^22-29, 103.22.234.0/23^23-29, 103.23.142.0/23^23-29, 103.29.90.0/23^23-29, 122.102.108.0/23^23-29, 140.200.230.0/23^23-29, 144.66.100.0/23^23-29, 192.206.156.0/23^23-29, 202.6.116.0/23^23-29, 202.27.38.0/23^23-29, 202.36.126.0/23^23-29, 202.36.134.0/23^23-29, 202.36.168.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.37.96.0/23^23-29, 202.37.124.0/23^23-29, 202.46.190.0/23^23-29, 202.49.80.0/23^23-29, 202.49.136.0/23^23-29, 202.49.164.0/23^23-29, 202.50.246.0/23^23-29, 202.65.160.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 103.4.121.0/24^24-29, 103.5.71.0/24^24-29, 103.5.111.0/24^24-29, 103.11.21.0/24^24-29, 103.23.212.0/24^24-29, 103.246.250.0/24^24-29, 144.66.99.0/24^24-29, 144.66.102.0/24^24-29, 144.66.115.0/24^24-29, 144.66.119.0/24^24-29, 144.66.244.0/24^24-29, 180.210.211.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.107.171.0/24^24-29, 192.107.172.0/24^24-29, 192.122.171.0/24^24-29, 192.122.180.0/24^24-29, 192.133.31.0/24^24-29, 192.138.251.0/24^24-29, 192.173.24.0/24^24-29, 192.195.219.0/24^24-29, 192.245.185.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.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.27.239.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.110.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.170.0/24^24-29, 202.36.221.0/24^24-29, 202.37.17.0/24^24-29, 202.37.93.0/24^24-29, 202.37.129.0/24^24-29, 202.37.162.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.0/24^24-29, 202.41.140.0/24^24-29, 202.46.188.0/24^24-29, 202.49.106.0/24^24-29, 202.49.168.0/24^24-29, 202.49.187.0/24^24-29, 202.49.215.0/24^24-29, 202.50.102.0/24^24-29, 202.50.252.0/24^24-29, 202.55.99.0/24^24-29, 202.55.105.0/24^24-29, 202.55.107.0/24^24-29, 202.74.33.0/24^24-29, 202.74.38.0/24^24-29, 202.89.57.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.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, 210.7.40.0/24^24-29, 210.7.46.0/24^24-29, 210.48.191.0/24^24-29, 202.89.43.0/25^25-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 20120308 source: NZRR ------------------------------------------------------------

1 0