Re: [ris-int] [NCC#2004119411: Peering SURFnet - RIPE werkt niet (ARS S9757) (fwd)]
Hi Arife,
It's what we expect on RRC00. We do announce and withdrawal Beacon prefix in fixed time intervals. Because of that you can not get the prefixes from us (AS12654) continously. You can get the time schedule of Beacon prefixes in the following link:
I understand beacons come and go, but shouldn't they at least see the anchor prefix 195.80.239.0/24 ??? -- Rene ---------- Forwarded message ---------- Date: Thu, 25 Nov 2004 18:56:29 +0100 From: Peter Blondel <blondel@sara.nl> Reply-To: nic@sara.nl To: "Henk Uijterwaal (RIPE-NCC)" <henk@ripe.net> Cc: nic@sara.nl Subject: Peering SURFnet - RIPE werkt niet (ARS S9757) Hallo Henk, Ik zag net 'toevallig' dat we geen prefixen binnen krijgen op jullie peering met de BR2.Amsterdam1 sinds vanmorgen: 193.0.4.28 4 12654 33 204375 2255254 0 0 08:39:31 0 -- uit de logging: Nov 24 23:49:54.962 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 Down Peer closed the session Nov 25 08:43:08.210 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 Up en resetten vanaf onze kant helpt niet. Hebben jullie iets veranderd ? met vriendelijke groeten Peter Blondel SARA NCC ----- End forwarded message -----
On Fri, 26 Nov 2004, Rene Wilhelm wrote:
Hi Arife,
It's what we expect on RRC00. We do announce and withdrawal Beacon prefix in fixed time intervals. Because of that you can not get the prefixes from us (AS12654) continously. You can get the time schedule of Beacon prefixes in the following link:
I understand beacons come and go, but shouldn't they at least see the anchor prefix 195.80.239.0/24 ???
Yes, but we are about to change this. Henk
-- Rene
---------- Forwarded message ---------- Date: Thu, 25 Nov 2004 18:56:29 +0100 From: Peter Blondel <blondel@sara.nl> Reply-To: nic@sara.nl To: "Henk Uijterwaal (RIPE-NCC)" <henk@ripe.net> Cc: nic@sara.nl Subject: Peering SURFnet - RIPE werkt niet (ARS S9757)
Hallo Henk,
Ik zag net 'toevallig' dat we geen prefixen binnen krijgen op jullie peering met de BR2.Amsterdam1 sinds vanmorgen: 193.0.4.28 4 12654 33 204375 2255254 0 0 08:39:31 0
-- uit de logging: Nov 24 23:49:54.962 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 Down Peer closed the session Nov 25 08:43:08.210 UTC: %BGP-5-ADJCHANGE: neighbor 193.0.4.28 Up
en resetten vanaf onze kant helpt niet. Hebben jullie iets veranderd ?
met vriendelijke groeten Peter Blondel SARA NCC
----- End forwarded message -----
------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Look here junior, don't you be so happy. And for Heaven's sake, don't you be so sad. (Tom Verlaine)
It's what we expect on RRC00. We do announce and withdrawal Beacon prefix in fixed time intervals. Because of that you can not get the prefixes from us (AS12654) continously. You can get the time schedule of Beacon prefixes in the following link:
I understand beacons come and go, but shouldn't they at least see the anchor prefix 195.80.239.0/24 ???
Rene has point. It looks we are announcing Anchor prefixes, continously. At least, this guys should get one prefix from us. I will check it out with him. Arife
participants (3)
-
Arife Vural -
Henk Uijterwaal (RIPE NCC) -
Rene Wilhelm