Over the next few weeks the addresses of the four Route Views
collectors in Oregon are changing:
Collector Old Address New Address
route-views.routeviews.org128.223.60.103 128.223.51.103
route-views2.routeviews.org 128.223.60.102 128.223.51.102
route-views3
Looking for "show ip bgp" or mrt format RIB files from prior to
November, 1997, for academic research.
Thanks!
Tom
Folks,
We are now up and running at the LINX (London Internet
Exchange) and would like to invite folks at the LINX to
peer with route-views. You can get to the open CLI via
'telnet route-views.linx.routeviews.org' (of course,
nothing much
Folks,
We are now up and running at the PAIX (Palo Alto) and
would like to invite folks at the PAIX to peer with
with Route-Views. Please contact us at [EMAIL PROTECTED]
if you would like contribute your view.
Thanks,
The Route-Views
As part of the "Route-Views Update" presentation
delivered at the NANOG 29 in Chicago, we openly invited
participants at the PAIX (install pending) and NSPIXP
(WIDE) exchanges to peer with Route-Views (AS6447).
For those who may have forgotten o
Greetings,
route-views (AS6447) is pleased to announce our presence
at NSPIXPII (202.249.2.166), courtesy of Akira Kato and
WIDE.
The route-views project operates BGP route collectors
that provide global routing data to both operator and
> Some prefixes in the Route Views routing table do not have a prefix
> length specified. For example,
because they are their 'natural' length, i.e. old style A/B/C
>
> Hello,
> Some prefixes in the Route Views routing table do not have a prefix
> length specified. For example,
> 4.0.0.0 and 61.0.0.0 do not have a prefix length specified in the Route
> Views routing table. 61/8 belongs to APNIC. 4/8 belongs to Genuity.
Its mean
Hello,
Some prefixes in the Route Views routing table do not have a prefix
length specified. For example,
4.0.0.0 and 61.0.0.0 do not have a prefix length specified in the Route
Views routing table. 61/8 belongs to APNIC. 4/8 belongs to Genuity.
Why is this? How does one find out the
