- NZNOG - lists.nznog.org

NZNOG 2007: Sysadmin Miniconf: Slides available
by Ewen McNeill 11 Feb '07

11 Feb '07

For those that attended the Sysadmin Miniconf at NZNOG 2007 (or wished to but had conflicts), the slide sets from most of the talks at the miniconf are now online: http://nznog.miniconf.org/ Thank you to everyone who participated in the miniconf and helped make it a success, and especially to those who spoke at the miniconf. If anyone has anything else that they want linked to the Sysadmin Miniconf page please email it to <talks(a)nznog.miniconf.org>. Ewen

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Feb '07

11 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061214 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Feb '07

11 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061218 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 11 Feb '07

11 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS38292 as-name: NZRR-AS38292 descr: Zero One descr: WIX peering at '202.7.1.17' descr: see Citylink RT job #245 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS38292 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nick(a)01.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS38292 descr: Route set advertised to AS9439 by Zero One - AS38292 members: 210.48.94.0/24^24-29, 210.48.103.192/26^26-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: nick(a)01.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR

1 0

Off Topic - Woosh VoIP engineer please contact me off list..
by Chris Hodgetts 09 Feb '07

09 Feb '07

I had VoIP issues with Woosh awhile ago, and was advised by a tech there that they would start to support RFC2833 as opposed to INBAND DTMF on their VoIP system (when he spoke to me he advised in about 3 weeks, but this was well before Christmas) This is yet to happen, and I am still having issues calling a few IVR systems and would like to get it resolved if I can - or at least know of a date this might take place. Cheers, and apologies for taking this off topic, and because I don't drink I cant bring it back on topic..... but I am sure someone can drink enough for me. Cheers thanks again.

5 4

Notification of NZRR Database changes
by NZRR Database Notifications 07 Feb '07

07 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- OBJECT BELOW CREATED: aut-num: AS17663 as-name: NZRR-AS17663 descr: Housing New Zealand Corporation descr: WIX peering at '202.7.0.149' descr: see Citylink RT job #8222 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS17663 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: ns(a)hnzc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070208 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS17663 descr: Route set advertised to AS9439 by Housing New Zealand Corporation - AS17663 members: 192.173.17.0/24^24-29, 202.37.197.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: ns(a)hnzc.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070208 source: NZRR

1 0

A new policy proposal "IPv4 countdown policy proposal" - APNIC 23
by Miwa Fujii 06 Feb '07

06 Feb '07

Hi All, Thanks for the NZNOG 2007 committee's efforts to make successful NZNOG 2007. Thanks also for NZNOG community pple's warm hospitality to us. I very much enjoyed technical presentations, the panel discussion and both formal/informal social events. As we discussed in the panel discussion "Where to spend the money, IPv6, or somewhere else?", there were quite a few dimensions to discuss this topic. As NZNOG is a technical community, naturally, the discussion was drawn into technical details of IPv6. However, we briefly discussed about the relationship between IPv4 address exhaustion and IPv6. There is a policy proposal for the upcoming APNIC 23 in Bali, titled "IPv4 countdown policy proposal" http://www.apnic.net/docs/policy/proposals/prop-046-v001.html I think having a wider community's input to this proposal would be good. If you have any comment, please feel free to post it to the APNIC sig-policy mailing list. You can subscribe the mailing list from: http://www.apnic.net/community/lists/index.html Looking forward to hearing your view. miwa

1 0

Thursday night curry in Hamilton?
by Ian McDonald 06 Feb '07

06 Feb '07

Jayne and I have thought about this and decided that it's really time Hamilton got their act together on this one. Various people/groups have talked about this but no-one has done this yet (that I'm aware of) and we'd like to see this kick off. Since many of you from Hamilton probably met each other at NZNOG (shame I couldn't make it) I thought it'd be a good time to mention it while you still remember each other. If you're interested please email me off list. Also can whoever looks after the domain/server (Jamie Baddeley?) contact me to see how we can put Hamilton on. NB I'm not going to make token reference to beer as think networking (in the social sense) is quite a relevant topic. And more than token amount of beer might get consumed anyway! Ian -- Web: http://wand.net.nz/~iam4 Blog: http://iansblog.jandi.co.nz WAND Network Research Group

1 1

NZNOG Photos (Group and others)
by Lin Nah 05 Feb '07

05 Feb '07

HI all Group photo for NZNOG 2007 http://coders.meta.net.nz/~perry/inet/nznog-07/index.php?photo=4 If you are in this photo and have NOT been named, please click on your mouse button when a ? appears on your face. We have tried to identify as many as possible. People are not indentified due to many reasons. Please don't take it personally. Btw if you want to look at the nznog photo of other years I've added a link in the group photo secion at wiki.nznog.org or NZNOG 2006 http://coders.meta.net.nz/~perry/inet/nznog-06/index.php?photo=3 NZNOG 2005 http://coders.meta.net.nz/~perry/inet/nznog-05/index.php?photo=1 nznog 2004 http://coders.meta.net.nz/~perry/inet/nznog-05/index.php?photo=2 If you took photos, please add a link to this page http://wiki.nznog.org/index.cgi/Pictures Also if you blogged about it, add a link to http://wiki.nznog.org/index.cgi/Blogs regards lin

1 0

elevated icmp last couple of days?
by Anton Smith 05 Feb '07

05 Feb '07

Hi all, Just wondering if anyone else has noticed elevated ICMP levels. I'm seeing a lot of what looks like ICMP from infected machines, both coming into our network and leaving it. Always with the same sequence number and going to and from many different machines: e.g. 13:41:45.682360 IP 196.211.95.177 > 202.65.160.195: icmp 72: echo request seq 20041 13:41:45.682395 IP 196.211.95.177 > 202.65.160.195: icmp 72: echo request seq 20041 13:41:45.684098 IP 196.211.95.177 > 202.65.160.195: icmp 72: echo request seq 20041 13:41:45.684185 IP 196.211.95.177 > 202.65.160.195: icmp 72: echo request seq 20041 and 13:45:23.759952 IP 203.110.28.211 > 24.149.23.167: icmp 41: echo request seq 39506 13:45:23.764000 IP 203.110.28.211 > 24.149.63.81: icmp 41: echo request seq 39762 13:45:23.764046 IP 203.110.28.211 > 24.149.20.160: icmp 41: echo request seq 40018 13:45:23.764426 IP 203.110.28.211 > 24.149.134.141: icmp 41: echo request seq 40274 13:45:23.766189 IP 203.110.28.211 > 24.149.81.135: icmp 41: echo request seq 40530 Seems to be the same sequence number for the same destination host. There are hundreds/thousands of these every second and seems to be ongoing. Just wondering if it is just us. Regards, Anton

1 1