Re: [ris-int] Re: [NCC#2004119411: Peering SURFnet - RIPE werkt niet (ARS S9757) (fwd)]
Peter Blondel wrote:
On Mon, 29 Nov 2004 13:19:30 +0100 Arife Vural <arife@ripe.net> wrote:
Hi Peter,
It looks I missed Anchor prefix, 195.80.239.0/24. We are announcing this prefix continously. That means you should get at least one prefix from us, and that would be 2 when we start to announce normal Beacon prefix.
Please, let us know if you still get no prefix from us.
Regards.
Arife,
We still get nothing from you; sh ip bgp neighbors 193.0.4.28 received-routes gives no entries.
Hmmm.. our bgpd definitely thinks it's sending something to you: | rrc00> sh ip bg nei 195.69.144.34 advertised-routes | BGP table version is 0, local router ID is 193.0.4.28 | Status codes: s suppressed, d damped, h history, * valid, > best, i - internal | Origin codes: i - IGP, e - EGP, ? - incomplete | | Network Next Hop Metric LocPrf Weight Path | *> 195.80.239.0 193.0.4.28 0 32768 i | | Total number of prefixes 1 James -- James Aldridge, Network Engineer, RIPE NCC Tel: +31 20 535 4421 Fax: +31 20 535 4445
James Aldridge wrote:
Peter Blondel wrote:
On Mon, 29 Nov 2004 13:19:30 +0100 Arife Vural <arife@ripe.net> wrote:
Hi Peter,
It looks I missed Anchor prefix, 195.80.239.0/24. We are announcing this prefix continously. That means you should get at least one prefix from us, and that would be 2 when we start to announce normal Beacon prefix.
Please, let us know if you still get no prefix from us.
Regards.
Arife,
We still get nothing from you; sh ip bgp neighbors 193.0.4.28 received-routes gives no entries.
Hmmm.. our bgpd definitely thinks it's sending something to you:
| rrc00> sh ip bg nei 195.69.144.34 advertised-routes | BGP table version is 0, local router ID is 193.0.4.28 | Status codes: s suppressed, d damped, h history, * valid, > best, i - internal | Origin codes: i - IGP, e - EGP, ? - incomplete | | Network Next Hop Metric LocPrf Weight Path | *> 195.80.239.0 193.0.4.28 0 32768 i | | Total number of prefixes 1
James
James, We seem to filter your prefix (a deny all filter) since as long as we can remember, so that explains a lot. When I removed the filter, for testing purposed, i got: br2.amsterdam1#sh ip bgp sum | incl 193.0.4.28 193.0.4.28 4 12654 110 586723 5703865 0 0 00:00:16 1 br2.amsterdam1# Question is however; are we supposed to filter any incoming prefixes on this peering or not? I am not entirely sure and therefore I'd like to verify this with you. Thanks -- Marco Davids SARA High Performance Networking - Amsterdam Phone: +315923000 Fax: +31847452840
participants (2)
-
James Aldridge -
Marco Davids (SARA)