- NZNOG - lists.nznog.org

OT: Bandwidth/Connectivity in Matamata
by Mark Derricutt 11 Jun '02

11 Jun '02

'lo, off topic, but you lot would be the best to ask I'm guessing... what bandwidth/connectivity options are there in Matamata these days? Is it ADSLable yet? Walker wireless? Thinking of running another cybercafe out there at a music fest and wanting something better than the dialup we had to suffer last year, or the ISDN we had the year before... The bitcher is that the connection would only be for 3-4 days. Mark -- \m/ -- "...if I seem super human I have been misunderstood." (c) Dream Theater mark(a)talios.com - ICQ: 1934853 JID: talios(a)myjabber.net - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 4

passport.com
by thom hooker 10 Jun '02

10 Jun '02

does anybody else think it strange that microsoft's passport.com domain has no MX record? and the A record listed for it isn't listening on port 25? i've had mail queueing for it for the past few months (mainly bounces for invalid addresses) and as far as i can tell microsoft are unwilling to do anything about all the bounce mail they're generating (i mean, how hard can it be to add 2 lines to dns?) is anybody else seeing this? -- thom hooker p: 64 9 3555 279 xtra.co.nz f: 64 9 3555 260 unix systems support c: 64 21 523 521 - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

NZ IP's
by Steve Winter 07 Jun '02

07 Jun '02

Hi I often find the discussions here well beyond my level of understanding, but never the less interesting...I expect that this question may be rather trivial, but this is the only place I could think where I may get an answer... I am trying to discover how I might find out all the IP ranges which are used in New Zealand. My ultimate goal is to check users visiting a website to see if they are connected to the internet within New Zealand and redirect them to different pages accordingly, much like Google seems to be able to do these days, ie when I enter www.google.com, I end up at www.google.co.nz, and I'm assuming that this is done based on the IP address of the machine I'm on...??.. Can anyone point me in the right direction for a source of this information...or if I'm heading in the wrong direction to achieve my goal, enlighten me as to how Google manages this... Thanks for any suggestions Steve +----------------------------------------------+ Steve Winter, Assistant Director National Science-Technology Roadshow Trust P.O. Box 598, Wellington New Zealand Phone +64 27 434 1577 Fax +64 8 326 3263 http://www.roadshow.org +----------------------------------------------+ - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

12 15

RE: NZ IP's
by Thomas Salmen 06 Jun '02

06 Jun '02

> > > The hostnames of my home machine and my colocated machine > both end in .net > - but I still see google.co.nz, not google.com :) > I suppose most people who are plain old ISP customers will have .nz > hostnames, but there'll be others who dont... especially > anyone who has > their own domain name (we all know that .com's are generally > cheaper than > .nz's - I know a few of my clients have realised the same.) - and the > ability to get their own DNS set up. > I know that I've given the idea some thought in the past. For a service provider that differentiates billing based on traffics geographical source/destination (eg, in New Zealand, whether traffic is domestic or international), one would expect that reasonable care would be taken to ensure that any address databases or lists would be accurate and well-maintained. The only thing I can suggest as being nearly accurate or up-to-date enough would be periodic analysis of routing tables. For example: if a route is learned from a particular peer, that prefix must be located in a certain area. You'd need to be sure of certain things, though. You'd have to be peering both locally and outside the country, or buying transit from a peer that feeds international and domestic routes separately. Or you might have some luck persuading a peer to tag locally-learned routes with a given community. If you happened to peer via APE/WIX, you could assume that you'd only be learning NZ routes there. You'd also have to be prepared for the inevitable mistakes whenever a route leaks where it shouldn't. And if you didn't peer with anyone, you'd have even more problems :-) I don't think it would work very well if we didn't have so few pipes into New Zealand. But I imagine that Google would peer with enough providers in enough places to make a pretty accurate guess as to which country a host is located. Anyway. I know that some providers use Packeteer-type systems to differentiate between local and international traffic: perhaps they would be willing to comment how they make the distinction? (I don't know anything about them myself - I expect they judge based on which circuit a packet enters or leaves by and don't take much notice of the actual address of the remote host (?) - actual analysis of source/destination probably isn't necessary.) > > At 01:23 7/06/02 -0500, Andy Gardner wrote: > >At 5:52 PM +1200 6/7/02, Chris Hellberg wrote: > > > > >It will work most of the time, but those few who do have > .com reverse > > >lookups will fail. > > > >What NZ ISP's have named their dial-up hostnames as .com instead of > >*.nz ? > > > >I guess it's not as bad as the UK. > > -- Regards, Thomas Salmen Network Manager Radionet Ltd. 72 Paul Matthews Road Albany, Auckland, New Zealand Ph: +64 9 4140 300 - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

The New Zealand Network Operators' Group[
by Donald Neal 06 Jun '02

06 Jun '02

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. This posting, or one like it, is sent to all subscribers each month. NZNOG 2002 Work is now under way towards a conference and social gathering to be held in Auckland on 11, 12 and possibly 13 July 2002. Registrations should open Real Soon Now. If you wish to act a sponsor and have not already discussed this either with me or the Convenor, please contact me at this email address. My thanks to 2Day Internet Ltd, Cisco, Ericsson and Juniper. 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. Auckland Peering Exchange See http://www.ape.net.nz/ for details of the Auckland Peering Exchange and those connected there. About This Mailing List This list has around 340 subscribers, increasing slightly each month. You may only post to the list from an address subscribed to one of the lists described below. (There's nowadays much more spam bounced than non-member postings.) The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by an employee of Telecom NZ Ltd. Neither of these organisations, nor the 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 administrator remains happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. Subscribing to the List To subscribe to the NZNOG list, send email to majordomo(a)list.waikato.ac.nz, where the body of the message reads subscribe nznog Digest Mailing List If you don't wish to receive postings as they are sent, you can instead subscribe to the nznog-digest mailiing list, on which all postings are sent out in a single "digest" every couple of days. Post-only Mailing List An address from which you wish to post, but which will not receive messages from the list, may be subscribed to nznog-postonly. You will presumably want to have another address subscribed to the main nznog list. 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." ------------------------------------------------------------------------------ - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Port 2017 TCP
by Denis Gordon 05 Jun '02

05 Jun '02

Juha, TCP 2000 + line_no provides reverse telnet to whatever is connected to that line on the 2500. So I would expect 2017 to connect to line 17. That's AUX on a 2511 - don't know about a 2503. regards Denis Gordon Network Administrator Information Systems Technical Support Dunedin City Council 50 The Octagon, PO Box 5045, Dunedin, New Zealand Ph: +64-3-474 3566 Fax: +64-3-474 3503 Mobile: 025 845 583 Email: denis(a)dcc.govt.nz WWW: http://www.CityOfDunedin.com/ -----Original Message----- From: Juha Saarinen [mailto:juha(a)saarinen.org] Sent: Thursday, 6 June 2002 8:31am To: NZNOG Subject: Port 2017 TCP That port is listed in services as "cypress-stat" but does anyone know what's listening on it, on a 2503? -- Juha Saarinen - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Port 2017 TCP
by Juha Saarinen 05 Jun '02

05 Jun '02

That port is listed in services as "cypress-stat" but does anyone know what's listening on it, on a 2503? -- Juha Saarinen - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

WIX/APE route servers (WARNING useful content)
by Dean Pemberton 04 Jun '02

04 Jun '02

Ok - Thought it was about time that the list had some more on-topic posts for the week. So I want to tackle the issue of the WIX and APE route servers. Any why some people just don't love them. First some background (excuse the lameness, but I thought I'd talk to a wider audience on the list while I was at it). If you want to ignore this then skip to the bottom where I get to the point (search for *THE POINT*) There are two route servers WIX and APE for the purpose of exchangeing a list of prefix's which are reacable locally via each of those networks. Network entities peer with these servers inorder to get local (wix/ape) nexthop information for prefix's rather than have to default route them through an upstream provider. Example: Company A and Company B both have a presence on Citylink in Wellington. They both have differernt upstream providers. Under normal routing conditions, the traffic between these companies would be routed to their upstream providers and delt with according to their routing/billing policy. It is possible however for Company A and Company B to route traffic directly to each other and thus bypass the upstream. Gaining all the speed and billing advantages along the way. This works well at the moment and there is no problem with this portion of the route servers. The issue comes from ISP's peering to the route servers. Most of the ISP's who have a presence on citylink also advertise routes to the route servers. This is great. It means that if I'm using ISP A for my upstream, I can pass traffic to ISP B's networks across Citylink . The majority of these ISP's however are not listening to any advertisments from the WIX/APE route servers. Which leads to the following situation. Company A uses ISP A as an upstream. Company A is learning prefix's for ISP B through the route server and will pass packets to them directly to ISP B. ISP B however is not listening to any advertisments from the route servers, and will pass all traffic BACK to Company A via ISP A. Thus negating the point of sending the traffic locally in the first place. *THE POINT* SO - I know a few of the reasons why ISP's are not listening to the routes from the servers, but I want to be able to understand them all. Some possible problems ("We don't think that they are safe enough") can be fixed. Other possible concerns ("We don't peer because we don't think we need to") can not. I want to see if it's worth pursueing this kind of network design. So I want to see how many problems fall into each of my catagories above. So if ISP's can send me the responses to: "What are the reasons that you are not listening to prefix's via the wix/ape route servers" I'd appreciate it (private email ok) If you are already listening to all the prefix's then keep the list noise down and stay quiet =) But I know who's not - so don't try and fool me. =) Here are some possible concerns/solutions that I prepared earlier. Might make your response easier C: "People are morons. There is no way that I'm letting little people like Company A inject BGP routes into my network. GOD it took me long enought to understand BGP I'm not trusting some snotty nosed small company administrator" S: Ok - first of all get back on the medication. Secondly - Simon Blake (the route server admin) assures me that he has been running full import and export filters on all peering sessions for the last 18 months. So there is no way that the small networks we are talking about can advertise anything that they have not cleared with Simon first. So in a sense you are not trusting every small company admin - you are trusting Simon. So make your judgement on that. C: "Piss off - I'm not providing domestic transit to other peoples customers. Are you mental" S: Well not last time I checked - but I have had a mountain bike accident since then. I'm not asking you to provide domestic transit for free. Just advertise the routes that you are happy to accept traffic for. for example - maybe you only advertise Wellington routes at WIX and Auckland routes at APE. You all have networks where you can tell the difference right? =) C: "I don't peer with anyone smaller than myself" S: Thats sad. I'm getting a network version of A Christmas Coral flashbacks =) Sure if thats your company policy then I'm not about to pass judgement on it. But if it were me - I'd want to get traffic out of my network as quick as possible. And passing it to a companies upstream is not always the best (read cheapest) way of doing that. Nuff said. C: "Peering is hard. Everytime you peer you add another level of complexity to the network" S: Sure. This is why Simon is also looking at automating the process using some route registry tools. If this is one of your concerns then make it known, but also keep in mind that it's in the pipes. And remember you only have one peer (the server) not all the different companies. Simon has already done one level of scrubbing for you. Pity him his job =) OK So mail me (private if you dont' want to do it to the list) your reasons for not loving the route servers. Even if all you have to say is "Didn't know about them" or "Far too busy" (don't lie though) Thanks Dean - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 13

Re: More Spam to All ISP's
by Steve Phillips 03 Jun '02

03 Jun '02

At 10:36 1/06/2002, Craig Whitmore wrote: >[snippage about spam] paradise customer, someone from paradise want to LART this person ? we have already asked for the domain aim.net.nz to be pulled by kudos.net.nz (our customer hosting the domain) http://aim.net.nz/pipermail/nzisps_aim.net.nz.mbox/nzisps_aim.net.nz.mbox :-) -- Steve. Systems Admin, ICONZ -- Steve Systems Admin, ICONZ - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

aim.net.nz null routed until further notice
by David Fox 01 Jun '02

01 Jun '02

FYI Regards David Fox Network Engineer ICONZ - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0