- NZNOG - lists.nznog.org

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

More Spam to All ISP's
by Craig Whitmore 01 Jun '02

01 Jun '02

Hi all, If you didn't notice aim.net.nz just added all ISP's to their own little New Zealand ISP Mailing list.(I guess to spam about the new ".kiwi" domain name (alternative DNS system) (http://aim.net.nz/pipermail/nzisps_aim.net.nz/2002-May/000000.html) I suggest if you are on this spam list, to remove yourself with the password they just emailed all the email addresses. (sales@ and help@ all the ISP's in NZ) (See http://aim.net.nz/mailman/roster/nzisps_aim.net.nz ) Thanks Craig Whitmore - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

Re: Ape Cabinet ringing again
by Mark Foster 30 May '02

30 May '02

At 19:23 31/05/02 +1200, you wrote: >FYI Someone was trying to ring the APE cabinet at wround 12:30pm today >Hope it wasn't urgent 8) See we go the other way.. our phone in there doesnt have a working ringer.. just a light that flashes... ... Last time I was up there I was working with Mark and he said 'i'll ring you on the phone up there'. Course I Didnt know it wouldnt ring. I got distracted, happened to glance at it and see the light flashing. I still don't know how long he'd been letting it ring for... =P - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Cisco Value added.
by Simon Lyall 30 May '02

30 May '02

I hope this is a joke. Nice to see where our money goes. http://www.theinquirer.net/29050203.htm PS: I sent this to the other list but it seems to be down. -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz Senior Network/System Admin | Postmaster | Home: simon(a)darkmere.gen.nz ihug, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

8 11

Ape Cabinet
by Matt Camp 30 May '02

30 May '02

I'm in the tower right now, and the APE cabinet was just ringing. Was someone trying to contact it? (Via phone)? --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 6

Attica/Callplus Prefix List Update
by James Tyson 30 May '02

30 May '02

Hi folks. Please be advised that we have added the following two networks: 202.36.244.0/24 202.36.245.0/25 Full prefix list is: ip prefix-list tranzpeer-networks seq 5 permit 192.100.53.0/24 ip prefix-list tranzpeer-networks seq 10 permit 202.14.252.0/24 ip prefix-list tranzpeer-networks seq 15 permit 202.27.48.0/21 ip prefix-list tranzpeer-networks seq 20 permit 202.36.204.0/23 ip prefix-list tranzpeer-networks seq 25 permit 202.36.244.0/24 ip prefix-list tranzpeer-networks seq 30 permit 202.36.245.0/24 ip prefix-list tranzpeer-networks seq 35 permit 202.37.129.0/24 ip prefix-list tranzpeer-networks seq 40 permit 202.49.62.0/24 ip prefix-list tranzpeer-networks seq 45 permit 202.49.82.0/24 ip prefix-list tranzpeer-networks seq 50 permit 202.49.83.0/24 ip prefix-list tranzpeer-networks seq 55 permit 202.49.152.0/21 ip prefix-list tranzpeer-networks seq 60 permit 202.49.250.0/24 ip prefix-list tranzpeer-networks seq 65 permit 202.50.60.0/22 ip prefix-list tranzpeer-networks seq 70 permit 202.50.170.0/24 ip prefix-list tranzpeer-networks seq 75 permit 202.154.128.0/19 ip prefix-list tranzpeer-networks seq 80 permit 202.180.64.0/18 ip prefix-list tranzpeer-networks seq 85 permit 202.180.113.16/28 ip prefix-list tranzpeer-networks seq 90 permit 202.180.116.0/24 ip prefix-list tranzpeer-networks seq 95 permit 203.96.16.0/20 ip prefix-list tranzpeer-networks seq 100 permit 203.96.48.0/20 ip prefix-list tranzpeer-networks seq 105 permit 210.55.111.0/24 ip prefix-list tranzpeer-networks seq 110 permit 210.55.158.0/24 ip prefix-list tranzpeer-networks seq 115 permit 210.55.254.0/24 -- Cheers. --- James Tyson Moebius Systems Ltd http://www.moebius.co.nz/

1 0