- NZNOG - lists.nznog.org

RE: [nznog] TelstraClear Inhternational / National Traffic billing
by Craig Spiers 14 Jun '04

14 Jun '04

Well.. You could get a link to both, but the only real benefit would be splitting the cost between two (probably slightly more expensive this way as a separate circuit is needed for both - generally cheaper to upgrade a 10meg to 100meg than it is to install 2x 10meg eg. one from each telco) However, you would have a shorter data path.. As with two circuits, the data goes direct to both carriers.. With just one circuit, data to clear, goes via telecom.. (provided they keep the peering between them). -----Original Message----- From: jfp [mailto:jfp(a)clearfield.com] Sent: Tuesday, 15 June 2004 12:16 p.m. To: 'Craig Spiers' Subject: RE: [nznog] TelstraClear Inhternational / National Traffic billing > They shouldn't be connected to the internet at all! They should be > shot in the foot for having such poor routing :) > > NZ > US > NZ :) Not being in the ISP business, but a client of ISP's, could you explain that one to me. I thought the whole point of peering at the APE and WIX was that you did not need to get point to point link to other providers. Why do you NEED to get a link to one of the telco's? jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Clearfield Software Ltd Phone (+64-9) 358 2081 4th Floor 8-10 Whitaker Place Fax (+64-9) 358 2083 P O Box 2348 Auckland, New Zealand ------------------------------------------------------------------------

1 0

Re: Map/schematic over NZ Internet connectivity?
by Kerry Milestone 13 Jun '04

13 Jun '04

The National Library of New Zealand has been given a lot! of money, i expect they will have a good map soon......... http://www.beehive.govt.nz/ViewDocument.cfm?DocumentID=19882 And an older National Business Review article: http://www.nbr.co.nz/home/column_article.asp?id=1978&cid=1&cname=Media Maybe some of it can be spent on peering networks together to help with the flow of _all_ websites ending in .nz to be harvested daily by the NatLib... This task is now part of the National Library Bill and can be thought of being the same as the Legal Deposit legislation.

1 0

xtra's MTA again??
by Dan Clark 13 Jun '04

13 Jun '04

Hi Guys, just wondering if anyone else isn't getting any mail through to XTRA. If you are and your mta is MailMarshal please let me know also, from last time there appeared to be an issue with MailMarshal threads. Kind Regards Dan Clark Network Manager Synaptic Ltd

4 3

RE: Map/schematic over NZ Internet connectivity?
by Brendan Murray 12 Jun '04

12 Jun '04

> Message: 3 > Date: Sun, 13 Jun 2004 11:26:20 +1200 > From: Juha Saarinen <juha(a)saarinen.org> > Subject: Re: [nznog] Map/schematic over NZ Internet connectivity? > To: jon.brewer(a)worldnet.att.net > Cc: 'NZ NOG' <nznog(a)list.waikato.ac.nz> > Message-ID: <40CB911C.3010600(a)saarinen.org> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Jonathan Brewer wrote: > > > I tried InternetNZ with this very question about a year ago, and the > > answer was no. > > I guess there was no follow-up along the lines of "... but we're working > on it"? Give me good/adequate/useful/whatever reasons for doing it and I'll take it to the INZ tech committee. Always nice to add things to the ToDo list. More usefully - others on this list probably already have some/all of a map - where can we access that information if INZ does decide its worth putting together? And how do we keep it up to date?

2 1

Re: [nznog] Zombies
by Ewen McNeill 10 Jun '04

10 Jun '04

In message <20040610051613.GJ20881(a)stateless>, Nicholas Lee writes: >On Thu, Jun 10, 2004 at 04:58:31PM +1200, Ewen McNeill wrote: >> [... suggesting] anti-spam legislation, a legal duty be placed on people >> not to connect/allow to remain connected an insecure/0wned/infected >> system under their control. > >Unlike vehicles, access to the internet for most people is not via a >"public road". [...] >A WOF/license for driving the internet just seems like needless legisation. I actually didn't suggest a WOF/license for driving on the Internet (this time -- although I do actually think it's a good idea). What I suggested was that those who have allowed systems they own to become unsafe/damaged so that they cause harm to others should be made responsible for that harm. And it doesn't seem like needless legislation to me. It's not _my_ systems (or any of the ones I'm responsible for administering) which are sending thousands of spam messages, viruses, worms, to machines across the world. I just get to receive thousands of them a day via all these machines of people who are not taking responisbility for the systems they're connecting to a common resource (viz, the Internet). As Juha says there is a problem with patches not being available. I'd be quite happy to allow "no vendor patch" as a complete defense for the end user (although if the issue is well known the vendor should perhaps be culpable). I'd even be willing to conceed "vendor patch too recently released, couldn't patch everything" with in a reasonable amount of time of the patch coming out. Simply persuading someone to take responsibility for the never-been-patched, installed-stuff-at-random, insecure-OS-design boxes would dramatically reduce the problem. >ISPs already have the power to regulate users this way via their TOS. Its >clear though that all ISPs would have to subscribe to the above for it >to have long-term effect. The days of ISPs taking responsibility for the actions of their users appear to be a fading memory. It's unlikely any ISP would block users with infected machines these days unless all ISPs did it; the only way that all ISPs are likely to do it is if it's a legal requirement. (Otherwise it's a prisoner's dilemma situation.) Ewen

7 6

Re: [nznog] Zombies
by neil gardner 10 Jun '04

10 Jun '04

OK, serious thought here... Bear with me... I may be a) Describing an existing system or b) way off base. Transparent SMTP proxy intercepts all messages and maintains a running total of emails sent per source IP. This running total is actually stored as a time distribution (ie. 10 emails in 10 minutes, then none in 10, then 100 in ten etc) Rulebase periodically examines this time distribution for each source IP. Something like If last 3 matches are >10, >10, >10 then block for 30 minutes per strikeout(sourceIP) and increment strikeout(sourceIP) by one. After expiry of downtime, open them up again. After (say) 90 minutes of non-abhorrent behaviour, decrement strikeout(sourceip) by one. If strikeout(sourceIP) gets to threshold (Say 10) then email user and 48 hours later disable account unless they contact helpdesk and claim to have addressed the situation. You probably want cleverer rules to identify bursts of email, and possibly a training period with rules referrent to earlier data from the same source - this should be able to reliably identify legitimate high volume users - especially if you build in a time of day factor. This should quickly throttle zombies and disable the account if not fixed, but allow for brief infections to be throttled, and if fixed, NOT need manual intervention to unblock. It may impact some legit heavy email users, but mail will bounce, and it should fix itself. Just a thought. Cheers - N. >>> Simon Lyall <simon(a)darkmere.gen.nz> 10/06/2004 1:46:38 p.m. >>> It looks like there are lot of NZ based Zombies sending very large amounts of Spam ( much of it in German) to some ISPs. This has really been going hard over the last hour. I'm seeing adsl accounts at xtra, iprolink and ihug, xtra dialups etc etc. As a related issue, how do people feel about a whitelist RBL of NZ mail servers, It looks like it's not good to just whitelist NZ IPs -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

6 7

Re: [nznog] Zombies
by Ewen McNeill 09 Jun '04

09 Jun '04

In message <s0c876cc.089(a)LEO.ALLIEDTELESYN.CO.NZ>, "neil gardner" writes: >To be fair though, in mentioning an opt-out system I was thinking of >clueful users deliberately running their own servers that would notice >within minutes that port 25 had been blocked - not the SMTP AUTH crowd >which may be significantly less clued up and not notice why their >previously working 'Email Thingy" isn't working anymore. The clueful users can always build tunnels and route stuff through the tunnels. I do this from my laptop when working in various organisations where I still want to send mail via my own mail server (because, eg, it's the only one listed in the SPF rules). SMTP AUTH is harder, but at least as a first cut simply permitting connections that did SMTP AUTH would probably select for the "good" connections and ignore the bad ones. Much the same for STARTTLS -- anything using that is probably not malware, at least at present. Most malware barely manages to interoperate with SMTP servers let alone actually supporting "fancy" features. As I've suggested before blocking some of these services by default, and providing an "enable this service again" automatic system for clueful users would be nearly as useful as trying to do layer-7 filtering on the protocol. It could even require turning on again with every reconnection, totally doing away with the need for the ISP to store anything associating permissions with the user. (Anyone who can't automate a GET of, eg, http://ihaveaclue.$ISP/enable?services=smtp or similar on reconnect doesn't have the necessary clue.) On a related tack, I am seriously considering writing to the appropriate government ministers and suggesting that, as part of their proposed anti-spam legislation, a legal duty be placed on people not to connect/allow to remain connected an insecure/0wned/infected system under their control. With the first breach resulting in mandatory disconnection of the system from the network, not to be reconnected until person had completed a course on "network security" and had their machine certified "cleaned up" by someone appropriate. Subsequent breaches resulting in that and fines and/or longer periods of mandatory disconnection. IMHO such insecure/0wned/infected systems are a nuisance (in the legal sense of the word) and thus the owners of them should be responsible for the damage they cause. Ewen

4 3

Google and MaxNet
by Cameron Kerr 09 Jun '04

09 Jun '04

Hello, is anyone getting `Your client has issued a malformed request' messages from Google when connected via MaxNet? I've tried with lynx, links, and Firefox. I'm getting these messages, not because my client is issuing a malformed request, but rather that MaxNet's transparent proxy is serving this. tcpflow reports the following in the response. Note the line that says `HIT' in it. HTTP/1.0 400 Bad Request Date: Tue, 08 Jun 2004 22:59:04 GMT Content-Type: text/html Server: GFE/1.3 Cneonction: Close <=== Hmmm, this is interesting. Content-Length: 1207 Age: 40 X-Cache: HIT from proxy2.akl1.maxnet.net.nz Connection: close This doesn't always happen under Firefox (it happened the first time, but after that, it worked ok. I'm guessing it's because of the short lifetime (Age: 40 seconds). Can anyone duplicate this? Just to be safe, I've disabled the transparent proxy here, and have no other proxy configured (direct connection). This was happening last night too. -- Cameron Kerr cameron.kerr(a)paradise.net.nz : http://nzgeeks.org/cameron/ Empowered by Perl!

12 22

Re: [nznog] Zombies
by neil gardner 09 Jun '04

09 Jun '04

To be fair though, in mentioning an opt-out system I was thinking of clueful users deliberately running their own servers that would notice within minutes that port 25 had been blocked - not the SMTP AUTH crowd which may be significantly less clued up and not notice why their previously working 'Email Thingy" isn't working anymore. I had the further thought that you could use some higher layer content inspection device to drop all SMTP traffic unless it's either to your own SMTP IP, or part of an SMTP AUTH conversation but that is way less than trivial as you'd need to completely proxy the sessions up until SMTP auth at least.... I'd say it was do-able, but not trivial. Cheers - N. >>> Nathan Ward <nznog(a)daork.net> 10/06/2004 2:50:13 p.m. >>> On 10/06/2004, at 2:43 PM, Perry Lorier wrote: > This breaks SMTP AUTH for people who send mail via another machine on > the Internet, because that host is the only one allowed to send with > SPF. > You conveniently ignored the opt-out system he mentioned. However for such an opt-out system to work, your packet filters would have to adjust themselves as dynamic users log in and out. That would suck. -- Nathan Ward _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

4 3

RE: [nznog] Zombies
by Gordon Smith 09 Jun '04

09 Jun '04

The problem with that would be dynamically assigned addresses, unless you included a lookup being done against your radius databases by the SMTP proxy, so that the user can be identified. Possibly, a better solution would be to analyse netflow data as it hits the collectors, and identify offending machines that way. By using netflow, you can extend detection of worms, etc to include all ports, rather than just port 25 Doing dynamic throttling of infected connections is much more difficult - there's not a large range of equipment out there that can do that reliably, although the Juniper ERX does spring to mind :-) But that's not a box you'd find in most ISPs Cheers, Gordon > -----Original Message----- > From: neil gardner [mailto:neil.gardner(a)alliedtelesyn.co.nz] > Sent: Thursday, 10 June 2004 3:20 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Zombies > > > OK, serious thought here... Bear with me... I may be a) Describing an > existing system or b) way off base. > > Transparent SMTP proxy intercepts all messages and maintains a running > total of emails sent per source IP. This running total is actually > stored as a time distribution (ie. 10 emails in 10 minutes, > then none in > 10, then 100 in ten etc) > > Rulebase periodically examines this time distribution for each source > IP. Something like > > If last 3 matches are >10, >10, >10 then block for 30 minutes per > strikeout(sourceIP) and increment strikeout(sourceIP) by one. > > After expiry of downtime, open them up again. After (say) 90 > minutes of > non-abhorrent behaviour, decrement strikeout(sourceip) by one. > > If strikeout(sourceIP) gets to threshold (Say 10) then email user and > 48 hours later disable account unless they contact helpdesk > and claim to > have addressed the situation. > > You probably want cleverer rules to identify bursts of email, and > possibly a training period with rules referrent to earlier > data from the > same source > - this should be able to reliably identify legitimate high volume > users - especially if you build in a time of day factor. > > This should quickly throttle zombies and disable the account if not > fixed, but allow for brief infections to be throttled, and if > fixed, NOT > need manual intervention to unblock. It may impact some legit heavy > email users, but mail will bounce, and it should fix itself. > > Just a thought. > > Cheers - N. > >

3 2

RE: [nznog] Zombies
by Gordon Smith 09 Jun '04

09 Jun '04

Neil gets my vote. This is by far the best solution I've seen in years :-) And it's extendable to other protocols as well..... Cheers, Gordon

1 0

Re: [nznog] Zombies
by neil gardner 09 Jun '04

09 Jun '04

Point taken. OK, revised suggestion is this: Cut port 25 entirely, when people call to complain, press a button to play this recorded message. "Dear customer, in order to combat the Child pornography, Terrorist communications and Spam being sent by infected computers - WHICH YOU MAY HAVE! - we have blocked all popular email programs form communicating to the Intarweb thingy. In future, please feel free to use http://webmail.isp.co.nz for your email requirements. If on the other hand you support Child Pornography, are a member of an active Terrorist Cell, or wish to get a b1gger p3nis now!, then please press (1) and we'll unblock your evil Email connection." Cheers - Neil G ps. Sorry - I'll get back ontopic by about Tuesday week. :-) >>> Juha Saarinen <juha(a)saarinen.org> 10/06/2004 2:58:56 p.m. >>> neil gardner wrote: > To be fair though, in mentioning an opt-out system I was thinking of > clueful users deliberately running their own servers that would notice > within minutes that port 25 had been blocked - "Hey Mr/Ms Helldesker, how come nobody can send us mail anymore?" -- Juha NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

Re: [nznog] Zombies
by neil gardner 09 Jun '04

09 Jun '04

>>> Simon Lyall <simon(a)darkmere.gen.nz> 10/06/2004 1:46:38 p.m. >>> >It looks like there are lot of NZ based Zombies sending very large amounts >of Spam ( much of it in German) to some ISPs. Would it not be relatively easy to drop all port 25 traffic unless it was directed at your own SMTP server? * (Or are the Zombies sending through your SMTP anyway?) Cheers - N. * - Allow an opt out for anyone that even notices - if they notice, they won't be part of the problem. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

3 2

Trade Me changes
by paul gold 09 Jun '04

09 Jun '04

Please be advised that the Trade Me group of sites are currently undergoing an addressing update. DNS records were changed last night, and all routing for our new address ranges continues to be via our upstream AT&T. Major sites affected; trademe.co.nz oldfriends.co.nz safetrader.co.nz findsomeone.co.nz (findsomeone.com.au, findsomeone.ca and personalstuff.co.nz plus other minority 'skins') circleoffriends.co.nz (circleoffriends.com.au) We are also physically moving the 'farm', which will introduce a number of interruptions and periods of downtime between Thursday 2300 and Friday 0700.

1 0

RE: [nznog] Google and MaxNet
by neil gardner 09 Jun '04

09 Jun '04

>>> "Craig Spiers" <craig(a)concept.net.nz> 10/06/2004 11:10:01 a.m. >>> >Heh.. Telecom ADSL's charges are for the data traveling across the telecom >data network, regardless where its come from.. This is a different situation >altogether.. You know what? I can't figure out if you're joking or serious :-) Really! N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

RE: [nznog] Google and MaxNet
by Regan Murphy 09 Jun '04

09 Jun '04

> In the past, caching has made some sense for accelerating > content to clients. I like it when I download a service pack from microsoft (for example) and the 100MB comes in at 20Mbps instead of the 512kbps that my international pipe is limited to. The fact that it may only technically be local traffic but I get charged for international traffic makes no difference because I would have no choice but to be paying international rates if there was no cache. When security/antivirus vendors release patches and updates is there a large increase in international bandwidth use or do the caches assist there? Caching must also be good for sites where there limited bandwith is at the server end too. -- Regan

4 5

RE: [nznog] Google and MaxNet
by Gordon Smith 08 Jun '04

08 Jun '04

Hahaha... but they were better than some of the other commercial offerings out there. I have heard good things about the more recent squid code (haven't tried it though) - but who wants to maintain bypass lists just because users want to use dodgy web software :-( > -----Original Message----- > From: Tony Wicks [mailto:nzog(a)road.gen.nz] > Sent: Wednesday, 9 June 2004 1:23 p.m. > To: 'David Fox'; 'Steve' > Cc: 'NZ Network Operators Group' > Subject: RE: [nznog] Google and MaxNet > > > Well, maybe it's just that Cacheflows suck ? > > -----Original Message----- > From: David Fox [mailto:foxy(a)morenet.net.nz] > Sent: Wednesday, 9 June 2004 1:12 p.m. > To: Steve > Cc: NZ Network Operators Group > Subject: RE: [nznog] Google and MaxNet > > > I agree wholeheartedly with Steve comments below, the cost saving is > negligible while the required resource to administer was > high. I redeployed > my cache to a new position in our network: it is working very > well as a > footrest under my desk. > > I found removing the cache actually improved overall performance, my > customers - and even managers - noticed the improvement ... > some of them > even rang to say Thanks (that makes a change!) > > David >

1 0

RE: [nznog] Google and MaxNet
by Gordon Smith 08 Jun '04

08 Jun '04

I don't think its so much particular brands that are an issue, but rather the sheer volume of poorly designed websites. With the popularity of MS Word & Frontpage, there seems to be a lot of ignorance relating to the W3C standards. In the past, caching has made some sense for accelerating content to clients. As far as bandwidth savings go, I've never seen that achieved to the point that it made them worthwhile in that role. They can improve performance as perceived by the customer, but bypass lists rapidly become unwieldy when trying to compensate for sites that don't adhere to standards. Overall, in terms of TCO, they're probably not worth having in place any more Cheers, Gordon > -----Original Message----- > From: Juha Saarinen [mailto:juha(a)saarinen.org] > Sent: Wednesday, 9 June 2004 1:13 p.m. > To: Alastair Johnson > Cc: NZ Network Operators Group > Subject: Re: [nznog] Google and MaxNet > > > So which caches have people had success/hassle with? > > -- > Juha

1 0

Re: [nznog] Google and MaxNet
by neil gardner 08 Jun '04

08 Jun '04

>>> Joe Abley <jabley(a)isc.org> 9/06/2004 12:52:46 p.m. >>> >Akamai has nodes in New Zealand, though. Or are you suggesting that NZ >ISPs routinely cache domestic content as well as content from overseas? >Joe Well they might have to start caching Domestic traffic shortly if Peering goes the way the big players would like it to go. Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

Transparent Caching (was Google and Maxnet)
by Templeman Colin 08 Jun '04

08 Jun '04

A good topic! I 'discovered' transparent proxies recently when I was trying to resolve a problem I had obtaining security patches from security.debian.org via http. Other than having recently changed to cable broadband via Telstraclear, nothing (including apt sources) was altered, yet I was getting timeouts. After a couple of weeks of this, I eventually provided a comparison of latency output from 'ping' vs 'hping' to security.debian.org before the call was tacitly acknowledged and the problem silently fixed. I agree with Joe that they are an overhead when it comes to managing exceptions. -- Colin Templeman Security Analyst IT Risk and Security New Zealand Post Ltd This email with any attachments is confidential and may be subject to legal privilege. If it is not intended for you please reply immediately, destroy it and do not copy, disclose or use it in any way.

1 0

.nz Registry Directors
by Keith Davidson 08 Jun '04

08 Jun '04

Hello, Please pardon the intrusion to the NZNOG list. InternetNZ's subsidiary company, New Zealand Domain Name Registry Ltd, (NZRS) is responsible for operating the registry for the .nz namespace. This Company is governed by a board comprising 5 directors. Two directors retire by rotation at the Annual Meeting on 30 July 2004. Both retiring directors have declared themselves available for re-election. InternetNZ wishes to invite applications from others who believe they may have specific skills that would be advantageous to the Company. A full description of the position and skill sets being sought is available at www.internetnz.net.nz/public/registry/reg040606directors.html. Applications close on Monday 14 June 2004 (PLEASE NOTE - the web page states 11 June, but is in the process of being amended), and should be addressed to president(a)internetnz.net.nz or President, InternetNZ, P O Box 11-881, Wellington. Thanks Keith Davidson President - InternetNZ

1 0

Team Cymru Darknet Project
by Rob Thomas 03 Jun '04

03 Jun '04

-----BEGIN PGP SIGNED MESSAGE----- Hi, team. We are happy to at last release some documentation on Darknets and the Team Cymru Darknet Project. You will find the details at the following URL: <http://www.cymru.com/Darknet/> We hope this helps you to gain greater insight into your networks and the flows on them. Comments, feedback, and coffee are always welcome! :) Thanks! Rob, for Team Cymru. - -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty); -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQCVAwUBQL/XxlkX3QAo5sgJAQFBLwP/akP6qwmfg0y20wPRmX0QuOENh0NU4fhN N7LFdPqnYU3jJv6MgAR7J/u2snLmpC1RLZLkSvEFx4OtiYqqdVci4/9jT4D+M9nU qxERosZJhS65zZCExMEMJLEATWpr29pONEEBFbHBZgNYMDhee+fgDB6/GaEqY/Cr Y0qNvD0KRs4= =mm6q -----END PGP SIGNATURE-----

2 1

Queenstown
by K. Anand Lal 02 Jun '04

02 Jun '04

Hi, ihug is looking to upgrade it's Queenstown POP and as part of the upgrade we are considering a physical move to a better site. Is anyone aware of a telehousing facility located in central Queenstown? We will supply our own UPS and 19" enclosure. Appreciate any help. -- K. Anand Lal ph: +64.9.3592767 Engineering Manager fax: +64.9.3581518 The Internet Group (ihug) Ltd. noc: +64.9.3592708

3 2

The New Zealand Network Operators' Group
by Donald Neal 31 May '04

31 May '04

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. At present it consists of the subscribers to this mailing list, which anyone is free to join. Meetings See http://www.nznog.org/ for details of the January 2004 conference, which drew something over 120 participants. We are now seeking to confirm arrangements for a similar gathering to be held in the first week of February 2005. Also see http://auckland.thursdaynightcurry.com/ if you live in or near Auckland. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators rather than by most customers. Internet Exchanges See http://www.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. See http://www.wix.net.nz/ for the Wellington Internet Exchange. About This Mailing List This list has around 650 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and ihug Ltd. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/archives/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins ------------------------------------------------------------------------------ "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." ------------------------------------------------------------------------------

1 0

Re: [nznog] TC & T Possible Peering changes
by neil gardner 30 May '04

30 May '04

>>> Simon Lyall <simon(a)darkmere.gen.nz> 28/05/2004 2:24:47 p.m. >>> No, they'll change their terms and conditions so that National traffic is no longer free and is instead part of your quota. [snip] Yeah, I knew this would probably be the way they handled it. Thanks Telecom and TelstraClear, for between you managing to keep cheap high speed Internet a far off dream. Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

3 2