- NZNOG - lists.nznog.org

Mail filters - vector.co.nz
by Simon Lyall 16 Feb '10

16 Feb '10

A very literal filter. ------------------- A mail from you (nznog-bounces(a)list.waikato.ac.nz) to (xxxx(a)vector.co.nz) was stopped and Quarantined because it contains objectionable content. objectionable content (file 234443, line 5, weight 100) ------------------- Translation: It is blocking the phrase "objectionable content" -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Re: [nznog] DIA Filters
by Scott Weeks 16 Feb '10

16 Feb '10

--- nznog(a)neilnz.com wrote: From: Neil Gardner <nznog(a)neilnz.com> I'm not convinced that discussions of naked network engineers playing on an oiled up slip and slide are appropriate given the sensitive nature of the discussion. -------------------------------------- Geez, now I'll NEVER get that image out of my mind no matter how much beer I drink. <shudder!> ;-) scott ------------------- ---------------------- -----------------------

1 0

Re: [nznog] DIA Filters
by Gary T. Benner 16 Feb '10

16 Feb '10

[Reply] HI all, At 12:24 on 17/02/2010 you wrote >I'm not convinced that discussions of naked network engineers playing >on an oiled up slip and slide are appropriate given the sensitive >nature of the discussion. I've seen too often noble causes used to justify actions / policies that in later years get divorced from the original motivation.. $peed cameras = safer roads anyone? yeah right. >On another note... > >WHHHEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!! Can go first!? Don't wanna go there ... cheers Gary Ref#: 41006

1 0

Re: [nznog] DIA Filters
by Gary T. Benner 16 Feb '10

16 Feb '10

[Reply] HI all, I had a conversation over dinner with an ECPAT person some years ago. While doing good work, they seemed to believe that because technology allowed images to be scanned for "flesh colours" then every email, attachment, and website should be filtered. I tried to explain technology and cost issues, and then the fact that any system, once implemented, would/could be easily bypassed by the "perverts", leaving Joe Public to pay the costs for an expensive white elephant. There was also blindness to the possible abuses by the operators of such a system, particularly where the filtering rules are hidden. So we may well have a case of political operators riding the "noble cause(s)". So we best be aware here. The slippery slope is indeed already well oiled. cheers Gary At 11:54 on 17/02/2010 you wrote >To : nznog(a)list.waikato.ac.nz >CC : >From: Florent Bouron, florentb(a)securify.co.nz >Content Type: text/html >Attached: image0011234567891011121314.png > > >This is a multi-part message in MIME format. > > > > >Am I the only one to spot that they're going to use a _Content_ filter to >actually filter URLs? > >A content filter is able to scan the pages for offending material, when they >talk about installing a black list of web sites. > > > >And a content filter has got far bigger technical challenges than just >filtering URLs and IPs ... or are they giving themselves the ability to >deploy further and smarter filtering in the future? > > > > > >From: nznog-bounces(a)list.waikato.ac.nz >[mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of McDonald Richards >Sent: Wednesday, 17 February 2010 11:45 a.m. >To: nznog(a)list.waikato.ac.nz >Subject: Re: [nznog] DIA Filters > > > >Out of curiosity does the NZ list also contain RC (refused classification) >material or is it purely child pornography - or are people being kept in the >dark about the exact contents of the list? Is it as useless as the proposed >AU one which will only stop HTTP? > > > >I guess you can say this is an issue close to all of our hearts (Aussies >that is) at the moment - both because of the wasted tax payers money (what >good is a filter that doesn't work) and the ability for our government to >censor what the public servants perceive as restricted content at whim! > > > >Macca > > > > > >From: nznog-bounces(a)list.waikato.ac.nz >[mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Tony Wicks >Sent: Wednesday, 17 February 2010 9:25 AM >To: nznog(a)list.waikato.ac.nz >Subject: [nznog] DIA Filters > > > >I don't suppose anyone is prepared to comment on If particular ISP's intend >to adopt whatever this is ? > > ><http://www.zdnet.com.au/news/communications/soa/NZ-s-filter-starts-next-mon >th/0,130061791,339301140,00.htm> >http://www.zdnet.com.au/news/communications/soa/NZ-s-filter-starts-next-mont >h/0,130061791,339301140,00.htm > >Tony Wicks | Network Architect Team Leader >DDI +64 9 978 8328 | Mobile +64 21 965362 > >Picture (Device Independent Bitmap) > >The information contained in this e-mail is confidential and may >be legally privileged. If you have received it in error, you may >not read, use, copy or disclose this email. If you are not the >intended recipient, please let us know by reply e-mail >immediately and then delete this email from your system. We shall >not be responsible for any changes to, or interception of, this >email or any attachment after it leaves our information systems. >We accept no responsibility for viruses or defects in this email >or any attachments. > > > >_______________________________________________ >NZNOG mailing list >NZNOG(a)list.waikato.ac.nz >http://list.waikato.ac.nz/mailman/listinfo/nznog Ref#: 41006

2 1

NZNOG 2010 Videos
by Richard Naylor 15 Feb '10

15 Feb '10

Video recordings from the 2010 NZNOG Conference are now available for viewing and/or download. The URL is http://www.r2.co.nz/20100128/ Happy Viewing Richard

2 1

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '10

14 Feb '10

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: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS24388:RS-ROUTES:AS9503 descr: advertised to AS24388 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100215 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '10

14 Feb '10

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: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS45279:RS-ROUTES:AS9503 descr: advertised to AS45279 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100215 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '10

14 Feb '10

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100215 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 14 Feb '10

14 Feb '10

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: tim(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100120 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 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, 119.15.0.0/19^19-29, 202.14.32.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, 124.248.128.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, 210.48.160.0/20^20-29, 112.109.80.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.37.32.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.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, 110.232.144.0/22^22-29, 113.197.64.0/22^22-29, 175.111.100.0/22^22-29, 192.206.152.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.99.132.0/22^22-29, 192.206.156.0/23^23-29, 202.36.214.0/23^23-29, 202.36.218.0/23^23-29, 202.46.190.0/23^23-29, 202.49.164.0/23^23-29, 203.84.134.0/23^23-29, 203.217.142.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.0/24^24-29, 192.105.10.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.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.36.33.0/24^24-29, 202.36.75.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.221.0/24^24-29, 202.37.93.0/24^24-29, 202.37.168.0/24^24-29, 202.37.205.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.50.247.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.89.57.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, 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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20100215 source: NZRR ------------------------------------------------------------

1 0

L2TP load generation
by Nathan Ward 13 Feb '10

13 Feb '10

Hi team, I'm working on some software that does L2TP LNS stuff. It's kind of experimental right now and may end up just being cast in to my bucket of code I can't be bothered with anymore, but I'd like to get an idea for how it performs nonetheless. Does anyone have a reasonably featured router tester, or some other way of generating lots of L2TP load (new connections, packet rate, etc.) that I could borrow some time on, or perhaps trade for some IPv6/etc. know how? WAND - Don't worry, you're already on my list. -- Nathan Ward

1 0