Looks OK to me. We are learning the route from QSI (our customer) and passing it to our peers. May be a return route problem? b2.sxb>tr 202.89.128.74 Type escape sequence to abort. Tracing the route to ns2.2day.com (202.89.128.74) 1 fa0-0.ape1.sky.tsnz.net (203.98.21.24) 4 msec 0 msec 4 msec 2 qsi1.ape.net.nz (192.203.154.28) 0 msec 0 msec 0 msec 3 ns2.2day.com (202.89.128.74) [AS 9727] 0 msec 0 msec 4 msec Regards, Phill.
-----Original Message----- From: owner-nznog(a)list.waikato.ac.nz [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Matt Camp Sent: Thursday, May 24, 2001 1:50 PM To: Chris Wedgwood Cc: nznog(a)list.waikato.ac.nz Subject: Re: Netgate peering and weirdness...
Looking much better... although Peter is still seeing some weirdness trying to reach his ns that we host.. not sure if this is the same problem though.
Tracing route to ns2.2day.com [202.89.128.74] over a maximum of 30 hops:
1 16 ms <10 ms <10 ms gateway1.2day.com [202.37.240.254] 2 16 ms <10 ms <10 ms gateway2.2day.com [202.37.241.253] 3 16 ms 16 ms <10 ms a3-0-7.tkcr1.global-gateway.net.nz [202.50.116.225] 4 15 ms <10 ms 16 ms A5-0-0-19.akcr5.netgate.net.nz [202.50.245.105] 5 15 ms 16 ms 31 ms f4-0.akcr1.netgate.net.nz [202.37.246.82] 6 63 ms 78 ms 47 ms S6-2.b2.sxb.tsnz.net [203.98.4.245] 7 78 ms 62 ms 63 ms fa0-0.ape1.sky.tsnz.net [203.98.21.24] 8 * * * Request timed out. 9 ^C
On Thu, 24 May 2001, Chris Wedgwood wrote:
Still busted? Works for me now... perhaps you tried at a bad time as there have been switch funnies and minor diagnostics going on I beleive (someone from Citylink can confirm/deny this).
--- Matt Camp
--------- 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