TURKIX

Connect to both TurkIX route servers

Use the following endpoints when establishing BGP sessions to the TurkIX route server platform.

AS34565

Route Server 01 rs1.turkix.bg

IPv4 address 194.42.47.1

IPv6 address 2001:7f8:161::1

Route Server 02 rs2.turkix.bg

IPv4 address 194.42.47.2

IPv6 address 2001:7f8:161::2

Recommended practice: establish sessions to both route servers for redundancy and smoother operations.

A typical deployment includes

Before activation, align your peering policy and operational workflow around the route server model.

An active TurkIX connection and your own ASN

BGP sessions toward both route server nodes

Defined import and export policy for the prefixes you announce and accept

Post-activation verification through your normal routing visibility workflow

IXP Manager community reference for TurkIX members

TurkIX route server filtering follows the standard IXP Manager model. Use route server ASN AS34565 in your policies. Large communities are recommended, especially for 32-bit ASN environments, and standard plus large communities should not be mixed on the same announcement.

Route server ASN 34565

Preferred control set Large communities

Target member placeholder PEER_ASN

Default behaviour Announce to all peers

Standard communities

Classic 16-bit filtering controls

Prevent announcement of a prefix to a peer 0:PEER_ASN

Announce a route to a certain peer 34565:PEER_ASN

Prevent announcement of a prefix to all peers 0:34565

Announce a route to all peers 34565:34565

Large communities

Recommended policy controls

Prevent announcement of a prefix to a peer 34565:0:PEER_ASN

Announce a route to a certain peer 34565:1:PEER_ASN

Prevent announcement of a prefix to all peers 34565:0:0

Announce a route to all peers 34565:1:0

AS path prepending

Per-peer prepend communities

Prepend to peer AS once 34565:101:PEER_ASN

Prepend to peer AS twice 34565:102:PEER_ASN

Prepend to peer AS three times 34565:103:PEER_ASN

Configuration examples Ready-to-use policy examples

Only announce to AS65001 and AS65002

Close distribution to everyone first, then explicitly allow the selected peers.

0:34565
34565:65001
34565:65002

Announce to everyone except AS65010

Use a single deny community to exclude one participant while keeping global route server distribution.

0:65010

Large community example for only AS65001

Recommended model for Bird v2 and modern 32-bit ASN environments.

34565:0:0
34565:1:65001

Apply two prepends toward AS65020

Use peer-specific prepend communities to influence path selection toward a single participant.

34565:102:65020

PEER_ASN represents the target member ASN on the route server. The plain “announce to all peers” community is already the default behaviour, so it usually does not need to be added explicitly.