- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 16 Aug '09

16 Aug '09

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:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 121.98.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 202.126.192.0/20^20-29, 202.191.32.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.193.144.0/21^21-29, 116.199.208.0/21^21-29, 202.49.64.0/21^21-29, 210.54.56.0/21^21-29, 210.79.48.0/21^21-29, 110.34.48.0/22^22-29, 113.21.224.0/22^22-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 120.138.22.0/23^23-29, 202.36.230.0/23^23-29, 202.37.82.0/23^23-29, 202.175.142.0/23^23-29, 192.203.216.0/24^24-29, 202.0.151.0/24^24-29, 202.12.104.0/24^24-29, 202.27.8.0/24^24-29, 202.27.77.0/24^24-29, 202.36.12.0/24^24-29, 202.36.174.0/24^24-29, 202.37.19.0/24^24-29, 202.37.78.0/24^24-29, 202.37.173.0/24^24-29, 202.46.189.0/24^24-29, 202.49.140.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.164.0/24^24-29, 202.50.246.0/24^24-29, 202.95.250.0/24^24-29, 202.129.253.0/24^24-29, 210.54.12.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.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: benny.treefoot(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20090817 source: NZRR ------------------------------------------------------------

1 0

Telstraclear international proxy?
by Jethro Carr 13 Aug '09

13 Aug '09

hi all, I am seeing an unusual problem with accessing international sites which I believe is being caused by a proxy on international HTTP access for Telstraclear cable internet users. I was attempting to setup virtualhosts on a new webserver (US based) and added entries to /etc/hosts in order to test the sites before I updated the DNS records. However, any access attempt to the new server on port 80 would just return the current production site, which was running on a different server (also in the US). Confirmed with tcpdump that my packets were leaving my computer for the correct IP. There is no proxy in place on my network. I believe there is some kind of proxy/cache for international traffic from Telstraclear's cable network. The proxy is set up in such a way, it ignores the destination IP address being requested and instead takes the requested hostname, resolves it via DNS and fetches the page from the resolved server IP. DEMONSTRATION If I take an international IP and use it for my browser's proxy settings, I find that I can use that IP as a proxy to access any other international website (but not domestic). eg: 74.125.67.100 (google.com) 212.58.254.252 (bbc.com) Using either IP as a proxy will allow me to reach any other international site, but will not allow access to domestic sites (returns blank page). ASSISTANCE Has anyone seen this problem before or know of any caching being taken place by Telstraclear? Would also be good to know if it's specific to Telstraclear cable customers, or other Telstraclear customers as well. Any advice on how I might be able to query the proxy to identify it's owner would be appreciated. thanks, jethro -- Jethro Carr www.jethrocarr.com/index.php?cms=blog www.amberdms.com

11 16

What is more important? - ipv4 vs. routing table size
by Skeeve Stevens 13 Aug '09

13 Aug '09

Hey all, I'd like to stimulate some discussion regarding IPv4 conservation vs. The size of the routing table. I'd like to hear what people think is more important - and why - which it is more important - or a miz? IPv4 conservation - possibly allocating smaller default allocations - or making it easier (/24, /23) vs. The size or the routing table. If by a more conservative allocation above was done, and the world table jumped to 400, 500 thousands or more routes - what implications would this have on routers and so on. APNIC's minimum is a /22 (was a /19 in 2000) (4 * /24's) ARIN is a /20 to ISPs (16 * /24's) RIPE is a /21 (8 * /24's) LANIC is a /21 (I think) AFRINIC is a /22 (4 * /24's) There are smaller hosting companies out there (here in ANZ at least) that want to be on, hosting, multi-homed, but only need a /24 or /23, but they're given the minimum allocation on a /22 - whether they need it or not. Thoughts? -- 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? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

5 5

KIWICON ]|[ - 2009 - Call For Papers
by Kiwicon <3 12 Aug '09

12 Aug '09

A wise deadite captain once yelled "Cry Havoc and let loose the Dogs of War!". Quite frankly, we couldn't have said it better ourselves: ~~ ~~ || || @@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@\___ @@@@@@@@@@@@@@@@@@ \ @@@@@@@@@@@@@@@@@ X___/ \/ KIWICON ]|[ 28TH & 29TH NOVEMBER 2009 With a current record of three arrests, seven conceptions and one committal Kiwicon is back for 2k9. The time has come to fake up an abstract and submit it to the Kiwicon Crue for judgement. In the coming months, we predict you will spend more time dreaming of kudos and UID 0 than actually working on your slides, since you'll be doing them the night before anyway. It's not New Zealand's only security conference, but it is the one where you're more likely to get a standing ovation for scanning an entire country than pointed questions regarding whether you were, perhaps, a little reckless in accessing systems without authorisation. _ _-(")- `%%%%% `KIWICON` // \\ The Crue holds a special place in their bowels for those who are aggravated that Kiwicon is held on a weekend so they don't get time off work. It is a gathering for those who are passionate about security. It has been hacked together by the .nz security scene for the .nz security community. Following in the tradition of previous cons, the atmosphere is extremely laid back; even the feds don't wear suits. Kiwicon is about sharing information. It's about intersections and cross-pollination and dissemination and other nouns disturbing reminiscent of a pre-AIDs key party. Sure, you could bring your RFID readers, your lockpicks or even your back track DVD but mostly you just need to bring yourself and the willingness to learn. For a little con down under we don't do too bad. Previously, Kiwicon has featured: the Crackstation, iKat (last seen at a airport near you), layer two telco shenanigans, a video montage of boardrooms across Japan, old school phreaking on new school kit, exposure of RIM's failure to hide their snooping capabilities, fun with the SCADA systems, making Microsoft look like turkeys, nuking various heap protections from space, and of course fucking up the certificate chain of your new passport. _ _-(")- `%%%%% // \\ `THE VENUE` The Crue is aware that location is everything, so once again we will be invading the Pipitea Campus which is surrounded by prestigious Wellington buildings such as Parliament house, the (partly renovated and badly secured) High Court, Ministry of Defence and various telecommunication hubs. All services are handy to the venue as well (train station, taxi rank, burger caravan, police cells / court etc). Caffeination will be provided by the lovely folks at Sweet Fanny-Anne's. _ _-(")- `%%%%% // \\ `THE PRICE` A recession-proof fifty bucks for the employed. Students and those otherwise supported by our precious taxpayer dollars (this does not include Members of Parliament) will pay $30. GST receipts will be available on request. The Crue will endeavour to leverage its synergies to architect a compelling ROI solution. _ _-(")- `%%%%% // \\ `THE TOPICS` Social networking/automated stalking, Cellular Networks (GSM,2degrees, openbts), State-sponsored surveillance, Malware (Viruses, Botnets), The Scam of EAL Certification, Industrial Espionage, Reverse Engineering, The Failwhale Rider, Virtualisation, Flash mobs, WebApps, 0hday The schedule will be made up as we go, so fifteen minutes or thirty minutes worth of material should be submitted as fifteen or thirty minutes worth of talk. We do place an upper limit of an hour (including questions), as anything longer than that can continue at the pub. _ _-(")- `%%%%% // \\ `SUBMISSIONS` These need to be in by the Witching Hour of the 31st October (NZST). Expats and wanna-be Kiwis will want to get their submissions in by 10th October, when we're going to be announcing the first round of Interesting Stuff. To submit a presentation to Kiwicon2k9, send an email to cfp(a)kiwicon.org with the following information: * Name or Handle: * Country of Residence: * Employer (if applicable): * Presentation Title: * Presentation Length: * Presentation Synopsis: * Brief Bio: If you do not provide a bio, one will be provided for you. _ _-(")- `%%%%% // \\ `BOTTOM LINE` The Crue want you to submit your talk to Kiwicon or the cute little header sheep gets it. _ -(")- `%%%%% // \\ `CONTACT` Email us: kiwicon(a)kiwicon.org Check the site: https://www.kiwicon.org/ Drop by silc: silc.kiwicon.org:2706/kiwicon Join the list: hackers-subscribe(a)kiwicon.org CFP online at https://kiwicon.org/cfp2k9.txt

1 0

Cable cuts in Asia
by Juha Saarinen 12 Aug '09

12 Aug '09

Reading in Commsday and Computerworld Singapore that APCN2, APCN, EAC and SMW3 near Taiwan have developed faults, possibly due to typhoon Morakot. Anyone in NZ noticing the effect of that? -- Juha

2 1

175/8 and 182/8 allocated to APNIC
by Leo Vegoda 11 Aug '09

11 Aug '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The IANA IPv4 registry has been updated to reflect the allocation of two /8 IPv4 blocks to APNIC in August 2009: 175/8 and 182/8. You can find the IANA IPv4 registry at: http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt Please update your filters as appropriate. Regards, Leo Vegoda Number Resources Manager, IANA -----BEGIN PGP SIGNATURE----- Version: 9.10.0.500 wj8DBQFKguZyvBLymJnAzRwRAmDCAKCCnxLNmk32v+sm786x5RyVLnLBDACcCu5I zCs7FdAdkIZRnfNtuVyVB0s= =6huK -----END PGP SIGNATURE-----

1 0

Re: [nznog] Telecom International HTTP Caching
by Paul Tinson 11 Aug '09

11 Aug '09

As a general rule if the content is in a page that gets retrieved by the cache it will be cached and served from the cache to subsequent requests. This includes mp3 files if they are an embedded object. If the mp3 is a single file then I would not expect it to be cached in parts, so it should not be missing pieces. If it's a streaming mp3 that may be different and if you supply an example URL I can check this. If you don't want it cached or want to control the time we keep it in cache then you can use cache control directives and expiry meta tags in the page. At this point in time we have not enabled caching of streaming media. If you have a specific example URL please send it to me and I can double check though. If we have cached it I will look into why. I am happy to look into specific examples of issues, but if you have a wider service effecting issues please continue to use the helpdesk as this will result in calls being handled correctly and not left unattended on the list. Hope this answers your questions. Regards Paul -----Original Message----- From: Richard Hulse [mailto:Richard.Hulse(a)radionz.co.nz] Sent: Wednesday, 12 August 2009 9:00 a.m. To: nznog; Paul Tinson Subject: Re: [nznog] Telecom International HTTP Caching Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

5 5

Re: [nznog] Telecom International HTTP Caching
by Richard Hulse 11 Aug '09

11 Aug '09

Hi Paul, I'll ask this on the list, as there are quite a few (other) audio and video content providers here... How will the cache handle MP3s that are served via HTTP? Is this content you want to cache? Should we be setting some sort of header to make it work better? Willl you also be caching on-demand Windows Media content? I ask because I have noticed that some of our visitors complain of Mp3 audio that is truncated or has bits missing out of the middle. It seems to clear itself after a few hours. cheers, Richard Hulse Webmaster Radio NZ

1 0

Telecom International HTTP Caching
by Paul Tinson 11 Aug '09

11 Aug '09

Good Morning, Telecom would like to advise that over the coming weeks we will be extending our international http caching service. This work should go unnoticed but if you or your customers do experience a loss of international browsing then please contact the Broadband Helpdesk on: adsl_helpdesk(a)xtra.co.nz Please make sure the subject has "HTTP Caching" included so that the Helpdesk can filter on these issues. If you would like to talk to the Helpdesk then please phone: 0800 22 55 98 Please state that you believe this to be an http caching issue when raising the case so that it will be routed to the correct resources. NB. Please note that the service is only in place for Telecom Broadband Customers and "International" in this case is based on the international routing tables, as such some domestic sites may appear to Telecom as international content. If you have any specific questions about the service then please feel free to post the questions on this mailing list and as time allows they will be answered. Regards Paul Tinson Senior Specialist Web App Services Shared & Other IS Operations E paul.tinson(a)telecom.co.nz <mailto:paul.tinson(a)telecom.co.nz> W www.telecom.co.nz <http://www.telecom.co.nz> Level 9, 31 Airedale Street Auckland ________________________________ "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 4

Re: [nznog] Telstraclear international proxy?
by Anton Smith 10 Aug '09

10 Aug '09

> Message: 12 > Date: Tue, 11 Aug 2009 10:31:53 +1200 > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog(a)list.waikato.ac.nz > Message-ID: <4A809FD9.3040700(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 11/08/09 12:31 AM, Anton Smith wrote: > > In the beginning when diagnosing the problem, an engineer might not > > even know that the problem lies with Telstra, and we have seen people > > posting http headers and so on in the past wondering what was going > > on. > > > > I don't believe that was the case in this instance. It was not a > general query about a general problem. It was a specific technical > issue with a specific ISP. In that case a trouble ticket should be > logged with the ISP first, then post to the list. I'd even accept if > these were both done at the same time. > > To not give the ISP involved a chance to address the issue through > normal customer support channels is not giving them a fair go. > Some ISPs are not very good at customer support, but if you don't log > the call, then how can you expect anything of them. > > I'll explain some more why this is so important; > In years gone by, NZNOG was seen by the major Telcos and some ISPs as a > bunch of troublemakers. I know this for a fact because I've worked for > them while they held this opinion. They viewed NZNOG as a group of > individuals constantly waiting to bash them at any opportunity. The > minute that someone found a bug, or a technical issue, they would post > it first to NZNOG and everyone would hang the associated ISP/Telco out > to dry. > > As such, no one from those organisations joined NZNOG, contributed to > NZNOG, attended the NZNOG conference, etc etc etc. > > Over time we have worked very hard to re-engage with the ISPs and > Telcos, making NZNOG a place where they can derive benefit from > contributing to. Just today we see Paul Tinson posting about Telecom's > cache changes. I doubt anyone would disagree that this is the sort of > involvement that we want. > > Do you think that TelstraClear are going to engage with NZNOG if just > the week previously an NZNOG member was posting publically about > technical issues on their network before giving them a chance to address > them? > > It's a bit like someone buying a shirt at a store, being unhappy with > it, and doing a spot on Campbell Live before going back to the shop and > asking for a refund. Now sure, Campbell Live has its place. It even > has a place for long running retail disputes, but it shouldn't be the > first port of call. And neither should NZNOG. > > We work hard with the Telcos to keep them engaged (the benefits of which > can be seen in Telecoms post this morning), please keep this in mind > when posting. Just make sure you've worked with them first. If you > have and they did a bad job, then by all means post and all bets are off =) > > > Dean > Hi Dean, Given the general difficulties in resolving problems with various ISP/Carriers it is sometimes a fact that the only place you can learn what you need to is here. I'm very heartened by the Telecom post about their caching, and being very specific about the path to follow if there are issues encountered. That is exactly what I believe is missing from Telstra. Perhaps our discussions here (that may be deemed off topic in which case I shall raise the virtues of beer later) are actually constructive in that they can help highlight to carriers how a proactive approach might be used. I do however completely agree with you that it is important to foster a greater sense of community that includes the carriers, ISPs and NZNOG. It is important that NZNOG is not just seen as a bashing list. However, I did not really see that the original post about the caching was negative, and far from "bashing".. so I hardly think that the relationship between NZNOG and Telstra would have been damaged. Maybe my own post had a disgruntled tone, for which I apologise - I shouldn't have done that. I do believe that proactive approaches from the bigger players towards the list (like the Telecom post) are brilliant, and I encourage others (Telstra) to do something similar. Regards, Anton

2 1

Re: [nznog] NZNOG Digest, Vol 80, Issue 9
by Anton Smith 10 Aug '09

10 Aug '09

Hi Dean, While I agree with the general notion that people should go to the ISP directly first, in the Telstra case with their transparent proxy I think it is okay posting here. Mainly because most people on this list know it is there, while most people on the ISPs desk probably don't. Telstra could make this a bit better for themselves by being more verbose about the proxies presence, rather than getting various levels of brokenness complaints. In the beginning when diagnosing the problem, an engineer might not even know that the problem lies with Telstra, and we have seen people posting http headers and so on in the past wondering what was going on. I just think that this kind of thing is a natural side effect of an ill publicised (and some would argue, annoying) network feature, and if Telstra are not proactive about letting people know they have it and the problems that may arise, then they deserve the occasional mail list post. Regards, Anton Disclaimer: I have run into their proxy before due to asymmetric routing + transparent proxy unhappiness (resulted in what looked like a black hole). On Mon, Aug 10, 2009 at 2:00 AM, <nznog-request(a)list.waikato.ac.nz> wrote: > From: Dean Pemberton <nznog(a)deanpemberton.com> > Subject: Re: [nznog] Telstraclear international proxy? > To: nznog <nznog(a)list.waikato.ac.nz> > Message-ID: <4A7F6257.9080104(a)deanpemberton.com> > Content-Type: text/plain; charset=ISO-8859-1 > > > I'd like to take this opportunity to remind people that the appropriate > way to handle situations like this is to log a support call with the > ISPs helpdesk before posting support questions to this list. > > If you believe that it is a problem which effects the NZ Operator > community as a whole and you have exhausted your options (including > escalations) with the ISP concerned then it is maybe appropriate to post. > > This is to eliminate the situation where an ISP finds its name/helpdesk > practices used in vain throughout a mailing list without being given a > chance to put the matter right in private first. > > > Thanks > Dean

5 4

Re: [nznog] Telstraclear international proxy?
by Philip D'Ath 09 Aug '09

09 Aug '09

I can see that becoming urban slang. -----Original Message----- From: Steve Phillips Sent: Mon 10/08/2009 15:15 To: nznog Subject: Re: [nznog] Telstraclear international proxy? Sorry for the completely pointless empty post. My cat did it ! -- Steve. Steve Phillips wrote: > Gordon Smith wrote: >> The bulk of the caching issues service providers are asked to deal >> with come about because people don't know how to configure web servers. >> >> Meta tags and expires are actually useful, but it seems that there are >> always a few people that don't use them, even though their content is >> dynamic.

2 1

Re: [nznog] Microsoft xbox spam ?
by Ian Batterbee 09 Aug '09

09 Aug '09

Just to head off further replies on this thread - I believe the problem was that I was forced to register with microsoft's games for windows (or some such name) when I installed GTA4 many months ago, and it seems that Microsoft have emailed everyone on there, rather than just xbox platform owners. So although unwanted, it was probably legit and just an oversight on their part. Ian Batterbee wrote: > >> Has anyone else received spam from Microsoft about an XBox service update >> ? >> >>

1 0

Google Wave
by James Jones 09 Aug '09

09 Aug '09

I am just curious if anyone else on NZNOG is play with Wave Federation Server? James Jones Managing Director Freedom Networks +64 6 3678300 +1 413 771 1402 james(a)freedomnet.co.nz

2 1

Microsoft xbox spam ?
by Ian Batterbee 07 Aug '09

07 Aug '09

Has anyone else received spam from Microsoft about an XBox service update ? The message claims that I received it as part of my XBox Live subscription, but since I don't have such a subscription, and don't even own an xbox, I think they're telling porkies.

1 0

APNIC training August 2009
by Elly Tawhai 06 Aug '09

06 Aug '09

________________________________________________________________________ APNIC training and hostmaster consultations in Wellington and Auckland, New Zealand, 3-4/5-6 August 2009 ________________________________________________________________________ Dear All, APNIC is pleased to invite you to attend the following training courses and hostmaster consultation sessions in New Zealand: Course: IRM (Internet Resource Management) and APNIC update Date: 3 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Course: IRM (Internet Resource Management) Date: 5 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Event: Hostmaster individual consultations Date: 4 August 2009 Location: Wellington, New Zealand Venue: InternetNZ Level 10 Exchange Place 5 - 7 Willeston Street Event: Hostmaster individual consultations Date: 6 August 2009 Location: Auckland, New Zealand Venue: CallPlus Level 4, Qantas House 191 Queen Street Fees: Fees are for training only. There is no charge for the consultation sessions Pay onsite (cash only) Pay online (credit card) ----------------------- ------------------------ APNIC members: NZD 100 AUD 65 Others: NZD 130 AUD 85 (The online fee is charged in Australian dollars and includes a 20% discount) Notes: ------ - The Hostmaster consultations and training sessions are two distinct events with separate registration processes. - Training courses run from 09:00 to 17:00. - Hostmaster consultations fun from 09:30 to 13:00. - Lunch, refreshments, and training materials are provided. - Seats are limited and the registration is on a 'first come-first served' basis with priority given to APNIC members. To register for the Wellington training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… To register for the Auckland training, please go to: http://www.apnic.net/events/whats-on/training-events/calendar/events/2009/n… For course information please go to: http://www.apnic.net/services/services-apnic-provides/training/courses/core… If you have problems registering please contact stella(a)apnic.net Hostmaster consultations ------------------------ APNIC is offering free, individual Hostmaster consultation sessions. At these sessions you can ask about: - How to request IPv4, IPv6, and AS numbers from APNIC - How APNIC hostmasters will evaluate your resource request - Current policies for IP and AS number management in the APNIC region - How to maintain and update your resource registration record in the APNIC Whois Database - Any individual issues you might have To register for the Hostmaster consultations, please email: elly(a)apnic.net Best regards, APNIC training team ________________________________________________________________________ APNIC Training training(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 ________________________________________________________________________

2 1

FW: Content again - legality question
by Skeeve Stevens 06 Aug '09

06 Aug '09

Again, any thoughts on the NZ situation (legally) regarding this? -- 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? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:59 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content again - legality question Hey all, Content question again - but this time a legal question. For any content that is 'freely available on the web' - what is the legality of acquiring this content and delivering it locally? For example.. many TV stations are uploading full episodes onto their websites after the show has aired. YouTube would be another example. I am only talking about free content - which is not paid for, but freely downloadable from websites. I guess I am talking about a 'pre-caching' kind of situation. Also, does anyone know at what point music becomes legally free to use in Australia?... like books after 50years after the authors death (in the US it is 20). ...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? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

8 9

FW: Content - Music, Movies, TV
by Skeeve Stevens 05 Aug '09

05 Aug '09

Hey all, Any comments on the NZ situation regarding this? -- 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? From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens Sent: Friday, 7 August 2009 12:55 AM To: ausnog(a)ausnog.net Subject: [AusNOG] Content - Music, Movies, TV Hey all, I have multiple clients who are wanting to sell content to their customers. There are multiple scenarios: - ISP's to their users - Hotspots in accommodation locations wanting to sell it to visitors - similar to in-room entertainment in big hotels - Providers of in building connectivity who want to delivery triple-play to their residents Does anyone know of any aggregators of this kind of content with the studios and so on? ...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? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.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.126.80.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, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.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.218.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.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.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, 123.100.117.192/27^27-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 20090727 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, 119.47.112.0/20^20-29, 124.248.128.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.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.126.80.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, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.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.218.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.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.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, 123.100.117.192/27^27-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 20090806 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 05 Aug '09

05 Aug '09

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, 119.47.112.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.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.126.80.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, 124.248.140.0/22^22-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 192.88.85.0/24^24-29, 192.88.99.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.218.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.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.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, 123.100.117.192/27^27-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 20090727 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, 119.47.112.0/20^20-29, 124.248.128.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.191.32.0/20^20-29, 210.48.160.0/20^20-29, 112.109.80.0/21^21-29, 120.89.80.0/21^21-29, 192.173.16.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.126.80.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, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 203.84.134.0/23^23-29, 192.88.85.0/24^24-29, 192.88.99.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.218.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.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.49.144.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, 123.100.117.192/27^27-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 20090806 source: NZRR ------------------------------------------------------------

1 0

Re: [nznog] [AusNOG] APNIC Policy SIG Co-Chair
by Skeeve Stevens 05 Aug '09

05 Aug '09

Hey there Andy, I've actually put myself down as well.... nowhere near as much experience as you clearly... just trying to get some ANZ representation. Will you need a co-chair-assistant lacky? ;-) Well, if you win, awesome... maybe next time for me! Clearly CN will have the votes.... I wonder how many from ANZ are going to Beijing? ...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: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog- > bounces(a)lists.ausnog.net] On Behalf Of Andy Linton > Sent: Wednesday, 5 August 2009 12:41 PM > To: ausnog(a)lists.ausnog.net > Subject: [AusNOG] APNIC Policy SIG Co-Chair > > This is a bit cheeky of me - join the AusNOG list and post off topic > immediateley but... > > There was a recent announcement on the APNIC sig-policy mailing list > seeking candidates for this role. You can see the announcement at: > > http://mailman.apnic.net/mailing-lists/sig- > policy/archive/2009/08/msg00005.html > > I have submitted a response to this (http://notnil.org/) and I'd like > to > ask for your support if we get to the point where there is an election > process. If I get the nod I will buy beer but you'll need to be in > Beijing for the APNIC meeting. > > I'd also encourage you to consider the proposals that are being > discussed on the sig-policy list and which will be on the agenda at > the Beijing meeting. A number of these could have an impact on > operations over the next year or so. See > http://www.apnic.net/community/policy/proposals > _______________________________________________ > AusNOG mailing list > AusNOG(a)lists.ausnog.net > http://lists.ausnog.net/mailman/listinfo/ausnog

3 3

Web Base Connectivity
by Dan Clark 04 Aug '09

04 Aug '09

Gidday, has anyone else got connectivity issues through to www.webabse.co.nz ? Connecting from XTRA/Telecom doesn't seem to get past MaxNet but connecting from via APE its fine?? Regards Dan Clark

9 9

Re: [nznog] Web Base Connectivity
by jamie baddeley 04 Aug '09

04 Aug '09

I thought of that too, but sadly it measures in a single dimension. And AFAIK it's not distributed. Happy to be proved wrong. jamie On Tue, 2009-08-04 at 21:21 +1200, Nathan Ward wrote: > Also, http://downforeveryoneorjustme.com/ > > On 4/08/2009, at 8:03 PM, jamie baddeley wrote: > > > I think something like this within NZ is quite good. > > > > http://internethealthreport.com/ > > > > Would help with operational problems like this. > > > > Surely WAND could do that thing? I think there's real value we could > > all > > add to that idea. > > > > It's nice to be able to go to a place which basically gives a > > dashboard > > display. Maybe an iPhone app or something for all you Beret wearing > > Apple folks out there ;-) > > > > Who's going to LCA Next year? > > > > cheers, > > > > jamie > > > > On Tue, 2009-08-04 at 18:58 +1200, Gerard Creamer wrote: > >> And OK from my TelstraClear cable connection: > >> > >> | > >> ------------------------------------------------------------------------------------------| > >> | WinMTR > >> statistics | > >> | Host - % | Sent | Recv | > >> Best | > >> Avrg | Wrst | Last | > >> | > >> ------------------------------------------------| > >> ------|------|------|------|------|------| > >> | 192.168.9.1 - 0 | 64 | 64 | 0 > >> | 1 | 93 | 0 | > >> | 121-73-66-1.cable.telstraclear.net - 0 | 64 | 64 | 0 > >> | 26 | 360 | 15 | > >> |ge-2-0-0-874-ie2-internet.telstraclear.net - 0 | 64 | 63 > >> | 15 > >> | 23 | 62 | 31 | > >> |ge-2-0-0-874-ie1-internet.telstraclear.net - 0 | 64 | 64 > >> | 15 > >> | 20 | 46 | 15 | > >> | 203.167.232.174 - 0 | 64 | 64 | 15 > >> | 28 | 203 | 31 | > >> | gi6-1.hsa2.alb.maxnet.net.nz - 0 | 64 | 64 | 15 > >> | 31 | 250 | 31 | > >> | gi3-819.akmn1-br2.webhost.co.nz - 0 | 64 | 64 | 15 > >> | 20 | 78 | 15 | > >> | gi1-9.akmn1-csw2.webhost.co.nz - 0 | 63 | 63 | 15 > >> | 22 | 62 | 31 | > >> | webbase.co.nz - 0 | 63 | 63 | 15 > >> | 26 | 125 | 31 | > >> |________________________________________________|______|______| > >> ______|______|______|______| > >> WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( > >> stanimir(a)cr.nivis.com ) > >> > >> Cheers, > >> Gerard > >> > >> > >> Lindsay Druett wrote: > >>> Now, did you mean www.webbase.co.nz <http://www.webbase.co.nz> ? > >>> > >>> lindsay(a)alcyone:~$ traceroute webbase.co.nz > >>> traceroute to webbase.co.nz (203.89.178.165), 30 hops max, 60 byte > >>> packets > >>> 1 tehlinzathome-14.fx.net.nz (131.203.124.14) 19.036 ms 19.381 ms > >>> 19.732 ms > >>> 2 GigabitEthernet0-3-200.akkin-rt2.fx.net.nz (131.203.80.254) > >>> 8.232 > >>> ms 9.912 ms 11.120 ms > >>> 3 131.203.252.130 (131.203.252.130) 12.144 ms 13.428 ms 14.687 > >>> ms > >>> 4 gi1-8.akmn1-csw2.webhost.co.nz (119.47.119.142) 15.706 ms > >>> 16.710 > >>> ms 17.737 ms > >>> 5 webbase.co.nz (203.89.178.165) 19.917 ms 20.276 ms 21.200 ms > >>> > >>> > >>> On Tue, 2009-08-04 at 18:28 +1200, Dan Clark wrote: > >>>> Gidday, has anyone else got connectivity issues through to > >>>> www.webabse.co.nz <http://www.webabse.co.nz>? > >>>> Connecting from XTRA/Telecom doesn't seem to get past MaxNet but > >>>> connecting from via APE its fine?? > >>>> > >>>> Regards > >>>> Dan Clark > >>>> > >>>> -- > >>>> This message has been scanned for viruses and > >>>> dangerous content by *MailScanner <http://www.mailscanner.info/>*, > >>>> and is > >>>> believed to be clean. > >>>> _______________________________________________ > >>>> NZNOG mailing list > >>>> NZNOG(a)list.waikato.ac.nz <mailto:NZNOG(a)list.waikato.ac.nz> > >>>> http://list.waikato.ac.nz/mailman/listinfo/nznog > >>>> > >>> > >>> -- > >>> This message has been scanned for viruses and > >>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, > >>> and is > >>> believed to be clean. > >>> ------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> NZNOG mailing list > >>> NZNOG(a)list.waikato.ac.nz > >>> http://list.waikato.ac.nz/mailman/listinfo/nznog > >>> > >> _______________________________________________ > >> NZNOG mailing list > >> NZNOG(a)list.waikato.ac.nz > >> http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > > > !DSPAM:22,4a77eb4773596020614038! > > > > > > -- > Nathan Ward

4 4

APNIC Policy SIG Co-Chair
by Andy Linton 04 Aug '09

04 Aug '09

There was a recent announcement on the APNIC sig-policy mailing list seeking candidates for this role. You can see the announcement at: http://mailman.apnic.net/mailing-lists/sig-policy/archive/2009/08/msg00005.… I have submitted a response to this and I'd like to ask for your support if we get to the point where there is an election process. If I get the nod I will buy beer but you'll need to be in Beijing for the APNIC meeting. I'd also encourage you to consider the proposals that are being discussed on the sig-policy list and which will be on the agenda at the Beijing meeting. A number of these could have an impact on operations over the next year or so. See http://www.apnic.net/community/policy/proposals

1 0

Cisco.com Outage FYI
by Skeeve Stevens 03 Aug '09

03 Aug '09

Cisco.com outage http://blogs.cisco.com/news/comments/final_update_ciscocom_outage/ -- 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? Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.

1 1