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

On Thu, 24 May 2001, Chris Wedgwood wrote:

Where are you tracing from (i.e. what address)? It's not coming from an APE number address is it?

Good question.... it was mailed to me.... Peter? --- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

:: 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 Hafta chime in here... [From Paradise] # ping netgate.ape.net.nz PING netgate.ape.net.nz (192.203.154.48) from 192.168.1.1 : 56(84) bytes of data.

From GE0-0-0.nzsx-core2.Auckland.telstra.net (203.98.4.4): Destination Host Unreachable

[From Asia Offline] $ ping netgate.ape.net.nz PING netgate.ape.net.nz (192.203.154.48): 56 data bytes 64 bytes from 192.203.154.48: icmp_seq=1 ttl=243 time=39.541 ms 64 bytes from 192.203.154.48: icmp_seq=2 ttl=243 time=41.400 ms 64 bytes from 192.203.154.48: icmp_seq=3 ttl=243 time=39.128 ms 64 bytes from 192.203.154.48: icmp_seq=4 ttl=243 time=52.195 ms ^C [From very close by] $ /sbin/ping netgate.ape.net.nz PING netgate.ape.net.nz (192.203.154.48): 56 data bytes 64 bytes from 192.203.154.48: icmp_seq=0 ttl=254 time=32.723 ms 64 bytes from 192.203.154.48: icmp_seq=1 ttl=254 time=3.138 ms 64 bytes from 192.203.154.48: icmp_seq=2 ttl=254 time=2.654 ms 64 bytes from 192.203.154.48: icmp_seq=3 ttl=254 time=3.049 ms -- Juha --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

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

I cant trace from any host on our network 202.37.240/23 but can from our router interface on 202.37.245.210

I have a terrible suspicion this is about the topic discussed yesterday re forcing Telecom to peer. Hope somebody proves me wrong.

Your on the right track, but it's nothing as sinister as that! It is as I suspected a return route problem. We are seeing and accepting an announcement from Netgate for 202.37.245.0/24 but we are not seeing an announcement for 202.37.240/23. This network is not in the prefix-list applied to our Netgate peering either. Please let me know if I can do anything here to help. Phill. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

Thanks to those who chipped in to help sort this problem. We are now back on the air.

Cancel that, we are down again, Telecom cant see QSI's network. :-( Peter Mott Chief Enthusiast 2day.com -/- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

On Thu, 24 May 2001, Joe Abley wrote:

On Thu, May 24, 2001 at 03:53:30PM +1200, Peter Mott wrote:

...

Thanks to those who chipped in to help sort this problem. We are now back on the air. I have come to the conclusion that reliable domestic peering is not something we should expect anytime soon.

It doesn't sound like domestic peering was the issue; more like "transit through netgate is broken". A sane network which didn't learn a route through some domestic method would send the traffic overseas to reach its destination rather than simply dropping it.

Mmm, not quite. The problem is at layer 2 - Attica learn routes from Clear, who learn them from Netgate, and so Attica have a bunch of routes that direct them to directly traverse APE to Netgate's router. Unfortunately, at this time we *do not* have layer 2 connectivity between Attica and Netgate - they can both ping most everything else on APE, but they can't ping each other. Reasons for this are unclear - it seems to involve spanning tree, VLAN (mis)configuration, increasing topology complexity, and the phase of the mooon - according to Peter M, it seems to come and go in 20 minute cycles. It certainly changes depending on who does or doesn't advertise spanning tree packets. *This* is why I'm harping on about spanning tree and total filtering of connected switches - because right here, right now, I believe it's causing APE to go like crap. Cheers Si --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

There have been no changes to the APE switch since about midday. I also note that there are *no* MAC addresses showing up on the Tangent port at the moment, even though the line is up. I would there be braced for more excitement when they do start using it again. Cheers Si 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).

ba2.acld#ping 192.203.154.48

Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 192.203.154.48, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

On Thu, May 24, 2001 at 12:53:45PM +1200, Matt Camp wrote:

netgate.ape.net.nz is now live and accepting traffic?

Because clear seem to be trying to tell me that i should be sending stuff to it... pity it doesn't even seem to exist. (at least, i can't ping it or anything from my ape gateway)

gateway1# sh ip bgp 202.37.240.22 *202.37.240.0/23 Neighbor: 192.203.154.8 ASPath: 4768 4648(IGP) Nexthop: 192.203.154.48 Weight: 0 Localpref: 100 Last update: Thu May 24 12:02:56 2001

bash-2.03# ping netgate.ape.net.nz PING netgate.ape.net.nz (192.203.154.48): 56 data bytes ping: sendto: Host is down ping: sendto: Host is down ^C --- netgate.ape.net.nz ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss

--cw

-- Chris Wedgwood chris.wedgwood(a)clear.co.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