- NZNOG - lists.nznog.org

Public providers and ASN on WIX
by Simon Blake 17 Jun '01

17 Jun '01

Matthew Grant from Plain was asking who the WIX route servers pee with, I figured the results may be of interest to others peering or considering peering on WIX: neighbor 202.7.0.1 remote-as 9439 neighbor 202.7.0.1 description Citylink neighbor 202.7.0.49 remote-as 2687 neighbor 202.7.0.49 description AT-T ! neighbor 202.7.0.65 remote-as 7714 ! neighbor 202.7.0.65 description Netlink1 neighbor 202.7.0.76 remote-as 9736 neighbor 202.7.0.76 description Domainz neighbor 202.7.0.78 remote-as 9718 neighbor 202.7.0.78 description Chello neighbor 202.7.0.129 remote-as 9343 neighbor 202.7.0.129 description Actrix neighbor 202.7.0.130 remote-as 9872 neighbor 202.7.0.130 description Actrix-LH neighbor 202.7.0.177 remote-as 9495 neighbor 202.7.0.177 description Clearview neighbor 202.7.0.192 remote-as 4768 neighbor 202.7.0.192 description Clear neighbor 202.7.0.241 remote-as 7657 neighbor 202.7.0.241 description IHUG neighbor 202.7.1.1 remote-as 4770 neighbor 202.7.1.1 description ICONZ neighbor 202.7.1.49 remote-as 9436 neighbor 202.7.1.49 description Globe-Net neighbor 202.7.1.65 remote-as 9445 neighbor 202.7.1.65 description Saturn neighbor 202.7.1.110 remote-as 4740 neighbor 202.7.1.110 description Voyager neighbor 202.7.1.129 remote-as 9345 neighbor 202.7.1.129 description Paradise neighbor 202.7.1.176 remote-as 9503 neighbor 202.7.1.176 description Comnet neighbor 202.7.1.193 remote-as 9338 neighbor 202.7.1.193 description NLNZ neighbor 202.7.1.241 remote-as 9325 neighbor 202.7.1.241 description Xtra neighbor 202.7.1.244 remote-as 9559 neighbor 202.7.1.244 description Plain Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 2

XTRA, blacklisted by 'mail.com' --- WHY?
by Chris Wedgwood 17 Jun '01

17 Jun '01

At present, some of my outband email is sent through XTRA's mail-server(s) as they block outgoing SMTP access when you are inflicted with Jetstream/Jetstart through Xtra. Not that I really mind all that much, it works pretty much flawlessly and Xtra are arguably being good people by blocking nasty evil users from injecting spam into other peoples open-relays (perhaps they block other ports too --- maybe someone from Xtra can comment?). Now, this just occured, which again doesn't really bother me in this instance, but I am curious as to _why_ this was blocked. The DSN I received says this: Reporting-MTA: dns; balthamel.xtra.co.nz Arrival-Date: Sun, 17 Jun 2001 23:13:47 +1200 Received-From-MTA: dns; tapu (210.55.42.93) Final-Recipient: RFC822; <wapterix(a)mail.com> Action: failed Status: 5.1.3 Remote-MTA: dns; mail-com-bk.mr.outblaze.com (205.158.62.36) Diagnostic-Code: smtp; 553 5.3.0 Mail from 203.96.92.15 refused. Blacklisted. yet when I check the common 'blacklisting' mechanisms I find nothing: tapu:~$ rblcheck 203.96.92.15 203.96.92.15 not RBL filtered by blackholes.mail-abuse.org 203.96.92.15 not RBL filtered by dialups.mail-abuse.org 203.96.92.15 not RBL filtered by relays.mail-abuse.org 203.96.92.15 not RBL filtered by inputs.orbs.org 203.96.92.15 not RBL filtered by outputs.orbs.org 203.96.92.15 not RBL filtered by manual.orbs.org 203.96.92.15 not RBL filtered by spamsources.orbs.org 203.96.92.15 not RBL filtered by untestable-netblocks.orbs.org 203.96.92.15 not RBL filtered by spamsource-netblocks.orbs.org so I wonder what else is out there that is used to blacklist evil people? And why is Xtra in this list? --cw --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

5 5

Lots of broken mail at Xtra
by Martin D Kealey 14 Jun '01

14 Jun '01

Has anyone else noticed a recent downturn in mail deliverability for domains hosted by Xtra? In particular, in the last month I have had 3 mailing lists royally screwed by having various clients of Xtra decide to disregard the envelope addressee and send the mail back into the list injection point. The common features in all cases have been the primary MX is mta.xtra.co.nz the mail is collected from there using a POP client the mail is then fed to an Exchange Server The first one was the worst because they were on a full-time IP connection, which meant that the mail loop just went berserk; to make it worse they had changed the domain, and therefore there was *no* identifying information in the list to figure out what had gone wrong. The others since have been easier because they've been on various dial-up connections (and therefore slower) and have had useful identifying information in the report headers. Is this a problem with Xtra, or is there a new (broken) version of Exchange that is flavour of the month for installing? -Martin -- CAUTION: The information contained in this message is consequential and subject to legacy provenance. If you are the intended recipient you are hereby notified that reading this message is permitted. If you have not received this message please notarise the sender and destroy the originator. Help Microsoft stamp out software piracy: give Linux to a friend today... --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

16 29

Orcon APE connection - FIXED :-)
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

Hi there everyone Our connection to APE now works properly :-) The problem was a faulty Fibre to Ethernet tranciever at Clear's end of the link. We have been doing tests for several hours, and the link looks stable enough to start putting traffic on. We are interested in peering with as many people as possible up here - because after all - that's what APE is for. I will post our ASN, prefixes etc tomorrow Cheers Seeby Orcon Internet - www.orcon.net.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: Orcon APE connection woes
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

Hmm we have forced full-duplex and turned off auto-negotiation on our Catalyst 5000 switch - but we have also tried all the other settings possible. Clear have told us to set it to 10Mbps Full-Duplex - so that's what it is at present. Cheers Seeby Orcon Internet - www.orcon.net.nz ----- Original Message ----- From: "Ian Quinn" <iquinn(a)juniper.net> To: "Seeby Woodhouse - Orcon" <seeby(a)orcon.net.nz> Sent: Wednesday, June 13, 2001 6:42 PM Subject: RE: Orcon APE connection woes > > I had some problems recently that were marginally similar. Although I had > the speed and duplex settings configured, it didn't come right until I > turned off auto negotiation as well (eg no negotiation or something along > those lines). > > No idea if it's your problem - just seems familiar. > > Good luck :-) > > Regards / Ian > > -----Original Message----- > > From: Seeby Woodhouse - Orcon [mailto:seeby(a)orcon.net.nz] > > Sent: Wednesday, 13 June 2001 6:27 p.m. > > To: NZNOG Mailing List > > Subject: Orcon APE connection woes > > > > > > Hi there everyone > > > > Orcon has just had a 10Mbit IPExpress connection to APE > > completed, and I > > have been fighting with it all day. > > > > If we ping anyone on APE, then we get around 2/3's of the > > pings through, and > > 1/3 are dropped. > > This happens in a pattern of 1/3 drop, 2/3 get through. > > > > I talked with Clear and they said that it could be the > > IPExpress connection > > re-negotiating because of what is on our end, so we have been > > playing with > > the settings on our Catalyst 5000 switch - we have forced the > > port to our > > IPExpress connection full duplex / half duplex / 100mb / 10mb > > but they all > > seem to give the same results. > > > > Clear has advised us to set our equipment to 10Mbit full > > duplex - so that's > > what it is at present. > > > > The connection from IPExpress is then VLan'd from our > > Catalyst switch into > > our core Cisco 7505 router. > > > > A ping report of 300 pings to ihug.ape.net.nz looks like this > > > > --------------------------------------------------- > > ORCON7505#ping > > Protocol [ip]: > > Target IP address: ihug.ape.net.nz > > Repeat count [5]: 300 > > Datagram size [100]: > > Timeout in seconds [2]: > > Extended commands [n]: > > Sweep range of sizes [n]: > > Type escape sequence to abort. > > Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout > > is 2 seconds: > > ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! > > !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! > > !!..........!!!!!!!! > > Success rate is 65 percent (197/300), round-trip min/avg/max > > = 1/3/24 ms > > -------------------------------------------------- > > > > Can anyone shed any light on this? > > > > Is this related the the spanning tree problems that have been > > happening up > > at APE recently? > > Or should we be hassling Clear about the service..... > > > > Cheers > > Seeby > > > > Orcon Internet - www.orcon.net.nz > > > > > > --------- > > 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

4 6

Zfree Delibratley slowing down access to Orcon's network
by Seeby Woodhouse - Orcon 13 Jun '01

13 Jun '01

It seems that Zfree is delibratley slowing down Internet access to some of Orcon's internal network. If we test by dialing up using a Zfree account, most of our network is blazingly fast, however access to our Mail server and FreeHost server is painfully slow. (mail.orcon.net.nz and freehost.orcon.net.nz) Last time we informed them of this problem, the issue mysteriously went away - but now it is back again a week later. I suspect that Zfree is delibratley rate-shaping the amount of traffic that can go to our mail server and our freehost server from their network to prevent people from accessing them. It is quite frustrating when it is our helpdesk that is recieving all the calls (because theirs is 0900), when it is actually their problem - especially when the customers that are calling us are not actually using us for dialup. Any system administrators for Clear got something to say about this? ;-) -- Cheers Seeby Orcon Internet - www.orcon.net.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: Orcon APE connection woes
by Seeby Woodhouse - Orcon 12 Jun '01

12 Jun '01

Hi there Tim I don't want to put any traffic over to APE until this link is working properly. As you know, BGP won't detect packet loss, so it is still better to keep sticking all our Traffic via Telecom until this issue is resolved. As soon as the link works reliably - then we will want to peer with everyone that we can. Hopefully we'll be able to get sub 10ms pings to most ISP's in the country at the end of this ;-) Cheers Seeby Orcon Internet - www.orcon.net.nz ----- Original Message ----- From: "Tim Philips" <tim.philips(a)attica.co.nz> To: "Seeby Woodhouse - Orcon" <seeby(a)orcon.net.nz> Sent: Wednesday, June 13, 2001 6:52 PM Subject: Re: Orcon APE connection woes > On Wed, 13 Jun 2001, Seeby Woodhouse - Orcon wrote: > > Seeby, > > We have had this problem before. Well are still having it with our > Tangent 100Mb. I will see what I can find. Would you like to peer with > us also once your link is up and running. > > If you do provide us with a prefix list and I or one of the other guys > will sort it all out. > > > Hi there everyone > > > > Orcon has just had a 10Mbit IPExpress connection to APE completed, and I > > have been fighting with it all day. > > > > If we ping anyone on APE, then we get around 2/3's of the pings through, and > > 1/3 are dropped. > > This happens in a pattern of 1/3 drop, 2/3 get through. > > > > I talked with Clear and they said that it could be the IPExpress connection > > re-negotiating because of what is on our end, so we have been playing with > > the settings on our Catalyst 5000 switch - we have forced the port to our > > IPExpress connection full duplex / half duplex / 100mb / 10mb but they all > > seem to give the same results. > > > > Clear has advised us to set our equipment to 10Mbit full duplex - so that's > > what it is at present. > > > > The connection from IPExpress is then VLan'd from our Catalyst switch into > > our core Cisco 7505 router. > > > > A ping report of 300 pings to ihug.ape.net.nz looks like this > > > > --------------------------------------------------- > > ORCON7505#ping > > Protocol [ip]: > > Target IP address: ihug.ape.net.nz > > Repeat count [5]: 300 > > Datagram size [100]: > > Timeout in seconds [2]: > > Extended commands [n]: > > Sweep range of sizes [n]: > > Type escape sequence to abort. > > Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout is 2 seconds: > > ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! > > !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! > > !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! > > !!..........!!!!!!!! > > Success rate is 65 percent (197/300), round-trip min/avg/max = 1/3/24 ms > > -------------------------------------------------- > > > > Can anyone shed any light on this? > > > > Is this related the the spanning tree problems that have been happening up > > at APE recently? > > Or should we be hassling Clear about the service..... > > > > Cheers > > Seeby > > > > Orcon Internet - www.orcon.net.nz > > > > > > --------- > > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > > where the body of your message reads: > > unsubscribe nznog > > > > -- > Thanks, > Tim Philips > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Orcon APE connection woes
by Seeby Woodhouse - Orcon 12 Jun '01

12 Jun '01

Hi there everyone Orcon has just had a 10Mbit IPExpress connection to APE completed, and I have been fighting with it all day. If we ping anyone on APE, then we get around 2/3's of the pings through, and 1/3 are dropped. This happens in a pattern of 1/3 drop, 2/3 get through. I talked with Clear and they said that it could be the IPExpress connection re-negotiating because of what is on our end, so we have been playing with the settings on our Catalyst 5000 switch - we have forced the port to our IPExpress connection full duplex / half duplex / 100mb / 10mb but they all seem to give the same results. Clear has advised us to set our equipment to 10Mbit full duplex - so that's what it is at present. The connection from IPExpress is then VLan'd from our Catalyst switch into our core Cisco 7505 router. A ping report of 300 pings to ihug.ape.net.nz looks like this --------------------------------------------------- ORCON7505#ping Protocol [ip]: Target IP address: ihug.ape.net.nz Repeat count [5]: 300 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout is 2 seconds: ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! !!..........!!!!!!!! Success rate is 65 percent (197/300), round-trip min/avg/max = 1/3/24 ms -------------------------------------------------- Can anyone shed any light on this? Is this related the the spanning tree problems that have been happening up at APE recently? Or should we be hassling Clear about the service..... Cheers Seeby Orcon Internet - www.orcon.net.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

WHOIS Survey - DNSO
by Andy Linton 12 Jun '01

12 Jun '01

The DNSO is conducting a survey on ICANN's WHOIS policy. http://www.icann.org/dnso/whois-survey-en-10jun01.htm --------- 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: subscribe NZOG
by Lindsay Druett 12 Jun '01

12 Jun '01

How does the subscribe kit work ? > -----Original Message----- > From: Michael White [mailto:MWHITE(a)clear.co.nz] > Sent: Wednesday, 13 June 2001 14:40 > To: Michael White; nznog(a)list.waikato.ac.nz; 'Juha Saarinen' > Subject: RE: subscribe NZOG > > Damn, wrong kit. > > Mike > > ---------- > From: Juha Saarinen > Sent: Wednesday, 13 June 2001 2:33 PM > To: 'Michael White'; nznog(a)list.waikato.ac.nz > Subject: RE: subscribe NZOG > > Heres how to unsubscribe: > > > Errr... I think the person wants to subscribe. > > -- Juha > > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0