Mmm, most likely. I need to go on a subscription drive - you'll get routes only from the these peers at the mo: Plain (192.203.154.12) 4 9559 0/0 0/0 0/0 0.01 Active Actrix (192.203.154.16) 4 9872 0/23 1/0 1/0 0.91 Established QSI (192.203.154.28) 4 9727 9/21 0/0 1/0 0.91 Established Telstra (192.203.154.32) 4 4763 0/0 0/0 0/0 0.01 Active IHUG (192.203.154.36) 4 7657 43/29 0/0 1/0 0.91 Established AOL (192.203.154.44) 4 4770 19/13 0/0 1/0 0.91 Established Zivo (192.203.154.45) 4 9495 4/19 0/0 1/0 0.91 Established Attica (192.203.154.46) 4 9790 3/20 0/0 1/0 0.91 Established WalkWire (192.203.154.49) 4 17412 1/29 0/0 1/0 0.91 Established Quest (192.203.154.64) 4 64512 0/23 0/0 1/0 0.91 Established Orcon (192.203.154.66) 4 17746 3/58 0/0 3/2 0.49 Established Some ISP's don't peer with the route servers, for a variety of reasons. I'm expecting that to change as the number of peers increase, as I put in place some more automated procedures for updating the route servers, and as I place some more pressure on the ISP's. Which is a long winded way of saying, nobody is obligated to peer with the route servers, you still may need to negotiate some bilateral arrangements. Anybody else who wants to peer with the route servers on APE, please sing out. Cheers Si On Mon, 18 Jun 2001, Craig Whitmore wrote:

I'm seeing...Is that all?

Thanks Craig

* 138.235.0.0 192.203.154.44 0 9560 4770 i * 192.173.16.0/21 192.203.154.44 0 9560 4770 i * 202.6.84.0 192.203.154.44 0 9560 4770 i * 202.12.70.0 192.203.154.44 0 9560 4770 i * 202.14.100.0 192.203.154.44 0 9560 4770 i *> 202.27.100.0/22 192.203.154.45 0 9560 9495 i *> 202.36.45.0 192.203.154.45 0 9560 9495 i * 202.37.85.0 192.203.154.44 0 9560 4770 i * 202.37.140.0/22 192.203.154.44 0 9560 4770 i * 202.37.144.0/21 192.203.154.44 0 9560 4770 i * 202.37.197.0 192.203.154.44 0 9560 4770 i * 202.37.200.0/22 192.203.154.44 0 9560 4770 i * 202.37.224.0/21 192.203.154.44 0 9560 4770 i * 202.49.144.0 192.203.154.44 0 9560 4770 i * 202.50.16.0/20 192.203.154.44 0 9560 4770 i *> 202.78.128.0/21 192.203.154.45 0 9560 9495 i *> 202.89.128.0/19 192.203.154.28 0 9560 9727 i * 202.180.64.0/19 192.203.154.46 0 9560 9790 i * 202.180.64.0/18 192.203.154.46 0 9560 9790 i * 202.180.96.0/19 192.203.154.46 0 9560 9790 i *> 203.96.120.0/23 192.203.154.45 0 9560 9495 i * 203.99.65.0 192.203.154.44 0 9560 4770 9511 i * 203.99.66.0 192.203.154.44 0 9560 4770 9511 i * 203.99.71.0 192.203.154.44 0 9560 4770 9511 i * 210.48.0.0/17 192.203.154.44 0 9560 4770 i *> 210.54.0.0/22 192.203.154.44 0 9560 4770 17427 i * 210.55.254.0 192.203.154.46 0 9560 9727 9790 i

----- Original Message ----- From: "Simon Blake" <simon(a)citylink.co.nz> To: "Craig Whitmore" <lennon(a)orcon.net.nz> Sent: Monday, June 18, 2001 1:51 PM Subject: Re: Orcon's Ranges

...

Hokay, .1 is peering, I'm seeing this from you:

magellan MRTd# sh bgp neigh 192.203.154.66 route in

Peer 192.203.154.66 ip unicast 11 routes P Pref Time Destination Next Hop If B 0 00:09:22 202.27.188.128/25 192.203.154.66 eth0 B 0 00:09:22 210.54.13.0/24 192.203.154.66 eth0 B 0 00:09:22 210.54.142.0/23 192.203.154.66 eth0 B 0 00:09:22 210.54.148.0/22 192.203.154.66 eth0 B 0 00:09:22 210.55.8.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.12.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.13.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.14.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.15.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.18.0/24 192.203.154.66 eth0 B 0 00:09:22 210.55.199.0/24 192.203.154.66 eth0

So, looks pretty good, you should be getting assorted stuff from the other ISP's viz the route server now. I'll have .2 going later in the afternoon.

Cheers Si

On Mon, 18 Jun 2001, Craig Whitmore wrote:

...

Hi Simon. Here are the prefix lists for Orcon. We will also be advertising Datacom's Ranges to APE (via our AS Number)

Do we peer with rs1.ape.net.nz and rs2.ape.net.nz with APE's (9560) Number...

Orcon: As 17746 IP : 192.203.154.6

ip prefix-list ORCON-networks description Orcon Internet <noc(a)orcon.net.nz> ip prefix-list ORCON-networks seq 5 permit 202.27.188.128/25 ip prefix-list ORCON-networks seq 10 permit 210.54.13.0/24 ip prefix-list ORCON-networks seq 15 permit 210.54.142.0/23 ip prefix-list ORCON-networks seq 20 permit 210.54.148.0/23 ip prefix-list ORCON-networks seq 25 permit 210.55.8.0/24 ip prefix-list ORCON-networks seq 30 permit 210.55.12.0/24 ip prefix-list ORCON-networks seq 35 permit 210.55.13.0/24 ip prefix-list ORCON-networks seq 40 permit 210.55.14.0/24 ip prefix-list ORCON-networks seq 45 permit 210.55.15.0/24 ip prefix-list ORCON-networks seq 50 permit 210.55.18.0/24 ip prefix-list ORCON-networks seq 55 permit 210.55.199.0/24

ip prefix-list DATACOM-networks description Datacom Network <noc(a)orcon.net.nz> ip prefix-list DATACOM-networks seq 5 permit 202.14.20.0/22 ip prefix-list DATACOM-networks seq 10 permit 202.27.76.0/23 ip prefix-list DATACOM-networks seq 15 permit 202.27.140.0/22 ip prefix-list DATACOM-networks seq 20 permit 210.27.250.0/24

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog