- NZNOG - lists.nznog.org

APNIC 22 update #2
by Nurani Nimpuno 09 May '06

09 May '06

Hi NZNOG:ers, I'm forwarding on an update about the APNIC 22 meeting in September. If you have any questions about it, don't hesitate to shoot me a mail. Also, if you want an invitation letter (pdf, or printed and posted to you), contact me and I can arrange it. Cheers! Nurani ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Asia Pacific Network Information Centre Ph :+61-7-38583100 PO Box 2131 Milton, QLD 4064 Fax:+61-7-38583199 Australia http://www.apnic.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [Apologies for duplicates] APNIC 22 update #2 Invitation to APNIC 22 ______________________________________ 22nd APNIC Open Policy Meeting 4-8 September, 2006, Kaohsiung, Taiwan ______________________________________ Dear APNIC members and friends, It is our pleasure to invite you to attend the 22nd APNIC Open Policy Meeting, being held in Kaohsiung, Taiwan. Hosted by TWNIC (Taiwan Network Information Center), APNIC 22 includes an innovative program that showcases presentations on operational Internet issues. Details of the program will be released closer to the meeting; however, a draft schedule is now available at: http://www.apnic.net/meetings/22/program Contents -------- 1. Meeting registraion is open 2. APNIC fellowships 3. Sponsorship opportunities 4. Visa information 1. Meeting registration ---------------------- Meeting registration site is now open. Please visit: http://www.apnic.net/cgi-bin/registration.pl?event_id=90 Early bird registration will end on 14 July, 2006. 2. APNIC fellowship ------------------- The APNIC fellowship program provides basic assistance to Internet professionals from developing economies around the region. If you are interested in applying for an APNIC 22 fellowship, please visit: http://www.apnic.net/meetings/22/fellows The deadline for applications is 26 May, 2006. 3. Sponsorship opportunities ---------------------------- Sponsoring an APNIC meeting will provide you with a range of opportunities to expose your organisation to the Asia Pacific Internet community. If your organisation is interested in sponsoring APNIC 22, please visit: http://www.apnic.net/meetings/22/sponsors 4. Visa information ------------------- Some meeting attendees may require a visa to visit Taiwan. Attendees who require a visa should apply promptly after completing the meeting registration to ensure that the visa is issued on time. All necessary information can be found at: http://www.apnic22.tw/apnic22_visas.htm Any questions? Please contact the APNIC Secretariat at <meetings(a)apnic.net>. We look forward to seeing you in Kaohsiung! Regards, ______________________________________________________________________ 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 ---------------------------------------------------------------------- See you at APNIC 22! Kaohsiung, 4-8 September, 2006 www.apnic.net/meetings ______________________________________________________________________

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 May '06

09 May '06

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: AS9897 as-name: NZRR-AS9897 descr: jsr.com descr: APE peering at '192.203.154.102' descr: see Citylink RT job #5456 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS9897 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jsr(a)jsr.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS9897 descr: Route set advertised to AS9560 by jsr.com - AS9897 members: 202.49.89.0/24^24-29, 205.233.243.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: jsr(a)jsr.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 09 May '06

09 May '06

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:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 124.197.0.0/18^18-29, 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 202.49.34.0/23^23-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060510 source: NZRR

1 0

New IP ranges for Xtra's email platform
by Ted Grenfell 08 May '06

08 May '06

Very shortly (later this week or early next week) we will be modifying DNS entries for Xtra's SMTP servers to point to a new email platform and we would like to draw your attention to the new network IP address ranges that will then be in use as per below: 210.54.141.0/24 210.55.11.0/24 If you've configured any of the existing Xtra mail server IP's in to any of your systems then it might be worthwhile adding the above ranges as well taking note not to delete any existing entries as that may impact normal delivery at this time. If you rely solely on DNS for selecting IP's to deliver email through to Xtra's SMTP servers then you do not need to make any changes. -- Kind Regards, Ted Grenfell ISP Performance Manager T +64 9 359 5854 (extn 93254) F +64 9 377 0781 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz <mailto:ted.grenfell(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 11, Telecom House, 8 Hereford Street, Private Bag 92028, Auckland CBD, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 08 May '06

08 May '06

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:AS9790 descr: advertised to AS9439 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.37.129.0/24^24-29, 202.49.34.0/23^23-29, 202.50.109.0/24^24-29, 202.180.64.0/18^18-29, 203.97.152.0/24^24-29, 203.100.208.0/20^20-29, 203.184.0.0/18^18-29, 203.215.142.0/23^23-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)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9790 descr: advertised to AS9439 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-27, 202.37.22.0/24^24-27, 202.37.129.0/24^24-27, 202.49.34.0/23^23-27, 202.50.109.0/24^24-27, 202.180.64.0/18^18-27, 203.97.152.0/24^24-27, 203.100.208.0/20^20-27, 203.184.0.0/18^18-27, 203.215.142.0/23^23-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by Callplus Limited - AS9790 members: 202.180.64.0/18^18-29, 203.184.0.0/18^18-29, 203.100.208.0/20^20-29, 203.160.112.0/20^20-29, 203.215.142.0/23^23-29, 202.36.232.0/24^24-29, 202.37.22.0/24^24-29, 202.50.109.0/24^24-29, 203.97.152.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: ops(a)noc.tranzpeer.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060509 source: NZRR

1 0

FYI: Trademe phish ...
by Jamie Riden 08 May '06

08 May '06

Haven't seen a trademe phish before. The actual link goes to http://www.furutech.co.kr/bbs/data/trademe.php . You might want to warn and filter. cheers, Jamie Subject: TradeMe Account Security Measures Dear foo(a)example.co.nz , We recently noticed one or more attempts to log in to your TradeMe account from a different IP addresses. If you recently accessed your account while traveling, the unusual log in attempts may have been initiated by you. However, if you did not initiate the log ins, please visit TradeMe as soon as possible to check-up your account information: http://www.trademe.co.nz/members/login.aspx Thanks for your patience. Sincerely, TradeMe ---------------------------------------------------------------- Please do not reply to this e-mail. Mail sent to this address cannot be answered. Email ID 376223

1 0

[Fwd: Skybox Security Solutions announcement]
by Justin Cook 07 May '06

07 May '06

Some interesting spam I received. Reading through it I noticed they claim to test your security with a botnet. Are these guys serious? I'm guessing that the only definition of' 'botnet' out there these days is an armada of compromised PCs. -------- Original Message -------- Subject: Skybox Security Solutions announcement Date: Mon, 08 May 2006 10:00:21 +0800 From: <114_reunited(a)jaydees.net> Reply-To: <114_reunited(a)jaydees.net> Skybox Security Solutions *Simulated DDoS Network Attacks and Network Intrusions* *Customer Challenge: * Large corporations often hire consultants to conduct quarterly penetration (DDoS) testing on specific segments of their corporate network. This testing can cost over hundreds of thousands of dollars, and also exposes the network to many potential disruptions. These disruptions are the result of the intense DDoS attacks testers can impose on live networks in order to isolate vulnerabilities and weaknesses. Since the network is constantly changing, and DDoS attacks are rarely dispersed from a centralized location, the penetration test results often become nullified and end up being limited to a small portion of the total network. *The Skybox Solution: *Skybox Security performs accurate and non-intrusive DDoS attacks across a larger portion of the corporate network. The tests are modeled and analyzed through an automated process via our large botnet network rather than manually performed on a live network. As a result, the tests are repeated rigorously on a scheduled basis without any fear of network disruption. Through DDoS attack and access simulation, vulnerability exposures as well as security control weaknesses are revealed instantly. DDoS attack simulation discovers all possible attack scenarios and reveals the step by step process that an attacker or worm may follow. It illustrates specific vulnerabilities to be exploited and network access traversed for each exploitable path. Access simulation calculates network access privileges determined by firewall and routing configuration. Our botnet helps characterize the interconnectivity between any two given points, reporting not just whether access is possible, but also the detailed path to reach a final destination. Based on these combined results, security personnel are able to determine what additional DDoS attacks are necessary and where to deploy our organizations penetration testers. *Awards:* Info Security - Info Security Hot Companies 2006 The Wall Street Journal - One of the most innovative companies in 2005 Information Security Magazine - Product of the year Network Magazine - Most Visionary Security Product Network Magazine - Best of the Best in all categories Secure Enterprise Magazine - Editor's Choice Gartner - " Cool Vendor " in the security & privacy space SC Magazine Awards 2006 Winner - The Best Security Solution for Financial Services IM2005 Award finalist - Information Security and Product of the Year *Company Profile:* Eran Reshef Founder, Chairman & CEO of Blue Security ( www.bluesecurity.com <http://www.bluesecurity.com>) A serial entrepreneur, Eran is currently the founder, chairman & CEO of Blue Security, the do-not-disturb registry pioneer. Prior to Blue, Eran co-founded Skybox Security and served as its Chairman. Prior to Skybox Eran founded and managed Sanctum (acquired by WatchFire), the leader in web application security. Eran holds a variety of security- related patents that are based on his inventions. Rina Shainski General Partner at Carmel Ventures ( www.carmelventures.com <http://www.carmelventures.com>) Following a successful career leading business development and R&D operations in high-growth software companies, Rina has been investing in software companies ever since. Before joining Carmel she served as the VP Business Development at Clal Industries and Investments where she was responsible for software investments. From 1989 to 1996, Rina held several managerial positions in Tecnomatix including VP Business Development and R&D Director. Rina serves on the boards of Followap Communications, Skybox Security, mFormation and Silicon Design Systems. Rina holds a B.Sc. degree in Physics from Tel Aviv University and a Master of Science degree in Computer Science from Weizmann Institute. *Contact Information:* 2077 Gateway Place, Suite 550 San Jose, California 95110 USA Phone: 866-6SKYBOX Phone: 408 441 8060 Fax: 408 441 8068 Regional Offices (Israel) 60 Medinat Hayehudim St. P.O.Box 4109 Herzliya Pituach 46140 Israel Phone: +972-9-9545922 Fax: +972-9-9545933

5 4

new netblocks for Callplus/Slingshot
by Kevin Stewart 07 May '06

07 May '06

We are about to start advertising our new address blocks at the APE and WIX 124.197.0.0 /18 and 203.160.112.0/20 here is our current prefix list ASN 9790 ip prefix-list callplus-networks seq 5 permit 124.197.0.0/18 ip prefix-list callplus-networks seq 10 permit 202.36.232.0 ip prefix-list callplus-networks seq 15 permit 202.37.22.0 ip prefix-list callplus-networks seq 20 permit 202.49.34.0/23 le 24 ip prefix-list callplus-networks seq 25 permit 202.50.109.0 ip prefix-list callplus-networks seq 30 permit 202.180.64.0/18 ip prefix-list callplus-networks seq 35 permit 203.97.152.0 ip prefix-list callplus-networks seq 40 permit 203.100.208.0/20 ip prefix-list callplus-networks seq 45 permit 203.160.112.0/20 ip prefix-list callplus-networks seq 50 permit 203.184.0.0/18 ip prefix-list callplus-networks seq 55 permit 203.215.142.0 ip prefix-list callplus-networks seq 60 permit 203.215.143.0 -- Kevin Stewart Network Engineer DDI ++ 64 9 919 6120 Mobile ++ 64 21 885 505 Email kevins(a)callplus.co.nz ----------------------------------------------------------------------------------------------- This message and any attachments contain privileged and confidential information. If you are not the intended recipient of this message, you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately via email and then destroy this message and any attachments.

2 1

Re: [nznog] Oh dear, no more room on the intarweb
by barry＠unix.co.nz 07 May '06

07 May '06

I'm sure majority of the devices would be added on an internal network such as telstra clears cable tv (digital) and cable modems (management), only 1 live ip is assigned for internet services. From memory a few mobile providers assign you a internal ip too and you're nat'ed out to the net. But yeah IPv6 is just around the corner. Thanks Barry > http://www.techweb.com/wire/networking/187200459 > > > -- > Juha Saarinen > www.geekzone.co.nz/juha > www.computerworld.co.nz > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

12 23

Re: [nznog] Oh dear, no more room on the intarweb
by Philip D'Ath 07 May '06

07 May '06

It allows each machine to have a globally unique IP address, without any form NAT. NAT breaks several protocols, and generally makes life more difficult. Also, if you want to use the same port for several machines (like 443) and you only have a single IP address then it makes life more difficult. For example, we have a single IPv4 address on a DSL tail. However, our entire network is IPv6 enabled using a 6to4 tunnel. We have several of our servers providing an https service. Thanks to IPv6 I can now easily browse to any of these servers from any of the remote locations that we have already IPv6 enabled. We are looking to actively start using IPv6 at many of our clients this year. We'll be using 6to4 tunnels again (because no one sells IPv6 transit ...). This means we can load a management agent on their machines, and have our server talk to those agents over a VPN. Normally we would have the grief of ensuring their private IP address range is different from all of our other client addresses ranges. With every machine having a globally unqiue IPv6 address this is no longer an issue. Of course, there is always an IPv4 RFC1918 clash, and we end up with the option of limited management, or a renumbering exercise. The sooner everyone adopts IPv6, and we can easily get native IPv6 transit the better. -----Original Message----- Still, I'm a little puzzled why a single IPv4 address (with lots of NAT behind it) is really any different from a single IPv6 prefix with lots of bits on the right hand side.

1 0