This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg]peering change on route-views.routeviews.org
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] New AS Number block allocated to the RIPE NCC
- Next message (by thread): [routing-wg]Working group session at RIPE 58.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
John Kemp
kemp at network-services.uoregon.edu
Fri Mar 13 18:37:59 CET 2009
We are losing the transit to the previous peering address for the route-views router: 198.32.162.100 Your peering to us there is/was: neighbor 193.0.0.56 remote-as 3333 neighbor 193.0.0.56 peer-group multicast-ebgp neighbor 193.0.0.56 description RIPE NCC If you could change that to peer with: 128.223.51.103 that session should come up now. It is actually the same router, but a different interface. Sorry about the short notice on this. If there is a different channel I should contact about this, please let me know. NOTE: route-views.routeviews.org is an operational looking glass. No data is currently being archived from this device, but the telnet cli remains for operational use. -- John Kemp RouteViews Engineer kemp at network-services.uoregon.edu 541-346-1714
- Previous message (by thread): [routing-wg]Re: [address-policy-wg] New AS Number block allocated to the RIPE NCC
- Next message (by thread): [routing-wg]Working group session at RIPE 58.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]