Peering Request

[marek22k]

Full Name

Marek H.E. Kuethe / Bandura Communications

ASN

202952

PeeringDB Integration

• [X] My PeeringDB Entries are current
• [ ] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)

blinky.mk16.de / Germany - 193.148.249.165 arcadia.mk16.de / Germany - 91.228.52.232 august.mk16.de / USA - 165.140.142.43

Multihop

• [X] Multihop Peering Request

Code of Conduct (TODO)

• [X] I agree to follow this project's Code of Conduct

Questions

• Which route should I export to the RC? Only routes that I also export to my upstreams or all routes that I also export to my downstreams?

Contact

• E-Mail: noc@mk16.de

[hanskuhn]

Hi Marek!

In response to your question, you might find our FAQ useful. The relevant section is 'What should my BGP policy on my Route Views peering look like?'

I'll setup the collector peering on our side and let you know when it it's up.

[hanskuhn]

The peering is up on our side:

    Neighbor        V         AS   MsgRcvd   MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd   PfxSnt Desc
    91.228.52.232   4     202952         0         0        0    0    0    never      Connect        0 Bandura
    165.140.142.43  4     202952         0         0        0    0    0    never      Connect        0 Bandura
    193.148.249.165 4     202952         0         0        0    0    0    never      Connect        0 Bandura

Our router information is as follows:

hostname: route-views5.routeviews.org asn: 6447 ip4: 128.223.51.105

Route Views collects routing data which is freely made available. For reference, real-time monitoring of the data you are contributing to this collector can be examined using the BGPStream/bgpreader toolkit.

example 1. live data

bgpreader -l -p routeviews -R -j

example 2. data past 24 hours

bgpreader -I 24h -c -j

For more information, please see: http://www.routeviews.org/routeviews/index.php/faq/ and https://bgpstream.caida.org/

If you have any questions, please contact us at help@routeviews.org

[marek22k]

I am trying to configure the session and I get BGP Error: Required capability missing.

$ birdc s p a routeviews
BIRD 2.0.12 ready.
Name       Proto      Table      State  Since         Info
routeviews BGP        ---        start  19:56:35.047  Idle          BGP Error: Required capability missing
  BGP state:          Idle
    Neighbor address: 128.223.51.105
    Neighbor AS:      6447
    Local AS:         202952
    Error wait:       43.702/60
    Last error:       BGP Error: Required capability missing
  Channel ipv6
    State:          DOWN
    Table:          master6
    Preference:     100
    Input filter:   REJECT
    Output filter:  (unnamed)
    Import limit:   200000
      Action:       block
    IGP IPv6 table: master6

Apparently the session is configured so that I can only export IPv4 data. However, my network is IPv6-only. I can therefore only export IPv6 data.