February 2010 - NZNOG - lists.nznog.org

Re: [nznog] Stateful firewalls
by Joel Wiramu Pauling 25 Feb '10

25 Feb '10

On 25 February 2010 22:30, Joel Wiramu Pauling <aenertia(a)aenertia.net> wrote: >> The place do to this is at the edges via routing policies and stateless ACLs, not in firewalls. >> >> And, no, the largest enterprise firewalls make all these marketing claims about the numbers they can handle, but the reality is quite different - having spent the better part of a decade working for the largest vendor of firewalls in the world, I can assure you of that. >> There is a trend in router manufacturers to offer flow classification add-in modules for doing service differentiation. While not state-full firewalls as such, they do deep packet inspection and flow tagging in much the same way. These are designed to scale with the routing capacity's. And they definitely exist. Also there is currently a bunch of cool pf kernalspace extensions being added to openbsd to allow similar offload to GPU's which would bring this sort of ability to consumer level hardware. This is a little off topic from the original context however. -JoelW

1 0

Be Heard! APNIC Community Consultation Next Week
by Elly Tawhai 25 Feb '10

25 Feb '10

_______________________________________________________________________ Be Heard! APNIC Community Consultation Next Week _______________________________________________________________________ Hi NZNOG Community, Internet address management may be on the brink of change. The ITU (International Telecommunications Union) is studying the creation of an alternative International Internet Registry model to operate in parallel to the existing RIR model. In collaboration with the NRO, APNIC is hosting a special session at APNIC 29 / APRICOT 2010 to give the global Internet community an opportunity to discuss the issues and ramifications of the alternative model proposed by the ITU. APNIC invites all Members of the global Internet Community to participate at: IPv6 Address Management and ITU - Is an "additional parallel structure" required? Where: APNIC 29, Kuala Lumpur, Malaysia When: 14:00 - 15:30 (UTC +8), Wednesday, 3 March 2010 APNIC is an ITU-D sector Member and will attend the ITU IPv6 Working Group meeting in March that has been commissioned to study this issue in depth. APNIC will be reporting feedback from our Consultation to ensure community feedback is heard. Topics of discussion -------------------- 1. Where is the demand for this alternative system coming from? Would competition between IP address management systems bring any benefits to current and future Internet stakeholders? 2. Is it realistic to expect the policies of an alternative model as proposed by the ITU, to be consistent with RIR policies? Would the possibility of nationalized addressing systems lead to divergent policy systems? What would be the risks to the Internet of divergent policy environments? 3. If the ITU were to become an Internet registry, how would the ITU model affect the existing RIR model of open, bottom-up, and consensus-driven policy-making? More detailed information is available on: http://meetings.apnic.net/29/program/consultation How can you participate? ------------------------ Onsite ------ APNIC 29, Conference Hall 2, Kuala Lumpur Convention Center, Kuala Lumpur, Malaysia. Remotely -------- Remote participants can watch via webcasting and can ask questions and make comments for the record via Jabber Chat. These tools can be adjusted to accommodate low bandwidth. Submissions ----------- APNIC is accepting written submissions. Please post your submission, identifying your name and affiliation and your comments on any or all of three discussion topics as well as general comments to: ipv6(a)apnic.net More Information ---------------- For more information on remote participation, visit: http://meetings.apnic.net/29/remote For more information on the APNIC 29 program, visit: http://meetings.apnic.net/29 For further assistance, contact: helpdesk(a)apnic.net _______________________________________________________________________ APNIC Secretariat Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 Level 1, 33 Park Road, Milton, QLD http://www.apnic.net _______________________________________________________________________

1 0

Re: [nznog] [Ticket #1751456] RE: Stateful firewalls
by Mark Foster 25 Feb '10

25 Feb '10

Erm, seriously? iSERVE support is going to generate a trouble ticket for EVERY new NZNOG thread? This could be entertaining... On Thu, 25 Feb 2010, iSERVE Support wrote: > > Hi, > > This is a quick, automatically generated email to let you know that we have got your email, and our team will get on to it just as soon as they can. > > If you need to get in touch with us in the mean time about the same issue please quote the ticket number or simply reply to this email. > > Thanks, > iSERVE Support > > >

6 5

FW: [Ticket #1750663] MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC
by Skeeve Stevens 24 Feb '10

24 Feb '10

Odd. ...Skeeve -- Skeeve Stevens, CEO/Technical Director eintellego Pty Ltd - The Networking Specialists skeeve(a)eintellego.net / www.eintellego.net Phone: 1300 753 383, Fax: (+612) 8572 9954 Cell +61 (0)414 753 383 / skype://skeeve www.linkedin.com/in/skeeve ; facebook.com/eintellego -- NOC, NOC, who's there? -----Original Message----- From: iSERVE Support [mailto:support(a)iserve.co.nz] Sent: Wednesday, 24 February 2010 5:54 PM To: Skeeve Stevens Subject: RE: [Ticket #1750663] [nznog] MEDIA RELEASE FROM EINTELLEGO - eintellego encourages APNIC Hi, This is a quick, automatically generated email to let you know that we have got your email, and our team will get on to it just as soon as they can. If you need to get in touch with us in the mean time about the same issue please quote the ticket number or simply reply to this email. Thanks, iSERVE Support

1 0

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

24 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:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.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, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.222.0.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 122.201.80.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 110.44.24.0/21^21-29, 112.140.176.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.212.64.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 119.63.216.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 124.248.136.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.49.64.0/21^21-29, 202.56.48.0/21^21-29, 202.67.120.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 119.15.96.0/22^22-29, 119.63.212.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 175.107.184.0/22^22-29, 180.148.24.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.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.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.89.4.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 58.179.136.0/23^23-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.160.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.63.208.0/23^23-29, 119.82.150.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 122.252.12.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.118.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.33.60.0/23^23-29, 203.33.70.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100210 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4826 descr: advertised to AS9560 by Vocus Communications - NO VERIFICATION NEEDED - AS4826 members: 118.92.0.0/15^15-29, 58.28.0.0/16^16-29, 118.90.0.0/16^16-29, 121.90.0.0/16^16-29, 131.203.0.0/16^16-29, 147.209.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, 113.203.0.0/17^17-29, 180.181.0.0/17^17-29, 203.60.128.0/17^17-29, 203.109.128.0/17^17-29, 210.48.0.0/17^17-29, 112.141.0.0/18^18-29, 112.141.128.0/18^18-29, 114.129.128.0/18^18-29, 125.253.0.0/18^18-29, 203.60.64.0/18^18-29, 203.114.128.0/18^18-29, 203.118.128.0/18^18-29, 203.173.128.0/18^18-29, 203.208.64.0/18^18-29, 210.185.0.0/18^18-29, 58.96.128.0/19^19-29, 112.141.64.0/19^19-29, 112.141.192.0/19^19-29, 113.192.0.0/19^19-29, 115.69.160.0/19^19-29, 118.127.0.0/19^19-29, 118.127.64.0/19^19-29, 118.127.160.0/19^19-29, 119.15.0.0/19^19-29, 119.77.64.0/19^19-29, 119.252.0.0/19^19-29, 121.79.192.0/19^19-29, 122.99.64.0/19^19-29, 123.50.128.0/19^19-29, 123.100.128.0/19^19-29, 124.6.192.0/19^19-29, 125.254.64.0/19^19-29, 175.107.128.0/19^19-29, 180.189.192.0/19^19-29, 180.222.0.0/19^19-29, 202.60.64.0/19^19-29, 202.62.128.0/19^19-29, 202.171.160.0/19^19-29, 202.181.0.0/19^19-29, 203.60.32.0/19^19-29, 203.89.64.0/19^19-29, 203.96.192.0/19^19-29, 203.129.32.0/19^19-29, 203.152.96.0/19^19-29, 203.173.192.0/19^19-29, 203.201.128.0/19^19-29, 210.54.160.0/19^19-29, 210.56.224.0/19^19-29, 221.121.128.0/19^19-29, 58.84.224.0/20^20-29, 111.67.0.0/20^20-29, 111.118.160.0/20^20-29, 112.109.64.0/20^20-29, 112.141.96.0/20^20-29, 112.141.224.0/20^20-29, 113.20.0.0/20^20-29, 114.31.192.0/20^20-29, 114.111.128.0/20^20-29, 115.146.64.0/20^20-29, 116.66.160.0/20^20-29, 117.55.224.0/20^20-29, 119.10.128.0/20^20-29, 119.47.112.0/20^20-29, 119.63.208.0/20^20-29, 119.160.224.0/20^20-29, 119.161.64.0/20^20-29, 121.127.208.0/20^20-29, 121.200.32.0/20^20-29, 122.102.96.0/20^20-29, 122.200.160.0/20^20-29, 124.155.224.0/20^20-29, 125.214.64.0/20^20-29, 125.253.96.0/20^20-29, 125.254.96.0/20^20-29, 175.107.160.0/20^20-29, 202.46.160.0/20^20-29, 202.53.176.0/20^20-29, 202.55.144.0/20^20-29, 202.56.32.0/20^20-29, 202.68.160.0/20^20-29, 202.73.192.0/20^20-29, 202.78.32.0/20^20-29, 202.79.160.0/20^20-29, 202.86.96.0/20^20-29, 202.126.192.0/20^20-29, 202.129.144.0/20^20-29, 202.144.160.0/20^20-29, 202.170.160.0/20^20-29, 202.174.160.0/20^20-29, 203.60.16.0/20^20-29, 203.83.192.0/20^20-29, 203.88.112.0/20^20-29, 203.96.0.0/20^20-29, 203.96.32.0/20^20-29, 203.130.160.0/20^20-29, 203.145.32.0/20^20-29, 203.149.64.0/20^20-29, 203.161.128.0/20^20-29, 203.212.144.0/20^20-29, 210.56.32.0/20^20-29, 110.44.24.0/21^21-29, 112.140.176.0/21^21-29, 112.141.112.0/21^21-29, 112.141.240.0/21^21-29, 114.31.72.0/21^21-29, 114.31.96.0/21^21-29, 114.110.32.0/21^21-29, 114.141.96.0/21^21-29, 115.124.32.0/21^21-29, 115.126.128.0/21^21-29, 115.178.16.0/21^21-29, 115.178.104.0/21^21-29, 116.212.64.0/21^21-29, 116.240.160.0/21^21-29, 117.18.80.0/21^21-29, 117.104.176.0/21^21-29, 119.63.200.0/21^21-29, 120.89.80.0/21^21-29, 120.138.16.0/21^21-29, 121.101.136.0/21^21-29, 121.127.200.0/21^21-29, 121.200.208.0/21^21-29, 122.49.200.0/21^21-29, 122.99.112.0/21^21-29, 122.201.72.0/21^21-29, 124.248.136.0/21^21-29, 125.213.160.0/21^21-29, 175.107.176.0/21^21-29, 175.176.200.0/21^21-29, 180.92.192.0/21^21-29, 180.92.216.0/21^21-29, 180.94.232.0/21^21-29, 180.214.168.0/21^21-29, 182.23.192.0/21^21-29, 202.4.232.0/21^21-29, 202.12.248.0/21^21-29, 202.36.16.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.136.0/21^21-29, 202.56.48.0/21^21-29, 202.67.120.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.86.208.0/21^21-29, 202.90.48.0/21^21-29, 202.90.240.0/21^21-29, 202.126.80.0/21^21-29, 202.137.240.0/21^21-29, 202.160.112.0/21^21-29, 202.162.176.0/21^21-29, 202.169.16.0/21^21-29, 202.169.200.0/21^21-29, 202.169.208.0/21^21-29, 202.191.8.0/21^21-29, 203.1.240.0/21^21-29, 203.60.8.0/21^21-29, 203.149.80.0/21^21-29, 203.170.8.0/21^21-29, 203.173.240.0/21^21-29, 203.174.16.0/21^21-29, 203.185.224.0/21^21-29, 203.190.208.0/21^21-29, 203.212.16.0/21^21-29, 210.4.208.0/21^21-29, 210.9.136.0/21^21-29, 210.50.56.0/21^21-29, 58.179.60.0/22^22-29, 58.179.124.0/22^22-29, 59.86.172.0/22^22-29, 59.86.176.0/22^22-29, 59.86.184.0/22^22-29, 61.69.0.0/22^22-29, 61.69.24.0/22^22-29, 63.217.120.0/22^22-29, 110.76.132.0/22^22-29, 110.76.136.0/22^22-29, 110.93.8.0/22^22-29, 110.173.224.0/22^22-29, 110.232.144.0/22^22-29, 111.118.208.0/22^22-29, 111.125.160.0/22^22-29, 111.235.140.0/22^22-29, 113.29.240.0/22^22-29, 113.52.128.0/22^22-29, 113.130.120.0/22^22-29, 114.111.144.0/22^22-29, 114.141.104.0/22^22-29, 114.142.160.0/22^22-29, 115.69.28.0/22^22-29, 116.90.72.0/22^22-29, 116.240.184.0/22^22-29, 119.15.96.0/22^22-29, 119.161.84.0/22^22-29, 119.161.92.0/22^22-29, 119.252.176.0/22^22-29, 121.127.192.0/22^22-29, 122.100.0.0/22^22-29, 122.100.8.0/22^22-29, 122.201.68.0/22^22-29, 122.201.100.0/22^22-29, 124.108.96.0/22^22-29, 125.254.112.0/22^22-29, 175.107.184.0/22^22-29, 175.111.100.0/22^22-29, 180.148.24.0/22^22-29, 180.148.176.0/22^22-29, 180.189.152.0/22^22-29, 180.222.192.0/22^22-29, 198.48.0.0/22^22-29, 202.4.228.0/22^22-29, 202.6.124.0/22^22-29, 202.36.24.0/22^22-29, 202.36.36.0/22^22-29, 202.37.32.0/22^22-29, 202.37.48.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.45.152.0/22^22-29, 202.49.0.0/22^22-29, 202.129.244.0/22^22-29, 202.130.32.0/22^22-29, 202.153.64.0/22^22-29, 202.160.48.0/22^22-29, 202.169.180.0/22^22-29, 202.169.196.0/22^22-29, 202.169.216.0/22^22-29, 202.177.220.0/22^22-29, 203.0.124.0/22^22-29, 203.4.200.0/22^22-29, 203.11.104.0/22^22-29, 203.16.200.0/22^22-29, 203.17.208.0/22^22-29, 203.22.236.0/22^22-29, 203.30.44.0/22^22-29, 203.55.232.0/22^22-29, 203.62.184.0/22^22-29, 203.80.60.0/22^22-29, 203.82.100.0/22^22-29, 203.83.208.0/22^22-29, 203.92.28.0/22^22-29, 203.99.132.0/22^22-29, 203.145.48.0/22^22-29, 203.145.56.0/22^22-29, 203.161.156.0/22^22-29, 203.175.120.0/22^22-29, 203.176.124.0/22^22-29, 203.176.184.0/22^22-29, 203.185.232.0/22^22-29, 203.188.216.0/22^22-29, 203.190.232.0/22^22-29, 203.202.132.0/22^22-29, 203.211.56.0/22^22-29, 203.212.128.0/22^22-29, 203.217.152.0/22^22-29, 210.11.144.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 58.179.136.0/23^23-29, 59.86.170.0/23^23-29, 59.86.188.0/23^23-29, 63.218.156.0/23^23-29, 110.76.128.0/23^23-29, 111.125.168.0/23^23-29, 114.111.148.0/23^23-29, 114.134.176.0/23^23-29, 114.141.108.0/23^23-29, 114.142.168.0/23^23-29, 115.178.6.0/23^23-29, 116.90.128.0/23^23-29, 116.90.132.0/23^23-29, 116.90.140.0/23^23-29, 118.107.60.0/23^23-29, 119.161.80.0/23^23-29, 121.127.196.0/23^23-29, 122.100.6.0/23^23-29, 122.100.14.0/23^23-29, 122.201.64.0/23^23-29, 141.243.8.0/23^23-29, 141.243.32.0/23^23-29, 180.235.104.0/23^23-29, 199.212.92.0/23^23-29, 202.4.162.0/23^23-29, 202.4.226.0/23^23-29, 202.6.56.0/23^23-29, 202.6.116.0/23^23-29, 202.7.2.0/23^23-29, 202.8.44.0/23^23-29, 202.12.70.0/23^23-29, 202.12.90.0/23^23-29, 202.14.32.0/23^23-29, 202.14.62.0/23^23-29, 202.14.248.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.36.218.0/23^23-29, 202.37.240.0/23^23-29, 202.46.176.0/23^23-29, 202.46.190.0/23^23-29, 202.49.62.0/23^23-29, 202.49.148.0/23^23-29, 202.49.164.0/23^23-29, 202.56.62.0/23^23-29, 202.61.2.0/23^23-29, 202.65.160.0/23^23-29, 202.67.118.0/23^23-29, 202.92.94.0/23^23-29, 202.92.240.0/23^23-29, 202.93.4.0/23^23-29, 202.150.60.0/23^23-29, 202.158.254.0/23^23-29, 202.162.64.0/23^23-29, 202.167.230.0/23^23-29, 202.167.244.0/23^23-29, 202.167.252.0/23^23-29, 202.169.176.0/23^23-29, 202.169.220.0/23^23-29, 202.174.6.0/23^23-29, 202.177.196.0/23^23-29, 202.177.214.0/23^23-29, 202.182.110.0/23^23-29, 202.182.124.0/23^23-29, 203.3.124.0/23^23-29, 203.4.182.0/23^23-29, 203.10.76.0/23^23-29, 203.16.60.0/23^23-29, 203.17.112.0/23^23-29, 203.18.102.0/23^23-29, 203.21.76.0/23^23-29, 203.22.70.0/23^23-29, 203.24.88.0/23^23-29, 203.25.170.0/23^23-29, 203.28.202.0/23^23-29, 203.29.208.0/23^23-29, 203.30.98.0/23^23-29, 203.33.60.0/23^23-29, 203.33.70.0/23^23-29, [snip... Object abbreviated for readability] changed: rpsl-admin(a)nzix.net 20100224 source: NZRR ------------------------------------------------------------

2 1

Re: [nznog] Counting Teredo traffic...
by Nathan Ward 22 Feb '10

22 Feb '10

Sorry, I know you replied off list but you're not the first person to talk about these sorts of things with me so I'm replying on list so more people benefit. On 22/02/2010, at 11:04 PM, Joel Wiramu Pauling wrote: >> No. >> Teredo servers are using for essentially control traffic. >> Teredo relays move data to/from the native IPv6 network (non-Teredo). >> >> Unless you really really know what you're doing, don't run a Teredo server. Run a Teredo *relay*. > > Sure, but you might want to do both so you can both: > > a) Grab the control traffic so it does not leave the network for > instances where it's impracticle to specify a teredo server to edge > clients. > b) Tell it to use your relay -> Feed into your native v6 > infrastructure and benefit from not having potentially long inefficent > routes. > c) This would work where you have v6 but for whatever reason can't get > it out to the edge. And don't want to push a tunnel client etc out. > (not ideal but, it's just another option in the whole transition > ecosystem). No, that won't work. 1) Your customer sends an ICMPv6 echo request to a web server, through your Teredo server (but they really mean to sent it elsewhere) 2) You send it to some server of yours that is configured to respond to every ICMPv6 echo request, with the source address set to the destination address of the request. 3) ICMPv6 echo reply goes through your Teredo relay, and then to the customer. 4) Customer's Teredo stack detects your relay's IPv4 and UDP port. 5) Customer sends a TCP SYN to the web server, through your relay. 6) Your relay decapsulates it, and sends it on to the IPv6 network, probably over a longer path than it would take than an automatically discovered relay would use. 7) No worry though, because the SYN+ACK will come back through the better relay. 8) Your customer will detect the IPv4 address and UDP port of the new, better relay. Don't try to shoe horn Teredo in to doing these things, it's designed to be hard for ISPs to control, quite intentionally. Install a relay when you roll out your native IPv6 network and move on. > It's essentially your TUI box idea, with dns hacks. ;-) Not really, the only thing that the Tui boxes do with Teredo is relay. They aren't Teredo servers. You could probably configure one to be because they just have Miredo inside, but that's not what they're for. The Tui boxes are also 6to4 relays, and they build a peering mesh over IPv4 best-paths between other Tui boxes. The only similarities between what you're proposing, and Tui, is that they both implement parts of Teredo. -- Nathan Ward

2 2

Counting Teredo traffic...
by Joel Wiramu Pauling 22 Feb '10

22 Feb '10

So, what is the best way to count teredo traffic on their networks, assume I just want packet counts and nothing else. * I know that if I have netflows I can look for the 2001:0000: address marker inside packets, but this is a) resource intensive, b) assumes I have full netflows. * I can also count traffic originating from the various teredo relays/servers... but this again would require being able to mark a full flow and track things Does anyone know of a better way or at least other techniques? Kind regards -JoelW

3 4

Re: [nznog] Proxy/online voting for APNIC EC election opens today
by jamie baddeley 19 Feb '10

19 Feb '10

Calling all APNIC account holders! Vote early! vote often! One of the names below will be strangely familiar to you. pass it on. jamie On Fri, 2010-02-19 at 19:26 +1100, Secretariat wrote: > _______________________________________________________________________ > > Proxy/online voting for APNIC EC election opens today > _______________________________________________________________________ > > > Online and proxy voting for the APNIC Executive Council (EC) election > opens today. The online/proxy voting period is only open until 09:00 > (UTC+8, Kuala Lumpur time), 3 March 2010. The EC Members whose > positions > are up for re-election are: > > - Akinori Maemura > - Che-Hoo Cheng > - Ma Yan > > The current nominees are: > > - Ma Yan > - Vinh Ngo > - Akinori Maemura > - Ravi Shanker > - Che-Hoo Cheng > - Jonny Martin > > APNIC Member organizations can vote using MyAPNIC. > > Online voting is available to APNIC Member Corporate Contacts and > Member Contacts with voting rights. By default, all Corporate Contacts > have voting rights, and can assign voting rights to other contacts. > > MyAPNIC (https://myapnic.net/) > > Full details of the election, including profiles of the candidates > and alternative voting methods are available at: > > http://meetings.apnic.net/29/elections/ec > > If you have any questions or need further assistance, please contact: > > helpdesk(a)apnic.net > > > _______________________________________________________________________ > > APNIC Secretariat > secretariat(a)apnic.net > Asia Pacific Network Information Centre (APNIC) Tel: +61 7 3858 3100 > PO Box 2131 Milton, QLD 4064 Australia Fax: +61 7 3858 3199 > Level 1, 33 Park Road, Milton, QLD http://www.apnic.net > _______________________________________________________________________ > To remove yourself from this email list click here >

1 0

IPv6 NZ name and shame page.
by Joel Wiramu Pauling 19 Feb '10

19 Feb '10

A while back there was a page which was querying major .nz sites for various ipv6 reachability. What happened to this page does it still exist, and if so can someone please furnish me with the URL. Kind regards -Joel W Pauling

3 2

Telecom interconnection
by Simon Lyall 18 Feb '10

18 Feb '10

I believe this is a followup to something that was mentioned at NZNOG. ---- Telecom to restart IP interconnection talks Telecom is signalling a restart to interconnection talks ahead of a planned December 2011 launch for IP interconnection charging. [..] http://computerworld.co.nz/news.nsf/telecommunications/telecom-to-restart-i… -- Simon Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

5 4